Lucid Imagination

Secondary links

  • Contact Us
  • Sign Up or Login
  • Downloads
  • Solutions
    • Partners |
    • Blog |
    • Software |
    • Services |
    • Training |
    • Case Studies |
    • Webcasts |
  • 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-08 03:48
On Mon, Feb 8, 2010 at 9:31 AM, Sanne Grinovero
<sanne.grinovero@gmail.com> wrote:
2010/2/8 Robert Muir <rcmuir@gmail.com>: ---->8 snip 8<----
how would this work when the Query analyzer differs from the Index analyzer? For example, using commongrams in solr means you use a different Query analyzer from Index analyzer, and there are some other use cases even in solr (synonyms expansion and things like that)
---->8 snip 8<---- They are two different Analyzer types, but I assume they want to use the same value for Version, right? The same version which was used to build the rest of the index.
So this is trick, if you have Analyzer A(Version.1) and Analyzer B(Version.2) and build an index with it you will likely have to maintain those version until you make a clean cut and upgrade to A(Version.X) B(Version.X). If you are upgrading to 2.9 from 2.x you can simply use Version.2.x for both of you analyzers. It always depends on the changes which have been applied to the Analyzers but it is very likely that they break your index compat if you blindly upgrade. One of the biggest problems is that some of your users might want to use analyzer X with Version.Y and analyzer X' with Version.Y' because of some weird "buggy" behavior. You have to find your way through this unfortunately. You might offer your users to define the versions themselves and warn them like Robert did in the blinking JavaDoc :) simon
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.