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-773) Incorporate Local Lucene/Solr
Date Sat, 25 Apr 2009 15:05:30 GMT

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

Yonik Seeley commented on SOLR-773:
-----------------------------------

It seems like quite a lot of work has gone into working around some of Solr's current limitations...
perhaps we should fix them instead? It seems like we should be able to avoid custom request
handlers, query components, or update processors and simply use generic mechanisms.

>From the user interface point of view, what's needed is:
- A way to filter by a bounding box. This could simply be a custom QParser
fq={!gbox p=101.2,234.5 f=position, d=1.5}
// a bounding box, centered on 101.2,234.5 including everything within 1.5 miles
- A function query that calculates distances
gdist(position,101.2,234.3)
- A way to sort by a function query... this is generic desired functionality anyway!
- A way to return the value of a function query for documents - also generic desired functionality.
Perhaps use meta as proposed in SOLR-705?

If we had that, then geo becomes very generic - no need for special distributed search support,
and one could do things like boosting the relevancy score by a function of the distance (not
even necessarily a linear boost because of the flexibility of function query). If/when we
get faceting on a function query, it will also automatically work with distances.

It seems like points should be stored and represented in a single field, that way there can
be multiple points per document (otherwise how would one correlate which latitude went with
which longitude). How it's indexed (multiple fields, etc) is more of an implementation detail.
There is an issue with *how* to allow a single field to index to multiple fields - another
Solr limitation we should figure out how to fix (an earlier version of TrieRangeQuery needed
this too). 

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


Mime
View raw message