You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Byrne (JIRA)" <ji...@apache.org> on 2013/04/26 22:10:16 UTC
[jira] [Commented] (LUCENE-1227) NGramTokenizer to handle more than
1024 chars
[ https://issues.apache.org/jira/browse/LUCENE-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13643200#comment-13643200 ]
David Byrne commented on LUCENE-1227:
-------------------------------------
I proposed a patch that fixes this problem on another ticket:
https://issues.apache.org/jira/browse/LUCENE-2947
> NGramTokenizer to handle more than 1024 chars
> ---------------------------------------------
>
> Key: LUCENE-1227
> URL: https://issues.apache.org/jira/browse/LUCENE-1227
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/analysis
> Reporter: Hiroaki Kawai
> Priority: Minor
> Attachments: LUCENE-1227.patch, NGramTokenizer.patch, NGramTokenizer.patch
>
>
> Current NGramTokenizer can't handle character stream that is longer than 1024. This is too short for non-whitespace-separated languages.
> I created a patch for this issues.
--
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org