You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So for users sticking to _doc for the lifetime of 7.0, it's necessary to pass this query/parameter.
It'd be great if support for this would be added. To avoid having to follow up future parameters, would it make sense to just allow passing any arbitrary parameters that the user elects to?
The text was updated successfully, but these errors were encountered:
To avoid having to follow up future parameters, would it make sense to just allow passing any arbitrary parameters that the user elects to?
To close this, specifying params={} allows passing arbitrary parameters -- serialization needs to be done by the user though, so best used only for strings. Thanks @honzakral .
This parameter (include_type_name) doesn't seem to be documented like the others (eg: wait_for_active_shards). Should it be?
I know this issue is closed, but it seemed like the most appropriate place for it.)
indices.create supports
wait_for_active_shards
however, the recent Elasticsearch commit: elastic/elasticsearch#38270 forces the use of?include_type_name=true
to allow use of the_doc
type in 7.0. Types are deprecated in 7.0 and will be completely removed in 8.0.So for users sticking to _doc for the lifetime of 7.0, it's necessary to pass this query/parameter.
It'd be great if support for this would be added. To avoid having to follow up future parameters, would it make sense to just allow passing any arbitrary parameters that the user elects to?
The text was updated successfully, but these errors were encountered: