[ 
https://issues.apache.org/jira/browse/LUCENE-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002838#comment-13002838
 ] 

Michael McCandless commented on LUCENE-2939:
--------------------------------------------


bq. Putting pressure is fine, but just because being an RM is hard is not a 
King for a day pass IMO

Putting pressure is precisely what Robert has done here (and on
SOLR-2390)?

He's acting just like an RM should act, as far as I can tell.  Moving
an issue out, stating that an issue won't make the RC,
is fair game.  These are the normal "tools" of the RM...

My point is, we all must expect/allow/not-get-upset-about this
"pressure" from the RM -- it comes with the territory, and it's the
RM's right to be very aggressive in order to get the release done.

Else releases will not get done, and we'll all keep one-more-thing'ing
the release, and that's bad for all of us.

We gotta remove the barriers to doing releases around here, not add to
them.  In fact, we should scrutinize our scary ReleaseTodo and pare it
back to the bare minimum... it's gotta become a push button process.


> Highlighter should try and use maxDocCharsToAnalyze in 
> WeightedSpanTermExtractor when adding a new field to MemoryIndex as well as 
> when using CachingTokenStream
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-2939
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2939
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: contrib/highlighter
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>            Priority: Minor
>             Fix For: 3.1.1, 3.2, 4.0
>
>         Attachments: LUCENE-2939.patch, LUCENE-2939.patch, LUCENE-2939.patch
>
>
> huge documents can be drastically slower than need be because the entire 
> field is added to the memory index
> this cost can be greatly reduced in many cases if we try and respect 
> maxDocCharsToAnalyze
> things can be improved even further by respecting this setting with 
> CachingTokenStream

-- 
This message is automatically generated by JIRA.
-
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

Reply via email to