[
https://issues.apache.org/jira/browse/LUCENE-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223355#comment-15223355
]
Karl Wright commented on LUCENE-7168:
-------------------------------------
bq. Right but I think we should try to simplify and reduce to the subset of
logic that lucene needs to index and run its queries. We sorta have to do this,
otherwise everything is completely open-ended ("well someone MIGHT have a use
case") and we can't do APIs that way.
Yes, but it's just another shape. Presumably you would not want to peel all of
the shapes that aren't explicitly used by lucene-core out of the package? I'd
make the case for it on that basis alone.
If the "shape API footprint" is worrying you, we should discuss what shapes you
think people will want to search for and what they won't, and then come up with
a place for the shapes you don't like to live. I'm less willing to judge that
up front, however.
> 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]
