[Lucene.Net] [jira] [Updated] (LUCENENET-422) Custom tokenizers may fail when indexing due to ReusableStringReader not implement some method of TextReader
[ https://issues.apache.org/jira/browse/LUCENENET-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] percyboy updated LUCENENET-422: --- Attachment: ReusableStringReader.cs my modifications. Custom tokenizers may fail when indexing due to ReusableStringReader not implement some method of TextReader Key: LUCENENET-422 URL: https://issues.apache.org/jira/browse/LUCENENET-422 Project: Lucene.Net Issue Type: Bug Components: Lucene.Net Core Affects Versions: Lucene.Net 2.9.2 Environment: from Lucene 2.3.x to current trunk Reporter: percyboy Attachments: ReusableStringReader.cs Lucene.Net.Index.ReusableStringReader is inherited from TextReader, but marks some methods as Not Implemented. Some custom tokenizers who call these unfinished methods will meet an error. It is, somewhat, like a trap. LUCENENET-150 is a similar issue to this one. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Updated] (LUCENENET-422) Custom tokenizers may fail when indexing due to ReusableStringReader not implement some method of TextReader
[ https://issues.apache.org/jira/browse/LUCENENET-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Digy updated LUCENENET-422: --- Fix Version/s: Lucene.Net 2.9.4g Lucene.Net 2.9.4 Custom tokenizers may fail when indexing due to ReusableStringReader not implement some method of TextReader Key: LUCENENET-422 URL: https://issues.apache.org/jira/browse/LUCENENET-422 Project: Lucene.Net Issue Type: Bug Components: Lucene.Net Core Affects Versions: Lucene.Net 2.9.2 Environment: from Lucene 2.3.x to current trunk Reporter: percyboy Fix For: Lucene.Net 2.9.4, Lucene.Net 2.9.4g Attachments: ReusableStringReader.cs Lucene.Net.Index.ReusableStringReader is inherited from TextReader, but marks some methods as Not Implemented. Some custom tokenizers who call these unfinished methods will meet an error. It is, somewhat, like a trap. LUCENENET-150 is a similar issue to this one. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
