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

Alan Woodward updated LUCENE-4883:
----------------------------------

    Attachment: LUCENE-4883.patch

OK, here's a patch that attempts to solve the problem of 32-bit vs 64-bit 
numeric values.  I don't really like it, but it seems to work, so it's a start. 
 Users of UninvertedFilterReader have to specify up-front the width of numeric 
fields they wish to uninvert.

This is hacky for any number of reasons, not the least of which is I have to 
define a whole new set of DocValuesTypes on Uninverter, which is a lot less 
elegant than just using the existing FieldInfo ones.  There doesn't seem to be 
a good way of detecting this at uninvert-time from the FieldInfo data, though.  
We could assume 64-bit values and fall back to 32-bit if we encounter an 
exception, but I worry that we're getting a performance hit here for every 
32-bit field.
                
> Hide FieldCache behind an UninvertingFilterReader
> -------------------------------------------------
>
>                 Key: LUCENE-4883
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4883
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Alan Woodward
>            Assignee: Alan Woodward
>            Priority: Minor
>         Attachments: LUCENE-4883.patch, LUCENE-4883.patch, LUCENE-4883.patch, 
> LUCENE-4883.patch
>
>
> From a discussion on the mailing list:
> {{
> rmuir:
> I think instead FieldCache should actually be completely package
> private and hidden behind a UninvertingFilterReader and accessible via
> the existing AtomicReader docValues methods.
> }}

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