humpf, do we actually need stored fields?

What is wrong with having byte[] DV  that stores all document  fields,  e.g.  
avro or something simpler  to serialise all document fields into one byte[]?

I am definitely missing something about DV/Stored fields diff,  not sure what?



On Mar 6, 2013, at 8:18 PM, "Andrzej Bialecki  (JIRA)" <[email protected]> wrote:

> 
>    [ 
> https://issues.apache.org/jira/browse/LUCENE-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594997#comment-13594997
>  ] 
> 
> Andrzej Bialecki  commented on LUCENE-3918:
> -------------------------------------------
> 
> bq. I still don't get why someone would use stored fields rather than doc 
> values (either binary, sorted or numeric) to sort his index. I think it's 
> important to make users understand that stored fields are only useful to 
> display results?
> 
> This is a legacy of the original usage of this tool in Nutch - indexes would 
> use a PageRank value as a document boost, and that was the value to be used 
> for sorting - but since the doc boost is not recoverable from an existing 
> index the value itself was stored in a stored field.
> 
> And definitely DV didn't exist yet at that time :)
> 
>> Port index sorter to trunk APIs
>> -------------------------------
>> 
>>                Key: LUCENE-3918
>>                URL: https://issues.apache.org/jira/browse/LUCENE-3918
>>            Project: Lucene - Core
>>         Issue Type: Task
>>         Components: modules/other
>>   Affects Versions: 4.0-ALPHA
>>           Reporter: Robert Muir
>>            Fix For: 4.2, 5.0
>> 
>>        Attachments: LUCENE-3918.patch, LUCENE-3918.patch, LUCENE-3918.patch, 
>> LUCENE-3918.patch, LUCENE-3918.patch, LUCENE-3918.patch, LUCENE-3918.patch, 
>> LUCENE-3918.patch, LUCENE-3918.patch, LUCENE-3918.patch, LUCENE-3918.patch, 
>> LUCENE-3918.patch, LUCENE-3918.patch
>> 
>> 
>> LUCENE-2482 added an IndexSorter to 3.x, but we need to port this
>> functionality to 4.0 apis.
> 
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators
> 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]
> 


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

Reply via email to