-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Closed as not planned
Labels
8.xRelates to a 8.x client versionRelates to a 8.x client versionCategory: QuestionState: Awaiting ResponseState: Stale
Description
Elastic.Clients.Elasticsearch version: 8.16.0
Elasticsearch version: 8.12.2
.NET runtime version: 8.0
Operating system version:
Description of the problem including expected versus actual behavior:
In previous versions, we were able to pass RequestParameters in ElasticsearchClient.Transport.RequestAsync method.
It seems that we cannot do that anymore. According to the release notes there were some changes to the Transport library, but once again, it is unclear what to do about them.
Steps to reproduce:
UpdateDocumentRequestParameters : RequestParameters
{
public Refresh Refresh
{
get => Q<Refresh>("refresh");
init => Q("refresh", value);
}
}
UpdateDocumentRequestParameters updateDocumentRequestParameters = new()
{
Refresh = refresh
};
StringResponse response = await _elasticsearchClient.Transport.RequestAsync<StringResponse>(
Elastic.Transport.HttpMethod.POST,
$"{indexName}/_update/{id}",
PostData.String(postData),
updateDocumentRequestParameters,
cancellationToken).ConfigureAwait(false);
How are we supposed to convert such code?
Expected behavior
Provide ConnectionSettings (if relevant):
Provide DebugInformation (if relevant):
Metadata
Metadata
Assignees
Labels
8.xRelates to a 8.x client versionRelates to a 8.x client versionCategory: QuestionState: Awaiting ResponseState: Stale