clairemcginty opened a new pull request, #1241: URL: https://github.com/apache/parquet-mr/pull/1241
https://issues.apache.org/jira/browse/PARQUET-2413 Adds support for Configurable `extraMetadata` in Parquet file footer. This makes it easier for users to migrate from Avro to Parquet (since Avro [supports custom metadata keys](https://github.com/apache/avro/blob/release-1.11.3/lang/java/avro/src/main/java/org/apache/avro/file/DataFileWriter.java#L285)). I chose this approach (parsing values from a preset `Configuration` key prefix) because (a) `Configuration` is already Stringable, so no need to worry about object-to-String conversion, and (b) it doesn't require any API changes (i.e. adding `withExtraMetadata` Builder options to all Parquet writers/implementations). Alternate approaches: - Add `withExtraMetadata` Builder method to `ParquetWriter`; in `ParquetWriter#build`, append all to the value of `WriteContext#getExtraMetadata()`. - Add `extraMetadata` class variables to all WriteSupport _implementations_, and pass to `WriteContext` in `WriteSupport#init` ([i.e. AvroWriteSupport](https://github.com/apache/parquet-mr/blob/apache-parquet-1.13.1/parquet-avro/src/main/java/org/apache/parquet/avro/AvroWriteSupport.java#L131-L152)). Let me know if either of those approaches are preferable to this one! ### Jira - [x] My PR addresses the following [Parquet Jira](https://issues.apache.org/jira/browse/PARQUET/) issues and references them in the PR title. For example, "PARQUET-1234: My Parquet PR" - https://issues.apache.org/jira/browse/PARQUET-XXX - In case you are adding a dependency, check if the license complies with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). ### Tests - [x] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason: ### Commits - [x] My commits all reference Jira issues in their subject lines. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)": 1. Subject is separated from body by a blank line 1. Subject is limited to 50 characters (not including Jira issue reference) 1. Subject does not end with a period 1. Subject uses the imperative mood ("add", not "adding") 1. Body wraps at 72 characters 1. Body explains "what" and "why", not "how" ### Style - [z] My contribution adheres to the code style guidelines and Spotless passes. - To apply the necessary changes, run `mvn spotless:apply -Pvector-plugins` ### Documentation - [x] In case of new functionality, my PR adds documentation that describes how to use it. - All the public functions and the classes in the PR contain Javadoc that explain what it does -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
