[VL] Align the timezone of timestamp partition value with Velox

[rui-mo]

What changes were proposed in this pull request?

In this way we don't need additional change for Velox.

How was this patch tested?

under test

[github-actions]

Thanks for opening a pull request!

Could you open an issue for this pull request on Github Issues?

https://github.com/apache/incubator-gluten/issues

Then could you also rename commit message and pull request title in the following format?

[GLUTEN-${ISSUES_ID}][COMPONENT]feat/fix: ${detailed message}

See also:

• Other pull requests

[surnaik]

Hey @rui-mo , when we construct Velox Timestamp object from either INT96 or INT64, is the timezone by default "America/Los Angeles"? - https://github.com/facebookincubator/velox/blob/c395c553bd9627b4a3211e34f16bb1949bbcd43a/velox/dwio/parquet/reader/TimestampColumnReader.h#L95

If the default timezone here is "America/Los Angeles", should we offset it assuming the underlying timezone for the timestamp is UTC?

[rui-mo]

Hi @surnaik, this issue is about the timestamp partition value, which is converted from string in Velox. During this conversion, the default timezone (which is set as "America/Los Angeles" in Velox) is used. This PR tries to adopt the same timezone as Velox to see if we can remove this additional change: oap-project/velox@567f7df.

https://github.com/facebookincubator/velox/blob/c395c553bd9627b4a3211e34f16bb1949bbcd43a/velox/connectors/hive/SplitReader.cpp#L58-L60

https://github.com/facebookincubator/velox/blob/c395c553bd9627b4a3211e34f16bb1949bbcd43a/velox/type/Timestamp.cpp#L96-L101