You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Brian Westphal (JIRA)" <ji...@apache.org> on 2010/01/13 02:35:54 UTC

[jira] Commented: (SOLR-773) Incorporate Local Lucene/Solr

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

Brian Westphal commented on SOLR-773:
-------------------------------------

We've got Localsolr (2.9.1 lucene-spatial library) running on Solr 1.4 with Tomcat 1.6. Everything's looking good, except for a couple little issues.

Issue #1:
If we specify fl=id (or fl= anything) and wt=json it seems that the fl parameter is ignored (thus we get a lot more detail in our results than we'd like).

If we specify fl=id and leave out wt=json (which defaults to returning xml results), we get the expected fields back. We'd really prefer to use wt=json because the results are easier for us to deal with (also, the same issue also arises with wt=python and wt=ruby).

Issue #2:
It looks like the defType parameter isn't properly passed through for geo queries, making it really hard to use things like dismax + geo.  I've been playing with the code a bit and have a "working" patch for it.  However, as I'm very new to the solr/localsolr source, I'd be uncomfortable submitting it without additional testing.

---------

If anyone knows any workarounds for these issues, please let me know.

> 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
>             Fix For: 1.5
>
>         Attachments: exampleSpatial.zip, lucene-spatial-2.9-dev.jar, lucene.tar.gz, screenshot-1.jpg, 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-spatial_solr.patch, SOLR-773.patch, SOLR-773.patch, solrGeoQuery.tar, 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.


Re: [jira] Commented: (SOLR-773) Incorporate Local Lucene/Solr

Posted by patrick o'leary <pj...@pjaol.com>.
Hey Brian

The fl issue is something I've seen just this week, I'll dig into it more,
gut feeling is that if it works for the xml writer then it might be
something in the json / python writers and using SolrDocuments vs DocList.

Send me over the patch for defType, I know it's applied on a patch in
solr-773, but I can't remember if it's in the localsolr code base.

Thanks
Patrick


On Tue, Jan 12, 2010 at 5:35 PM, Brian Westphal (JIRA) <ji...@apache.org>wrote:

>
>    [
> https://issues.apache.org/jira/browse/SOLR-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799515#action_12799515]
>
> Brian Westphal commented on SOLR-773:
> -------------------------------------
>
> We've got Localsolr (2.9.1 lucene-spatial library) running on Solr 1.4 with
> Tomcat 1.6. Everything's looking good, except for a couple little issues.
>
> Issue #1:
> If we specify fl=id (or fl= anything) and wt=json it seems that the fl
> parameter is ignored (thus we get a lot more detail in our results than we'd
> like).
>
> If we specify fl=id and leave out wt=json (which defaults to returning xml
> results), we get the expected fields back. We'd really prefer to use wt=json
> because the results are easier for us to deal with (also, the same issue
> also arises with wt=python and wt=ruby).
>
> Issue #2:
> It looks like the defType parameter isn't properly passed through for geo
> queries, making it really hard to use things like dismax + geo.  I've been
> playing with the code a bit and have a "working" patch for it.  However, as
> I'm very new to the solr/localsolr source, I'd be uncomfortable submitting
> it without additional testing.
>
> ---------
>
> If anyone knows any workarounds for these issues, please let me know.
>
> > 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
> >             Fix For: 1.5
> >
> >         Attachments: exampleSpatial.zip, lucene-spatial-2.9-dev.jar,
> lucene.tar.gz, screenshot-1.jpg, 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-spatial_solr.patch, SOLR-773.patch, SOLR-773.patch,
> solrGeoQuery.tar, 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.
>
>