[Bug]: Updating an Oracle Date column with a Date read from Postgres fails (unless "Skip lookup" is checked)
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 476
- Avg merge
- 19h
- Merged PRs (30d)
- 227
Description
### Apache Hop version?
2.15.0
### Java version?
OpenJDK 17
### Operating system
Windows
### What happened?
The "Table input" transform reads a "date" from a Postgres database,
the "Update" transform tries to update a corresponding "Date" in an Oracle database with the value read from Postgres.
Unless "Skip lookup" is checked, the update fails with:
```
2025/10/08 07:50:20 - Update.0 - ERROR: Error in transform, asking everyone to stop because of:
2025/10/08 07:50:20 - Update.0 - ERROR: org.apache.hop.core.exception.HopDatabaseException:
2025/10/08 07:50:20 - Update.0 - Couldn't get row from result set
2025/10/08 07:50:20 - Update.0 -
2025/10/08 07:50:20 - Update.0 - Unable to get value 'None' from database resultset, index 0
2025/10/08 07:50:20 - Update.0 - No data read
```
In the case of unchecking "Skip lookup", checking/unchecking "Ignore lookup failures" and providing a field for the Y/N values if the key was found makes no difference.
Using a "Select values" transform to convert the Date stream field into a String or Timestamp changes nothing in the behavior.
Fields of other types (String, Integer...) have no problems with updates with unchecked "Skip lookup".
See the attached pipeline:
[date-update-test-public.zip](https://github.com/user-attachments/files/22759764/date-update-test-public.zip)
### Issue Priority
Priority: 3
### Issue Component
Component: Transforms
Contributor guide
Research direction
Start by running the attached date-update-test-public.zip pipeline with the Table input and Update transforms against PostgreSQL and Oracle, reproducing the failure when Skip lookup is unchecked. Trace the Update transform's date lookup and result-set handling; done means a PostgreSQL-read date can update the corresponding Oracle Date without Skip lookup, while existing String and Integer behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, postgresql
- Domain
- data-engineering, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100