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

Robert Muir commented on LUCENE-3433:
-------------------------------------

Here is the way i see the problem:
* Currently docvalues is a bit confusing... I think a lot of this is due to the 
current API
* no offense to simon but i think in a way this forces him to feel responsible 
for doing all work on it. The complexity makes it hard for others to get 
involved.
* with this patch, the api becomes a lot simpler: i'm sure its not perfect but 
the API seems to correspond to what DV does, at least it makes sense to me.

can we temporarily drop SortedSource, open a new issue to add it back (mark it 
blocker for 4.0 even?!). This way, we can rethink how to implement this 
functionality (maybe it doesnt even belong as docvalues but something on top of 
it, or something else entirely).

                
> Random access non RAM resident IndexDocValues (CSF)
> ---------------------------------------------------
>
>                 Key: LUCENE-3433
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3433
>             Project: Lucene - Java
>          Issue Type: New Feature
>    Affects Versions: 4.0
>            Reporter: Yonik Seeley
>            Assignee: Simon Willnauer
>             Fix For: 4.0
>
>         Attachments: LUCENE-3433.patch, LUCENE-3433.patch, LUCENE-3433.patch, 
> sorted_source.patch
>
>
> There should be a way to get specific IndexDocValues by going through the 
> Directory rather than loading all of the values into memory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Reply via email to