Query parser doesn't warn about unmatched ')'
-
Key: LUCENE-694
URL: http://issues.apache.org/jira/browse/LUCENE-694
Project: Lucene - Java
Issue Type: Bug
Components: QueryParser
Aff
Improve BufferedIndexInput.readBytes() performance
--
Key: LUCENE-695
URL: http://issues.apache.org/jira/browse/LUCENE-695
Project: Lucene - Java
Issue Type: Improvement
Components: S
[ http://issues.apache.org/jira/browse/LUCENE-695?page=all ]
Nadav Har'El updated LUCENE-695:
Attachment: readbytes.patch
The patch, which includes the change to BufferedIndexInput.readBytes(), and a
new unit test for that class.
> Improve BufferedInde
[
http://issues.apache.org/jira/browse/LUCENE-551?page=comments#action_12444300 ]
Marcel Reutegger commented on LUCENE-551:
-
Are there any plans to also publish the new release to the Maven 1 repository
on ibiblio.org? We at Jackrabbit s
[
http://issues.apache.org/jira/browse/LUCENE-695?page=comments#action_12444316 ]
Yonik Seeley commented on LUCENE-695:
-
> I wonder why this happened.
readBytes on less than a buffer size probably only happens with binary (or
compressed) fi
[
http://issues.apache.org/jira/browse/LUCENE-693?page=comments#action_12444317 ]
Peter Keegan commented on LUCENE-693:
-
Yonik,
I tried out your patch, but it causes an exception on some boolean queries.
This one occurred on a boolean query
[
http://issues.apache.org/jira/browse/LUCENE-693?page=comments#action_12444319 ]
Yonik Seeley commented on LUCENE-693:
-
Thanks for trying it out Peter.
Odd it could fail after passing all the Lucene unit tests... I assume this was
the lucen
[
http://issues.apache.org/jira/browse/LUCENE-693?page=comments#action_12444320 ]
Yonik Seeley commented on LUCENE-693:
-
Ah, I see the problem... in the constructor I have
boolean more = scorers[i].next();
for each scorer... but note th
[
http://issues.apache.org/jira/browse/LUCENE-695?page=comments#action_12444322 ]
Nadav Har'El commented on LUCENE-695:
-
Sorry, I didn't notice that my fix broke this unit test. Thanks for catching
that.
What is happening is interesting: th
[
http://issues.apache.org/jira/browse/LUCENE-693?page=comments#action_12444334 ]
Yonik Seeley commented on LUCENE-693:
-
I'm not sure how it's possible, but my version is *solwer* in the performance
test I came up with.
Very odd... I'm not s
[ http://issues.apache.org/jira/browse/LUCENE-693?page=all ]
Yonik Seeley updated LUCENE-693:
Attachment: conjunction.patch
Here is my current patch and test code (which currently seems to be slower with
this patch).
> ConjunctionScorer - more tuneup
>
[ http://issues.apache.org/jira/browse/LUCENE-695?page=all ]
Nadav Har'El updated LUCENE-695:
Attachment: readbytes.patch
A fixed patch, which now checks that we don't read past of of file. This is now
checked correctly in all three cases (1. data alrea
[
http://issues.apache.org/jira/browse/LUCENE-695?page=comments#action_12444350 ]
Yonik Seeley commented on LUCENE-695:
-
> One unit test assumed that readBytes() can work if given a null array, if the
> length requested is 0. Unfortunately,
[
http://issues.apache.org/jira/browse/LUCENE-693?page=comments#action_1208 ]
Peter Keegan commented on LUCENE-693:
-
Well, I'm seeing a good 7% increase over the trunk version. Conjunction
scorer time is mostly in 'skipto' now, which seem
[
http://issues.apache.org/jira/browse/LUCENE-693?page=comments#action_1211 ]
Yonik Seeley commented on LUCENE-693:
-
> Well, I'm seeing a good 7% increase over the trunk version.
Yay! Now only if I could get my random synthetic tests to
[ http://issues.apache.org/jira/browse/LUCENE-693?page=all ]
Yonik Seeley updated LUCENE-693:
Attachment: conjunction.patch
This version removes the docs[] array and seems to be slightly faster.
Still slower on the synthetic random ConstantScoreQuery tes
[
http://issues.apache.org/jira/browse/LUCENE-693?page=comments#action_1236 ]
Peter Keegan commented on LUCENE-693:
-
fwiw, my tests were done using 'real world' queries and index. Most queries
have several required clauses. The jvm is 1.6
[
http://issues.apache.org/jira/browse/LUCENE-686?page=comments#action_1238 ]
Hoss Man commented on LUCENE-686:
-
Quick summary of some discussion from the mailing list...
1) i replied to paul's comments in the bug indicating that while there
: I got a bit of a surprise trying to re-implement the ConjunctionScorer.
: It turns out that skipTo(0) does not always return the same thing as
: next() on a newly created scorer. Some scorers give invalid results
: if skipTo() is called before next().
that sounds like a bug to me...
: The javd
[
http://issues.apache.org/jira/browse/LUCENE-693?page=comments#action_1287 ]
Paul Elschot commented on LUCENE-693:
-
Yonik,
you wrote:
> but then learned that calling skipTo() before calling next() doesn't always
> work.
Could you des
Scorer.skipTo() doesn't always work if called before next()
---
Key: LUCENE-696
URL: http://issues.apache.org/jira/browse/LUCENE-696
Project: Lucene - Java
Issue Type: Bug
Affects V
[
http://issues.apache.org/jira/browse/LUCENE-693?page=comments#action_1296 ]
Yonik Seeley commented on LUCENE-693:
-
> Could you describe a case in which skipTo() before next() does not work?
I don't recall, but my attempt to speed up Co
[
http://issues.apache.org/jira/browse/LUCENE-696?page=comments#action_12444500 ]
Yonik Seeley commented on LUCENE-696:
-
It would also simplify some scorers if doc() wasn't undefined before next() or
skipTo() was called, but instead -1.
This
[
http://issues.apache.org/jira/browse/LUCENE-696?page=comments#action_12444506 ]
Paul Elschot commented on LUCENE-696:
-
Repeating a comment just posted at LUCENE-693:
skipTo() as first call on a scorer should work. ReqExclScorer and
ReqOpt
: It would also simplify some scorers if doc() wasn't undefined before
: next() or skipTo() was called, but instead -1.
+1 ... but if we are goingg to change the API requirements for doc(),
we should clarify the requirements or score() ... with doc(), negative
numbers can easily be used as a mark
[ http://issues.apache.org/jira/browse/LUCENE-528?page=all ]
Ning Li updated LUCENE-528:
---
Attachment: AddIndexesNoOptimize.patch
This patch implements addIndexesNoOptimize() following the algorithm described
earlier.
- The patch is based on the latest versi
[ http://issues.apache.org/jira/browse/LUCENE-696?page=all ]
Yonik Seeley updated LUCENE-696:
Attachment: dismax.patch
DisjunctionMaxScorer turned out to be the only scorer I could see with that
problem.
Here's the patch w/ tests.
> Scorer.skipTo() doe
Scorer.skipTo affects sloppyPhrase scoring
--
Key: LUCENE-697
URL: http://issues.apache.org/jira/browse/LUCENE-697
Project: Lucene - Java
Issue Type: Bug
Components: Search
Affects Versio
[
http://issues.apache.org/jira/browse/LUCENE-697?page=comments#action_12444565 ]
Yonik Seeley commented on LUCENE-697:
-
Here's the ant output from test code to be checked in shortly.
The test code calls skipTo(), skipTo(), next(), next(), et
FilteredQuery ignores boost
---
Key: LUCENE-698
URL: http://issues.apache.org/jira/browse/LUCENE-698
Project: Lucene - Java
Issue Type: Bug
Affects Versions: 2.0.0
Reporter: Yonik Seeley
Filtered que
[
http://issues.apache.org/jira/browse/LUCENE-698?page=comments#action_12444570 ]
Yonik Seeley commented on LUCENE-698:
-
I just commited hashCode() and equals() changes to take boost into account so
that
generic tests in QueryUtils.check(que
[ http://issues.apache.org/jira/browse/LUCENE-696?page=all ]
Yonik Seeley resolved LUCENE-696.
-
Fix Version/s: 2.0.1
Resolution: Fixed
Assignee: Yonik Seeley
Patch committed after further tests were added.
> Scorer.skipTo() doesn't alway
[
http://issues.apache.org/jira/browse/LUCENE-697?page=comments#action_12444573 ]
Yonik Seeley commented on LUCENE-697:
-
Comment out line 104 of QueryUtils.java to reproduce this problem:
scoreDiff=0; // TODO: remove this go get LU
33 matches
Mail list logo
