PARQUET-1126: Write unencrypted Parquet files without Hadoop

[dlvenable]

If you want to write an unencrypted Parquet file without Hadoop, the existing code will use Hadoop to try to get encryption properties.

parquet-java/parquet-hadoop/src/main/java/org/apache/parquet/hadoop/ParquetWriter.java

Lines 388 to 393 in fbe13d8

	if (encryptionProperties == null) {
	String path = file == null ? null : file.getPath();
	Configuration hadoopConf = ConfigurationUtil.createHadoopConfiguration(conf);
	encryptionProperties = ParquetOutputFormat.createEncryptionProperties(
	hadoopConf, path == null ? null : new Path(path), writeContext);
	}

However, if you have these null, we really didn't need to go through Hadoop. Also, it calls a helper method in ParquetOutputFormat. This class inherits from Hadoop's FileOutputFormat. So calling this method at all, requires Hadoop classes. To resolve this, I moved this helper into a package-protected EncryptionPropertiesHelper class.

Make sure you have checked all steps below.

Jira

• My PR addresses the following Parquet Jira issues and references
  them in the PR title. For example, "PARQUET-1234: My Parquet PR"
  • https://issues.apache.org/jira/browse/PARQUET-1126
  • In case you are adding a dependency, check if the license complies with
    the ASF 3rd Party License Policy.

Tests

• My PR adds the following unit tests OR does not need testing for this extremely good reason:

testLoadEncPropertiesFactoryParquetConfiguration

Commits

• 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":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters (not including Jira issue reference)
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

Style

• My contribution adheres to the code style guidelines and Spotless passes.
  • To apply the necessary changes, run mvn spotless:apply -Pvector-plugins

Documentation

• 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

[ggershinsky]

this will trigger a second loading of the factory class. Can we replace ll40-41 with the l52 code?

[dlvenable]

@ggershinsky , Thank you for taking a look at the PR. This is a good point. I corrected it in the latest commit.