Abacn opened a new pull request, #39414: URL: https://github.com/apache/beam/pull/39414
**Please** add a meaningful description for your change here In AvroUtils.toGenericRecord, https://github.com/apache/beam/blob/83fcb2f9cdfa630f63743bde1c48c88c49812e59/sdks/java/extensions/avro/src/main/java/org/apache/beam/sdk/extensions/avro/schemas/utils/AvroUtils.java#L646 A SqlTypes.DATE field will resolve to schema of date logic type backed by an INT: https://github.com/apache/beam/blob/83fcb2f9cdfa630f63743bde1c48c88c49812e59/sdks/java/extensions/avro/src/main/java/org/apache/beam/sdk/extensions/avro/schemas/utils/AvroUtils.java#L1218 However, its value is set to a long: https://github.com/apache/beam/blob/83fcb2f9cdfa630f63743bde1c48c88c49812e59/sdks/java/extensions/avro/src/main/java/org/apache/beam/sdk/extensions/avro/schemas/utils/AvroUtils.java#L1383 LocalDate.toEpochDay returns a long This causes error on encoding: ``` SEVERE: Error handling executePlan org.apache.avro.UnresolvedUnionException: Not in union ["null",{"type":"int","logicalType":"date"}]: 10957 (field=d) at org.apache.avro.generic.GenericDatumWriter.writeField(GenericDatumWriter.java:247) at org.apache.avro.generic.GenericDatumWriter.writeRecord(GenericDatumWriter.java:234) at org.apache.avro.generic.GenericDatumWriter.writeWithoutConversion(GenericDatumWriter.java:145) at org.apache.avro.generic.GenericDatumWriter.write(GenericDatumWriter.java:95) at org.apache.avro.generic.GenericDatumWriter.write(GenericDatumWriter.java:82) at org.apache.beam.sdk.extensions.avro.coders.AvroCoder.encode(AvroCoder.java:466) at org.apache.beam.sdk.coders.Coder.encode(Coder.java:140) at org.apache.beam.sdk.util.CoderUtils.encodeToSafeStream(CoderUtils.java:86) at org.apache.beam.sdk.util.CoderUtils.encodeToByteArray(CoderUtils.java:70) at org.apache.beam.sdk.util.CoderUtils.encodeToByteArray(CoderUtils.java:55) at org.apache.beam.sdk.util.CoderUtils.clone(CoderUtils.java:168) at org.apache.beam.runners.core.InMemoryStateInternals.uncheckedClone(InMemoryStateInternals.java:910) ``` ------------------------ Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily: - [ ] Mention the appropriate issue in your description (for example: `addresses #123`), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment `fixes #<ISSUE NUMBER>` instead. - [ ] Update `CHANGES.md` with noteworthy changes. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). See the [Contributor Guide](https://beam.apache.org/contribute) for more tips on [how to make review process smoother](https://github.com/apache/beam/blob/master/CONTRIBUTING.md#make-the-reviewers-job-easier). To check the build health, please visit [https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md) GitHub Actions Tests Status (on master branch) ------------------------------------------------------------------------------------------------ [](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule) [](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule) [](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule) [](https://github.com/apache/beam/actions?query=workflow%3A%22Go+tests%22+branch%3Amaster+event%3Aschedule) See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more information about GitHub Actions CI or the [workflows README](https://github.com/apache/beam/blob/master/.github/workflows/README.md) to see a list of phrases to trigger workflows. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
