arrowToRecord() produce wrong timestamp for some future dates

[Yifeng-Sigma]

Super easy to reproduce,

https://github.com/sigmacomputing/gosnowflake/blob/17fd0144860b6ee0164c398488ad9fa02fb65f36/converter_test.go#L850
change year to >= 2263 or <= 1677 and the the unit test will fail.
While per documentation it's within the range "Snowflake recommends using years between 1582 and 9999".

[sfc-gh-dszmolka]

hi and thank you for submitting this issue with us, we'll take a look

[sfc-gh-dszmolka]

PR #918 with the fix in progress. Thank you for bearing with us while this is getting fixed !

[sfc-gh-dszmolka]

PR merged and will be part of the October release, expected towards the end of October

[sfc-gh-dszmolka]

gosnowflake 1.7.0 released with the fix, thank you all for bearing with us !

[madisonchamberlain]

Hello, I am wondering if there are any recommendations on how ArrowSnowflakeTimestampToTime should be used.

[sfc-gh-dszmolka]

hi there - we seem to have some in converter_test.go; would that suffice as an example or should we provide something more ?

[Yifeng-Sigma]

hi there - we seem to have some in converter_test.go; would that suffice as an example or should we provide something more ?

@sfc-gh-dszmolka Thank you, this is helpful. One more question:
Is it possible for you to provide timestamp in microsecond precision? microsecond should be able to fit in arrow.Timestamp without the need of using arrow.Struct.
In our use case, the connector passes the arrow record from Snowflake to another service for decoding. If we have microsecond precision, we can avoid the need to port the arrowSnowflakeTimestampToTime logic.

[sfc-gh-dszmolka]

we'll check @Yifeng-Sigma , started a discussion on that.