title: How is deprecated.legacy-timestamp supposed to work in Presto 0.220?
body: <p>I'm encountering an issue with reading timestamps properly, without any automatic conversions on Presto on EMR. </p>
  
  <p>Example: within the AWS Glue catalog, i have a table with timestamp columns in UTC time (data type timestamp). When querying in Athena, they return as expected. When querying in Presto on EMR (EMR 5.26, Presto 0.220), there is an automatic conversion happening to a different time zone. </p>
  
  <p>Presto docs describe a method of disabling this behavior here - <a href="https://prestosql.io/docs/current/language/timestamp" rel="nofollow noreferrer">https://prestosql.io/docs/current/language/timestamp</a>.</p>
  
  <p><code>The legacy semantics can be enabled using the deprecated.legacy-timestamp config property. Setting it to true (the default) enables the legacy semantics, whereas setting it to false enables the new semantics.</code></p>
  
  <p>They outline their result differences with this option set to true vs false at the bottom</p>
  
  <p><code>Query: SELECT TIME '10:00:00 Asia/Kathmandu' AT TIME ZONE 'UTC'
  Legacy result: 04:30:00.000 UTC
  New result: 04:15:00.000 UTC</code></p>
  
  <p>After including <code>deprecated.legacy-timestamp</code> set to <code>true</code> in my EMR config (within presto-config), I'm still getting the new result according to this test query, (and my UTC timestamps are still being auto converted).</p>
  
  <p>Any suggestions on what else i need to do to enable the legacy timestamp behavior?</p>