[ 
https://issues.apache.org/jira/browse/LUCENE-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Muir resolved LUCENE-3629.
---------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 4.3)
                   4.2
    
> Hide storage details for IndexDocValues inside the codec
> --------------------------------------------------------
>
>                 Key: LUCENE-3629
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3629
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/index
>    Affects Versions: 4.0-ALPHA
>            Reporter: Simon Willnauer
>             Fix For: 4.2
>
>
> Currently ValueType exposes a lot of impl. details about how values are 
> stored. However, since those are really impl details we should move those 
> into the codec and decide during indexing which storage variant we are using. 
> (robert convinced me this is the right thing and we should explore it)
> We can basically reduce the ValuesType to { Bytes, SortedBytes, FixedInts, 
> Floats, VarInts }. The implementation ie. the codec can decide based on how 
> many unique values and if values have all the same size what storage variant 
> it should use. For merging we would need some statistics exposed on the 
> Source ie. how many unique values and if all value have a fixed size to 
> decide what the target "type" is going to be. 
> This change would make usage of the API a lot easier and less confusing and 
> at the same time it makes merging and type promotion straight forward since 
> we can decide what type we promote to without loading the IDV provider to get 
> the actual size and compare it. 

--
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]

Reply via email to