You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steve Rowe (JIRA)" <ji...@apache.org> on 2013/08/12 22:22:48 UTC

[jira] [Resolved] (SOLR-5119) Managed schema problems after adding fields via Schema Rest API

     [ https://issues.apache.org/jira/browse/SOLR-5119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Rowe resolved SOLR-5119.
------------------------------

       Resolution: Fixed
    Fix Version/s: 5.0
                   4.5

Committed to trunk and branch_4x.

Thanks Nils!
                
> Managed schema problems after adding fields via Schema Rest API 
> ----------------------------------------------------------------
>
>                 Key: SOLR-5119
>                 URL: https://issues.apache.org/jira/browse/SOLR-5119
>             Project: Solr
>          Issue Type: Bug
>          Components: Schema and Analysis
>    Affects Versions: 4.4
>            Reporter: NilsK
>            Assignee: Steve Rowe
>            Priority: Critical
>             Fix For: 4.5, 5.0
>
>         Attachments: SOLR-5119.patch
>
>
> After adding fields with the Schema API the schema cannot be shown on the Admin UI anymore and reloading the Collection/Core throws an NullPointerException. The schema itself seems to work.
> Steps to reproduce:
> 1. enable managed schema in example/solr/collection1/conf/solrconfig.xml
> 2. upload that config
> {code}sh example/cloud-scripts/zkcli.sh -z localhost:8575 -cmd upconfig -d example/solr/collection1/conf/ -n myconfig{code}
> 3. create a new collection 
> {code}curl "http://localhost:8983/solr/admin/collections?action=CREATE&name=mycollection&numShards=1&replicationFactor=1&collection.configName=myconfig"{code}
> 4. add some fields
> {code}curl http://localhost:8983/solr/mycollection/schema/fields -X POST -H 'Content-type:application/json' --data-binary '[
> {
>   "name": "my_field",
>   "type": "string",
>   "stored": true,
>   "indexed": true
> },
> {
>   "name": "my_field2",
>   "type": "string",
>   "stored": true,
>   "indexed": true
> }
> ]'{code}
> 5. *Problem 1*: http://localhost:8983/solr/#/mycollection_shard1_replica1/schema
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <response>
> <lst name="responseHeader"><int name="status">404</int><int name="QTime">2</int></lst><lst name="error"><str name="msg">Can not find: /configs/myconfig/null</str><int name="code">404</int></lst>
> </response>
> {code}
> 6. *Problem 2*: http://localhost:8983/solr/admin/collections?action=RELOAD&name=mycollection
> {code}
> <response>
> <lst name="responseHeader"><int name="status">0</int><int name="QTime">845</int></lst><lst name="failure"><str name="10.147.252.2:8983_solr">org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException:Server at http://10.147.252.2:8983/solr returned non ok status:500, message:Server Error</str></lst>
> </response>
> {code}
> 7. when restarting Solr, both 5 and 6 work 

--
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org