Avro adapter: AvroStringConsumer should use readString instead of readBytes

Open
#832 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
55/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
java
Domain
data

Research direction

Start in AvroStringConsumer.java at the consume method and inspect how the decoder is used for Avro strings. Reproduce the ResolvingDecoder case described in the issue, then verify that the consumer handles string data without the reported AvroTypeException.

Written by the indexing model from the issue text.

Description

Type: bug
Describe the bug, including details regarding any error messages, version, and platform.

Currently, AvroStringConsumer calls decoder.readBytes instead of decoder.readString. This can lead to exceptions when using ResolvingDecoder:

org.apache.avro.AvroTypeException: Attempt to process a bytes when a string was expected.

	at org.apache.avro.io.parsing.Parser.advance(Parser.java:91)
	at org.apache.avro.io.ResolvingDecoder.readBytes(ResolvingDecoder.java:236)
	at org.apache.arrow.adapter.avro.consumers.AvroStringConsumer.consume(AvroStringConsumer.java:41)
Dominant language
Java
Stars
95
Forks
154
Avg merge
2d 10h
Merged PRs (30d)
11

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/arrow-java

All issues in apache/arrow-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.