[Bug]: reading an Oracle TIMESTAMP WITH TIME LOCAL ZONE column infers a String instead of a timestamp
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 476
- Avg merge
- 18h 32m
- Merged PRs (30d)
- 216
Description
### Apache Hop version?
2.19
### Java version?
21.0.2
### Operating system
macOS
### What happened?
A Table Input action against an Oracle Database table with one or more columns of type TIMESTAMP WITH TIME LOCAL ZONE infers a String field type instead of a Timestamp field type which is correctly inferred if column type is TIMESTAMP only.
Occurs with both Oracle JDBC driver 19 and 26 (23.26.3).
The "Show Layout" function of the "Database explorer" shows the same problem.
### Issue Priority
Priority: 2
### Issue Component
Component: Actions
Contributor guide
Research direction
Start with the Table Input action and the Database explorer's Show Layout function, then trace how Oracle column metadata distinguishes TIMESTAMP from TIMESTAMP WITH TIME LOCAL ZONE. Reproduce the issue with the reported Oracle JDBC drivers and verify that both contexts infer a Timestamp field type for the local-time-zone column.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100