Best Of

Query 1 and Query 2 are not joining on the same column:

Q1 where
a.netif_unique_id = c.netif_unique_id
and a.netif_unique_id in ('d946b79e-7d9a-4575-91c3-893172f32a5b' )

Q2 where
a.node_unique_id = c.node_unique_id
and a.netif_unique_id in ('d946b79e-7d9a-4575-91c3-893172f32a5b' )

I missed column is_up_to_date in projection systems table.

@scherepanov we are supporting TIME with PARQUET starting 24.3 and it is backported to all versions till 23.4

https://docs.vertica.com/24.3.x/en/sql-reference/statements/copy/parsers/parquet/

Do you have any user created projections on that table? if so, could you please try dropping those projections first?

169.254.169.254 is in AWS a direct link to the EC2 instances metadata. 169.254.0.0/16 is an RFC 1918 network.

this issue is being fixed in major version(24.4). do you need backport for it?

This behavior is not necessarily related to the Vertica JDBC client, as DBeaver, using the same JDBC client, displays arrays in square brackets [], while DbVisualizer uses curly brackets {} for array formatting.

The requested post is attached.

Configure JDBC clients to Work with Your Kerberos-Enabled Vertica Cluster: DbVisualizer, DBeaver, and Others
Posted August 1, 2017 by Sarah Lemaire

@scherepanov there is no need to upgrade to 23.4 or 24.x. you can directly upgrade from 12.0.4 to 24.2 . Please find the doc link which mentions about non sequential upgrades.

https://docs.vertica.com/24.2.x/en/setup/upgrading/

@Sergey_Cherepan_1 Did you configure your authentication to only allow TLS?
for instance
CREATE AUTHENTICATION v_ldap METHOD 'ldap' HOST TLS '10.0.0.0/23';
Would also allow TLS connections from specified host. A plaintext connection attempt would fail.