Lucid Imagination

Secondary links

  • Contact Us
  • Sign Up or Login
  • Downloads
  • Solutions
    • Partners |
    • Blog |
    • Software |
    • Services |
    • Training |
    • Case Studies |
    • Webinars |
  • Developers
    • Blog |
    • Tech Articles |
    • Community |
    • Docs |
    • Downloads |
    • Whitepapers |
    • Podcasts |
  • About
    • Market Overview |
    • Management |
    • Company News |
    • In the Media |
    • Contact |

beta

Start new search

Back to search results

  1. FromDate
  2. Sanne Grinovero2010-02-07 12:33
  3. Simon Willnauer2010-02-07 12:49
  4. Uwe Schindler2010-02-07 12:53
  5. Uwe Schindler2010-02-07 13:15
  6. Robert Muir2010-02-07 13:33
  7. Sanne Grinovero2010-02-07 14:17
  8. Robert Muir2010-02-07 14:31
  9. Simon Willnauer2010-02-07 14:34
  10. Robert Muir2010-02-07 14:38
  11. Simon Willnauer2010-02-07 14:46
  12. Sanne Grinovero2010-02-07 17:32
  13. DM Smith2010-02-07 18:09
  14. Robert Muir2010-02-07 18:13
  15. Marvin Humphrey2010-02-07 19:47
  16. Sanne Grinovero2010-02-08 03:31
  17. Simon Willnauer2010-02-08 03:48
  18. Uwe Schindler2010-02-08 04:57
  19. Sanne Grinovero2010-02-08 05:35

[java-dev] Having a default constructor in Analyzers

Subject:
Re: Having a default constructor in Analyzers
From:
Simon Willnauer <simon.willnauer@...>
Date:
2010-02-07 12:49
Almost no Analyzer has a default ctor anymore due to the introduction
of Version. This should not be an issue for API users loading
Analyzers per reflection. You can still call the version Ctor
alternatively. Providing a default ctor with the current version could
be very risky in many regards, a backwards break based on version
could break older indexes etc etc.

I don't see that this keeps other applications from upgrading lucene.

simon

On Sun, Feb 7, 2010 at 6:33 PM, Sanne Grinovero
<sanne.grinovero@gmail.com> wrote:
Hello, I've seen that some core Analyzers are now missing a default constructor; this is preventing many applications to configure/load Analyzers by reflection, which is a common use case to have Analyzers chosen in configuration files. Would it be possible to add, for example, a constructor like public StandardAnalyzer() {   this(Version.LUCENE_CURRENT); } ? Of course more advanced use cases would need to pass parameters but please make the advanced usage optional; I have now seen more than a single project break because of this (and revert to older Lucene). Regards, Sanne --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org For additional commands, e-mail: java-dev-help@lucene.apache.org
--------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org For additional commands, e-mail: java-dev-help@lucene.apache.org

Solr Powered

Give us your feedback

  • Lucene
  • Solr
  • Nutch
  • Tika
  • Mahout
  • Droids
  • PyLucene
  • Lucene.Net
  • Lucy
  • Lucene4c
  • Open Relevance Project
  • How We Can Help:
    • Getting Started |
    • Support Subscriptions |
    • White Papers |
    • Training |
    • Consulting |
    • Contact Us |
  • Developers:
    • Blog |
    • Documentation |
    • Tech Articles |
    • Podcasts and Videos |
    • Community |
  • Downloads:
    • LucidWorks for Solr |
    • LucidWorks for Lucene |
    • LucidGaze for Solr |
    • LucidGaze for Lucene |
  • Products:
  • Services:

Contact | Privacy Policy | Legal Terms of Use | Copyrights and Disclaimers | Admin

Apache Solr, Apache Lucene, ApacheCon and their logos are trademarks of the Apache Software Foundation.

© 2010 Lucid Imagination. All Right reserved.