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
To be able to access restrict the usage of ES the settings rest.action.multi.allow_explicit_index should be set to false, this will make it possible to disallow _bulk-operations where the index are included in the bulk-operations. (elastic/elasticsearch#3636)
When I look into the src of NEST the NestSerializer.SerializeBulkDescriptor-method automatic assign the index and type a value if it not already are set, this make it impossible to get them as null.
What is the best solution to solve the problem? Settings on IConnectionSettings so that automatic assigning values to the index can be turned on/off for the ElasticSearchClient, settings should be used for the bulk and multiserach operations.
The text was updated successfully, but these errors were encountered:
@Tasteful that ES settings is completely new to me! We should probably spot when the index/type is the same as the one provided in the url and null it.
To be able to access restrict the usage of ES the settings rest.action.multi.allow_explicit_index should be set to false, this will make it possible to disallow _bulk-operations where the index are included in the bulk-operations. (elastic/elasticsearch#3636)
example on current request
the server will then respond with
To get this to work the request should be without the _index and _type in the body or the value should be null.
When I look into the src of NEST the NestSerializer.SerializeBulkDescriptor-method automatic assign the index and type a value if it not already are set, this make it impossible to get them as null.
What is the best solution to solve the problem? Settings on IConnectionSettings so that automatic assigning values to the index can be turned on/off for the ElasticSearchClient, settings should be used for the bulk and multiserach operations.
The text was updated successfully, but these errors were encountered: