-
Notifications
You must be signed in to change notification settings - Fork 25k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
exists template needs a template name #25988
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The flat_settings
parameter should remain, it is supported on HEAD
template requests.
"description": "The comma separated names of the index templates" | ||
} | ||
}, | ||
"params": { | ||
"flat_settings": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
flat_settings
is supported on HEAD
requests; the behavior of GET
and HEAD
are aligned when both methods are supported.
@@ -8,15 +8,11 @@ | |||
"parts": { | |||
"name": { | |||
"type": "list", | |||
"required": false, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change is correct.
Thanks for the review, updated the commit. Out of curiosity, what does |
Per the HTTP specification, when an endpoint supports both the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
@honzakral just going through older open PRs, seems like this one is ready to merge. Do you want to go ahead or should we do it? |
@cbuescher, please go ahead, I am not up-to-date with all the necessary backporting policies and other steps. Thank you! |
@honzakral not entirely sure how rest-api-specs are used, but I suppose this change should be applied to all active branches down to 5.6? |
I'd say yes, but not sure what is the current status of freezes/branch policies etc. That is why I try to stay away from merging patches to es myself since I am no longer familiar enough with the process... |
* master: (63 commits) [Docs] Fix note in bucket_selector [Docs] Fix indentation of examples (elastic#27168) [Docs] Clarify `span_not` query behavior for non-overlapping matches (elastic#27150) [Docs] Remove first person "I" from getting started (elastic#27155) [Docs] Correct link target for datatype murmur3 (elastic#27143) Fix division by zero in phrase suggester that causes assertion to fail Enable Docstats with totalSizeInBytes for 6.1.0 Adds average document size to DocsStats (elastic#27117) Upgrade Painless from ANTLR 4.5.1-1 to ANTLR 4.5.3. (elastic#27153) Exists template needs a template name (elastic#25988) [Tests] Fix occasional test failure due to two random values being the same Fix beidermorse phonetic token filter for unspecified `languageset` (elastic#27112) Fix max score tracking with field collapsing (elastic#27122) [Doc] Add Ingest CSV Processor Plugin to plugin as a community plugin (elastic#27105) Removed the beta tag from cross-cluster search fixed typo in ConstructingObjectParse (elastic#27129) Allow for the Painless Definition to have multiple instances (elastic#27096) Apply missing request options to the expand phase (elastic#27118) Only pull SegmentReader once in getSegmentInfo (elastic#27121) Fix BWC for discovery stats ...
running
curl -X HEAD localhost:9200/_template
results in405 Method Not Allowed