@kevinjqliu i have a few questions about the these test case scenarios

• the first scenario is already present i think, test_pyarrow_time64_us_to_iceberg function checks with us precision
• secondly, can you please explain a bit about the test case you want me to write on the read/write path, what file should that be in and what specifically should it test for

You can find some information in my previous PR.
#1206

• Time64Type with us precision. This was already supported by the previous code.
• Time64Type with ns precision, _downcast_ns_timestamp_to_us not set. Should error
• Time64Type with ns precision, _downcast_ns_timestamp_to_us is set. Should downcast precision to us
• Able to write pyarrow dataframe with a column with Time64Type with ns precision.

You can use #848 as an example where timestamp downcast was implemented

This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that's incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@iceberg.apache.org list. Thank you for your contributions.

This pull request has been closed due to lack of activity. This is not a judgement on the merit of the PR in any way. It is just a way of keeping the PR queue manageable. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time.

It would be great to revive this, please