[jira] Updated: (LUCENE-2295) Create a MaxFieldLengthAnalyzer to wrap any other Analyzer and provide the same functionality as MaxFieldLength provided on IndexWriter
[ https://issues.apache.org/jira/browse/LUCENE-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shai Erera updated LUCENE-2295: --- Attachment: LUCENE-2295-2-3x.patch Patch against 3x. Removed the get/set from IWC and changed code which used it. I also added some clarifying notes to the deprecation note in IW.setMaxFieldLength. I will post a separate patch for trunk where this setting will be removed altogether. Create a MaxFieldLengthAnalyzer to wrap any other Analyzer and provide the same functionality as MaxFieldLength provided on IndexWriter --- Key: LUCENE-2295 URL: https://issues.apache.org/jira/browse/LUCENE-2295 Project: Lucene - Java Issue Type: Improvement Components: contrib/analyzers Reporter: Shai Erera Assignee: Uwe Schindler Fix For: 3.1, 4.0 Attachments: LUCENE-2295-2-3x.patch, LUCENE-2295-trunk.patch, LUCENE-2295.patch A spinoff from LUCENE-2294. Instead of asking the user to specify on IndexWriter his requested MFL limit, we can get rid of this setting entirely by providing an Analyzer which will wrap any other Analyzer and its TokenStream with a TokenFilter that keeps track of the number of tokens produced and stop when the limit has reached. This will remove any count tracking in IW's indexing, which is done even if I specified UNLIMITED for MFL. Let's try to do it for 3.1. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Updated: (LUCENE-2295) Create a MaxFieldLengthAnalyzer to wrap any other Analyzer and provide the same functionality as MaxFieldLength provided on IndexWriter
[ https://issues.apache.org/jira/browse/LUCENE-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shai Erera updated LUCENE-2295: --- Attachment: LUCENE-2295-2-trunk.patch Patch against trunk - removes maxFieldLength handling from all the code. Create a MaxFieldLengthAnalyzer to wrap any other Analyzer and provide the same functionality as MaxFieldLength provided on IndexWriter --- Key: LUCENE-2295 URL: https://issues.apache.org/jira/browse/LUCENE-2295 Project: Lucene - Java Issue Type: Improvement Components: contrib/analyzers Reporter: Shai Erera Assignee: Uwe Schindler Fix For: 3.1, 4.0 Attachments: LUCENE-2295-2-3x.patch, LUCENE-2295-2-trunk.patch, LUCENE-2295-trunk.patch, LUCENE-2295.patch A spinoff from LUCENE-2294. Instead of asking the user to specify on IndexWriter his requested MFL limit, we can get rid of this setting entirely by providing an Analyzer which will wrap any other Analyzer and its TokenStream with a TokenFilter that keeps track of the number of tokens produced and stop when the limit has reached. This will remove any count tracking in IW's indexing, which is done even if I specified UNLIMITED for MFL. Let's try to do it for 3.1. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Updated: (LUCENE-2295) Create a MaxFieldLengthAnalyzer to wrap any other Analyzer and provide the same functionality as MaxFieldLength provided on IndexWriter
[ https://issues.apache.org/jira/browse/LUCENE-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-2295: -- Attachment: LUCENE-2295-trunk.patch Updated patch for trunk. Create a MaxFieldLengthAnalyzer to wrap any other Analyzer and provide the same functionality as MaxFieldLength provided on IndexWriter --- Key: LUCENE-2295 URL: https://issues.apache.org/jira/browse/LUCENE-2295 Project: Lucene - Java Issue Type: Improvement Components: contrib/analyzers Reporter: Shai Erera Assignee: Uwe Schindler Fix For: 3.1, 4.0 Attachments: LUCENE-2295-trunk.patch, LUCENE-2295.patch A spinoff from LUCENE-2294. Instead of asking the user to specify on IndexWriter his requested MFL limit, we can get rid of this setting entirely by providing an Analyzer which will wrap any other Analyzer and its TokenStream with a TokenFilter that keeps track of the number of tokens produced and stop when the limit has reached. This will remove any count tracking in IW's indexing, which is done even if I specified UNLIMITED for MFL. Let's try to do it for 3.1. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Updated: (LUCENE-2295) Create a MaxFieldLengthAnalyzer to wrap any other Analyzer and provide the same functionality as MaxFieldLength provided on IndexWriter
[ https://issues.apache.org/jira/browse/LUCENE-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-2295: -- Fix Version/s: 3.1 Create a MaxFieldLengthAnalyzer to wrap any other Analyzer and provide the same functionality as MaxFieldLength provided on IndexWriter --- Key: LUCENE-2295 URL: https://issues.apache.org/jira/browse/LUCENE-2295 Project: Lucene - Java Issue Type: Improvement Components: contrib/analyzers Reporter: Shai Erera Assignee: Uwe Schindler Fix For: 3.1, 4.0 Attachments: LUCENE-2295-trunk.patch, LUCENE-2295.patch A spinoff from LUCENE-2294. Instead of asking the user to specify on IndexWriter his requested MFL limit, we can get rid of this setting entirely by providing an Analyzer which will wrap any other Analyzer and its TokenStream with a TokenFilter that keeps track of the number of tokens produced and stop when the limit has reached. This will remove any count tracking in IW's indexing, which is done even if I specified UNLIMITED for MFL. Let's try to do it for 3.1. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
