If by changes you also mean deprecated features, then take a look at
LUCENE-1614 - if you have your own Scorers/DISIs, you might want to
implement the new methods, since the current ones are deprecated.
On Thu, May 28, 2009 at 1:23 AM, Yonik Seeley yo...@lucidimagination.comwrote:
We're aiming
[
https://issues.apache.org/jira/browse/LUCENE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-1614:
---
Attachment: LUCENE-1614.patch
Deprecated SpanScorer.firstTime and removed the use of it. (in
[
https://issues.apache.org/jira/browse/LUCENE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12713918#action_12713918
]
Shai Erera commented on LUCENE-1252:
I must admit that I read the issue briefly, and
The IndexWriter diagnostics (LUCENE-1654: recording Lucene version,
Java/OS version, etc into each segment created) also bumped the index
file format.
And LUCENE-1623 (fixing back-compat issue w/ field names that have
non-ascii characters) also bumped the format of the fnm file.
Offhand I can't
[
https://issues.apache.org/jira/browse/LUCENE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12713928#action_12713928
]
Michael McCandless commented on LUCENE-1252:
I agree, we would want to do a
[
https://issues.apache.org/jira/browse/LUCENE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12713931#action_12713931
]
Michael McCandless commented on LUCENE-1614:
{quote}
After I made add()
[
https://issues.apache.org/jira/browse/LUCENE-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1657.
Resolution: Fixed
Make boolean readOnly a required arg to IndexReader.open
[
https://issues.apache.org/jira/browse/LUCENE-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved LUCENE-1653.
-
Resolution: Fixed
Lucene Fields: [New, Patch Available] (was: [New])
Thanks Shai!
On Thu, May 28, 2009 at 5:35 AM, Michael McCandless
luc...@mikemccandless.com wrote:
The IndexWriter diagnostics (LUCENE-1654: recording Lucene version,
Java/OS version, etc into each segment created) also bumped the index
file format.
And LUCENE-1623 (fixing back-compat issue w/ field names
On Thu, May 28, 2009 at 2:56 AM, Shai Erera ser...@gmail.com wrote:
If by changes you also mean deprecated features, then take a look at
LUCENE-1614 - if you have your own Scorers/DISIs, you might want to
implement the new methods, since the current ones are deprecated.
Yes, we have our own
Constants causing NullPointerException when fetching metadata Implementation
Version in MANIFEST
--
Key: LUCENE-1666
URL:
[
https://issues.apache.org/jira/browse/LUCENE-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-1542:
Summary: Lucene can incorrectly set the position of tokens that start a
field with positonInc 0.
[
https://issues.apache.org/jira/browse/LUCENE-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Renaud Delbru updated LUCENE-1666:
--
Attachment: LUCENE-1666.patch
Constants causing NullPointerException when fetching metadata
[
https://issues.apache.org/jira/browse/LUCENE-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-1542:
Attachment: LUCENE-1542.patch
something like this to fix
Lucene can incorrectly set the
[
https://issues.apache.org/jira/browse/LUCENE-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12713999#action_12713999
]
Mark Miller commented on LUCENE-1542:
-
so that appears to fix it - but i'm not sure
On May 28, 2009, at 10:24 AM, Yonik Seeley wrote:
removing all the deprecated stuff related to Token/TokenStream is for
another day...
I think Lucene needs to re-look at the TokenStream stuff anyway. I
seem to recall talking with Michael B. about changing it at
ApacheCon. I'd be
[
https://issues.apache.org/jira/browse/LUCENE-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-1666:
--
Assignee: Michael McCandless
Constants causing NullPointerException when
[
https://issues.apache.org/jira/browse/LUCENE-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1666.
Resolution: Fixed
Woops, thanks Renaud -- I just committed this.
Constants
[
https://issues.apache.org/jira/browse/LUCENE-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714020#action_12714020
]
Michael McCandless commented on LUCENE-1542:
Alas, this looks like a dup of
[
https://issues.apache.org/jira/browse/LUCENE-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1666:
--
Attachment: LUCENE-1666.patch
Mike, you were a little bit too fast :-)
I worked out a better
[
https://issues.apache.org/jira/browse/LUCENE-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-1542:
Attachment: LUCENE-1542.patch
with unit test
Lucene can incorrectly set the position of tokens
[
https://issues.apache.org/jira/browse/LUCENE-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1666:
--
Attachment: LUCENE-1666.patch
Oh forget the -dev thing... Attached is fixed patch.
[
https://issues.apache.org/jira/browse/LUCENE-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1666:
--
Attachment: (was: LUCENE-1666.patch)
Constants causing NullPointerException when
[
https://issues.apache.org/jira/browse/LUCENE-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714033#action_12714033
]
Mark Miller commented on LUCENE-1542:
-
I don't think the fix here needs to disallow
[
https://issues.apache.org/jira/browse/LUCENE-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714039#action_12714039
]
Mark Miller commented on LUCENE-1255:
-
why should the first token have an increment of
[
https://issues.apache.org/jira/browse/LUCENE-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714046#action_12714046
]
Michael McCandless commented on LUCENE-1666:
Much simpler, thanks Uwe!
But,
[
https://issues.apache.org/jira/browse/LUCENE-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1666:
--
Attachment: LUCENE-1666.patch
I think the check should be simply if getPackage() returns null
I will be out of the office starting 27/05/2009 and will not return until
31/05/2009.
I will respond to your message when I return.
-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands,
[
https://issues.apache.org/jira/browse/LUCENE-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714065#action_12714065
]
Shai Erera commented on LUCENE-1542:
Just wanted to say we've had an internal
[
https://issues.apache.org/jira/browse/LUCENE-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714068#action_12714068
]
Uwe Schindler commented on LUCENE-1654:
---
I found a bug for indexes with the
[
https://issues.apache.org/jira/browse/LUCENE-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714074#action_12714074
]
Michael McCandless commented on LUCENE-1666:
Excellent -- I just committed
[
https://issues.apache.org/jira/browse/LUCENE-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714068#action_12714068
]
Uwe Schindler edited comment on LUCENE-1654 at 5/28/09 10:50 AM:
[
https://issues.apache.org/jira/browse/LUCENE-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714087#action_12714087
]
Michael McCandless commented on LUCENE-1654:
Woops -- thanks Uwe!
Include
An interesting discussion came up. How do we handle IW.getReader turnaround
time on large new segments?
This is exactly why we added IndexReaderWarmer -- it pre-warms a newly
merged segment before committing to SegmentInfos.
So, while such warming is happening, if getReader() is called, the
returned reader will still read the old segments.
Mike
On Thu, May 28, 2009 at 3:06 PM, Jason Rutherglen
And warming a segment in mergeMiddle doesn't block the addition of new
segments.
On Thu, May 28, 2009 at 12:30 PM, Michael McCandless
luc...@mikemccandless.com wrote:
This is exactly why we added IndexReaderWarmer -- it pre-warms a newly
merged segment before committing to SegmentInfos.
So,
Right. If you play w/ this please report back on how it goes!
Mike
On Thu, May 28, 2009 at 3:38 PM, Jason Rutherglen
jason.rutherg...@gmail.com wrote:
And warming a segment in mergeMiddle doesn't block the addition of new
segments.
On Thu, May 28, 2009 at 12:30 PM, Michael McCandless
Also important to note that only with ConcurrentMergeScheduler will the
segmentReader warming occur in the background. When using
SerialMergeScheduler, the warming will happen in the foreground.
On Thu, May 28, 2009 at 12:40 PM, Michael McCandless
luc...@mikemccandless.com wrote:
Right. If
ConcurrentMergeScheduler use a thread pool (per directory)
--
Key: LUCENE-1667
URL: https://issues.apache.org/jira/browse/LUCENE-1667
Project: Lucene - Java
Issue Type: Improvement
Some folks may want to have IW.getReader (LUCENE-1516) use custom readers
underneath, we can have IW support an IndexReaderFactory?
On Thu, May 28, 2009 at 3:30 PM, Michael McCandless
luc...@mikemccandless.com wrote:
This is exactly why we added IndexReaderWarmer -- it pre-warms a newly
merged segment before committing to SegmentInfos.
So, while such warming is happening, if getReader() is called, the
returned reader will
Newly added docs are still free to make new segments, and be reopened,
while this warming is taking place.
So, getReader() will wait for newly added/deleted docs to be flushed
reopened, but will not wait for any running merges to complete (finish
writing the files finish warming a SegmentReader
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 wait for newly added/deleted docs to be flushed
reopened, but will not wait for
This is for Marvin who previously mentioned loading the term
dictionary directly from the filesystem (rather than load every
Nth term into Java heap) which could improve latency of opening
new readers.
Were you able to take this idea any further?
[
https://issues.apache.org/jira/browse/LUCENE-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714285#action_12714285
]
Otis Gospodnetic commented on LUCENE-1629:
--
I just got to look at this code and I
[
https://issues.apache.org/jira/browse/LUCENE-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714293#action_12714293
]
Xiaoping Gao commented on LUCENE-1629:
--
I think the algorithm of Hidden Markov Model
[
https://issues.apache.org/jira/browse/LUCENE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714298#action_12714298
]
Shai Erera commented on LUCENE-1614:
Mike, I think we may have relaxed the policy of
47 matches
Mail list logo
