[
https://issues.apache.org/jira/browse/LUCENE-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221819#comment-15221819
]
Robert Muir commented on LUCENE-7152:
-------------------------------------
{quote}
I don't think the current situation is "madness" but you do... okay... yet
isn't it self-imposed? I was always a fan of keeping all our spatial code in
one spatial module. Clearly that's simple for users to grok too.
{quote}
Because putting all stuff (both 99% case and more esoteric stuff) in a module
does not solve the problem. It means as i just mentioned above, things like
expressions have to rely on spatial/ just to do very basic things like make a
bounding box.
This is why i think the 99% basic use case should be in core. It keeps things
from being a rat's nest.
> Refactor lucene-spatial GeoUtils to core
> ----------------------------------------
>
> Key: LUCENE-7152
> URL: https://issues.apache.org/jira/browse/LUCENE-7152
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Nicholas Knize
> Attachments: LUCENE-7152.patch, LUCENE-7152.patch
>
>
> {{GeoUtils}} contains a lot of common spatial mathematics that can be reused
> across multiple packages. As discussed in LUCENE-7150 this issue will
> refactor GeoUtils to a new {{o.a.l.util.geo}} package in core that can be the
> home for other reusable spatial utility classes required by field and query
> implementations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
