You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2009/03/13 11:15:50 UTC

[jira] Created: (LUCENE-1560) maxDocBytesToAnalyze should be required arg up front

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
             Fix For: 2.9



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-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org

[jira] Updated: (LUCENE-1560) maxDocBytesToAnalyze should be required arg up front

Posted by "Michael McCandless (JIRA)" <ji...@apache.org>.
     [ 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org