rachel88888 opened a new issue, #39924: URL: https://github.com/apache/arrow/issues/39924
### Describe the bug, including details regarding any error messages, version, and platform. In GH-35352, there was a [timezone check](https://github.com/apache/arrow/blob/main/java/vector/src/main/java/org/apache/arrow/vector/TimeStampMicroTZVector.java#L164-L166) added to the `TimeStamp*TZVector.set` methods that verified that the `*TimeStamp*TZHolder` had the same timezone as the vector that was being set. Before this change was committed, this snippet to unset the value at an index worked: ``` TimeStampMicroTZVector vector = new TimeStampMicroTZVector("vector", allocator, "UTC"); NullableTimeStampMicroTZHolder holder = new NullableTimeStampMicroTZHolder(); vector.setSafe(0, holder); ``` However, after the change, it now throws `IllegalArgumentException: holder.timezone: null not equal to vector timezone: UTC` when trying to unset the value in the vector. We currently have a workaround for this issue by explicitly setting `holder.timezone = vector.getTimeZone();` before calling the `setSafe` method. I'm wondering if it is expected behavior to require that `holder.timezone` match the vector's timezone when unsetting the value. It also differs from the `get` behavior which [does not set the timezone on the holder when the vector's value is unset](https://github.com/apache/arrow/blob/main/java/vector/src/main/java/org/apache/arrow/vector/TimeStampMicroTZVector.java#L121-L123). I'm happy to help submit a patch if the existing behavior is indeed unintended. ### Component(s) Java -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@arrow.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
