[jira] Commented: (LUCENE-1567) New flexible query parser

[ https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717560#action_12717560 ] Luis Alves commented on LUCENE-1567: There will be a couple of more changes need: We a

[jira] Commented: (LUCENE-1567) New flexible query parser

[ https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717543#action_12717543 ] Adriano Crestani commented on LUCENE-1567: -- I went through the new QP and listed

[jira] Commented: (LUCENE-1567) New flexible query parser

[ https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717535#action_12717535 ] Luis Alves commented on LUCENE-1567: I actually think we should give the parser to con

Re: [jira] Commented: (LUCENE-1567) New flexible query parser

I actually think we should give the parser to contrib on 2.9 using jdk 1.5 syntax and move it to main on 3.0 using jdk1.5 syntax. I don't think it's a small change, and will affect the interfaces, and all implementations of QueryNode Objects. I would see nothing wrong with having a jdk 1.4 ver

[jira] Commented: (LUCENE-1567) New flexible query parser

[ https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717492#action_12717492 ] Adriano Crestani commented on LUCENE-1567: -- It's mostly internal stuffs, the only

[jira] Commented: (LUCENE-1567) New flexible query parser

[ https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717486#action_12717486 ] Michael Busch commented on LUCENE-1567: --- Is it mostly internal stuff you need to cha

[jira] Updated: (LUCENE-1453) When reopen returns a new IndexReader, both IndexReaders may now control the lifecycle of the underlying Directory which is managed by reference counting

[ https://issues.apache.org/jira/browse/LUCENE-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-1453: -- Attachment: LUCENE-1453-with-FSDir-open.patch This is a variant for testing the same with FSDi

[jira] Updated: (LUCENE-1453) When reopen returns a new IndexReader, both IndexReaders may now control the lifecycle of the underlying Directory which is managed by reference counting

[ https://issues.apache.org/jira/browse/LUCENE-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-1453: -- Attachment: LUCENE-1453.patch This is the solution using the FilterIndexReader, all tests now

Some thoughts around the use of reader.isDeleted and hasDeletions

Hi I recently read CHANGES to learn more about the readOnly parameter IndexReader now supports, and came across LUCENE-1329 with a comment that isDeleted was made not synchronized if readOnly=true (e.g. ReadOnlyIndexReader), which can affect search code, as it is usually the bottleneck for search

Re: WebLuke - include Jetty in Lucene binary distribution?

Hi John/Grant. I haven't done any more in developing WebLuke - although still use it regularly. As Grant suggests there was an unease (mine) about bloating the Lucene distribution size with GWT dependencies so it wasn't rolled into contrib. However I guess I'm comfortable if no one else is conce

Re: WebLuke - include Jetty in Lucene binary distribution?

Hey John, I like WebLuke too, but am not sure what ever became of it. It seemed like it had a lot of traction (http://www.lucidimagination.com/search/document/3b06db2b12dffb70/webluke_include_jetty_in_lucene_binary_distribution ) but that the main objection was the size of the GWT stuff and a

[jira] Commented: (LUCENE-1453) When reopen returns a new IndexReader, both IndexReaders may now control the lifecycle of the underlying Directory which is managed by reference counting

[ https://issues.apache.org/jira/browse/LUCENE-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717244#action_12717244 ] Michael McCandless commented on LUCENE-1453: But the refcounting is also depre

[jira] Commented: (LUCENE-1453) When reopen returns a new IndexReader, both IndexReaders may now control the lifecycle of the underlying Directory which is managed by reference counting

[ https://issues.apache.org/jira/browse/LUCENE-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717242#action_12717242 ] Uwe Schindler commented on LUCENE-1453: --- Because the error sometimes also occurs wit

[jira] Commented: (LUCENE-1453) When reopen returns a new IndexReader, both IndexReaders may now control the lifecycle of the underlying Directory which is managed by reference counting

[ https://issues.apache.org/jira/browse/LUCENE-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717231#action_12717231 ] Michael McCandless commented on LUCENE-1453: Since we've deprecated all method