[jira] [Updated] (LUCENE-1560) maxDocBytesToAnalyze should be required arg up front
[ https://issues.apache.org/jira/browse/LUCENE-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Smiley updated LUCENE-1560: - Fix Version/s: (was: 4.7) 4.8 maxDocBytesToAnalyze should be required arg up front Key: LUCENE-1560 URL: https://issues.apache.org/jira/browse/LUCENE-1560 Project: Lucene - Core Issue Type: Improvement Components: modules/highlighter Affects Versions: 2.4.1 Reporter: Michael McCandless Labels: dead Fix For: 4.8 We recently changed IndexWriter to require you to specify up-front MaxFieldLength, on creation, so that you are aware of this dangerous loses stuff setting. Too many developers had fallen into the trap of how come my search can't find this document I think we should do the same with maxDocBytesToAnalyze with highlighter? Spinoff from this thread: http://www.nabble.com/Lucene-Highlighting-and-Dynamic-Summaries-p22385887.html -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-1560) maxDocBytesToAnalyze should be required arg up front
[ https://issues.apache.org/jira/browse/LUCENE-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Bowyer updated LUCENE-1560: Labels: dead (was: ) maxDocBytesToAnalyze should be required arg up front Key: LUCENE-1560 URL: https://issues.apache.org/jira/browse/LUCENE-1560 Project: Lucene - Core Issue Type: Improvement Components: modules/highlighter Affects Versions: 2.4.1 Reporter: Michael McCandless Labels: dead Fix For: 4.4 We recently changed IndexWriter to require you to specify up-front MaxFieldLength, on creation, so that you are aware of this dangerous loses stuff setting. Too many developers had fallen into the trap of how come my search can't find this document I think we should do the same with maxDocBytesToAnalyze with highlighter? Spinoff from this thread: http://www.nabble.com/Lucene-Highlighting-and-Dynamic-Summaries-p22385887.html -- 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (LUCENE-1560) maxDocBytesToAnalyze should be required arg up front
[ https://issues.apache.org/jira/browse/LUCENE-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-1560: -- Fix Version/s: (was: 4.3) 4.4 maxDocBytesToAnalyze should be required arg up front Key: LUCENE-1560 URL: https://issues.apache.org/jira/browse/LUCENE-1560 Project: Lucene - Core Issue Type: Improvement Components: modules/highlighter Affects Versions: 2.4.1 Reporter: Michael McCandless Fix For: 4.4 We recently changed IndexWriter to require you to specify up-front MaxFieldLength, on creation, so that you are aware of this dangerous loses stuff setting. Too many developers had fallen into the trap of how come my search can't find this document I think we should do the same with maxDocBytesToAnalyze with highlighter? Spinoff from this thread: http://www.nabble.com/Lucene-Highlighting-and-Dynamic-Summaries-p22385887.html -- 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Updated: (LUCENE-1560) maxDocBytesToAnalyze should be required arg up front
[ https://issues.apache.org/jira/browse/LUCENE-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-1560: --- Description: We recently changed IndexWriter to require you to specify up-front MaxFieldLength, on creation, so that you are aware of this dangerous loses stuff setting. Too many developers had fallen into the trap of how come my search can't find this document I think we should do the same with maxDocBytesToAnalyze with highlighter? Spinoff from this thread: http://www.nabble.com/Lucene-Highlighting-and-Dynamic-Summaries-p22385887.html was: We recently changed IndexWriter to require you to specify up-front MaxFieldLength, on creation, so that you are aware of this dangerous loses stuff setting. Too many developers had fallen into the trap of how come my search can't find this document I think we should do the same with maxDocBytesToAnalyze with highlighter? Spinoff from this thread: http://www.nabble.com/Lucene-Highlighting-and-Dynamic-Summaries-p22385887.html Fix Version/s: (was: 2.9) Moving out. maxDocBytesToAnalyze should be required arg up front Key: LUCENE-1560 URL: https://issues.apache.org/jira/browse/LUCENE-1560 Project: Lucene - Java Issue Type: Improvement Components: contrib/highlighter Affects Versions: 2.4.1 Reporter: Michael McCandless We recently changed IndexWriter to require you to specify up-front MaxFieldLength, on creation, so that you are aware of this dangerous loses stuff setting. Too many developers had fallen into the trap of how come my search can't find this document I think we should do the same with maxDocBytesToAnalyze with highlighter? Spinoff from this thread: http://www.nabble.com/Lucene-Highlighting-and-Dynamic-Summaries-p22385887.html -- 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: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org