Skip to content
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

Elastic.Transport.UnexpectedTransportException with Ingest.GetPipelineAsync #8083

Closed
gpetrou opened this issue Apr 5, 2024 · 3 comments · Fixed by #8087
Closed

Elastic.Transport.UnexpectedTransportException with Ingest.GetPipelineAsync #8083

gpetrou opened this issue Apr 5, 2024 · 3 comments · Fixed by #8087
Labels
8.x Relates to 8.x client version Area: Generator Category: Bug

Comments

@gpetrou
Copy link
Contributor

gpetrou commented Apr 5, 2024

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):

@gpetrou gpetrou added 8.x Relates to 8.x client version Category: Bug labels Apr 5, 2024
@flobernd
Copy link
Member

flobernd commented Apr 5, 2024

Hi @gpetrou,

could you please show me how you configured your pipeline_test. Especially the used processors would be nice to know.

Thank you!

@gpetrou
Copy link
Contributor Author

gpetrou commented Apr 5, 2024

I just used:

PUT: /_ingest/pipeline/pipeline_test

{
  "description": "description_test1",
  "processors": [
    {
      "geoip": {
        "field": "location_1",
        "ignore_missing": true
      }
    },
    {
      "user_agent": {
        "field": "user_agent_1",
        "ignore_missing": true
      }
    }
  ]
}

@flobernd
Copy link
Member

flobernd commented Apr 5, 2024

Thanks! I was able to reproduce the issue. A fix will be released soon, together with the Fields improvements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8.x Relates to 8.x client version Area: Generator Category: Bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants