René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Java] IllegalArgumentException when unsetting TimeStamp*TZVector values","articleBody":"### Describe the bug, including details regarding any error messages, version, and platform.\n\nIn apache/arrow#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.\r\n\r\nBefore this change was committed, this snippet to unset the value at an index worked:\r\n```\r\nTimeStampMicroTZVector vector = new TimeStampMicroTZVector(\"vector\", allocator, \"UTC\");\r\nNullableTimeStampMicroTZHolder holder = new NullableTimeStampMicroTZHolder();\r\nvector.setSafe(0, holder);\r\n```\r\nHowever, 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.\r\n\r\nWe 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.\n\n### Component(s)\n\nJava","author":{"url":"https://github.com/rachel88888","@type":"Person","name":"rachel88888"},"datePublished":"2024-02-02T22:07:16.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/125/arrow-java/issues/125"}