Unable to write Timestamp Logical Type

[kharlm16]

Issue description

Issue

Writing DateTimes using DateTimeDataField uses TIMESTAMP_MILLIS Converted Type instead of TIMESTAMP(isAdjusted, unit) Logical Type.
Is this by design or are there any plans to support writing TIMESTAMP logical type?

[aloneguid]

I have no plans to support this at the moment, so happy for you to pick it up.

[kja-xyt]

It would be great to have it (NANOS to be specific). Files written with Apache Arrow have something like that in Thrift Metadata:

      {
        "Path": "MyNanoTime",
        "Type": "INT64",
        "TypeLength": null,
        "LogicalType": {
          "Name": "TIME",
          "IsAdjustedToUTC": false,
          "Unit": "NANOS"
        },
        "RepetitionType": "REQUIRED",
        "ConvertedType": "",
        "Children": []
      },

and you can read them in Python without the need to cast anything.

[cliedeman]

@kja-xyt DateTime in dotnet doesn't have nanosecond precision though. So I don't recommend using it if you need that level of accuracy.

https://learn.microsoft.com/en-us/dotnet/api/system.datetime.ticks?view=net-8.0#remarks

The max precision is 100 nanoseconds