Mage version

v0.9.63

Describe the bug

When setting a key column and/or setting a column as datetime only for a pipeline block involving an OracleDB yaml data exporter, the block execution fails with an IndexError: list index out of range exception. This occurs despite successful block execution when no key column is assigned.

To reproduce

1. Configure a Python data integrations OracleDB exporter block with a key column in a pipeline.
How I created the block (there is no OracleDB exporter block template in Data explorer -> Databases):

Stream schema settings:

3. Execute the block.
4. Observe that the execution fails with an IndexError.

Expected behavior

The data exporter block should handle the key column assignment without causing an IndexError. The expected behavior is a successful execution of the block and proper export of the data to the OracleDB with the assigned key column.

Screenshots

No response

Operating system

• OS: Red Hat Enterprise Linux release 8.9 (Ootpa)
• podman version 4.6.1

Additional context

1. The issue arises specifically either when assigning a key column, when assigning a column as datetime only, or both, using the OracleDB yaml data exporter.
2. The error message indicates a list index out of range, suggesting that the code might be attempting to access a list element that does not exist.
3. @johnson-mage suggested that the error might be due to the type not being set for certain columns in the catalog.json.
   
4. The temporary workaround suggested by @johnson-mage (adding a string type to datetime columns) has not led to errors, but resulted in the columns with both string and datetime types becoming CHAR(52) in the Oracle DB, in my specific case, which is not ideal.