[ 
https://issues.apache.org/jira/browse/SOLR-4123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508005#comment-13508005
 ] 

Shawn Heisey commented on SOLR-4123:
------------------------------------

I tried looking at Default.rbbi so I could determine what part of that file 
defines the tokenization on punctuation, but the identifiers that are there 
don't mean very much to me.

I'd like to give this patch a test spin for my use case - turning off 
tokenization on standard punctuation.  If there is any such thing as exotic 
punctuation, I can probably just let ICU tokenize on that.  What would I define 
for rulefiles, where should the rbbi file(s) go, and what should be in them?

                
> ICUTokenizerFactory - per-script RBBI customization
> ---------------------------------------------------
>
>                 Key: SOLR-4123
>                 URL: https://issues.apache.org/jira/browse/SOLR-4123
>             Project: Solr
>          Issue Type: Improvement
>          Components: Schema and Analysis
>    Affects Versions: 4.0
>            Reporter: Shawn Heisey
>             Fix For: 4.1, 5.0
>
>         Attachments: SOLR-4123.patch
>
>
> Initially this started out as an idea for a configuration knob on 
> ICUTokenizer that would allow me to tell it not to tokenize on punctuation.  
> Through IRC discussion on #lucene, it sorta ballooned.  The committers had a 
> long discussion about it that I don't really understand, so I'll be including 
> it in the comments.
> I am a Solr user, so I would also need the ability to access the 
> configuration from there, likely either in schema.xml or solrconfig.xml.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to