lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grant Ingersoll (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-1586) Create Spatial Point FieldTypes
Date Tue, 29 Dec 2009 15:38:29 GMT

    [ https://issues.apache.org/jira/browse/SOLR-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795070#action_12795070
] 

Grant Ingersoll commented on SOLR-1586:
---------------------------------------

bq. Unlike PointType, it seems odd that a user would need to understand and declare any kind
of subFieldTyp/Suffiix for SpatialTileField... seems like this one we really want to be an
implementation detail somehow..

I suppose they could just always be a DoubleField subtype, but how do you guarantee it is
registered in the schema?  I suppose it is 99.99% likely it will be there, so we could just
assume it.  I can change it to do this.

bq. and ultimately it seems like we want to allow the SpacialTileFIeld to be an implementation
detail as well. It would be nice to just define a SpacialTilePoint and just use it for everything
(filtering, distance calculations, etc).

I'm not sure I see how to use a tile for anything other than filtering (is the point in the
box or not).  I suppose it could be used for vary crude distance calculations, but that doesn't
seem all that useful.  I think there may be too much of a goal to hide all the details from
the application.  The choice of the data structure is going to depend on the application,
just as one chooses to use int, float or double depending on their application needs.  Many
applications will do just fine using PointType with a double, even for range queries.  Others
may specifically want a tile approach as it best solves their problem.

> Create Spatial Point FieldTypes
> -------------------------------
>
>                 Key: SOLR-1586
>                 URL: https://issues.apache.org/jira/browse/SOLR-1586
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Grant Ingersoll
>            Assignee: Grant Ingersoll
>            Priority: Minor
>             Fix For: 1.5
>
>         Attachments: examplegeopointdoc.patch.txt, SOLR-1586-geohash.patch, SOLR-1586.Mattmann.112209.geopointonly.patch.txt,
SOLR-1586.Mattmann.112209.geopointonly.patch.txt, SOLR-1586.Mattmann.112409.geopointandgeohash.patch.txt,
SOLR-1586.Mattmann.112409.geopointandgeohash.patch.txt, SOLR-1586.Mattmann.112509.geopointandgeohash.patch.txt,
SOLR-1586.Mattmann.120709.geohashonly.patch.txt, SOLR-1586.Mattmann.121209.geohash.outarr.patch.txt,
SOLR-1586.Mattmann.121209.geohash.outstr.patch.txt, SOLR-1586.Mattmann.122609.patch.txt, SOLR-1586.patch,
SOLR-1586.patch
>
>
> Per SOLR-773, create field types that hid the details of creating tiers, geohash and
lat/lon fields.
> Fields should take in lat/lon points in a single form, as in:
> <field name="foo">lat lon</field>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message