Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-dev@lucene.apache.org
Message-ID: <1285142374.1240856070940.JavaMail.jira@brutus>
Date: Mon, 27 Apr 2009 11:14:30 -0700 (PDT)
From: "Ryan McKinley (JIRA)" <jira@apache.org>
To: solr-dev@lucene.apache.org
Subject: [jira] Commented: (SOLR-773) Incorporate Local Lucene/Solr
In-Reply-To: <1089092633.1221505424636.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ryan McKinley commented on SOLR-773:
------------------------------------

Yonik -- I like all 4 proposals.  

I am not familiar with the function query internal -- would it get called for things that do not match the filter?  Distance calculations are typically the most expensive part of the query.

re "It seems like points should be stored and represented in a single field..."  -- I agree that the schema and URL API should point to a single field to represent the geometry field.  In practice, the indexing will probably need multiple fields to get the job done (efficiently).

It would be great if the schema field type could define everything needed to index and search.  There are (at least) three approaches to indexing points that each have their advantages (and disadvantages) -- we should be able to support any of these options.   

{panel}
 * GeoPointField  (abstract?  the standard stuff about dealing with points)
 ** GeoPointFieldHash (represented as a GeoHash, fast bounds query (with limited accuracy))
 ** GeoPointFieldTiers (highly scalable, fast, complex)
 ** GeoPointFieldTrie (...)
 * GeoLineField...
 * GeoPolygonField...
{panel}

I think it makes sense to try to follow the [georss|http://georss.org/simple] format to represent geometry:
{code:xml}
  <georss:point>45.256 -71.92</georss:point>
{code}

{code:xml}
<georss:line>45.256 -110.45 46.46 -109.48 43.84 -109.86</georss:line>
{code}

{code:xml}
<georss:polygon>
	45.256 -110.45 46.46 -109.48 43.84 -109.86 45.256 -110.45
</georss:polygon>
{code}

{code:xml}
<georss:box>42.943 -71.032 43.039 -69.856</georss:box>
{code}

> Incorporate Local Lucene/Solr
> -----------------------------
>
>                 Key: SOLR-773
>                 URL: https://issues.apache.org/jira/browse/SOLR-773
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Grant Ingersoll
>            Assignee: Grant Ingersoll
>            Priority: Minor
>         Attachments: lucene.tar.gz, SOLR-773-local-lucene.patch, SOLR-773-local-lucene.patch, SOLR-773-local-lucene.patch, SOLR-773-local-lucene.patch, SOLR-773-local-lucene.patch, SOLR-773.patch, SOLR-773.patch, spatial-solr.tar.gz
>
>
> Local Lucene has been donated to the Lucene project.  It has some Solr components, but we should evaluate how best to incorporate it into Solr.
> See http://lucene.markmail.org/message/orzro22sqdj3wows?q=LocalLucene

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