[jira] Commented: (LUCENE-1614) Add next() and skipTo() variants to DocIdSetIterator that return the current doc, instead of boolean

[ https://issues.apache.org/jira/browse/LUCENE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714366#action_12714366 ] Michael McCandless commented on LUCENE-1614: bq. Consider the code in BS2

Re: NRT getReader turnaround on large segments

On Thu, May 28, 2009 at 4:59 PM, Yonik Seeley yo...@lucidimagination.com wrote: On Thu, May 28, 2009 at 4:18 PM, Michael McCandless luc...@mikemccandless.com wrote: Newly added docs are still free to make new segments, and be reopened, while this warming is taking place. So, getReader() will

[jira] Updated: (LUCENE-1542) Lucene can incorrectly set the position of tokens that start a field with positonInc 0.

[ https://issues.apache.org/jira/browse/LUCENE-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-1542: --- Attachment: LUCENE-1542.patch New patch attached, that merges in Mark's test fix,

[jira] Commented: (LUCENE-1614) Add next() and skipTo() variants to DocIdSetIterator that return the current doc, instead of boolean

[ https://issues.apache.org/jira/browse/LUCENE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714399#action_12714399 ] Shai Erera commented on LUCENE-1614: I don't like that code also. But if we allow to

[jira] Commented: (LUCENE-1542) Lucene can incorrectly set the position of tokens that start a field with positonInc 0.

[ https://issues.apache.org/jira/browse/LUCENE-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714400#action_12714400 ] Shai Erera commented on LUCENE-1542: So Mike, just for clarification - let's say I

[jira] Commented: (LUCENE-1614) Add next() and skipTo() variants to DocIdSetIterator that return the current doc, instead of boolean

[ https://issues.apache.org/jira/browse/LUCENE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714467#action_12714467 ] Shai Erera commented on LUCENE-1614: bq. First off, Scorer.score(Collector, int) (and

[jira] Commented: (LUCENE-1542) Lucene can incorrectly set the position of tokens that start a field with positonInc 0.

[ https://issues.apache.org/jira/browse/LUCENE-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714481#action_12714481 ] Yonik Seeley commented on LUCENE-1542: -- Most bug fixes aren't back compatible :-)

[jira] Commented: (LUCENE-1313) Realtime Search

[ https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714491#action_12714491 ] Jason Rutherglen commented on LUCENE-1313: -- I had forgotten about concurrency

[jira] Commented: (LUCENE-1313) Realtime Search

[ https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714494#action_12714494 ] Michael McCandless commented on LUCENE-1313: bq. I had forgotten about

[jira] Commented: (LUCENE-1614) Add next() and skipTo() variants to DocIdSetIterator that return the current doc, instead of boolean

[ https://issues.apache.org/jira/browse/LUCENE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714500#action_12714500 ] Michael McCandless commented on LUCENE-1614: bq. Agreed. I'll take a look at

[jira] Commented: (LUCENE-1313) Realtime Search

[ https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714522#action_12714522 ] Jason Rutherglen commented on LUCENE-1313: -- I guess I'm confused about the doc

[jira] Commented: (LUCENE-1313) Realtime Search

[ https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714535#action_12714535 ] Michael McCandless commented on LUCENE-1313: {quote} The SR should then be

[jira] Commented: (LUCENE-1614) Add next() and skipTo() variants to DocIdSetIterator that return the current doc, instead of boolean

[ https://issues.apache.org/jira/browse/LUCENE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714567#action_12714567 ] Shai Erera commented on LUCENE-1614: bq. Under what cases are NPE AIOOBE thrown by

[jira] Commented: (LUCENE-1542) Lucene can incorrectly set the position of tokens that start a field with positonInc 0.

[ https://issues.apache.org/jira/browse/LUCENE-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714577#action_12714577 ] Shai Erera commented on LUCENE-1542: I don't think there's a user-visible impact. This

ReadOnly IndexReaders

Does it make sense to add isReadOnly() to IndexReader such that one can easily introspect whether a Reader is read only? -Grant - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail:

Re: ReadOnly IndexReaders

Yeah! On Fri, May 29, 2009 at 2:21 PM, Grant Ingersoll gsing...@apache.orgwrote: Does it make sense to add isReadOnly() to IndexReader such that one can easily introspect whether a Reader is read only? -Grant - To

Re: Lucene's default settings back compatibility

So ... I've this happen a lot of times (especially in my thesis work) - someone raises a controversial topic, or one that touches the nervous of the system, there's a flurry of activity and then it dies unexpectedly, even though it feels to everyone that there's an extra mile that should be taken

[jira] Commented: (LUCENE-1629) contrib intelligent Analyzer for Chinese

[ https://issues.apache.org/jira/browse/LUCENE-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714670#action_12714670 ] Mingfai Ma commented on LUCENE-1629: re. 平假名 and 片假名 in Japanese