Original install method (e.g. download page, yum, from source, etc.):
deb package
Describe the bug:
When I remove index setting (JSON line) and click "Save" Kibana shows "Successfully updated settings for index ..." but no actual update request was sent to the server, so setting wasn't actually removed. If I change value to null then Kibana properly sends request to /api/index_management/settings/my-index-name.
Steps to reproduce:
Go to Management app > Index Management > Indices
Click on index
Go to Edit settings tab
Change "index.priority": "1", to "index.priority": "2",
Click Save, return to Edit settings tab
Remove line with "index.priority": "2",`
Click Save, return to Edit settings tab
Setting is still there with its old value
Bonus bug: click on another index name, settings form disappears.
Expected behavior:
Kibana recognizes change and issues request to sever that changes removed setting (sets it to null).
Kibana version: 7.4.0
Elasticsearch version: 7.4.0
Server OS version: Uubntu 16.04
Browser version: Firefox 69.0.2
Browser OS version: Windows 10
Original install method (e.g. download page, yum, from source, etc.): deb package
Describe the bug: When I remove index setting (JSON line) and click "Save" Kibana shows "Successfully updated settings for index ..." but no actual update request was sent to the server, so setting wasn't actually removed. If I change value to
null
then Kibana properly sends request to/api/index_management/settings/my-index-name
.Steps to reproduce:
"index.priority": "1",
to"index.priority": "2",
Expected behavior: Kibana recognizes change and issues request to sever that changes removed setting (sets it to
null
).