mattcasters opened a new pull request, #9210: URL: https://github.com/apache/hop/pull/9210
Binary-file Avro output writes one file with `AvroIO.writeGenericRecords` and `withoutSharding()`. The filename, including date and time, is resolved when the pipeline is submitted. A transform copy number or a partition number in the filename is refused, as are nested Avro paths and enum fields. Binary-field and JSON-field output still go through the generic handler. Avro file input reads the file named by each incoming row and appends each record to that row. A positive row limit is the most records a worker emits. `BeamAvroFileIOTest` runs both paths on the Direct runner (6 tests, 0 failures). Remote runners were not exercised. `AvroOutput.createAvroSchema` is now a public static method so the handler and the local transform share one schema. fixes #2358 ------------------------ Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily: - [ ] Run `mvn clean install apache-rat:check` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [x] If you have a group of commits related to the same change, please squash your commits into one and force push your branch using `git rebase -i`. - [x] Mention the appropriate issue in your description (for example: `addresses #123`), if applicable. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [x] I hereby declare this contribution to be licensed under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- 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]
