[
https://issues.apache.org/jira/browse/LUCENE-7094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210194#comment-15210194
]
David Smiley commented on LUCENE-7094:
--------------------------------------
BTW even if UninvertingReader doesn't work when the field names are the same, I
think that's fine. Whoever may be using UninvertingReader should have enabled
docValues. Perhaps it's a requirement, not just a suggestion, based on your
observations; I'd like to see for myself but either way I think you should
remove the addition of a field suffix to your patch. That will limit the
changes in the patch a bit too.
I slept on this a bit and I think we'll need a better way for BBoxStrategy
users to articulate what index options they want; it's now insufficient /
ambiguous to provide a FieldType:
* terms index (legacy)
* pointValues index?
* docValues?
* stored?
* type: double or float? (needed for pointValues & docValues)
By default we can have pointValues, docValues, type double, not stored.
Perhaps a little inner builderclass would work well. For legacy purposes, we
could support the fieldType but it's either-or with the builder. It may take a
bit of time to make double vs float configurable so that could be a follow-on
issue. As it was, it was a TODO.
> spatial-extras BBoxStrategy and (confusingly!) PointVectorStrategy use legacy
> numeric encoding
> ----------------------------------------------------------------------------------------------
>
> Key: LUCENE-7094
> URL: https://issues.apache.org/jira/browse/LUCENE-7094
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Assignee: Nicholas Knize
> Attachments: LUCENE-7094.patch
>
>
> We need to deprecate these since they work on the old encoding and provide
> points based alternatives.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
