You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (Created) (JIRA)" <ji...@apache.org> on 2012/03/26 00:04:27 UTC
[jira] [Created] (LUCENE-3919) more thorough testing of analysis
chains
more thorough testing of analysis chains
----------------------------------------
Key: LUCENE-3919
URL: https://issues.apache.org/jira/browse/LUCENE-3919
Project: Lucene - Java
Issue Type: Task
Components: modules/analysis
Affects Versions: 3.6, 4.0
Reporter: Robert Muir
In lucene we essentially test each analysis component separately. we also give some
good testing to the example Analyzers we provide that combine them.
But we don't test various combinations that are possible: which is bad because
it doesnt test possibilities for custom analyzers (especially since lots of solr users
etc define their own).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-3919) more thorough testing of analysis
chains
Posted by "Robert Muir (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238036#comment-13238036 ]
Robert Muir commented on LUCENE-3919:
-------------------------------------
I committed fix and tests for empty term (only Czech stemmer seemed to have one).
I opened LUCENE-3920 for the strange NGram+Shingle offsets bug.
> more thorough testing of analysis chains
> ----------------------------------------
>
> Key: LUCENE-3919
> URL: https://issues.apache.org/jira/browse/LUCENE-3919
> Project: Lucene - Java
> Issue Type: Task
> Components: modules/analysis
> Affects Versions: 3.6, 4.0
> Reporter: Robert Muir
> Attachments: LUCENE-3919.patch
>
>
> In lucene we essentially test each analysis component separately. we also give some
> good testing to the example Analyzers we provide that combine them.
> But we don't test various combinations that are possible: which is bad because
> it doesnt test possibilities for custom analyzers (especially since lots of solr users
> etc define their own).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-3919) more thorough testing of analysis
chains
Posted by "Robert Muir (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237993#comment-13237993 ]
Robert Muir commented on LUCENE-3919:
-------------------------------------
That one is ant test -Dtestcase=TestRandomChains -Dtestmethod=testRandomChains -Dtests.seed=104b56460756fb6:33a429fcfb5503db:-1d952b2910440c7d -Dargs="-Dfile.encoding=UTF-8"
I'll see if i can figure out whats going on.
> more thorough testing of analysis chains
> ----------------------------------------
>
> Key: LUCENE-3919
> URL: https://issues.apache.org/jira/browse/LUCENE-3919
> Project: Lucene - Java
> Issue Type: Task
> Components: modules/analysis
> Affects Versions: 3.6, 4.0
> Reporter: Robert Muir
> Attachments: LUCENE-3919.patch
>
>
> In lucene we essentially test each analysis component separately. we also give some
> good testing to the example Analyzers we provide that combine them.
> But we don't test various combinations that are possible: which is bad because
> it doesnt test possibilities for custom analyzers (especially since lots of solr users
> etc define their own).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-3919) more thorough testing of analysis
chains
Posted by "Robert Muir (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249286#comment-13249286 ]
Robert Muir commented on LUCENE-3919:
-------------------------------------
I'm going to commit this. its a test: we can improve it later.
> more thorough testing of analysis chains
> ----------------------------------------
>
> Key: LUCENE-3919
> URL: https://issues.apache.org/jira/browse/LUCENE-3919
> Project: Lucene - Java
> Issue Type: Task
> Components: modules/analysis
> Affects Versions: 3.6, 4.0
> Reporter: Robert Muir
> Attachments: LUCENE-3919.patch, LUCENE-3919.patch, LUCENE-3919.patch
>
>
> In lucene we essentially test each analysis component separately. we also give some
> good testing to the example Analyzers we provide that combine them.
> But we don't test various combinations that are possible: which is bad because
> it doesnt test possibilities for custom analyzers (especially since lots of solr users
> etc define their own).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (LUCENE-3919) more thorough testing of analysis
chains
Posted by "Robert Muir (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir updated LUCENE-3919:
--------------------------------
Attachment: LUCENE-3919.patch
really rough initial stab.
first time i ran this it seems like it found a bug:
{noformat}
[junit] Exception from random analyzer: tokenizer=class org.apache.lucene.analysis.core.KeywordTokenizer
[junit] filters=class org.apache.lucene.analysis.cz.CzechStemFilter,class org.apache.lucene.analysis.cjk.CJKWidthFilter
[junit] java.lang.ArrayIndexOutOfBoundsException: -1
[junit] at org.apache.lucene.analysis.cz.CzechStemmer.normalize(CzechStemmer.java:148)
[junit] at org.apache.lucene.analysis.cz.CzechStemmer.stem(CzechStemmer.java:47)
[junit] at org.apache.lucene.analysis.cz.CzechStemFilter.incrementToken(CzechStemFilter.java:52)
[junit] at org.apache.lucene.analysis.cjk.CJKWidthFilter.incrementToken(CJKWidthFilter.java:62)
{noformat}
> more thorough testing of analysis chains
> ----------------------------------------
>
> Key: LUCENE-3919
> URL: https://issues.apache.org/jira/browse/LUCENE-3919
> Project: Lucene - Java
> Issue Type: Task
> Components: modules/analysis
> Affects Versions: 3.6, 4.0
> Reporter: Robert Muir
> Attachments: LUCENE-3919.patch
>
>
> In lucene we essentially test each analysis component separately. we also give some
> good testing to the example Analyzers we provide that combine them.
> But we don't test various combinations that are possible: which is bad because
> it doesnt test possibilities for custom analyzers (especially since lots of solr users
> etc define their own).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (LUCENE-3919) more thorough testing of analysis
chains
Posted by "Uwe Schindler (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Uwe Schindler updated LUCENE-3919:
----------------------------------
Attachment: LUCENE-3919-generics-fixes.patch
Here the generics fixes and some additional checks to exclude all shit of non public anonymous or member classes.
> more thorough testing of analysis chains
> ----------------------------------------
>
> Key: LUCENE-3919
> URL: https://issues.apache.org/jira/browse/LUCENE-3919
> Project: Lucene - Java
> Issue Type: Task
> Components: modules/analysis
> Affects Versions: 3.6, 4.0
> Reporter: Robert Muir
> Assignee: Robert Muir
> Fix For: 4.0
>
> Attachments: LUCENE-3919-generics-fixes.patch, LUCENE-3919.patch, LUCENE-3919.patch, LUCENE-3919.patch
>
>
> In lucene we essentially test each analysis component separately. we also give some
> good testing to the example Analyzers we provide that combine them.
> But we don't test various combinations that are possible: which is bad because
> it doesnt test possibilities for custom analyzers (especially since lots of solr users
> etc define their own).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-3919) more thorough testing of analysis
chains
Posted by "Robert Muir (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238002#comment-13238002 ]
Robert Muir commented on LUCENE-3919:
-------------------------------------
The CzechStemmer bug is easy, its because of a zero-length term from KeywordTokenizer :)
I'll commit a trivial fix and test for that.
The next time I ran the test, i got a new fail:
{noformat}
[junit] TEST FAIL: useCharFilter=true text=⩀⪴⫈⪆⩞ ye ه
[junit] Exception from random analyzer: tokenizer=class org.apache.lucene.analysis.ngram.NGramTokenizer
[junit] filters=class org.apache.lucene.analysis.shingle.ShingleFilter
[junit] NOTE: reproduce with: ant test -Dtestcase=TestRandomChains -Dtestmethod=testRandomChains -Dtests.seed=104b56460756fb6:33a429fcfb5503db:-1d952b2910440c7d -Dargs="-Dfile.encoding=UTF-8"
[junit] java.lang.AssertionError: endOffset must be >= startOffset
[junit] java.lang.RuntimeException: java.lang.AssertionError: endOffset must be >= startOffset
[junit] at org.apache.lucene.analysis.BaseTokenStreamTestCase.checkRandomData(BaseTokenStreamTestCase.java:397)
{noformat}
This is gonna be fun...
> more thorough testing of analysis chains
> ----------------------------------------
>
> Key: LUCENE-3919
> URL: https://issues.apache.org/jira/browse/LUCENE-3919
> Project: Lucene - Java
> Issue Type: Task
> Components: modules/analysis
> Affects Versions: 3.6, 4.0
> Reporter: Robert Muir
> Attachments: LUCENE-3919.patch
>
>
> In lucene we essentially test each analysis component separately. we also give some
> good testing to the example Analyzers we provide that combine them.
> But we don't test various combinations that are possible: which is bad because
> it doesnt test possibilities for custom analyzers (especially since lots of solr users
> etc define their own).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-3919) more thorough testing of analysis
chains
Posted by "Michael McCandless (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237994#comment-13237994 ]
Michael McCandless commented on LUCENE-3919:
--------------------------------------------
Awesome!
> more thorough testing of analysis chains
> ----------------------------------------
>
> Key: LUCENE-3919
> URL: https://issues.apache.org/jira/browse/LUCENE-3919
> Project: Lucene - Java
> Issue Type: Task
> Components: modules/analysis
> Affects Versions: 3.6, 4.0
> Reporter: Robert Muir
> Attachments: LUCENE-3919.patch
>
>
> In lucene we essentially test each analysis component separately. we also give some
> good testing to the example Analyzers we provide that combine them.
> But we don't test various combinations that are possible: which is bad because
> it doesnt test possibilities for custom analyzers (especially since lots of solr users
> etc define their own).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-3919) more thorough testing of analysis
chains
Posted by "Uwe Schindler (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238001#comment-13238001 ]
Uwe Schindler commented on LUCENE-3919:
---------------------------------------
Please don't commit... I will take care :-) - tomorrow!
There should be also improvements in ctor detectors: all Tokenizers/Tokenfilters with matchVersion will not work, I will think about some more intelligent ctor parsing: Class.getConstructors() -> choose one which has at least a Reader/TokenStream param, if a version is also there fill in matchVersion and all other parameters maybe random (int, bool,...)? Random params should always produce something correct, or they should throw IllegalArgumentException/... on the ctor.
> more thorough testing of analysis chains
> ----------------------------------------
>
> Key: LUCENE-3919
> URL: https://issues.apache.org/jira/browse/LUCENE-3919
> Project: Lucene - Java
> Issue Type: Task
> Components: modules/analysis
> Affects Versions: 3.6, 4.0
> Reporter: Robert Muir
> Attachments: LUCENE-3919.patch
>
>
> In lucene we essentially test each analysis component separately. we also give some
> good testing to the example Analyzers we provide that combine them.
> But we don't test various combinations that are possible: which is bad because
> it doesnt test possibilities for custom analyzers (especially since lots of solr users
> etc define their own).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (LUCENE-3919) more thorough testing of analysis
chains
Posted by "Robert Muir (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir updated LUCENE-3919:
--------------------------------
Attachment: LUCENE-3919.patch
updated patch: disabling the n-gram filters (see LUCENE-3920), and looking for Version+TokenStream to get a few more filters. also sped up the test a bit...
now it passes so Uwe can do his work :)
> more thorough testing of analysis chains
> ----------------------------------------
>
> Key: LUCENE-3919
> URL: https://issues.apache.org/jira/browse/LUCENE-3919
> Project: Lucene - Java
> Issue Type: Task
> Components: modules/analysis
> Affects Versions: 3.6, 4.0
> Reporter: Robert Muir
> Attachments: LUCENE-3919.patch, LUCENE-3919.patch, LUCENE-3919.patch
>
>
> In lucene we essentially test each analysis component separately. we also give some
> good testing to the example Analyzers we provide that combine them.
> But we don't test various combinations that are possible: which is bad because
> it doesnt test possibilities for custom analyzers (especially since lots of solr users
> etc define their own).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (LUCENE-3919) more thorough testing of analysis
chains
Posted by "Robert Muir (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir updated LUCENE-3919:
--------------------------------
Attachment: LUCENE-3919.patch
updated patch: looking for Version+Reader ctors and avoiding CachingTokenFilter :)
> more thorough testing of analysis chains
> ----------------------------------------
>
> Key: LUCENE-3919
> URL: https://issues.apache.org/jira/browse/LUCENE-3919
> Project: Lucene - Java
> Issue Type: Task
> Components: modules/analysis
> Affects Versions: 3.6, 4.0
> Reporter: Robert Muir
> Attachments: LUCENE-3919.patch, LUCENE-3919.patch
>
>
> In lucene we essentially test each analysis component separately. we also give some
> good testing to the example Analyzers we provide that combine them.
> But we don't test various combinations that are possible: which is bad because
> it doesnt test possibilities for custom analyzers (especially since lots of solr users
> etc define their own).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-3919) more thorough testing of analysis
chains
Posted by "Robert Muir (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238003#comment-13238003 ]
Robert Muir commented on LUCENE-3919:
-------------------------------------
{quote}
Please don't commit... I will take care - tomorrow!
{quote}
Thank you Uwe! We can just leave this issue open.
In the meantime I will run the test and try to fix the bugs it finds!
> more thorough testing of analysis chains
> ----------------------------------------
>
> Key: LUCENE-3919
> URL: https://issues.apache.org/jira/browse/LUCENE-3919
> Project: Lucene - Java
> Issue Type: Task
> Components: modules/analysis
> Affects Versions: 3.6, 4.0
> Reporter: Robert Muir
> Attachments: LUCENE-3919.patch
>
>
> In lucene we essentially test each analysis component separately. we also give some
> good testing to the example Analyzers we provide that combine them.
> But we don't test various combinations that are possible: which is bad because
> it doesnt test possibilities for custom analyzers (especially since lots of solr users
> etc define their own).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (LUCENE-3919) more thorough testing of analysis
chains
Posted by "Robert Muir (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir updated LUCENE-3919:
--------------------------------
Fix Version/s: 3.6.1
> more thorough testing of analysis chains
> ----------------------------------------
>
> Key: LUCENE-3919
> URL: https://issues.apache.org/jira/browse/LUCENE-3919
> Project: Lucene - Java
> Issue Type: Task
> Components: modules/analysis
> Affects Versions: 3.6, 4.0
> Reporter: Robert Muir
> Assignee: Robert Muir
> Fix For: 4.0, 3.6.1
>
> Attachments: LUCENE-3919-generics-fixes.patch, LUCENE-3919.patch, LUCENE-3919.patch, LUCENE-3919.patch
>
>
> In lucene we essentially test each analysis component separately. we also give some
> good testing to the example Analyzers we provide that combine them.
> But we don't test various combinations that are possible: which is bad because
> it doesnt test possibilities for custom analyzers (especially since lots of solr users
> etc define their own).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-3919) more thorough testing of analysis
chains
Posted by "Robert Muir (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237996#comment-13237996 ]
Robert Muir commented on LUCENE-3919:
-------------------------------------
By the way: generics are totally broken with the test!
> more thorough testing of analysis chains
> ----------------------------------------
>
> Key: LUCENE-3919
> URL: https://issues.apache.org/jira/browse/LUCENE-3919
> Project: Lucene - Java
> Issue Type: Task
> Components: modules/analysis
> Affects Versions: 3.6, 4.0
> Reporter: Robert Muir
> Attachments: LUCENE-3919.patch
>
>
> In lucene we essentially test each analysis component separately. we also give some
> good testing to the example Analyzers we provide that combine them.
> But we don't test various combinations that are possible: which is bad because
> it doesnt test possibilities for custom analyzers (especially since lots of solr users
> etc define their own).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Resolved] (LUCENE-3919) more thorough testing of analysis
chains
Posted by "Robert Muir (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir resolved LUCENE-3919.
---------------------------------
Resolution: Fixed
Fix Version/s: 4.0
Assignee: Robert Muir
committed first iteration... lets improve the test later
> more thorough testing of analysis chains
> ----------------------------------------
>
> Key: LUCENE-3919
> URL: https://issues.apache.org/jira/browse/LUCENE-3919
> Project: Lucene - Java
> Issue Type: Task
> Components: modules/analysis
> Affects Versions: 3.6, 4.0
> Reporter: Robert Muir
> Assignee: Robert Muir
> Fix For: 4.0
>
> Attachments: LUCENE-3919.patch, LUCENE-3919.patch, LUCENE-3919.patch
>
>
> In lucene we essentially test each analysis component separately. we also give some
> good testing to the example Analyzers we provide that combine them.
> But we don't test various combinations that are possible: which is bad because
> it doesnt test possibilities for custom analyzers (especially since lots of solr users
> etc define their own).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org