[
https://issues.apache.org/jira/browse/SOLR-18214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christos Malliaridis updated SOLR-18214:
----------------------------------------
Description:
h2. Description
[According to our
documentation|https://solr.apache.org/guide/solr/latest/configuration-guide/configsets-api.html#configsets-create],
when creating a new configset with the v2 APi, the base configset field
{{baseConfigset}} is optional and defaults to {{{}_default{}}}. This raises two
issues:
* When the configset {{_default}} is not available (users are able to remove
and not create it at all), it cannot be used as the default value
* When no {{baseConfigset}} is provided, it defaults to {{null}} and the
request fails, as {{null}} is not allowed
h2. Expected Behavior
The {{baseConfigset}} is truly optional and can be omitted in the request body.
h2. Actual Behavior
The {{baseConfigset}} field is mandatory and cannot be omitted.
h2. Additional Information
Please not that in theory it is possible to create a configset from scratch and
not use a {{baseConfigset}} at all. If the {{baseConfigset}} is omitted and we
set the value to {{_default}} this is no longer possible.
Additionally, when using a {{baseConfigset}} the new configset is not updated
when its {{baseConfigset}} is updated (no linking exists, base configset is
just cloned). This may however be an expected behavior and may require
clarification in documentation.
Another discovery is that when the user deletes all configsets, this endpoint
can no longer be used as it is right now, because without being able to select
a base configset (no configset available) this endpoint fails. The user has to
upload a configset as zip to workaround this issue.
was:
h2. Description
[According to our
documentation|https://solr.apache.org/guide/solr/latest/configuration-guide/configsets-api.html#configsets-create],
when creating a new configset with the v2 APi, the base configset field
{{baseConfigset}} is optional and defaults to {{{}_default{}}}. This raises two
issues:
* When the configset {{_default}} is not available (users are able to remove
and not create it at all), it cannot be used as the default value
* When no {{baseConfigset}} is provided, it defaults to {{null}} and the
request fails, as {{null}} is not allowed
h2. Expected Behavior
The {{baseConfigset}} is truly optional and can be omitted in the request body.
h2. Actual Behavior
The {{baseConfigset}} field is mandatory and cannot be omitted.
h2. Additional Information
Please not that in theory it is possible to create a configset from scratch and
not use a {{baseConfigset}} at all. If the {{baseConfigset}} is omitted and we
set the value to {{_default}} this is no longer possible.
Additionally, when using a {{baseConfigset}} the new configset is not updated
when its {{baseConfigset}} is updated (no linking exists, base configset is
just cloned). This may however be an expected behavior and may require
clarification in documentation.
> Base configset during configset creation is not optional
> --------------------------------------------------------
>
> Key: SOLR-18214
> URL: https://issues.apache.org/jira/browse/SOLR-18214
> Project: Solr
> Issue Type: Bug
> Components: configset-api, v2 API
> Affects Versions: 10.0
> Reporter: Christos Malliaridis
> Priority: Major
> Labels: V2, api, configset, newdev
>
> h2. Description
> [According to our
> documentation|https://solr.apache.org/guide/solr/latest/configuration-guide/configsets-api.html#configsets-create],
> when creating a new configset with the v2 APi, the base configset field
> {{baseConfigset}} is optional and defaults to {{{}_default{}}}. This raises
> two issues:
> * When the configset {{_default}} is not available (users are able to remove
> and not create it at all), it cannot be used as the default value
> * When no {{baseConfigset}} is provided, it defaults to {{null}} and the
> request fails, as {{null}} is not allowed
> h2. Expected Behavior
> The {{baseConfigset}} is truly optional and can be omitted in the request
> body.
> h2. Actual Behavior
> The {{baseConfigset}} field is mandatory and cannot be omitted.
> h2. Additional Information
> Please not that in theory it is possible to create a configset from scratch
> and not use a {{baseConfigset}} at all. If the {{baseConfigset}} is omitted
> and we set the value to {{_default}} this is no longer possible.
> Additionally, when using a {{baseConfigset}} the new configset is not updated
> when its {{baseConfigset}} is updated (no linking exists, base configset is
> just cloned). This may however be an expected behavior and may require
> clarification in documentation.
> Another discovery is that when the user deletes all configsets, this endpoint
> can no longer be used as it is right now, because without being able to
> select a base configset (no configset available) this endpoint fails. The
> user has to upload a configset as zip to workaround this issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
