...
FAQ for the Vertica jOOQ Upgrade
What is happening?
We plan to upgrade the The jOOQ library for the Vertica Snap Pack is upgraded from v3.9.1 to v3.17.x, which will be part of the Latest release.
Why are we upgrading the Vertica jOOQ library?
...
This upgrade will be available on <TBD> as part of 437patches26900
(Latest release) on June 28, 2024, and will be part of the 4.38 GA release on August 14, 2024 (Stable release).
...
We recommend you investigate your pipelines and check the Snaps downstream of Vertica Snaps for any of the affected scenarios. Update any dependencies that the downstream Snaps might have with respect to the changing error and outputs (especially in expressions) to conform to the new expected errors and outputs.
How
...
In a production Org
If you have a production Org to validate connections to your Vertica instances, you may upload a PostgreSQL JDBC driver JAR compatible with
postgres 9.4.1207.jar
.Upload that JAR file to your Org’s shared folder and specify it in the PostgreSQL Account.
Validate the account.
After you verify that the updated JDBC driver works, you may remove it.
How do you override the behavior changes?
...
Behavior Changes
This library upgrade will result resulted in specific behavior changes in the Snap Pack. These changes are for status codes and success and failure messages. This table lists these changes:
Previously, when you passed
NaN
toDate/Integer/Timestamp
data type, the Vertica -Execute Snap displayed a null value in the reason for the error message. The Snap now displays a query in the reason.Change in the output message of Vertica Snaps where the Snaps displayed date, time, and timestamp as objects in the output message. Now, the Snap displays the values directly.
Vertica Snaps | Scenario | Error/Output from the Old (v3.9.1) JOOQ Library | Error/Output from the New (v3.17.x) JOOQ Library | ||||
Vertica-Execute | When you pass |
|
| Vertica-Execute | |||
When you pass | [{"error":"SQL operation failed","reason":"SQL [null]; [Vertica][VJDBC](3681) ERROR: Invalid input syntax for integer: \"NaN\""}]
| [{"error":"SQL operation failed","reason":"SQL [insert into public.table_nan (c_int) values ('NaN')]; [Vertica][VJDBC](3681) ERROR: Invalid input syntax for integer: \"NaN\""}] | |||||
Vertica-Execute | When you pass | [{"error":"SQL operation failed","reason":"SQL [null]; [Vertica][VJDBC](3679) ERROR: Invalid input syntax for date: \"NaN\""}]
| [{"error":"SQL operation failed","reason":"SQL [insert into public.table_nan (c_date) values ('NaN')]; [Vertica][VJDBC](4883) ERROR: Table \"public.table_nan\" does not exist"}] | ||||
Vertica-Execute | when you pass a spl a special character( ' ). |
|
| ||||
Vertica-Select
| When Order by field is expression enabled. | Output message: | Output message: | ||||
When you provide a value in Order by field. | Output message:
| Output message:
| |||||
Vertica-Select | When you provide table and schema name as pipeline parameters. | Output message:
| Output message:
| ||||
Vertica-Select | When you provide a table and schema name as input from Snap. | Output message:
| Output message:
| ||||
Vertic- Select | When you select the Match data types checkbox. | Output message:
| Output message:
| ||||
When you preserve date and time values. | Output message:
| Output message: Output message:
| Vertica-Select | Basic test | Output message:
|
| |
Vertica-Select | When you enable the second output view | IS_AUTOINCREMENT column details appear in response. | IS_AUTOINCREMENT column details do not appear in response. | Vertica-Bulk Load | When the Auto commit checkbox is deselected. | Output message:
| Output message:
|
Vertica-Lookup Vertica-Delete | When you provide a value in the Number of retries. | Output message:
| Output message:
| ||||
All Vertica Snaps | Boundary values check. | Output message:
| Output message:
|
...