[
https://issues.apache.org/jira/browse/LUCENE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723473#action_12723473
]
Uwe Schindler commented on LUCENE-1693:
---
{quote}
bq. The big difference is, that you
I've been following this list for the last month and last week I
checked out the source code to create a patch for Lucene-1260. I had
to do some investigating of build-files before I found how to build
the whole project and run the tests, but eventually I found the right
way.
In the last week ther
But TimeLimitingCollector's logic is coded in its collect() method. The top
scorer calls nextDoc() or advance() on all its sub-scorers, and only when a
match is found it calls collect().
If we want the sub-scorers to check whether they should abort, we'd need to
revamp (liked the word :)) TimeLimi
[
https://issues.apache.org/jira/browse/LUCENE-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723500#action_12723500
]
Michael McCandless commented on LUCENE-1466:
bq. an additional test for CharFi
Re: "I think such a parameter should not exist on individual search methods
since it's more of a global setting (i.e., I want my searches to be
limited to 5 seconds, always, not just for a particular query). Right?"
I am not sure about this one, we had cases where one phisical index served two
lo
Could you re-ask this on java-user? This list discusses changes to
Lucene's source code. Thanks!
Mike
On Tue, Jun 23, 2009 at 6:13 PM, mitu2009 wrote:
>
> Hi,
>
> I've a batch job which generates Lucene search indexes every night. I first
> get all the records from the database and add it to Luc
Having scorers check timeouts while advancing will definetly increase
the frequency of said timeouts.
On Wed, Jun 24, 2009 at 13:13, eks dev wrote:
> Re: "I think such a parameter should not exist on individual search methods
> since it's more of a global setting (i.e., I want my searches to be li
[
https://issues.apache.org/jira/browse/LUCENE-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1652.
Resolution: Invalid
The ideas in this issue were largely fixed under other issues.
[
https://issues.apache.org/jira/browse/LUCENE-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723511#action_12723511
]
Michael McCandless commented on LUCENE-1652:
I think TopScorer is the only pos
OK I agree we should remove the way-old files leftover from our
cutover to all/core/contrib subdir switch back in December.
And it does seem simplest to just move the current javadoc dir out of
the way and let the next build repopulate.
So I just did that.
Mike
On Mon, Jun 22, 2009 at 6:23 AM,
[
https://issues.apache.org/jira/browse/LUCENE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723527#action_12723527
]
Uwe Schindler commented on LUCENE-1713:
---
OK, so:
* RangeFilter -> TermRangeFilter
[
https://issues.apache.org/jira/browse/LUCENE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723064#action_12723064
]
Uwe Schindler edited comment on LUCENE-1713 at 6/24/09 3:43 AM:
[
https://issues.apache.org/jira/browse/LUCENE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1713:
--
Comment: was deleted
(was: OK, so:
* RangeFilter -> TermRangeFilter
* RangeQuery -> TermR
Fine, have seen this.
Maybe we should add an index.html to the main javadocs folder on Hudson or
directly into trunk (list of doc modules) to prevent 404 when clicking on
the javadocs link.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
>
[
https://issues.apache.org/jira/browse/LUCENE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723536#action_12723536
]
Mark Miller commented on LUCENE-1693:
-
Ah, okay. Sounds like some magic you have worke
OK wanna work one out and I'll install?
Mike
On Wed, Jun 24, 2009 at 6:47 AM, Uwe Schindler wrote:
> Fine, have seen this.
>
> Maybe we should add an index.html to the main javadocs folder on Hudson or
> directly into trunk (list of doc modules) to prevent 404 when clicking on
> the javadocs link
[
https://issues.apache.org/jira/browse/LUCENE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1693:
--
Attachment: LUCENE-1693.patch
Hi Michael,
this was a small bug in the translation next(Token)
[
https://issues.apache.org/jira/browse/LUCENE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723549#action_12723549
]
Uwe Schindler commented on LUCENE-1693:
---
bq. But I'll definitely buy Uwe a beer if h
How about this solution (patch for trunk)? It advises ant to build the
index.html file after the global javadocs-target. The index file produced
should be automatically copied by Hudson.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
>
Slightly extended patch, the spezial bdb contrib is now also supported...
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Uwe Schindler [mailto:u...@thetaphi.de]
> Sent: Wednesday, June 24, 2009 3:24 PM
>
[
https://issues.apache.org/jira/browse/LUCENE-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-1707:
---
Attachment: LUCENE-1707.patch
Patch includes:
# remove all calls to ensureOpen in IndexReader and de
+1
I applied it, ran "ant javadocs", and it set up the index.html
correctly. I say commit it!
Mike
On Wed, Jun 24, 2009 at 9:40 AM, Uwe Schindler wrote:
> Slightly extended patch, the spezial bdb contrib is now also supported...
>
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
>
Our biggest bottleneck in searching is in a custom scorer which calls
AllTermDocs.next() very frequently. This class uses Lucene's own BitVector,
which I think is already highly optimized. Farther down in the list are
DocSetHitCollector.collect() and FieldSortedQueue.insert(). For indexing,
the mai
I just want to point out that I don't consider these bottlenecks to be an
issue. This is exactly where I'd expect to see hotspots from the profiler,
and the overall performance of Lucene search is still stunning.
Peter
On Wed, Jun 24, 2009 at 10:13 AM, Peter Keegan wrote:
> Our biggest bottlen
Done. Thanks for testing!
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Michael McCandless [mailto:luc...@mikemccandless.com]
> Sent: Wednesday, June 24, 2009 4:13 PM
> To: java-dev@lucene.apache.org
>
[
https://issues.apache.org/jira/browse/LUCENE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723587#action_12723587
]
Mark Miller commented on LUCENE-1583:
-
I'm going to commit this soon.
> SpanOrQuery s
[
https://issues.apache.org/jira/browse/LUCENE-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723589#action_12723589
]
Mark Miller commented on LUCENE-1650:
-
Im going to commit this soon, both changes.
>
[
https://issues.apache.org/jira/browse/LUCENE-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723591#action_12723591
]
Mark Miller commented on LUCENE-1448:
-
Will you have time for this Michael?
It would
[
https://issues.apache.org/jira/browse/LUCENE-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-1707:
---
Component/s: Index
Fix Version/s: 2.9
Lucene Fields: [New, Patch Available] (was: [New])
[
https://issues.apache.org/jira/browse/LUCENE-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated LUCENE-1706:
Attachment: LUCENE-1706.patch
The Lucene site is in two parts, one for a specific version
Good point! Queries that timeout can be lengthy nested boolean queries so
perhaps there's some other approach besides checking for each hit and
minimize CPU usage?
On Wed, Jun 24, 2009 at 2:25 AM, Earwin Burrfoot wrote:
> Having scorers check timeouts while advancing will definetly increase
> t
[
https://issues.apache.org/jira/browse/LUCENE-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723670#action_12723670
]
Simon Willnauer commented on LUCENE-1566:
-
I will look into this issue closer next
[
https://issues.apache.org/jira/browse/LUCENE-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer reassigned LUCENE-1566:
---
Assignee: Simon Willnauer
> Large Lucene index can hit false OOM due to Sun JRE issu
[
https://issues.apache.org/jira/browse/LUCENE-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1461:
--
Attachment: LUCENE-1461.patch
Here is an first version of retrofitted FieldCacheRangeFilter. I
[
https://issues.apache.org/jira/browse/LUCENE-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-1688:
Attachment: LUCENE-1688.patch
To trunk. Still needs a bit of a look over.
> Deprecating StopAnaly
[
https://issues.apache.org/jira/browse/LUCENE-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723680#action_12723680
]
Michael McCandless commented on LUCENE-1566:
Excellent, thanks Simon!
> Large
[
https://issues.apache.org/jira/browse/LUCENE-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723682#action_12723682
]
Mark Miller commented on LUCENE-1688:
-
all tests pass
> Deprecating StopAnalyzer ENGL
[
https://issues.apache.org/jira/browse/LUCENE-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-1599:
Attachment: LUCENE-1599.patch
Test + Fix (properly implement clone on near,or,not span queries)
>
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723699#action_12723699
]
Mark Miller commented on LUCENE-1486:
-
Hey Mark, this doesn't work correctly with the
[
https://issues.apache.org/jira/browse/LUCENE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723720#action_12723720
]
Michael Busch commented on LUCENE-1693:
---
Sorry, I don't want to be the bad guy here,
[
https://issues.apache.org/jira/browse/LUCENE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723727#action_12723727
]
Uwe Schindler commented on LUCENE-1693:
---
In your example, you mean SinkTokenizer is
[
https://issues.apache.org/jira/browse/LUCENE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723727#action_12723727
]
Uwe Schindler edited comment on LUCENE-1693 at 6/24/09 1:46 PM:
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Harwood updated LUCENE-1486:
-
Attachment: LUCENE-1486.patch
Added fix for ConstantScoreQuery changes
> Wildcards, ORs etc ins
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723742#action_12723742
]
Mark Harwood commented on LUCENE-1486:
--
The fix was relatively straight-forward from
[
https://issues.apache.org/jira/browse/LUCENE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch updated LUCENE-1693:
--
Attachment: TestCompatibility.java
Not sure if we're talking about the same thing here. The pr
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723747#action_12723747
]
Mark Miller commented on LUCENE-1486:
-
Figured thats all it would take. I just was fee
[
https://issues.apache.org/jira/browse/LUCENE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723749#action_12723749
]
Uwe Schindler commented on LUCENE-1693:
---
bq. Not sure if we're talking about the sam
[
https://issues.apache.org/jira/browse/LUCENE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723751#action_12723751
]
Uwe Schindler commented on LUCENE-1693:
---
One solution around this poblem would be to
[
https://issues.apache.org/jira/browse/LUCENE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723759#action_12723759
]
Michael Busch edited comment on LUCENE-1693 at 6/24/09 2:50 PM:
[
https://issues.apache.org/jira/browse/LUCENE-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723759#action_12723759
]
Michael Busch commented on LUCENE-1693:
---
{quote}
I decided a while ago that you'll d
[
https://issues.apache.org/jira/browse/LUCENE-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723764#action_12723764
]
Michael Busch commented on LUCENE-1448:
---
Oh man, what did I do suggesting you as the
I think the Collector approach makes the most sense to me, since
it's the only object I fully control in the search process. I cannot
control Query implementations, and I cannot control the decisions
made by IndexSearcher. But I can always wrap someone else's
Collector with TLC and pass it
This would be good however how would we obtain the thread? I
believe this would require using a ThreadLocalish type of system
which could be quite slow (to obtain the thread and lookup in
the hashmap).
One implementation I looked at before was to add this check in
IndexReader.isDeleted (by overrid
[
https://issues.apache.org/jira/browse/LUCENE-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723782#action_12723782
]
Michael McCandless commented on LUCENE-1707:
I'd actually rather not remove th
[
https://issues.apache.org/jira/browse/LUCENE-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723784#action_12723784
]
Michael McCandless commented on LUCENE-1677:
OK, since they are broken already
[
https://issues.apache.org/jira/browse/LUCENE-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reopened LUCENE-1677:
> Remove GCJ IndexReader specializations
> --
>
>
[
https://issues.apache.org/jira/browse/LUCENE-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723785#action_12723785
]
Michael McCandless commented on LUCENE-1677:
I'll remove src/gcj in a day or t
[
https://issues.apache.org/jira/browse/LUCENE-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723810#action_12723810
]
Jason Rutherglen commented on LUCENE-1709:
--
Given my limited understanding of ANT
[
https://issues.apache.org/jira/browse/LUCENE-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723815#action_12723815
]
Jason Rutherglen commented on LUCENE-1709:
--
So am thinking we'd create a Parallel
[
https://issues.apache.org/jira/browse/LUCENE-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1461:
--
Attachment: LUCENE-1461.patch
Patch that implements all FieldCache data types. The Double/Floa
(Please remain calm, this is just a request for clarification/summation)
As I slowly catch up on the 9000+ Lucene related emails that I accumulated
during my 2 month hiatus, I notice several rather large threads (i think
totally ~400 messages) on the subject of our back compat policy (where
i
: Done. Thanks for testing!
I hate to be a buzz kill, but all this really does is replace the outdated
javadoc generated index.html file with a new one that points at the
subdirs we've created ... I don't see how this solves the root problem:
Hudson doesn't delete the old files
https://h
[
https://issues.apache.org/jira/browse/LUCENE-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723850#action_12723850
]
Hoss Man commented on LUCENE-1709:
--
if you're looking to extend ant it might be better to
[
https://issues.apache.org/jira/browse/LUCENE-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723867#action_12723867
]
Jason Rutherglen commented on LUCENE-1709:
--
Thanks for the links!
> Parallelize
Hey Hoss,
Almost everyone agreed to the backwards-compatibility changes I posted
here: JIRA-1698. (It turned out that Shai had proposed an almost
identical proposal in one of the long threads that I admittedly didn't
fully read either).
I suggested to send a note to java-user to get some fee
Me, too. I noticed Grant mentioned this in one of the long emails/threads,
too, a few weeks back, but I didn't want to pull out just that piece and
disturb the thread. And I bet people outside Lucene would love to have
search-independent set of chainable tokenizers, token filters, and such.
> : Done. Thanks for testing!
>
> I hate to be a buzz kill, but all this really does is replace the outdated
> javadoc generated index.html file with a new one that points at the
> subdirs we've created ... I don't see how this solves the root problem:
> Hudson doesn't delete the old files
>
67 matches
Mail list logo
