[
https://issues.apache.org/jira/browse/LUCENE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487706
]
Paul Elschot commented on LUCENE-584:
-
That could be improved in a DisjunctionMatcher.
With a bit of bookkeeping
I have been hoping to put up mechanism for (easier) deployment of m2
artifacts to maven repositories (both Apache snapshot repository and the
main maven repository at ibiblio).
The most convenient way would be to use maven2 to build the various lucene
projects but as the mailing list
[
https://issues.apache.org/jira/browse/LUCENE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487789
]
Otis Gospodnetic commented on LUCENE-584:
-
Ah, too bad. :(
Last time I benchmarked Lucene searching on Sun's
If I remember well, the last time we profiled search with high density OR
queries scoring was taking up to 30% of the time. This was a 8Mio collection
of short documents fitting comfortably in RAM. So I am sure disabling scoring
in some cases could bring us something.
I am not all that
See http://lucene.zones.apache.org:8080/hudson/job/Lucene-Nightly/53/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/LUCENE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487847
]
Sean O'Connor commented on LUCENE-794:
--
I was able to apply the spanhighlighter5.patch. I'm inexperienced with
[
https://issues.apache.org/jira/browse/LUCENE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Ericson updated LUCENE-855:
Attachment: TestRangeFilterPerformanceComparison.java
Andy thank you for that test
I took at
[
https://issues.apache.org/jira/browse/LUCENE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Ericson updated LUCENE-855:
Attachment: FieldCacheRangeFilter.patch
Fixed a bug with the BitSets nextSetBit(i) and
[
https://issues.apache.org/jira/browse/LUCENE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487860
]
Mark Miller commented on LUCENE-794:
Sorry Sean, I forgot to mention that the patch is off of the latest
Lucene
On 4/10/07, Marvin Humphrey [EMAIL PROTECTED] wrote:
In DisjunctionSumScorer, both skipTo() and next() invoke
initScorerDocQueue() on the first iteration. However, since all
subscorers are added en masse via the constructor instead of
individually via an add() method which does not exist for
[
https://issues.apache.org/jira/browse/LUCENE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487882
]
Paul Elschot commented on LUCENE-584:
-
By fastest cache I meant the L1 cache of the processor. The size is
On Tuesday 10 April 2007 17:41, eks dev wrote:
If I remember well, the last time we profiled search with high density OR
queries scoring was taking up to 30% of the time. This was a 8Mio collection
of short documents fitting comfortably in RAM. So I am sure disabling scoring
in some cases
On Tuesday 10 April 2007 20:24, Yonik Seeley wrote:
On 4/10/07, Marvin Humphrey [EMAIL PROTECTED] wrote:
In DisjunctionSumScorer, both skipTo() and next() invoke
initScorerDocQueue() on the first iteration. However, since all
subscorers are added en masse via the constructor instead of
: I thought it would avoid accessing the index as much as
: possible before actually doing a search, but I did not
: verify whether that is important.
: In case it is not, any simplification is off course welcome.
conceptually: once Query.createWeight(Searcher) is called, the Search
has already
[
https://issues.apache.org/jira/browse/LUCENE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487897
]
Andy Liu commented on LUCENE-855:
-
Hey Matt, I get this exception when running your newest FCRF with the
site should call project Lucene Java, not just Lucene
-
Key: LUCENE-860
URL: https://issues.apache.org/jira/browse/LUCENE-860
Project: Lucene - Java
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/LUCENE-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated LUCENE-860:
Attachment: LUCENE-860.patch
Here's a patch that replaces Apache Lucene with Apache Lucene Java in
[
https://issues.apache.org/jira/browse/LUCENE-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated LUCENE-860:
Lucene Fields: [Patch Available] (was: [New])
site should call project Lucene Java, not just
Just saw this test fail:
[junit] Testcase:
testExpirationTimeDeletionPolicy(org.apache.lucene.index.TestDeletionPolicy):
FAILED
[junit] commit point was older than 2.0 seconds but did not get deleted
[junit] junit.framework.AssertionFailedError: commit point was older than
2.0
[
https://issues.apache.org/jira/browse/LUCENE-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic resolved LUCENE-857.
-
Resolution: Fixed
Thanks for the persistence and patience, Hoss. I see the light now!
[
https://issues.apache.org/jira/browse/LUCENE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Ericson updated LUCENE-855:
Attachment: FieldCacheRangeFilter.patch
Lets try this again.
I am very sorry to everyone for the
Otis Gospodnetic [EMAIL PROTECTED] wrote:
Just saw this test fail:
[junit] Testcase:
testExpirationTimeDeletionPolicy(org.apache.lucene.index.TestDeletionPolicy):
FAILED
[junit] commit point was older than 2.0 seconds but did not get
deleted
[junit]
[
https://issues.apache.org/jira/browse/LUCENE-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic updated LUCENE-730:
Lucene Fields: [New, Patch Available] (was: [New])
Restore top level disjunction
[
https://issues.apache.org/jira/browse/LUCENE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487940
]
Hoss Man commented on LUCENE-584:
-
I'm a little behind on following this issue, but if i can attempt to sum up the
[
https://issues.apache.org/jira/browse/LUCENE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487962
]
Hoss Man commented on LUCENE-855:
-
On Mon, 9 Apr 2007, Otis Gospodnetic (JIRA) wrote:
: I'd love to know what Hoss
I was motivated to start this thread by LUCENE-860, but it's been in the
back of my mind for a while.
As the Lucene Top Level Project grows and get's more Sub-Projects, I
(personally) have been finding it hard in email/documentation/discussion
to clarify when people are refering to the Lucene
[
https://issues.apache.org/jira/browse/LUCENE-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man reopened LUCENE-857:
-
Lucene Fields: [New, Patch Available] (was: [New])
Actually Otis: for the backwards compatibility to
No, you are not the only one... Many a sleepless night spent on
it... :-)
I usually try to refer to it as Lucene Java, but old habits die hard
and often times I just call it Lucene. I think the name has a good
brand at this point and is very strongly associated w/ the Java
library. I
[
https://issues.apache.org/jira/browse/LUCENE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487966
]
Otis Gospodnetic commented on LUCENE-584:
-
Right. I was under the wrong impression that the Matcher also
[
https://issues.apache.org/jira/browse/LUCENE-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic resolved LUCENE-857.
-
Resolution: Fixed
Lucene Fields: [New, Patch Available] (was: [Patch Available,
[
https://issues.apache.org/jira/browse/LUCENE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487981
]
Sean O'Connor commented on LUCENE-794:
--
Thanks Mark. I had the trunk from a few days ago (perhaps a week), so
31 matches
Mail list logo