java.lang.IllegalArgumentException: Class class co.elastic.clients.elasticsearch.core.bulk.UpdateOperation cannot be read from JSON
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- elasticsearch, java
- Domain
- backend-api-design, search
Research direction
Start by reproducing the exception from the supplied BulkOperation and UpdateOperation builder snippet using the reported Elasticsearch Java Client 8.5.3 or 8.4.1 and JDK 11. Inspect the withJson entry point and the JSON input shown in the attached example; done means the update operation can be read from JSON without the reported IllegalArgumentException.
Written by the indexing model from the issue text.
Description
Java API client version
8.5.3 and 8.4.1
Java version
jdk11
Elasticsearch Version
8.4.1
Problem description
java.lang.IllegalArgumentException: Class class co.elastic.clients.elasticsearch.core.bulk.UpdateOperation cannot be read from JSON
StringReader reader = new StringReader(json);
BulkOperation updateOp = new BulkOperation.Builder()
.update(new UpdateOperation.Builder<>()
.index(topic)
.id("1")
.withJson(reader)
.retryOnConflict(Math.min(1, 5))
.build())
.build();
- Dominant language
- Java
- Stars
- 524
- Forks
- 299
- Avg merge
- 16m
- Merged PRs (30d)
- 13
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from elastic/elasticsearch-java
-
Delete By Query deserialization will not account for search failuresPossibly taken @l-trotta claimed this today. Open
elastic/elasticsearch-java#1349 · 1 assignee ·
Maintainers usually reply within 1 day
-
Nested index settings that do not end up deserialized in otherSettings leads to requiring properties on parent JSON nodesPossibly taken @l-trotta claimed this today. OpenArea: Specification Category: Bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
elastic/elasticsearch-java#1347 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
RestClientTransport sends bulk bodies as one HTTP chunk / TLS record / syscall per NDJSON buffer, burning ~45x the reactor CPU of the HLRCPossibly taken @l-trotta claimed this 16 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 72/100
elastic/elasticsearch-java#1339 · 5 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
elastic/elasticsearch-java#1212 · 8 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
elastic/elasticsearch-java#1165 · 5 comments ·
Maintainers usually reply within 1 day
All issues in elastic/elasticsearch-java
Similar issues
-
Update license yearOpen0 - Backlog 1 - Ready documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
cbor
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
FasterXML/jackson-dataformats-binary#844 ·
Maintainers usually reply within 1 day
-
Issue: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
OpenAPITools/openapi-generator#25107 ·
Maintainers usually reply within 1 day
-
improvement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/iceberg#18351 · 1 comment ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
repowise-dev/repowise#2945 · 1 comment ·
Maintainers usually reply within 1 day