[jira] [Updated] (SOLR-6594) deprecate the one action only APIs for schema editing
[
https://issues.apache.org/jira/browse/SOLR-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-6594:
-
Description:
with SOLR-6476 done and committed , we have more than one way of writing to
schema . Having two different ways of doing the same thing is counter
productive .
I would like to mark them as deprecated and the calls to those APIs will
succeed but will give a deprecation message in the output. The read APIs would
continue to be the same , though .
Details: the following operations have been deprecated as of Solr 5.5, and
support for them will be removed in Solr 6.0:
* Create new field(s): POST to {{/_collection_/schema/fields}} or PUT to
{{/_collection_/schema/fields/_fieldname_}}
* Create new dynamic field(s): POST to {{/_collection_/schema/dynamicfields}}
or PUT to {{/_collection_/schema/dynamicfields/_glob_}}
* Create new field type(s): POST to {{/_collection_/schema/fieldtypes}} or PUT
to {{/_collection_/schema/fieldtypes/_name_}}
* Create new copyField rule(s): POST to {{/_collection_/schema/copyfields}}.
Note that all of the above operations can instead be performed using the bulk
schema API, documented since the 5.0 Solr ref guide here:
https://cwiki.apache.org/confluence/display/solr/Schema+API
To be clear, read-only GET operations on the above-mentioned endpoints will not
be changed, deprecated or removed - they will continue to return information
about fields, dynamicFields, fieldTypes, and copyField rules, respectively.
was:
with SOLR-6476 done and committed , we have more than one way of writing to
schema . Having two different ways of doing the same thing is counter
productive .
I would like to mark them as deprecated and the calls to those APIs will
succeed but will give a deprecation message in the output. The read APIs would
continue to be the same , though .
Details: the following operations have been deprecated as of Solr 5.5, and
support for them will be removed in Solr 6.0:
* Create new field(s): POST to {{/_collection_/schema/fields}} or PUT to
{{/_collection_/schema/fields/_fieldname_}}
* Create new dynamic field(s): POST to {{/_collection_/schema/dynamicfields}}
or PUT to {{/_collection_/schema/dynamicfields/_glob_}}
* Create new field type(s): POST to {{/_collection_/schema/fieldtypes}} or PUT
to {{/_collection_/schema/fieldtypes/_name_}}
* Create new copyField rule(s): POST to {{/_collection_/schema/copyfields}}.
Note that all of the above operations can instead be performed using the bulk
schema API, documented since the 5.0 Solr ref guide here:
https://cwiki.apache.org/confluence/display/solr/Schema+API
To be clear, read-only GET operations on the above-mentioned endpoints will not
be changed, deprecated or removed - they will continue to return information
about fields, dynamicFields and copyField rules.
> deprecate the one action only APIs for schema editing
> -
>
> Key: SOLR-6594
> URL: https://issues.apache.org/jira/browse/SOLR-6594
> Project: Solr
> Issue Type: Bug
>Reporter: Noble Paul
> Fix For: 5.5, 6.0
>
>
> with SOLR-6476 done and committed , we have more than one way of writing to
> schema . Having two different ways of doing the same thing is counter
> productive .
> I would like to mark them as deprecated and the calls to those APIs will
> succeed but will give a deprecation message in the output. The read APIs
> would continue to be the same , though .
> Details: the following operations have been deprecated as of Solr 5.5, and
> support for them will be removed in Solr 6.0:
> * Create new field(s): POST to {{/_collection_/schema/fields}} or PUT to
> {{/_collection_/schema/fields/_fieldname_}}
> * Create new dynamic field(s): POST to {{/_collection_/schema/dynamicfields}}
> or PUT to {{/_collection_/schema/dynamicfields/_glob_}}
> * Create new field type(s): POST to {{/_collection_/schema/fieldtypes}} or
> PUT to {{/_collection_/schema/fieldtypes/_name_}}
> * Create new copyField rule(s): POST to {{/_collection_/schema/copyfields}}.
> Note that all of the above operations can instead be performed using the bulk
> schema API, documented since the 5.0 Solr ref guide here:
> https://cwiki.apache.org/confluence/display/solr/Schema+API
> To be clear, read-only GET operations on the above-mentioned endpoints will
> not be changed, deprecated or removed - they will continue to return
> information about fields, dynamicFields, fieldTypes, and copyField rules,
> respectively.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-6594) deprecate the one action only APIs for schema editing
[
https://issues.apache.org/jira/browse/SOLR-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-6594:
-
Description:
with SOLR-6476 done and committed , we have more than one way of writing to
schema . Having two different ways of doing the same thing is counter
productive .
I would like to mark them as deprecated and the calls to those APIs will
succeed but will give a deprecation message in the output. The read APIs would
continue to be the same , though .
Details: the following operations have been deprecated as of Solr 5.5, and
support for them will be removed in Solr 6.0:
* Create new field(s): POST to {{/_collection_/schema/fields}} or PUT to
{{/_collection_/schema/fields/_fieldname_}}
* Create new dynamic field(s): POST to {{/_collection_/schema/dynamicfields}}
or PUT to {{/_collection_/schema/dynamicfields/_glob_}}
* Create new field type(s): POST to {{/_collection_/schema/fieldtypes}} or PUT
to {{/_collection_/schema/fieldtypes/_name_}}
* Create new copyField rule(s): POST to {{/_collection_/schema/copyfields}}.
Note that all of the above operations can instead be performed using the bulk
schema API, documented since the 5.0 Solr ref guide here:
https://cwiki.apache.org/confluence/display/solr/Schema+API
To be clear, read-only GET operations on the above-mentioned endpoints will not
be changed, deprecated or removed - they will continue to return information
about fields, dynamicFields and copyField rules.
was:
with SOLR-6476 done and committed , we have more than one way of writing to
schema . Having two different ways of doing the same thing is counter
productive .
I would like to mark them as deprecated and the calls to those APIs will
succeed but will give a deprecation message in the output. The read APIs would
continue to be the same , though .
Details: the following operations have been deprecated as of Solr 5.5, and
support for them will be removed in Solr 6.0:
* Create new field(s): POST to {{/_collection_/schema/fields}} or PUT to
{{/_collection_/schema/fields/_fieldname_}}
* Create new dynamic field(s): POST to {{/_collection_/schema/dynamicfields}}
or PUT to {{/_collection_/schema/dynamicfields/_glob_}}
* Create new copyField rules: POST to {{/_collection_/schema/copyfields}}.
Note that all of the above operations can instead be performed using the bulk
schema API, documented since the 5.0 Solr ref guide here:
https://cwiki.apache.org/confluence/display/solr/Schema+API
To be clear, read-only GET operations on the above-mentioned endpoints will not
be changed, deprecated or removed - they will continue to return information
about fields, dynamicFields and copyField rules.
> deprecate the one action only APIs for schema editing
> -
>
> Key: SOLR-6594
> URL: https://issues.apache.org/jira/browse/SOLR-6594
> Project: Solr
> Issue Type: Bug
>Reporter: Noble Paul
> Fix For: 5.5, 6.0
>
>
> with SOLR-6476 done and committed , we have more than one way of writing to
> schema . Having two different ways of doing the same thing is counter
> productive .
> I would like to mark them as deprecated and the calls to those APIs will
> succeed but will give a deprecation message in the output. The read APIs
> would continue to be the same , though .
> Details: the following operations have been deprecated as of Solr 5.5, and
> support for them will be removed in Solr 6.0:
> * Create new field(s): POST to {{/_collection_/schema/fields}} or PUT to
> {{/_collection_/schema/fields/_fieldname_}}
> * Create new dynamic field(s): POST to {{/_collection_/schema/dynamicfields}}
> or PUT to {{/_collection_/schema/dynamicfields/_glob_}}
> * Create new field type(s): POST to {{/_collection_/schema/fieldtypes}} or
> PUT to {{/_collection_/schema/fieldtypes/_name_}}
> * Create new copyField rule(s): POST to {{/_collection_/schema/copyfields}}.
> Note that all of the above operations can instead be performed using the bulk
> schema API, documented since the 5.0 Solr ref guide here:
> https://cwiki.apache.org/confluence/display/solr/Schema+API
> To be clear, read-only GET operations on the above-mentioned endpoints will
> not be changed, deprecated or removed - they will continue to return
> information about fields, dynamicFields and copyField rules.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-6594) deprecate the one action only APIs for schema editing
[
https://issues.apache.org/jira/browse/SOLR-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-6594:
-
Description:
with SOLR-6476 done and committed , we have more than one way of writing to
schema . Having two different ways of doing the same thing is counter
productive .
I would like to mark them as deprecated and the calls to those APIs will
succeed but will give a deprecation message in the output. The read APIs would
continue to be the same , though .
Details: the following operations have been deprecated as of Solr 5.5, and
support for them will be removed in Solr 6.0:
* Create new field(s): POST to {{/_collection_/schema/fields}} or PUT to
{{/_collection_/schema/fields/_fieldname_}}
* Create new dynamic field(s): POST to {{/_collection_/schema/dynamicfields}}
or PUT to {{/_collection_/schema/dynamicfields/_glob_}}
* Create new copyField rules: POST to {{/_collection_/schema/copyfields}}.
Note that all of the above operations can instead be performed using the bulk
schema API, documented since the 5.0 Solr ref guide here:
https://cwiki.apache.org/confluence/display/solr/Schema+API
To be clear, read-only GET operations on the above-mentioned endpoints will not
be changed, deprecated or removed - they will continue to return information
about fields, dynamicFields and copyField rules.
was:
with SOLR-6476 done and committed , we have more than one way of writing to
schema . Having two different ways of doing the same thing is counter
productive .
I would like to mark them as deprecated and the calls to those APIs will
succeed but will give a deprecation message in the output. The read APIs would
continue to be the same , though .
Details: the following operations have been deprecated as of Solr 5.5, and
support for them will be removed in Solr 6.0:
* Create new field(s): POST to {{/_collection_/schema/fields}} or
{{/_collection_/schema/fields/_fieldname_}}
* Create new dynamic field(s): POST to {{/_collection_/schema/dynamicfields}}
or {{/_collection_/schema/dynamicfields/_glob_}}
* Create new copyField rules: POST to {{/_collection_/schema/copyfields}}.
Note that all of the above operations can instead be performed using the bulk
schema API, documented since the 5.0 Solr ref guide here:
https://cwiki.apache.org/confluence/display/solr/Schema+API
To be clear, read-only GET operations on the above-mentioned endpoints will not
be changed, deprecated or removed - they will continue to return information
about fields, dynamicFields and copyField rules.
> deprecate the one action only APIs for schema editing
> -
>
> Key: SOLR-6594
> URL: https://issues.apache.org/jira/browse/SOLR-6594
> Project: Solr
> Issue Type: Bug
>Reporter: Noble Paul
> Fix For: 5.5, 6.0
>
>
> with SOLR-6476 done and committed , we have more than one way of writing to
> schema . Having two different ways of doing the same thing is counter
> productive .
> I would like to mark them as deprecated and the calls to those APIs will
> succeed but will give a deprecation message in the output. The read APIs
> would continue to be the same , though .
> Details: the following operations have been deprecated as of Solr 5.5, and
> support for them will be removed in Solr 6.0:
> * Create new field(s): POST to {{/_collection_/schema/fields}} or PUT to
> {{/_collection_/schema/fields/_fieldname_}}
> * Create new dynamic field(s): POST to {{/_collection_/schema/dynamicfields}}
> or PUT to {{/_collection_/schema/dynamicfields/_glob_}}
> * Create new copyField rules: POST to {{/_collection_/schema/copyfields}}.
> Note that all of the above operations can instead be performed using the bulk
> schema API, documented since the 5.0 Solr ref guide here:
> https://cwiki.apache.org/confluence/display/solr/Schema+API
> To be clear, read-only GET operations on the above-mentioned endpoints will
> not be changed, deprecated or removed - they will continue to return
> information about fields, dynamicFields and copyField rules.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-6594) deprecate the one action only APIs for schema editing
[
https://issues.apache.org/jira/browse/SOLR-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-6594:
-
Description:
with SOLR-6476 done and committed , we have more than one way of writing to
schema . Having two different ways of doing the same thing is counter
productive .
I would like to mark them as deprecated and the calls to those APIs will
succeed but will give a deprecation message in the output. The read APIs would
continue to be the same , though .
Details: the following operations have been deprecated as of Solr 5.5, and
support for them will be removed in Solr 6.0:
* Create new field(s): POST to {{/_collection_/schema/fields}} or
{{/_collection_/schema/fields/_fieldname_}}
* Create new dynamic field(s): POST to {{/_collection_/schema/dynamicfields}}
or {{/_collection_/schema/dynamicfields/_glob_}}
* Create new copyField rules: POST to {{/_collection_/schema/copyfields}}.
Note that all of the above operations can instead be performed using the bulk
schema API, documented since the 5.0 Solr ref guide here:
https://cwiki.apache.org/confluence/display/solr/Schema+API
To be clear, read-only GET operations on the above-mentioned endpoints will not
be changed, deprecated or removed - they will continue to return information
about fields, dynamicFields and copyField rules.
was:
with SOLR-6476 done and committed , we have more than one way of writing to
schema . Having two different ways of doing the same thing is counter
productive .
I would like to mark them as deprecated and the calls to those APIs will
succeed but will give a deprecation message in the output. The read APIs would
continue to be the same , though .
Details: the following operations have been deprecated as of Solr 5.5, and
support for them will be removed in Solr 6.0:
* Create new field(s): POST to {{/_collection_/schema/fields}} or
{{/_collection_/schema/fields/_fieldname_}}
* Create new dynamic field(s): POST to {{/_collection_/schema/dynamicfields}}
or {{/_collection_/schema/dynamicfields/_glob_}}
* Create new copyField rules: POST to {{/_collection_/schema/copyfields}}.
Note that all of the above operations can instead be performed using the bulk
schema API, documented since the 5.0 Solr ref guide here:
https://cwiki.apache.org/confluence/display/solr/Schema+API
To be clear, GET operations on the above-mentioned endpoints will not be
deprecated or removed.
> deprecate the one action only APIs for schema editing
> -
>
> Key: SOLR-6594
> URL: https://issues.apache.org/jira/browse/SOLR-6594
> Project: Solr
> Issue Type: Bug
>Reporter: Noble Paul
> Fix For: 5.5, 6.0
>
>
> with SOLR-6476 done and committed , we have more than one way of writing to
> schema . Having two different ways of doing the same thing is counter
> productive .
> I would like to mark them as deprecated and the calls to those APIs will
> succeed but will give a deprecation message in the output. The read APIs
> would continue to be the same , though .
> Details: the following operations have been deprecated as of Solr 5.5, and
> support for them will be removed in Solr 6.0:
> * Create new field(s): POST to {{/_collection_/schema/fields}} or
> {{/_collection_/schema/fields/_fieldname_}}
> * Create new dynamic field(s): POST to {{/_collection_/schema/dynamicfields}}
> or {{/_collection_/schema/dynamicfields/_glob_}}
> * Create new copyField rules: POST to {{/_collection_/schema/copyfields}}.
> Note that all of the above operations can instead be performed using the bulk
> schema API, documented since the 5.0 Solr ref guide here:
> https://cwiki.apache.org/confluence/display/solr/Schema+API
> To be clear, read-only GET operations on the above-mentioned endpoints will
> not be changed, deprecated or removed - they will continue to return
> information about fields, dynamicFields and copyField rules.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-6594) deprecate the one action only APIs for schema editing
[
https://issues.apache.org/jira/browse/SOLR-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-6594:
-
Description:
with SOLR-6476 done and committed , we have more than one way of writing to
schema . Having two different ways of doing the same thing is counter
productive .
I would like to mark them as deprecated and the calls to those APIs will
succeed but will give a deprecation message in the output. The read APIs would
continue to be the same , though .
Details: the following operations have been deprecated as of Solr 5.5, and
support for them will be removed in Solr 6.0:
* Create new field(s): POST to {{/_collection_/schema/fields}} or
{{/_collection_/schema/fields/_fieldname_}}
* Create new dynamic field(s): POST to {{/_collection_/schema/dynamicfields}}
or {{/_collection_/schema/dynamicfields/_glob_}}
* Create new copyField rules: POST to {{/_collection_/schema/copyfields}}.
Note that all of the above operations can instead be performed using the bulk
schema API, documented since the 5.0 Solr ref guide here:
https://cwiki.apache.org/confluence/display/solr/Schema+API
To be clear, GET operations on the above-mentioned endpoints will not be
deprecated or removed.
was:
with SOLR-6476 done and committed , we have more than one way of writing to
schema . Having two different ways of doing the same thing is counter
productive .
I would like to mark them as deprecated and the calls to those APIs will
succeed but will give a deprecation message in the output. The read APIs would
continue to be the same , though .
> deprecate the one action only APIs for schema editing
> -
>
> Key: SOLR-6594
> URL: https://issues.apache.org/jira/browse/SOLR-6594
> Project: Solr
> Issue Type: Bug
>Reporter: Noble Paul
> Fix For: 5.5, 6.0
>
>
> with SOLR-6476 done and committed , we have more than one way of writing to
> schema . Having two different ways of doing the same thing is counter
> productive .
> I would like to mark them as deprecated and the calls to those APIs will
> succeed but will give a deprecation message in the output. The read APIs
> would continue to be the same , though .
> Details: the following operations have been deprecated as of Solr 5.5, and
> support for them will be removed in Solr 6.0:
> * Create new field(s): POST to {{/_collection_/schema/fields}} or
> {{/_collection_/schema/fields/_fieldname_}}
> * Create new dynamic field(s): POST to {{/_collection_/schema/dynamicfields}}
> or {{/_collection_/schema/dynamicfields/_glob_}}
> * Create new copyField rules: POST to {{/_collection_/schema/copyfields}}.
> Note that all of the above operations can instead be performed using the bulk
> schema API, documented since the 5.0 Solr ref guide here:
> https://cwiki.apache.org/confluence/display/solr/Schema+API
> To be clear, GET operations on the above-mentioned endpoints will not be
> deprecated or removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
