[jira] [Updated] (SOLR-12481) update.autoCreateFields must be set via Config API command 'set-user-property', but 'bin/solr create' tells users to use the default action 'set-property', which fails be
[
https://issues.apache.org/jira/browse/SOLR-12481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-12481:
--
Fix Version/s: (was: 7.5)
7.4
> update.autoCreateFields must be set via Config API command
> 'set-user-property', but 'bin/solr create' tells users to use the default
> action 'set-property', which fails because the property is not editable
>
>
> Key: SOLR-12481
> URL: https://issues.apache.org/jira/browse/SOLR-12481
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Steve Rowe
>Assignee: Steve Rowe
>Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: SOLR-12481.patch
>
>
> {{bin/solr}} advises default config users to turn off data driven schema
> functionality, e.g.:
> {noformat}
> PROMPT$ bin/solr start -c
> [...]
> Waiting up to 180 seconds to see Solr running on port 8983 [-]
> Started Solr server on port 8983 (pid=74200). Happy searching!
> PROMPT$ bin/solr create -c mycoll
> WARNING: Using _default configset with data driven schema functionality. NOT
> RECOMMENDED for production use.
> To turn off: bin/solr config -c mycoll -p 8983 -property
> update.autoCreateFields -value false
> {noformat}
> When I try the above command, it claims to succeed, but in fact silently
> fails - see below (I'll open a separate JIRA for the false success problem).
> When I attempt to set this property via the equivalent direct call to the
> Config API, it fails:
> {noformat}
> PROMPT$ curl -X POST http://localhost:8983/solr/mycoll/config -d
> '{set-property: { update.autoCreateFields: false }}'
> {
> "responseHeader":{
> "status":0,
> "QTime":8},
> "errorMessages":[{
> "set-property":{"update.autoCreateFields":false},
> "errorMessages":["'update.autoCreateFields' is not an editable property"]}],
> "WARNING":"This response format is experimental. It is likely to change in
> the future."}
> {noformat}
> The correct action to use here is {{set-user-property}} rather than
> {{set-property}}. SOLR-11108 changed the {{bin/solr}} output from the
> correct Config API command to an incorrect {{bin/solr config}} command.
> {{bin/solr}} should instead be printing (note the {{-action}} param):
> {noformat}
> To turn off: bin/solr config -c mycoll -action set-user-property -p [...]
> -property update.autoCreateFields -value false
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-12481) update.autoCreateFields must be set via Config API command 'set-user-property', but 'bin/solr create' tells users to use the default action 'set-property', which fails be
[
https://issues.apache.org/jira/browse/SOLR-12481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-12481:
--
Attachment: SOLR-12481.patch
> update.autoCreateFields must be set via Config API command
> 'set-user-property', but 'bin/solr create' tells users to use the default
> action 'set-property', which fails because the property is not editable
>
>
> Key: SOLR-12481
> URL: https://issues.apache.org/jira/browse/SOLR-12481
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Steve Rowe
>Priority: Major
> Attachments: SOLR-12481.patch
>
>
> {{bin/solr}} advises default config users to turn off data driven schema
> functionality, e.g.:
> {noformat}
> PROMPT$ bin/solr start -c
> [...]
> Waiting up to 180 seconds to see Solr running on port 8983 [-]
> Started Solr server on port 8983 (pid=74200). Happy searching!
> PROMPT$ bin/solr create -c mycoll
> WARNING: Using _default configset with data driven schema functionality. NOT
> RECOMMENDED for production use.
> To turn off: bin/solr config -c mycoll -p 8983 -property
> update.autoCreateFields -value false
> {noformat}
> When I try the above command, it claims to succeed, but in fact silently
> fails - see below (I'll open a separate JIRA for the false success problem).
> When I attempt to set this property via the equivalent direct call to the
> Config API, it fails:
> {noformat}
> PROMPT$ curl -X POST http://localhost:8983/solr/mycoll/config -d
> '{set-property: { update.autoCreateFields: false }}'
> {
> "responseHeader":{
> "status":0,
> "QTime":8},
> "errorMessages":[{
> "set-property":{"update.autoCreateFields":false},
> "errorMessages":["'update.autoCreateFields' is not an editable property"]}],
> "WARNING":"This response format is experimental. It is likely to change in
> the future."}
> {noformat}
> The correct action to use here is {{set-user-property}} rather than
> {{set-property}}. SOLR-11108 changed the {{bin/solr}} output from the
> correct Config API command to an incorrect {{bin/solr config}} command.
> {{bin/solr}} should instead be printing (note the {{-action}} param):
> {noformat}
> To turn off: bin/solr config -c mycoll -action set-user-property -p [...]
> -property update.autoCreateFields -value false
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-12481) update.autoCreateFields must be set via Config API command 'set-user-property', but 'bin/solr create' tells users to use the default action 'set-property', which fails be
[
https://issues.apache.org/jira/browse/SOLR-12481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-12481:
--
Description:
{{bin/solr}} advises default config users to turn off data driven schema
functionality, e.g.:
{noformat}
PROMPT$ bin/solr start -c
[...]
Waiting up to 180 seconds to see Solr running on port 8983 [-]
Started Solr server on port 8983 (pid=74200). Happy searching!
PROMPT$ bin/solr create -c mycoll
WARNING: Using _default configset with data driven schema functionality. NOT
RECOMMENDED for production use.
To turn off: bin/solr config -c mycoll -p 8983 -property
update.autoCreateFields -value false
{noformat}
When I try the above command, it claims to succeed, but in fact silently fails
- see below (I'll open a separate JIRA for the false success problem).
When I attempt to set this property via the equivalent direct call to the
Config API, it fails:
{noformat}
PROMPT$ curl -X POST http://localhost:8983/solr/mycoll/config -d
'{set-property: { update.autoCreateFields: false }}'
{
"responseHeader":{
"status":0,
"QTime":8},
"errorMessages":[{
"set-property":{"update.autoCreateFields":false},
"errorMessages":["'update.autoCreateFields' is not an editable property"]}],
"WARNING":"This response format is experimental. It is likely to change in the
future."}
{noformat}
The correct action to use here is {{set-user-property}} rather than
{{set-property}}. SOLR-11108 changed the {{bin/solr}} output from the correct
Config API command to an incorrect {{bin/solr config}} command.
{{bin/solr}} should instead be printing (note the {{-action}} param):
{noformat}
To turn off: bin/solr config -c mycoll -action set-user-property -p [...]
-property update.autoCreateFields -value false
{noformat}
was:
{{bin/solr}} advises default config users to turn off data driven schema
functionality, e.g.:
{noformat}
PROMPT$ bin/solr start -c
[...]
Waiting up to 180 seconds to see Solr running on port 8983 [-]
Started Solr server on port 8983 (pid=74200). Happy searching!
PROMPT$ bin/solr create -c mycoll
WARNING: Using _default configset with data driven schema functionality. NOT
RECOMMENDED for production use.
To turn off: bin/solr config -c mycoll -p 8983 -property
update.autoCreateFields -value false
{noformat}
When I try the above command, it claims to succeed, but in fact silently fails
- see below (I'll open a separate JIRA for the false success problem).
When I attempt to set this property via the equivalent direct call to the
Config API, it fails:
{noformat}
PROMPT$ curl -X POST http://localhost:8983/solr/mycoll/config -d
'{set-property: { update.autoCreateFields: false }}'
{
"responseHeader":{
"status":0,
"QTime":8},
"errorMessages":[{
"set-property":{"update.autoCreateFields":false},
"errorMessages":["'update.autoCreateFields' is not an editable property"]}],
"WARNING":"This response format is experimental. It is likely to change in the
future."}
{noformat}
The correct action to use here is {{set-user-property}} rather than
{{set-property}}. SOLR-11108 changed the {{bin/solr}} output from the correct
Config API command to an incorrect {{bin/solr config}} command.
{{bin/solr}} should instead be printing (note the {{-action}} param):
{noformat}
To turn off: bin/solr config -c mycoll -action set-user-property -p [...]
-property update.autoCreateFields -value false
{noformat}
> update.autoCreateFields must be set via Config API command
> 'set-user-property', but 'bin/solr create' tells users to use the default
> action 'set-property', which fails because the property is not editable
>
>
> Key: SOLR-12481
> URL: https://issues.apache.org/jira/browse/SOLR-12481
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Steve Rowe
>Priority: Major
>
> {{bin/solr}} advises default config users to turn off data driven schema
> functionality, e.g.:
> {noformat}
> PROMPT$ bin/solr start -c
> [...]
> Waiting up to 180 seconds to see Solr running on port 8983 [-]
> Started Solr server on port 8983 (pid=74200). Happy searching!
> PROMPT$ bin/solr create -c mycoll
> WARNING: Using _default configset with data driven schema functionality. NOT
> RECOMMENDED for production use.
> To turn off: bin/solr config -c mycoll -p 8983 -property
> update.autoCreateFields -value false
> {noformat}
> When I try the above command, it claims to succeed, but in fact silently
> fails - see below (I'll open a separate JIRA for the false success problem).
> When I attempt to set this property via the equivalent direct call to the
> Config API, it fails:
[jira] [Updated] (SOLR-12481) update.autoCreateFields must be set via Config API command 'set-user-property', but 'bin/solr create' tells users to use the default action 'set-property', which fails be
[
https://issues.apache.org/jira/browse/SOLR-12481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-12481:
--
Description:
{{bin/solr}} advises default config users to turn off data driven schema
functionality, e.g.:
{noformat}
PROMPT$ bin/solr start -c
[...]
Waiting up to 180 seconds to see Solr running on port 8983 [-]
Started Solr server on port 8983 (pid=74200). Happy searching!
PROMPT$ bin/solr create -c mycoll
WARNING: Using _default configset with data driven schema functionality. NOT
RECOMMENDED for production use.
To turn off: bin/solr config -c mycoll -p 8983 -property
update.autoCreateFields -value false
{noformat}
When I try the above command, it claims to succeed, but in fact silently fails
- see below (I'll open a separate JIRA for the false success problem).
When I attempt to set this property via the equivalent direct call to the
Config API, it fails:
{noformat}
PROMPT$ curl -X POST http://localhost:8983/solr/mycoll/config -d
'{set-property: { update.autoCreateFields: false }}'
{
"responseHeader":{
"status":0,
"QTime":8},
"errorMessages":[{
"set-property":{"update.autoCreateFields":false},
"errorMessages":["'update.autoCreateFields' is not an editable property"]}],
"WARNING":"This response format is experimental. It is likely to change in the
future."}
{noformat}
The correct action to use here is {{set-user-property}} rather than
{{set-property}}. SOLR-11108 changed the {{bin/solr}} output from the correct
Config API command to an incorrect {{bin/solr config}} command.
{{bin/solr}} should instead be printing (note the {{-action}} param):
{noformat}
To turn off: bin/solr config -c mycoll -action set-user-property -p [...]
-property update.autoCreateFields -value false
{noformat}
was:
{{bin/solr}} advises default config users to turn off data driven schema
functionality, e.g.:
{noformat}
PROMPT$ bin/solr start -c
[...]
Waiting up to 180 seconds to see Solr running on port 8983 [-]
Started Solr server on port 8983 (pid=74200). Happy searching!
PROMPT$ bin/solr create -c mycoll
WARNING: Using _default configset with data driven schema functionality. NOT
RECOMMENDED for production use.
To turn off: bin/solr config -c mycoll -p 8983 -property
update.autoCreateFields -value false
{noformat}
When I try the above command, it claims to succeed, but in fact silently fails
- see below (I'll open a separate JIRA for the false success problem).
When I attempt to set this property via the equivalent direct call to the
Config API, it fails:
{noformat}
PROMPT$ curl -X POST http://localhost:8983/solr/mycoll/config -d
'{set-property: { update.autoCreateFields: false }}'
{
"responseHeader":{
"status":0,
"QTime":8},
"errorMessages":[{
"set-property":{"update.autoCreateFields":false},
"errorMessages":["'update.autoCreateFields' is not an editable property"]}],
"WARNING":"This response format is experimental. It is likely to change in the
future."}
{noformat}
The correct action to use here is {{set-user-property}} rather than
{{set-property}}. SOLR-11108 changed the {{bin/solr}} output from the correct
Config API command to the incorrect {{bin/solr config}} command.
{{bin/solr}} should instead be printing (note the {{-action}} param):
{noformat}
To turn off: bin/solr config -c mycoll -action set-user-property -p 8983
-property update.autoCreateFields -value false
{noformat}
> update.autoCreateFields must be set via Config API command
> 'set-user-property', but 'bin/solr create' tells users to use the default
> action 'set-property', which fails because the property is not editable
>
>
> Key: SOLR-12481
> URL: https://issues.apache.org/jira/browse/SOLR-12481
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Steve Rowe
>Priority: Major
>
> {{bin/solr}} advises default config users to turn off data driven schema
> functionality, e.g.:
> {noformat}
> PROMPT$ bin/solr start -c
> [...]
> Waiting up to 180 seconds to see Solr running on port 8983 [-]
> Started Solr server on port 8983 (pid=74200). Happy searching!
> PROMPT$ bin/solr create -c mycoll
> WARNING: Using _default configset with data driven schema functionality. NOT
> RECOMMENDED for production use.
> To turn off: bin/solr config -c mycoll -p 8983 -property
> update.autoCreateFields -value false
> {noformat}
> When I try the above command, it claims to succeed, but in fact silently
> fails - see below (I'll open a separate JIRA for the false success problem).
> When I attempt to set this property via the equivalent direct call to the
> Config API, it fails:
[jira] [Updated] (SOLR-12481) update.autoCreateFields must be set via Config API command 'set-user-property', but 'bin/solr create' tells users to use the default action 'set-property', which fails be
[
https://issues.apache.org/jira/browse/SOLR-12481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-12481:
--
Description:
{{bin/solr}} advises default config users to turn off data driven schema
functionality, e.g.:
{noformat}
PROMPT$ bin/solr start -c
[...]
Waiting up to 180 seconds to see Solr running on port 8983 [-]
Started Solr server on port 8983 (pid=74200). Happy searching!
PROMPT$ bin/solr create -c mycoll
WARNING: Using _default configset with data driven schema functionality. NOT
RECOMMENDED for production use.
To turn off: bin/solr config -c mycoll -p 8983 -property
update.autoCreateFields -value false
{noformat}
When I try the above command, it claims to succeed, but in fact silently fails
- see below (I'll open a separate JIRA for the false success problem).
When I attempt to set this property via the equivalent direct call to the
Config API, it fails:
{noformat}
PROMPT$ curl -X POST http://localhost:8983/solr/mycoll/config -d
'{set-property: { update.autoCreateFields: false }}'
{
"responseHeader":{
"status":0,
"QTime":8},
"errorMessages":[{
"set-property":{"update.autoCreateFields":false},
"errorMessages":["'update.autoCreateFields' is not an editable property"]}],
"WARNING":"This response format is experimental. It is likely to change in the
future."}
{noformat}
The correct action to use here is {{set-user-property}} rather than
{{set-property}}. SOLR-11108 changed the {{bin/solr}} output from the correct
Config API command to the incorrect {{bin/solr config}} command.
{{bin/solr}} should instead be printing (note the {{-action}} param):
{noformat}
To turn off: bin/solr config -c mycoll -action set-user-property -p 8983
-property update.autoCreateFields -value false
{noformat}
was:
{{bin/solr}} advises default config users to turn off data driven schema
functionality, e.g.:
{noformat}
PROMPT$ bin/solr start -c
[...]
Waiting up to 180 seconds to see Solr running on port 8983 [-]
Started Solr server on port 8983 (pid=74200). Happy searching!
PROMPT$ bin/solr create -c mycoll
WARNING: Using _default configset with data driven schema functionality. NOT
RECOMMENDED for production use.
To turn off: bin/solr config -c mycoll -p 8983 -property
update.autoCreateFields -value false
{noformat}
When I try the above command, it claims to succeed (I'll open a separate JIRA
for the false success problem).
When I attempt to set this property via the equivalent direct call to the
Config API, it fails:
{noformat}
PROMPT$ curl -X POST http://localhost:8983/solr/mycoll/config -d
'{set-property: { update.autoCreateFields: false }}'
{
"responseHeader":{
"status":0,
"QTime":8},
"errorMessages":[{
"set-property":{"update.autoCreateFields":false},
"errorMessages":["'update.autoCreateFields' is not an editable property"]}],
"WARNING":"This response format is experimental. It is likely to change in the
future."}
{noformat}
The correct action to use here is {{set-user-property}} rather than
{{set-property}}. SOLR-11108 changed the {{bin/solr}} output from the correct
Config API command to the incorrect {{bin/solr config}} command.
{{bin/solr}} should instead be printing (note the {{-action}} param):
{noformat}
To turn off: bin/solr config -c mycoll -action set-user-property -p 8983
-property update.autoCreateFields -value false
{noformat}
> update.autoCreateFields must be set via Config API command
> 'set-user-property', but 'bin/solr create' tells users to use the default
> action 'set-property', which fails because the property is not editable
>
>
> Key: SOLR-12481
> URL: https://issues.apache.org/jira/browse/SOLR-12481
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Steve Rowe
>Priority: Major
>
> {{bin/solr}} advises default config users to turn off data driven schema
> functionality, e.g.:
> {noformat}
> PROMPT$ bin/solr start -c
> [...]
> Waiting up to 180 seconds to see Solr running on port 8983 [-]
> Started Solr server on port 8983 (pid=74200). Happy searching!
> PROMPT$ bin/solr create -c mycoll
> WARNING: Using _default configset with data driven schema functionality. NOT
> RECOMMENDED for production use.
> To turn off: bin/solr config -c mycoll -p 8983 -property
> update.autoCreateFields -value false
> {noformat}
> When I try the above command, it claims to succeed, but in fact silently
> fails - see below (I'll open a separate JIRA for the false success problem).
> When I attempt to set this property via the equivalent direct call to the
> Config API, it fails:
> {noformat}
> PROMPT$ curl -X POST
[jira] [Updated] (SOLR-12481) update.autoCreateFields must be set via Config API command 'set-user-property', but 'bin/solr create' tells users to use the default action 'set-property', which fails be
[
https://issues.apache.org/jira/browse/SOLR-12481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-12481:
--
Description:
{{bin/solr}} advises default config users to turn off data driven schema
functionality, e.g.:
{noformat}
PROMPT$ bin/solr start -c
[...]
Waiting up to 180 seconds to see Solr running on port 8983 [-]
Started Solr server on port 8983 (pid=74200). Happy searching!
PROMPT$ bin/solr create -c mycoll
WARNING: Using _default configset with data driven schema functionality. NOT
RECOMMENDED for production use.
To turn off: bin/solr config -c mycoll -p 8983 -property
update.autoCreateFields -value false
{noformat}
When I try the above command, it claims to succeed (I'll open a separate JIRA
for the false success problem).
When I attempt to set this property via the equivalent direct call to the
Config API, it fails:
{noformat}
PROMPT$ curl -X POST http://localhost:8983/solr/mycoll/config -d
'{set-property: { update.autoCreateFields: false }}'
{
"responseHeader":{
"status":0,
"QTime":8},
"errorMessages":[{
"set-property":{"update.autoCreateFields":false},
"errorMessages":["'update.autoCreateFields' is not an editable property"]}],
"WARNING":"This response format is experimental. It is likely to change in the
future."}
{noformat}
The correct action to use here is {{set-user-property}} rather than
{{set-property}}. SOLR-11108 changed the {{bin/solr}} output from the correct
Config API command to the incorrect {{bin/solr config}} command.
{{bin/solr}} should instead be printing (note the {{-action}} param):
{noformat}
To turn off: bin/solr config -c mycoll -action set-user-property -p 8983
-property update.autoCreateFields -value false
{noformat}
was:
{{bin/solr}} advises default config users to turn off data driven schema
functionality, e.g.:
{noprompt}
PROMPT$ bin/solr start -c
[...]
Waiting up to 180 seconds to see Solr running on port 8983 [-]
Started Solr server on port 8983 (pid=74200). Happy searching!
PROMPT$ bin/solr create -c mycoll
WARNING: Using _default configset with data driven schema functionality. NOT
RECOMMENDED for production use.
To turn off: bin/solr config -c mycoll -p 8983 -property
update.autoCreateFields -value false
{noprompt}
When I try the above command, it claims to succeed (I'll open a separate JIRA
for the false success problem).
When I attempt to set this property via the equivalent direct call to the
Config API, it fails:
{noformat}
PROMPT$ curl -X POST http://localhost:8983/solr/mycoll/config -d
'{set-property: { update.autoCreateFields: false }}'
{
"responseHeader":{
"status":0,
"QTime":8},
"errorMessages":[{
"set-property":{"update.autoCreateFields":false},
"errorMessages":["'update.autoCreateFields' is not an editable property"]}],
"WARNING":"This response format is experimental. It is likely to change in the
future."}
{noformat}
The correct action to use here is {{set-user-property}} rather than
{{set-property}}. SOLR-11108 changed the {{bin/solr}} output from the correct
Config API command to the incorrect {{bin/solr config}} command.
{{bin/solr}} should instead be printing (note the {{-action}} param):
{noformat}
To turn off: bin/solr config -c mycoll -action set-user-property -p 8983
-property update.autoCreateFields -value false
{noformat}
> update.autoCreateFields must be set via Config API command
> 'set-user-property', but 'bin/solr create' tells users to use the default
> action 'set-property', which fails because the property is not editable
>
>
> Key: SOLR-12481
> URL: https://issues.apache.org/jira/browse/SOLR-12481
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Steve Rowe
>Priority: Major
>
> {{bin/solr}} advises default config users to turn off data driven schema
> functionality, e.g.:
> {noformat}
> PROMPT$ bin/solr start -c
> [...]
> Waiting up to 180 seconds to see Solr running on port 8983 [-]
> Started Solr server on port 8983 (pid=74200). Happy searching!
> PROMPT$ bin/solr create -c mycoll
> WARNING: Using _default configset with data driven schema functionality. NOT
> RECOMMENDED for production use.
> To turn off: bin/solr config -c mycoll -p 8983 -property
> update.autoCreateFields -value false
> {noformat}
> When I try the above command, it claims to succeed (I'll open a separate JIRA
> for the false success problem).
> When I attempt to set this property via the equivalent direct call to the
> Config API, it fails:
> {noformat}
> PROMPT$ curl -X POST http://localhost:8983/solr/mycoll/config -d
> '{set-property: {
[jira] [Updated] (SOLR-12481) update.autoCreateFields must be set via Config API command 'set-user-property', but 'bin/solr create' tells users to use the default action 'set-property', which fails be
[
https://issues.apache.org/jira/browse/SOLR-12481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-12481:
--
Description:
{{bin/solr}} advises default config users to turn off data driven schema
functionality, e.g.:
{noformat}
PROMPT$ bin/solr start -c
[...]
Waiting up to 180 seconds to see Solr running on port 8983 [-]
Started Solr server on port 8983 (pid=74200). Happy searching!
PROMPT$ bin/solr create -c mycoll
WARNING: Using _default configset with data driven schema functionality. NOT
RECOMMENDED for production use.
To turn off: bin/solr config -c mycoll -p 8983 -property
update.autoCreateFields -value false
{noformat}
When I try the above command, it claims to succeed (I'll open a separate JIRA
for the false success problem).
When I attempt to set this property via the equivalent direct call to the
Config API, it fails:
{noformat}
PROMPT$ curl -X POST http://localhost:8983/solr/mycoll/config -d
'{set-property: { update.autoCreateFields: false }}'
{
"responseHeader":{
"status":0,
"QTime":8},
"errorMessages":[{
"set-property":{"update.autoCreateFields":false},
"errorMessages":["'update.autoCreateFields' is not an editable property"]}],
"WARNING":"This response format is experimental. It is likely to change in the
future."}
{noformat}
The correct action to use here is {{set-user-property}} rather than
{{set-property}}. SOLR-11108 changed the {{bin/solr}} output from the correct
Config API command to the incorrect {{bin/solr config}} command.
{{bin/solr}} should instead be printing (note the {{-action}} param):
{noformat}
To turn off: bin/solr config -c mycoll -action set-user-property -p 8983
-property update.autoCreateFields -value false
{noformat}
was:
{{bin/solr}} advises default config users to turn off data driven schema
functionality, e.g.:
{noformat}
PROMPT$ bin/solr start -c
[...]
Waiting up to 180 seconds to see Solr running on port 8983 [-]
Started Solr server on port 8983 (pid=74200). Happy searching!
PROMPT$ bin/solr create -c mycoll
WARNING: Using _default configset with data driven schema functionality. NOT
RECOMMENDED for production use.
To turn off: bin/solr config -c mycoll -p 8983 -property
update.autoCreateFields -value false
{noformat}
When I try the above command, it claims to succeed (I'll open a separate JIRA
for the false success problem).
When I attempt to set this property via the equivalent direct call to the
Config API, it fails:
{noformat}
PROMPT$ curl -X POST http://localhost:8983/solr/mycoll/config -d
'{set-property: { update.autoCreateFields: false }}'
{
"responseHeader":{
"status":0,
"QTime":8},
"errorMessages":[{
"set-property":{"update.autoCreateFields":false},
"errorMessages":["'update.autoCreateFields' is not an editable property"]}],
"WARNING":"This response format is experimental. It is likely to change in the
future."}
{noformat}
The correct action to use here is {{set-user-property}} rather than
{{set-property}}. SOLR-11108 changed the {{bin/solr}} output from the correct
Config API command to the incorrect {{bin/solr config}} command.
{{bin/solr}} should instead be printing (note the {{-action}} param):
{noformat}
To turn off: bin/solr config -c mycoll -action set-user-property -p 8983
-property update.autoCreateFields -value false
{noformat}
> update.autoCreateFields must be set via Config API command
> 'set-user-property', but 'bin/solr create' tells users to use the default
> action 'set-property', which fails because the property is not editable
>
>
> Key: SOLR-12481
> URL: https://issues.apache.org/jira/browse/SOLR-12481
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Steve Rowe
>Priority: Major
>
> {{bin/solr}} advises default config users to turn off data driven schema
> functionality, e.g.:
> {noformat}
> PROMPT$ bin/solr start -c
> [...]
> Waiting up to 180 seconds to see Solr running on port 8983 [-]
> Started Solr server on port 8983 (pid=74200). Happy searching!
> PROMPT$ bin/solr create -c mycoll
> WARNING: Using _default configset with data driven schema functionality. NOT
> RECOMMENDED for production use.
> To turn off: bin/solr config -c mycoll -p 8983 -property
> update.autoCreateFields -value false
> {noformat}
> When I try the above command, it claims to succeed (I'll open a separate JIRA
> for the false success problem).
> When I attempt to set this property via the equivalent direct call to the
> Config API, it fails:
> {noformat}
> PROMPT$ curl -X POST http://localhost:8983/solr/mycoll/config -d
> '{set-property: {
