[
https://issues.apache.org/jira/browse/LUCENE-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223367#comment-15223367
]
Robert Muir commented on LUCENE-7168:
-------------------------------------
I think (ultimately) we should have Geo3DPoint.java and whatever it uses in its
newXXXQuery() methods is all we need, nothing more :)
Remember we can always choose to expose more advanced functionality at any
time. We can revive things from git and so on. We can try to repackage things
(but we must be careful this doesnt cause more harm than good) to be better.
We can add new methods like the newPathQuery (which seems useful and general)
that are things Geo3D can do that nobody else can do: stuff like this is great.
We can also try to start rounding out an expert API that does more stuff: make
Custom3DPoint or Advanced3DPoint or whatever we want to call it that is even
more expert: e.g. custom planet models/distance metrics/crazy shapes. I just
think we should restrict ourselves to real use-cases there too to keep things
bounded.
I do think we have to err towards simplicity rather than worrying about
experts. But we can still make expert stuff possible.
> Remove geo3d test leniency
> --------------------------
>
> Key: LUCENE-7168
> URL: https://issues.apache.org/jira/browse/LUCENE-7168
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Michael McCandless
>
> Today the test hides possible failures by leniently handling quantization
> issues.
> We should fix it to do what geo2d tests now do: pre-quantized indexed points,
> but don't quantize query shapes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
