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

2013-08-06 Thread NilsK (JIRA)
NilsK created SOLR-5119:
---

 Summary: 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
Priority: Critical


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=CREATEname=mycollectionnumShards=1replicationFactor=1collection.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=responseHeaderint name=status404/intint 
name=QTime2/int/lstlst name=errorstr name=msgCan not find: 
/configs/myconfig/null/strint name=code404/int/lst
/response
{code}

6. *Problem 2*: 
http://localhost:8983/solr/admin/collections?action=RELOADname=mycollection

{code}
response
lst name=responseHeaderint name=status0/intint 
name=QTime845/int/lstlst name=failurestr 
name=10.147.252.2:8983_solrorg.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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



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

2013-08-06 Thread NilsK (JIRA)

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

NilsK updated SOLR-5119:


Description: 
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=CREATEname=mycollectionnumShards=1replicationFactor=1collection.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=responseHeaderint name=status404/intint 
name=QTime2/int/lstlst name=errorstr name=msgCan not find: 
/configs/myconfig/null/strint name=code404/int/lst
/response
{code}

6. *Problem 2*: 
http://localhost:8983/solr/admin/collections?action=RELOADname=mycollection

{code}
response
lst name=responseHeaderint name=status0/intint 
name=QTime845/int/lstlst name=failurestr 
name=10.147.252.2:8983_solrorg.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 

  was:
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=CREATEname=mycollectionnumShards=1replicationFactor=1collection.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=responseHeaderint name=status404/intint 
name=QTime2/int/lstlst name=errorstr name=msgCan not find: 
/configs/myconfig/null/strint name=code404/int/lst
/response
{code}

6. *Problem 2*: 
http://localhost:8983/solr/admin/collections?action=RELOADname=mycollection

{code}
response
lst name=responseHeaderint name=status0/intint 
name=QTime845/int/lstlst name=failurestr 
name=10.147.252.2:8983_solrorg.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 


 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
Priority: Critical

 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=CREATEname=mycollectionnumShards=1replicationFactor=1collection.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=responseHeaderint name=status404/intint 
 name=QTime2/int/lstlst name=errorstr name=msgCan not find: