lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-1131) Allow a single field type to index multiple fields
Date Sat, 19 Dec 2009 14:51:18 GMT

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

Yonik Seeley commented on SOLR-1131:
------------------------------------

bq. I think we want generic. Some geo stuff will want 3D (elevation).

I imagine 99% of the users of Point will be those wanting straight 2D geo search (limit by
simple distance, or sort by simple distance).
I don't see how elevation would help in isolation since more accurate distance measures would
presumably need map info for driving distance.
I could see people wanting to *store* 3D points, etc, but they can do that today.

bq. I thought about that, but why should we have to figure out what the dynamic field is every
time when we already know it?

It's more of an issue of directly creating fields... that's currently up to the schema (or
the FieldType if some form of SOLR-1664 goes in).

bq. > make PointType actually delegate to the subFieldType... before it was assuming thinks
like TermQuery and TermRangeQuery... this would have actually disabled NumericRangeQuery speedups!

bq. Where do you mean? In createField? Or in the getFieldQuery?

In getFieldQuery and getRangeQuery... I changed to actually delegate to the subFieldType.getFieldQuery
and getRangeQuery.

> Allow a single field type to index multiple fields
> --------------------------------------------------
>
>                 Key: SOLR-1131
>                 URL: https://issues.apache.org/jira/browse/SOLR-1131
>             Project: Solr
>          Issue Type: New Feature
>          Components: Schema and Analysis
>            Reporter: Ryan McKinley
>            Assignee: Grant Ingersoll
>             Fix For: 1.5
>
>         Attachments: diff.patch, SOLR-1131-IndexMultipleFields.patch, SOLR-1131.Mattmann.121009.patch.txt,
SOLR-1131.Mattmann.121109.patch.txt, SOLR-1131.patch, SOLR-1131.patch, SOLR-1131.patch, SOLR-1131.patch,
SOLR-1131.patch, SOLR-1131.patch, SOLR-1131.patch, SOLR-1131.patch, SOLR-1131.patch, SOLR-1131.patch,
SOLR-1131.patch, SOLR-1131.patch, SOLR-1131.patch
>
>
> In a few special cases, it makes sense for a single "field" (the concept) to be indexed
as a set of Fields (lucene Field).  Consider SOLR-773.  The concept "point" may be best indexed
in a variety of ways:
>  * geohash (sincle lucene field)
>  * lat field, lon field (two double fields)
>  * cartesian tiers (a series of fields with tokens to say if it exists within that region)

-- 
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