There are a couple of Vector:s in the code. Is it really necessary to
use this expensive thread safe artifact from the dark ages?
What I really don't get is the need for it in the index package as
IndexWriter already is synchronized. And how often do you modify the
clauses of a BooleanQuery from m
[
http://issues.apache.org/jira/browse/LUCENE-563?page=comments#action_12378158 ]
Daniel Naber commented on LUCENE-563:
-
Thanks, I just committed the patch. However, I cannot see errors in lucli, can
you make a patch for those cases, too?
> IndexReade
[
http://issues.apache.org/jira/browse/LUCENE-366?page=comments#action_12378147 ]
Hoss Man commented on LUCENE-366:
-
FYI: Test code failed to compile because of removed deprecated methods on the
trunk in prep for 2.0 release, with those methods changed th
[ http://issues.apache.org/jira/browse/LUCENE-366?page=all ]
paul.elschot resolved LUCENE-366:
-
Resolution: Cannot Reproduce
Assign To: (was: Lucene Developers)
The posted code won't compile against current trunk,
and I could never reproduc
[
http://issues.apache.org/jira/browse/LUCENE-551?page=comments#action_12378084 ]
Martin Cooper commented on LUCENE-551:
--
Note that the recommendation for Maven 2 is such that the Lucene groupId should
change from just 'lucene' to 'org.apache.lucene'.
[
http://issues.apache.org/jira/browse/LUCENE-396?page=comments#action_12378067 ]
Yonik Seeley commented on LUCENE-396:
-
The patch is also incorrect in that token positions are not preserved in the
cases where positionIncrement!=1
> [PATCH] Add positio
[ http://issues.apache.org/jira/browse/LUCENE-556?page=all ]
Doug Cutting updated LUCENE-556:
Fix Version: 2.0
> MatchAllDocsQuery, MultiSearcher and a custom HitCollector throwing exception
> -
[
http://issues.apache.org/jira/browse/LUCENE-396?page=comments#action_12378056 ]
Doug Cutting commented on LUCENE-396:
-
This is incompatible. Are there folks who rely on the old behavior? I'd guess
there are.
> [PATCH] Add position increment back in
[ http://issues.apache.org/jira/browse/LUCENE-546?page=all ]
Doug Cutting updated LUCENE-546:
Fix Version: 2.0
> Index corruption when using RAMDirectory( Directory) constructor
>
>
>
Let's try to coordinate this through Jira.
Can folks please vote for bugs that they'd like to see fixed?
Then, committers, if you think a bug is either urgent enough that we
should not release without it, and/or that it has a patch that is safe
to commit, then please change its "Fix Version" t
Chris Hostetter wrote:
: It's got one difference from yours, in that the terms are allowed to
: occur in any order in the sub-phrases (so phrase "C B" from your
: original example is scored like "B C").
there's a much bigger differnece, in that your technique won't reqard
documents where B and C
Marvin Humphrey wrote:
More problematic than the "Modified UTF-8" actually, is the definition
of a Lucene String. According to the File Formats document, "Lucene
writes strings as a VInt representing the length, followed by the
character data." The word "length" is ambiguous in that context,
[ http://issues.apache.org/jira/browse/LUCENE-433?page=all ]
paul.elschot resolved LUCENE-433:
-
Resolution: Fixed
Resolved this by reopening the original issue.
I'm sorry about the extra jira update messages,
but this is more tidy in the end.
> Is
[ http://issues.apache.org/jira/browse/LUCENE-352?page=all ]
paul.elschot reopened LUCENE-352:
-
Assign To: (was: Lucene Developers)
The fix in patch.txt is not in the trunk, and there was some recent discussion
on
what might be the same bug, s
[ http://issues.apache.org/jira/browse/LUCENE-330?page=all ]
paul.elschot resolved LUCENE-330:
-
Resolution: Fixed
Assign To: (was: Lucene Developers)
This was added to FilteredQuery not so long ago.
> [PATCH] Use filter bits for next() an
[ http://issues.apache.org/jira/browse/LUCENE-563?page=all ]
paul.elschot updated LUCENE-563:
Component: Index
Fix Version: (was: 2.0)
Version: (was: 2.0)
Priority: Minor (was: Major)
> IndexReader currently has javadoc erro
[ http://issues.apache.org/jira/browse/LUCENE-563?page=all ]
paul.elschot updated LUCENE-563:
Attachment: IndexReaderPatch1.txt
Fixes javadoc errors in IndexReader.
Remaining javadoc errors are in:
contrib/ant
contrib/lucli
contrib/regex
> IndexReade
IndexReader currently has javadoc errors
Key: LUCENE-563
URL: http://issues.apache.org/jira/browse/LUCENE-563
Project: Lucene - Java
Type: Improvement
Versions: 2.0
Reporter: paul.elschot
Fix For: 2.0
Curre
See also here:
http://issues.apache.org/jira/browse/LUCENE-433
Regards,
Paul Elschot
On Monday 01 May 2006 20:17, Chris Hostetter wrote:
>
> : I am having problems running span queries with more than one
> : negative clauses:
>
> i believe you mean when the exclude clause contains a SpanNear
On Monday 01 May 2006 20:17, Chris Hostetter wrote:
>
> : I am having problems running span queries with more than one
> : negative clauses:
>
> i believe you mean when the exclude clause contains a SpanNear query
> correct?
>
> : Is the span query nested correctly?
>
> I'm not very good at r
20 matches
Mail list logo
