[
https://issues.apache.org/jira/browse/LUCENE-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607445#action_12607445
]
Jason Rutherglen commented on LUCENE-1312:
--
Will be interesting to try out your n
[
https://issues.apache.org/jira/browse/LUCENE-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wettin updated LUCENE-1312:
Attachment: lucene-1312.patch
Thanks for the updated patch Jason!
I worked a bit on it:
* Factor
[
https://issues.apache.org/jira/browse/LUCENE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607437#action_12607437
]
Mark Miller commented on LUCENE-794:
FYI: This has been applied to the trunk as well.
Add setIndexReader in IndexSearcher
Key: LUCENE-1315
URL: https://issues.apache.org/jira/browse/LUCENE-1315
Project: Lucene - Java
Issue Type: Improvement
Components: Search
Affects Version
[
https://issues.apache.org/jira/browse/LUCENE-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Urso updated LUCENE-1315:
-
Attachment: setIndexReader.diff
Patch attached.
> Add setIndexReader in IndexSearcher
> --
[
https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated LUCENE-1313:
-
Attachment: lucene-1313.patch
lucene-1313.patch
Removed http://reader.imagero.com/uio/
[
https://issues.apache.org/jira/browse/LUCENE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607415#action_12607415
]
Tavi Nathanson commented on LUCENE-794:
---
Hi,
I'm new to Lucene and the highlighter,
[
https://issues.apache.org/jira/browse/LUCENE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-1314:
--
Assignee: Michael McCandless
> IndexReader.reopen(boolean force)
> ---
Project -> Properties -> Java Editor -> Save Actions Check "Perform the
selected actions on save" Uncheck Organize Imports is the correct answer now
in Google
On Mon, Jun 23, 2008 at 4:07 PM, Mike Klaas <[EMAIL PROTECTED]> wrote:
> On 23-Jun-08, at 10:14 AM, Jason Rutherglen (JIRA) wrote:
>
>>
>
On 23-Jun-08, at 10:14 AM, Jason Rutherglen (JIRA) wrote:
Does anyone know how to turn off Eclipse automatically changing the
import statements? I am not making it reformat but if I edit some
code in a file it sees fit to reformat the imports.
http://www.google.com/search?q=turn%20off%20e
[
https://issues.apache.org/jira/browse/LUCENE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated LUCENE-1314:
-
Attachment: lucene-1314.patch
lucene-1314.patch
First cut at this, seems to work as des
IndexReader.reopen(boolean force)
-
Key: LUCENE-1314
URL: https://issues.apache.org/jira/browse/LUCENE-1314
Project: Lucene - Java
Issue Type: New Feature
Components: Index
Affects Versions: 2.3.
[
https://issues.apache.org/jira/browse/LUCENE-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated LUCENE-1312:
-
Attachment: lucene-1312.patch
lucene-1312.patch
Added the code to InstantiatedIndex(Ind
[
https://issues.apache.org/jira/browse/LUCENE-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated LUCENE-1312:
-
Attachment: lucene-1312.patch
lucene-1312.patch
The problem with TermEnum is term() nee
"you need to forcefully get a new reader which you can make changes to, such
that it does not affect the original reader"
exactly. I was thinking reopen(boolean forceNew) given people probably
expect to use reopen for this behavior, and may not think to look at clone.
Currently the reopen seems t
My guess is your newIndexReader is in fact the same as your
previousIndexReader, in which case getting the same gen in your
LOG.info is expected.
It seems like what you want is a way to force a new reader to be
returned by reopen() even if there were no changes to the index. Ie,
you ne
When this code is run, why are the generation numbers the same? The desired
behavior is that the delete happens only to the newIndexReader, leaving the
previousIndexReader unaffected.
IndexReader previousIndexReader = latestIndexSnapshot.getIndexReader();
IndexReader newIndexReader = previousInde
17 matches
Mail list logo
