[
https://issues.apache.org/jira/browse/SOLR-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653057#comment-13653057
]
Naomi Dushay commented on SOLR-905:
-----------------------------------
I believe I just hit the same bug. Our schema was updated with a new field on
master; the schema propagated to the slaves. The slaves are happy to serve
the document with the xml response writer, but the ruby response writer causes
the error above for the new field.
tomcat logs show no error either way:
INFO: [] webapp=/solr path=/select/ params={wt=ruby&id=qq440cn7337&qt=document}
hits=1 status=0 QTime=0
INFO: [] webapp=/solr path=/select/ params={id=qq440cn7337&qt=document} hits=1
status=0 QTime=0
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
