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 "Matt Mitchell (JIRA)" <ji...@apache.org> on 2008/12/10 03:12:44 UTC

[jira] Created: (SOLR-905) wt type of json or ruby triggers error with legacy fields

wt type of json or ruby triggers error with legacy fields
---------------------------------------------------------

                 Key: SOLR-905
                 URL: https://issues.apache.org/jira/browse/SOLR-905
             Project: Solr
          Issue Type: Bug
          Components: search
    Affects Versions: 1.3
            Reporter: Matt Mitchell


Given an index/schema with a field of "word"
then the field name is changed to "spell"
querying with a wt=json or ruby gives an error of (pasted in below)
where querying with a wt=xml does not.

will return the expected results:
q=*:*&wt=xml

returns the error:
q=*:*&wt=json

ERROR ->

HTTP Status 400 - undefined field word

type Status report

message undefined field word

description The request sent by the client was syntactically incorrect (undefined field word).

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


[jira] Updated: (SOLR-905) wt type of json or ruby triggers error with legacy fields

Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SOLR-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hoss Man updated SOLR-905:
--------------------------

    Component/s:     (was: search)
                 Response Writers

> wt type of json or ruby triggers error with legacy fields
> ---------------------------------------------------------
>
>                 Key: SOLR-905
>                 URL: https://issues.apache.org/jira/browse/SOLR-905
>             Project: Solr
>          Issue Type: Bug
>          Components: Response Writers
>    Affects Versions: 1.3
>            Reporter: Matt Mitchell
>
> Given an index/schema with a field of "word"
> then the field name is changed to "spell"
> querying with a wt=json or ruby gives an error of (pasted in below)
> where querying with a wt=xml does not.
> will return the expected results:
> q=*:*&wt=xml
> returns the error:
> q=*:*&wt=json
> ERROR ->
> HTTP Status 400 - undefined field word
> type Status report
> message undefined field word
> description The request sent by the client was syntactically incorrect (undefined field word).

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