Ah, ok. that one fails for me too on 6x, was trying on trunk. Thanks... Digging.
On Tue, May 30, 2017 at 12:44 PM, Steve Rowe (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/LUCENE-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030016#comment-16030016 > ] > > Steve Rowe commented on LUCENE-7705: > ------------------------------------ > > My seed reproduces for me both on Linux and on my Macbook pro (Sierra > 10.12.5, Oracle JDK 1.8.0_112). Note that the original failure was on > branch_6x (and that's where I repro'd). > >> Allow CharTokenizer-derived tokenizers and KeywordTokenizer to configure the >> max token length >> --------------------------------------------------------------------------------------------- >> >> Key: LUCENE-7705 >> URL: https://issues.apache.org/jira/browse/LUCENE-7705 >> Project: Lucene - Core >> Issue Type: Improvement >> Reporter: Amrit Sarkar >> Assignee: Erick Erickson >> Priority: Minor >> Fix For: master (7.0), 6.7 >> >> Attachments: LUCENE-7705, LUCENE-7705.patch, LUCENE-7705.patch, >> LUCENE-7705.patch, LUCENE-7705.patch, LUCENE-7705.patch, LUCENE-7705.patch, >> LUCENE-7705.patch, LUCENE-7705.patch, LUCENE-7705.patch >> >> >> SOLR-10186 >> [~erickerickson]: Is there a good reason that we hard-code a 256 character >> limit for the CharTokenizer? In order to change this limit it requires that >> people copy/paste the incrementToken into some new class since >> incrementToken is final. >> KeywordTokenizer can easily change the default (which is also 256 bytes), >> but to do so requires code rather than being able to configure it in the >> schema. >> For KeywordTokenizer, this is Solr-only. For the CharTokenizer classes >> (WhitespaceTokenizer, UnicodeWhitespaceTokenizer and LetterTokenizer) >> (Factories) it would take adding a c'tor to the base class in Lucene and >> using it in the factory. >> Any objections? > > > > -- > This message was sent by Atlassian JIRA > (v6.3.15#6346) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
