[ 
https://issues.apache.org/jira/browse/LUCENE-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778882#action_12778882
 ] 

Robert Muir commented on LUCENE-2073:
-------------------------------------

bq. Which components are affected by this? I think just Analyzers and query 
parsers, yes? 

I think just tokenstreams / analyzers.

bq. This isn't a fundamental problem with the Lucene architecture; it's an 
artifact of the way certain classes are implemented.

yes, you are exactly right. StandardTokenizer does not have this problem. its 
behavior is independent of the users JVM, although dependent on the JVM of the 
developer who last re-ran jflex :)

bq. Perhaps there could be an "ICUAnalysis" package which depends on ICU4J

yeah, this is what I think most of us who need unicode support do anyway. so i 
tried to start a good impl of this in LUCENE-1488.
even if you do not care about unicode support, maybe you care that things like 
.isWhiteSpace() are faster than in the jdk:
http://site.icu-project.org/home/why-use-icu4j (see under Performance section).



> Document issues involved in building your index with one jdk version and then 
> searching/updating with another
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-2073
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2073
>             Project: Lucene - Java
>          Issue Type: Task
>            Reporter: Mark Miller
>
> I think this needs to go in something of a permenant spot - this isn't a one 
> time release type issues - its going to present over multiple release.
> {quote}
> If there is nothing we can do here, then we just have to do the best we can -
> such as a prominent notice alerting that if you transition JVM's between 
> building and searching the index and you are using or doing X, things will 
> break.
> We should put this in a spot that is always pretty visible - perhaps even a 
> new readme file titlted something like IndexBackwardCompatibility or 
> something, to which we can add other tips and gotchyas as they come up. Or 
> MaintainingIndicesAcrossVersions, or 
> FancyWhateverGetsYourAttentionAboutUpgradingStuff. Or a permanent 
> entry/sticky entry at the top of Changes.
> {quote}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org

Reply via email to