Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Add support for BIGINT aka LONG.
Details
When an input topic has a Long in the Avro schema, the resulting pipeline was trying to cast from Long down to Int, causing a ClassCastException within Flink (see below). This is because
AvroConverter
was essentially equating Ints and Longs, which works one way but not the other!Testing Done
I added a BIGINT field to the built-in PERSON table. The existing integration tests should validate this now works.
Appendix
Relevant stack trace: