Re: Lucene 1.9 release date?

How about setting some preliminary due dates, so that things don't just hang there. ray, On 10/15/05, Otis Gospodnetic <[EMAIL PROTECTED]> wrote: > Re Votes - yes, please use that feature to help prioritize. > > Otis > > --- Ray Tsang <[EMAIL PROTECTED]> wrote: > > > Ah I see it. Should we start

Fwd: skipInterval

Hi, All, I should have sent to this email address rather than the old jakarta email address. Sorry if double-posted. Jian -- Forwarded message -- From: jian chen <[EMAIL PROTECTED]> Date: Oct 15, 2005 6:36 PM Subject: skipInterval To: Lucene Developers List Hi, All, I was read

skipInterval

Hi, All, I was reading some research papers regarding quick inverted index lookups. The classical approach to skipping dictates that a skip should be positioned every sqrt(df) document pointers. I looked at the the current Lucene implementation. The skipInterval is hardcoded as follows in TermInf

[jira] Commented: (LUCENE-328) Some utilities for a compact sparse filter

[ http://issues.apache.org/jira/browse/LUCENE-328?page=comments#action_12332156 ] Yonik Seeley commented on LUCENE-328: - I've been working a little on a faster version of BitSet. That's one place where a stateful iterator implementing nextDocNr() can b

[jira] Commented: (LUCENE-328) Some utilities for a compact sparse filter

[ http://issues.apache.org/jira/browse/LUCENE-328?page=comments#action_12332155 ] paul.elschot commented on LUCENE-328: - About adding a nextDocNr() without current doc argument to DocNrSkipper: I considered that but left it out initially for code simplic

Re: Lucene 1.9 release date?

Re Votes - yes, please use that feature to help prioritize. Otis --- Ray Tsang <[EMAIL PROTECTED]> wrote: > Ah I see it. Should we start assigning and voting for issues that > should make it into the 1.9 release? Maybe set a due date for > submitting these 1.9-bound issues, a week for voting a

[jira] Commented: (LUCENE-440) FilteredQuery should have getFilter()

[ http://issues.apache.org/jira/browse/LUCENE-440?page=comments#action_12332154 ] paul.elschot commented on LUCENE-440: - See also LUCENE-330 > FilteredQuery should have getFilter() > - > > Key: LUCENE-440 >

[jira] Closed: (LUCENE-422) Performance improvement in search

[ http://issues.apache.org/jira/browse/LUCENE-422?page=all ] paul.elschot closed LUCENE-422: --- Resolution: Duplicate Assign To: (was: Lucene Developers) > Performance improvement in search > - > > Key:

[jira] Commented: (LUCENE-422) Performance improvement in search

[ http://issues.apache.org/jira/browse/LUCENE-422?page=comments#action_12332153 ] paul.elschot commented on LUCENE-422: - The suggested improvement is part of the FilteredQuery In LUCENE-330, so I'll close this. See: http://issues.apache.org/jira/browse/L

[jira] Commented: (LUCENE-370) BooleanQuery assumes everything else implements skipTo

[ http://issues.apache.org/jira/browse/LUCENE-370?page=comments#action_12332149 ] paul.elschot commented on LUCENE-370: - I think all scorers in the trunk implement skipTo() now, so this can be closed. Regards, Paul Elschot > BooleanQuery assumes everyt