lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Rutherglen" <jason.rutherg...@gmail.com>
Subject Re: [jira] Commented: (SOLR-773) Incorporate Local Lucene/Solr
Date Thu, 18 Sep 2008 13:28:12 GMT
Does Geohash enable range based queries?  It's unclear from the wiki site.

Can we do something like this
http://code.google.com/apis/base/attrs-queries.html#LocDatQuer  I
would rather see SOLR go in the direction of being compatible with
GData and GBase and invent more unique things, unless they are better
somehow.

GBase has a notation for doing function queries as well that we should
build into SOLR, current SOLR function queries really are very
non-intuitive for me and I spend a lot of time each time trying to
figure out how to do them.

Check this stuff out.
http://code.google.com/apis/base/ranking-lang-spec.html#functions  I'm
not sure we need to create something quite this complex.  However, I
would like a way to do something like this without having to reboot
the server.  I personally thing this is best implemented using dynamic
classloading.  If people find that interesting, then we could look at
scripting.  I'm not a big fan of scripting because it's not object
oriented, it's not maintainable, scripts always grow and get too
complex to read so that when new people take a look at it the ramp up
time is high.  With dynamic classes, all of the functionality of what
is available is there.  No need to create new script functions, test
them out, load them, fix bugs and all that.

On Wed, Sep 17, 2008 at 7:01 PM, Ryan McKinley (JIRA) <jira@apache.org> wrote:
>
>    [ https://issues.apache.org/jira/browse/SOLR-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631992#action_12631992
]
>
> Ryan McKinley commented on SOLR-773:
> ------------------------------------
>
> LocalLucene/Solr are currently designed to do exactly points 1-4.
>
> As for storing lat/lon in a single field... that sounds really interesting.  Currently
the local lucene stuff uses two fields and [NumberUtils.java|http://svn.apache.org/repos/asf/lucene/solr/trunk/src/java/org/apache/solr/util/NumberUtils.java]
to index/store the distance.  It does a lot of good work to break various bounding box levels
into tokens and only performs math on the minimum result set.
>
> We should consider a geohash field type: http://en.wikipedia.org/wiki/Geohash to store
lat/lon in a single string.  This has some really interesting features that are ideal for
lucene.  In particular, checking if a point is within a bounding box is simply a lexicographic
range query.
>
> Here is a public domain python geohash implementation: http://mappinghacks.com/code/geohash.py.txt
>
>> 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
>>            Priority: Minor
>>
>> 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