[Java] NullableDateMilliVector.getObject() should return a LocalDate, not a LocalDateTime
- Dominant language
- Java
- Stars
- 94
- Forks
- 152
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 11
Description
NullableDateMilliVector.getObject() today returns a LocalDateTime. However, this vector is used to store date information, and thus, getObject() should return a LocalDate.
Please note: there already exists a vector that returns LocalDateTime –
the NullableTimestampMilliVector.
**Reporter**: [Vanco Buca](https://issues.apache.org/jira/browse/ARROW-1984)
#### PRs and other links:
- [GitHub Pull Request apache/arrow#5315](https://github.com/apache/arrow/pull/5315)
**Note**: *This issue was originally created as [ARROW-1984](https://issues.apache.org/jira/browse/ARROW-1984). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
Contributor guide
Research direction
Start at NullableDateMilliVector.getObject() and compare its behavior with NullableTimestampMilliVector, which the issue identifies as the LocalDateTime implementation. Confirm the existing GitHub pull request and migration context before making changes; done means the date vector returns LocalDate while the timestamp vector remains distinct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100