Timezone Conversion Issue with INT96 Timestamps During Parquet Stream Load in Doris

[sjahongir]

Issue Description:

I'm encountering an issue when using Doris' Stream Load feature to load Parquet files that contain INT96-formatted timestamps. The timestamps appear to be automatically converted to UTC+8 during the load process, which is not the expected behavior. These timestamps should be absolute date, but Doris seems to be applying an incorrect timezone offset, leading to discrepancies in the data.

Steps to Reproduce:
Create a Parquet file with INT96 timestamps using a tool like Parquet.Net.
Use Doris Stream Load feature to load the Parquet file.
Observe that the timestamps are converted to UTC+8 during the load process.
Expected Behavior:
The INT96 timestamps should be absolute date, or Doris should allow configuration of the timezone for timestamp fields during the load. Alternatively, the timestamps should be loaded without any automatic timezone conversion.

Actual Behavior:
The timestamps in the INT96 format are incorrectly converted to UTC+8 during the load process when using the Stream Load feature. This results in inaccurate data in the loaded Parquet files.

Metadata of the Parquet File:
The metadata for the Parquet file is as follows:

{
  "Version": 1,
  "NumRows": 3,
  "NumRowGroups": 1,
  "NumFields": 2,
  "CreatedBy": "Parquet.Net version 5.0.2 (build b7322effa264da943718efdbca76d182b450b949)",
  "Schema": {
    "Path": "root",
    "Children": [
      {
        "Path": "vchreferencenumber",
        "Type": "BYTE_ARRAY",
        "LogicalType": {
          "Name": "STRING"
        },
        "RepetitionType": "OPTIONAL",
        "ConvertedType": "UTF8",
        "Children": []
      },
      {
        "Path": "dtcreatedate",
        "Type": "INT96",
        "LogicalType": null,
        "RepetitionType": "OPTIONAL",
        "ConvertedType": "",
        "Children": []
      }
    ]
  },
  "RowGroups": [
    {
      "NumRows": 3,
      "TotalByteSize": 221
    }
  ]
}

[zclllyybb]

We need more information to reproduce this problem:

1. the value of session variable time_zone
2. the parameters used in stream load
3. some of the import data to let us know the data format.