[
http://issues.apache.org/jira/browse/LUCENE-555?page=comments#action_12444827 ]
Tero Hagström commented on LUCENE-555:
--
We've experienced Lucene index corruption a few times on a production system.
What makes it tricky is, that 1) the abi
[
http://issues.apache.org/jira/browse/LUCENE-700?page=comments#action_12444830 ]
kaineci commented on LUCENE-700:
i see.
.
more = false;
end += BucketTable.SIZE;//corresponding one term
for (SubScorer sub = scorers; sub != null;
Hi,
Univ. of Amsterdam has provided a downloadable version of a language
modelling version of Lucene. Their language model is not BM25 but is
quite similar in nature. The version is at:
http://ilps.science.uva.nl/Resources/#lm-lucen
I have worked on their version a bit, they have created new clas
[
http://issues.apache.org/jira/browse/LUCENE-695?page=comments#action_12444903 ]
Nadav Har'El commented on LUCENE-695:
-
> If "given" a null array? Is this ever done in Lucene? Which should be fixed,
> the testcase or the code?
I don't kno
[ http://issues.apache.org/jira/browse/LUCENE-528?page=all ]
Ning Li updated LUCENE-528:
---
Lucene Fields: [Patch Available]
> Optimization for IndexWriter.addIndexes()
> -
>
> Key: LUCENE-528
>
[
http://issues.apache.org/jira/browse/LUCENE-555?page=comments#action_12444919 ]
Otis Gospodnetic commented on LUCENE-555:
-
Tero - I suggest you open a new issue, if you want. Unlike the original issue
here, you know why your index got
[
http://issues.apache.org/jira/browse/LUCENE-700?page=comments#action_12444921 ]
Otis Gospodnetic commented on LUCENE-700:
-
Is that while loop in your initial comment endless?
Can you write a little class/unit test that shows this?
I can
[
http://issues.apache.org/jira/browse/LUCENE-555?page=comments#action_12444925 ]
Michael McCandless commented on LUCENE-555:
---
I would also add: I'm very surprised disk full corrupts the Lucene index. I
can't explain it. I'd like to
From what I read in the Javadoc of ResouceBundle, it does cache the values.
Patrick Turcotte
On 10/26/06, Otis Gospodnetic (JIRA) <[EMAIL PROTECTED]> wrote:
[
http://issues.apache.org/jira/browse/LUCENE-682?page=comments#action_12444776]
Otis Gospodnetic commented on LUCENE-682:
Chris Hostetter wrote:
this is the past thread i was thinking about before...
http://www.archivum.info/java-dev@lucene.apache.org/2006-06/msg00012.html
...refering to leaving the release branches clean untill just before a
point release when all the desired changes can get merged in.
That's t
[
http://issues.apache.org/jira/browse/LUCENE-700?page=comments#action_12444949 ]
Paul Elschot commented on LUCENE-700:
-
It looks like the initially posted code is from BooleanScorer, but nowadays
normally BooleanScorer2 is used.
Would it be
Another approach is to make all patches first in the release
branch,
then merge them to trunk. Personally I find that to be a pain,
A royal pain, I agree. And very, very possibly a waste of time, since
there may never be a 2.0.1 release.
I think a lot comes down to the thinking
[ http://issues.apache.org/jira/browse/LUCENE-700?page=all ]
Yonik Seeley resolved LUCENE-700.
-
Lucene Fields: (was: [New])
Resolution: Cannot Reproduce
I don't see a problem with that code (and it's not used by default anyway).
If you have a te
[
http://issues.apache.org/jira/browse/LUCENE-555?page=comments#action_12444998 ]
Michael McCandless commented on LUCENE-555:
---
Tero, one question: are you copying or rsync'ing the index from where the
writers write it, to where the rea
[ http://issues.apache.org/jira/browse/LUCENE-489?page=all ]
Steven Parkes updated LUCENE-489:
-
Attachment: LUCENE-489.patch
I think "allowLeadingWildcard" would be more descriptive
Agree. Changed.
> Allow QP subclasses to support Wildcard Q
: I guess I figure the process for 2.0.1, if there was a compelling need
: for it, would be to review all the changes that have happened since 2.0
: was cut. Were I to do this, I'd look at the ones flagged as 2.1 as well
: as the 2.0.1, so I don't see that flagging early really buys much.
It's ki
[ http://issues.apache.org/jira/browse/LUCENE-695?page=all ]
Yonik Seeley resolved LUCENE-695.
-
Resolution: Fixed
Committed. Thanks Nadav!
> Improve BufferedIndexInput.readBytes() performance
> --
>
>
[
http://issues.apache.org/jira/browse/LUCENE-686?page=comments#action_12445027 ]
Steven Parkes commented on LUCENE-686:
--
You're right, and that's actually at the heart of the issue.
Seems like part of what needs to be clarified is what clo
[ http://issues.apache.org/jira/browse/LUCENE-528?page=all ]
Yonik Seeley resolved LUCENE-528.
-
Resolution: Fixed
Assignee: Yonik Seeley (was: Otis Gospodnetic)
Thanks Ning, I just committed this.
Wish I had had it some time ago :-)
http://www.mai
[ http://issues.apache.org/jira/browse/LUCENE-569?page=all ]
Hoss Man updated LUCENE-569:
Attachment: LUCENE-569.ubber.patch
Okay, I've attached a cosolidation of SpanScorer.explain.testcase.patch and
NearSpans20060903.patch, with a few small modifications.
[ http://issues.apache.org/jira/browse/LUCENE-569?page=all ]
Hoss Man updated LUCENE-569:
Lucene Fields: [Patch Available]
Assignee: Hoss Man
> NearSpans skipTo bug
>
>
> Key: LUCENE-569
> URL: ht
: Here is a version of the QueryParser that can "understand" the AND, OR
: and NOT keyword in other languages.
I finally got a chance to skim this ... i don't know a lot about javaCC or
ResourceBundles, but this looks really cool to me. Mainly because it
looks like this would make it really easy
I've been thinking this all through and I guess my question is with the
synchronization between Jira and svn. The fact that Resolved/Fixed is
usually tied to a commit shows we all think they are related: we're all
using Jira to reflect svn to some extent, right?
I'd like to be able to look at Jira
: Here is a version of the QueryParser that can "understand" the AND, OR
: and NOT keyword in other languages.
I finally got a chance to skim this ... i don't know a lot about javaCC or
ResourceBundles, but this looks really cool to me. Mainly because it
looks like this would make it really eas
[
http://issues.apache.org/jira/browse/LUCENE-682?page=comments#action_12445062 ]
Patrick Turcotte commented on LUCENE-682:
-
>From what I read in the Javadoc of ResouceBundle, it does cache the values.
> QueryParser with Locale Based Ope
- Original Message
From: Chris Hostetter <[EMAIL PROTECTED]>
: But consistency would help me and I suppose I still favor flagging
: everything as 2.1 now. If not for the simple reason that I don't know
: how to decide if something should go into some 2.0.1 when I don't know
: what's going
Hi,
- Original Message
From: Steven Parkes <[EMAIL PROTECTED]>
And an observation: shouldn't everything currently in Resolved have a
FVs that includes 2.1? I can see optionally adding 2.0.1, too, but since
OG: I never specify FV. I bet you will see most issues in Resolved state have
n
[ http://issues.apache.org/jira/browse/LUCENE-489?page=all ]
Otis Gospodnetic resolved LUCENE-489.
-
Resolution: Fixed
Applied, thanks.
> Allow QP subclasses to support Wildcard Queries with leading "*"
> -
28 matches
Mail list logo
