[jira] [Commented] (LUCENE-7664) Deprecate GeoPointField & queries
[
https://issues.apache.org/jira/browse/LUCENE-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854758#comment-15854758
]
ASF subversion and git services commented on LUCENE-7664:
-
Commit 3e730f9bd2124ac72fe03c56793477e6c0902c3d in lucene-solr's branch
refs/heads/master from Mike McCandless
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=3e730f9b ]
LUCENE-7664: remove GeoPointField and its queries
> Deprecate GeoPointField & queries
> -
>
> Key: LUCENE-7664
> URL: https://issues.apache.org/jira/browse/LUCENE-7664
> Project: Lucene - Core
> Issue Type: Improvement
>Reporter: Michael McCandless
>Assignee: Michael McCandless
> Fix For: master (7.0), 6.5.0
>
> Attachments: LUCENE-7664.patch
>
>
> The new dimensional points implementations for geo distance, polygon, shape
> filtering are substantially faster and creates a smaller index than the
> postings based {{GeoPointField}}. They also offer nearest neighbor search,
> which {{GeoPointField}} doesn't.
> I think we should deprecate {{GeoPointField}} and focus on the points
> implementations.
> We have still other legacy postings based geo implementations but I think we
> should keep them for now since they have functionality that points doesn't
> yet have: the ability to index a shape and search for shapes overlapping the
> indexed shapes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7664) Deprecate GeoPointField & queries
[
https://issues.apache.org/jira/browse/LUCENE-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854713#comment-15854713
]
ASF subversion and git services commented on LUCENE-7664:
-
Commit d1135b4d29039628cc3097e4cb1b0e09216b1814 in lucene-solr's branch
refs/heads/branch_6x from Mike McCandless
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d1135b4 ]
LUCENE-7664: deprecate GeoPointField and its queries
> Deprecate GeoPointField & queries
> -
>
> Key: LUCENE-7664
> URL: https://issues.apache.org/jira/browse/LUCENE-7664
> Project: Lucene - Core
> Issue Type: Improvement
>Reporter: Michael McCandless
>Assignee: Michael McCandless
> Fix For: master (7.0), 6.5.0
>
> Attachments: LUCENE-7664.patch
>
>
> The new dimensional points implementations for geo distance, polygon, shape
> filtering are substantially faster and creates a smaller index than the
> postings based {{GeoPointField}}. They also offer nearest neighbor search,
> which {{GeoPointField}} doesn't.
> I think we should deprecate {{GeoPointField}} and focus on the points
> implementations.
> We have still other legacy postings based geo implementations but I think we
> should keep them for now since they have functionality that points doesn't
> yet have: the ability to index a shape and search for shapes overlapping the
> indexed shapes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7664) Deprecate GeoPointField & queries
[
https://issues.apache.org/jira/browse/LUCENE-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843885#comment-15843885
]
David Smiley commented on LUCENE-7664:
--
+1I believe GeoPointField also never quite got distance sorting added. I
could sense development halted once LatLonPoint started showing it was going to
win out.
Hey [~nknize] the GeoPointField was really excellent work -- the ideal geo
field that was based on an inverted index. Maybe someone out there would find
it useful who either has an old Lucene index or who wishes to port to something
else like LevelDB.
> Deprecate GeoPointField & queries
> -
>
> Key: LUCENE-7664
> URL: https://issues.apache.org/jira/browse/LUCENE-7664
> Project: Lucene - Core
> Issue Type: Improvement
>Reporter: Michael McCandless
>Assignee: Michael McCandless
> Fix For: master (7.0), 6.5.0
>
>
> The new dimensional points implementations for geo distance, polygon, shape
> filtering are substantially faster and creates a smaller index than the
> postings based {{GeoPointField}}. They also offer nearest neighbor search,
> which {{GeoPointField}} doesn't.
> I think we should deprecate {{GeoPointField}} and focus on the points
> implementations.
> We have still other legacy postings based geo implementations but I think we
> should keep them for now since they have functionality that points doesn't
> yet have: the ability to index a shape and search for shapes overlapping the
> indexed shapes.
--
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
