[ 
https://issues.apache.org/jira/browse/LUCENE-5524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065699#comment-14065699
 ] 

ASF GitHub Bot commented on LUCENE-5524:
----------------------------------------

GitHub user PaulElschot opened a pull request:

    https://github.com/apache/lucene-solr/pull/62

    efbytesref of 20140717, move Elias-Fano code to eliasfano package

    efbytesref as of 20140717
    
    LUCENE-5524
    
    This closes #60
    
    Update to recent trunk, and move all Elias-Fano classes into a separate 
package o.a.l.util.packed.eliasfano. The existing EliasFano* classes are 
restored to trunk, the packed.eliasfano package can be merged back into  the 
packed package later.
    Otherwise no changes to pull request 60.
    
    The idea is to prepare a port to 4.9.0 and/or to prepare compilation into a 
separate jar.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/PaulElschot/lucene-solr efbytesref-201407a

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/lucene-solr/pull/62.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #62
    
----
commit 51a76c7789f38c2644f4019552a41c8199884557
Author: Paul Elschot <[email protected]>
Date:   2014-07-17T19:59:29Z

    efbytesref of 20140717, move Elias-Fano code to eliasfano package

----


> Elias-Fano sequence also on BytesRef
> ------------------------------------
>
>                 Key: LUCENE-5524
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5524
>             Project: Lucene - Core
>          Issue Type: New Feature
>          Components: core/other
>            Reporter: Paul Elschot
>            Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to