Skip to content

Elastic.Transport.UnexpectedTransportException with Ingest.GetPipelineAsync #8083

@gpetrou

Description

@gpetrou

Elastic.Clients.Elasticsearch version: 8.13.1

Elasticsearch version: 8.11

.NET runtime version: 8.0

Operating system version:

Description of the problem including expected versus actual behavior:
When trying to use elasticsearchClient.Ingest.GetPipelineAsync(r => r.Id("pipeline_test")); there is an exception.
This used to work in 8.12.1.

 'The converter 'Elastic.Clients.Elasticsearch.Ingest.ProcessorConverter' read too much or not enough. Path: $.pipeline_test.processors[0] | LineNumber: 10 | BytePositionInLine: 7.'

Steps to reproduce:
1.
2.
3.

Expected behavior
A clear and concise description of what you expected to happen.

Provide ConnectionSettings (if relevant):

Provide DebugInformation (if relevant):

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions