[
https://issues.apache.org/jira/browse/LUCENE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223268#comment-15223268
]
Karl Wright commented on LUCENE-7167:
-------------------------------------
bq. So if its gonna do that, why does it do this ridiculous garbage to try to
"correct" for quantization. If we truncate someone's data at index time this
cannot be undone. It cannot be corrected for. So making this complex
XYZSolidFactory that, produces one of 8 possible XYZ's (which are all public
too!!!! why have a factory!!!!!!!), this is so complex to try to "correct" for
damage we have already done.
I honestly don't know what the heck you are talking about here.
Would you care to present a case that you think isn't going to work? I
challenge that it is broken in any way; it's been beasted practically to death.
And you clearly don't understand at all how Geo3D works, so maybe you and I
ought to talk a bit before you conclude stuff like this.
> Re-engineer or remove all of geo3D
> ----------------------------------
>
> Key: LUCENE-7167
> URL: https://issues.apache.org/jira/browse/LUCENE-7167
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Karl Wright
>
> Geo3D has led to a lot of consternation because it has a relatively open API.
> The task is to either drastically restrict it or remove the package entirely.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
