lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3892) Add a useful intblock postings format (eg, FOR, PFOR, PFORDelta, Simple9/16/64, etc.)
Date Sat, 02 Jun 2012 14:41:24 GMT


Michael McCandless commented on LUCENE-3892:

bq. Hmm, that means I should remove This testcase works fine for the patch.

Oh it's fine to keep TestMin now that you wrote it ... I was just saying that TestDemo is
the test I run when I want the most trivial test for a new big change.

I'm not quite familiar with these sign stuff, shall I change all the 
 "TODO" sign into "nocommit"? Are the signs related to documentation, 
 or just marked to remember not to commit current codes?

Sorry - this is just a convention I use: I put a // nocommit comment whenever there's a "blocker"
to committing; this way I can grep for nocommit to see what still needs fixing... and towards
the end, nocommits will often be downgraded to TODOs since on closer inspection they really
don't have to block committing...
> Add a useful intblock postings format (eg, FOR, PFOR, PFORDelta, Simple9/16/64, etc.)
> -------------------------------------------------------------------------------------
>                 Key: LUCENE-3892
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>              Labels: gsoc2012, lucene-gsoc-12
>             Fix For: 4.1
>         Attachments: LUCENE-3892_pfor.patch, LUCENE-3892_settings.patch, LUCENE-3892_settings.patch
> On the flex branch we explored a number of possible intblock
> encodings, but for whatever reason never brought them to completion.
> There are still a number of issues opened with patches in different
> states.
> Initial results (based on prototype) were excellent (see
> ).
> I think this would make a good GSoC project.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message