title: Problems when writing parquet with timestamps prior to 1900 in AWS Glue 3.0
body: <p>When switching from Glue 2.0 to 3.0, which means also switching from Spark 2.4 to 3.1.1,
  my jobs start to fail when processing timestamps prior to 1900 with this error:</p>
  <pre><code>An error occurred while calling z:org.apache.spark.api.python.PythonRDD.runJob.
  You may get a different result due to the upgrading of Spark 3.0: reading dates before 1582-10-15 or timestamps before 1900-01-01T00:00:00Z from Parquet INT96 files can be ambiguous, 
  as the files may be written by Spark 2.x or legacy versions of Hive, which uses a legacy hybrid calendar that is different from Spark 3.0+s Proleptic Gregorian calendar.
  See more details in SPARK-31404.
  You can set spark.sql.legacy.parquet.int96RebaseModeInRead to 'LEGACY' to rebase the datetime values w.r.t. the calendar difference during reading. 
  Or set spark.sql.legacy.parquet.int96RebaseModeInRead to 'CORRECTED' to read the datetime values as it is.
  </code></pre>
  <p>I tried everything to set the <code>int96RebaseModeInRead</code> config in Glue, even contacted the Support, but it seems that currently Glue is overwriting that flag and you can not set it yourself.</p>
  <p>If anyone knows a workaround, that would be great. Otherwise I will continue with Glue 2.0. and wait for the Glue dev team to fix this.</p>