Is there any possibility for us to use a more recent version?
Namely >= v1.1.0 (2019), which introduced SASL OAUTHBEARER authentication.

Vertica Analytic Database v24.2.0-2
Enterprise mode

I know these Debezium types are not listed in the supported logical types in the Vertica docs, but this would be a very welcome addition

Debezium documentation Table 14 describes logical type io.debezium.time.Timestampbeing stored as milliseconds (while io.debezium.time.MicroTimestamp would be the correct logical type for microseconds).

Example:

• Raw value: 1687892129000
• KafkaAvroParser to Vertica timestamp column: 1970-01-20 14:51:32.129 (equivalent of to_timestamp(raw_ts / 1000^2))
• Correct value: 2023-06-27 21:55:29.000 (equivalent of to_timestamp(raw_ts / 1000))

Vertica Analytic Database v24.2.0-2
Enterprise Mode

According to wikipedia :
"In relational databases, the information schema (information_schema) is an ANSI-standard set of read-only views which provide information about all of the tables, views, columns, and procedures in a database"

I think such a feature would help the support of Vertica by many more tools and it's never a bad thing when you follow the SQL norm. Standard, normalization and interoperability matter. Especially when your competition has it (these last years, it has been implemented in Hive or Monet DB as an example)

Best regards,

Simon

I have installed Vertica but getting below error:

2023/12/14 14:35:50 init.go:25: error dbinit: Failed to get user dbadmin. Did you create it?
2023/12/14 14:35:50 main.go:135: fatal dbinit: dbinit failed: user: unknown user dbadmin

vertica_rwuser
vertica_rouser

Just a finding I wanted to share.

We are running a Microsoft SSAS server containing both a Multidimensional instance and a Tabular model instance. Both are connecting to our Vertica cluster running v11.1.1-11. SSAS version is 2019.

We recently upgraded to driver package version 12 on the Microsoft servers since we are moving towards version 12 on Vertica also. With that came of course OleDB driver version 12.

After installing the driver a reboot was done on the server and things went haywire. The event log started giving errors similar to this, but ONLY for the Multidimensional instance:
Faulting application name: msmdsrv.exe, version: 2018.150.35.33, time stamp: 0x62cd011d
Faulting module name: vertica_12.0_oledb.dll, version: 12.0.2.0, time stamp: 0x636bef08

Also the processing of dimensions stopped as running into a wall after exactly 1 minute.

Note! Tabular models and Power BI reports work fine.

After downgrading to driver pack Version 11, the cube processing on Multidimensional instance went back to working.

Anyone else experiencing the same?

Best regards,
Sören

FunctionError: Method 'features_importance' for 'XGBoostClassifier' doesn't exist.

It seems that it should (https://www.vertica.com/python/documentation_last/learn/XGBoostClassifier/index.php) and indeed does work with the Random Forest Classifier.

I believe that XGBoost (the algorithm) handles missing values without needing to impute, however Vertica's implementation appears to reject rows where a predictor (X) contains NULL. Is that correct?

Thanks.

ALTER SESSION SET AWSAuth='test:test';
ALTER SESSION SET AWSRegion='us-east-1';
ALTER SESSION SET AWSEndpoint='localhost:4566';
ALTER SESSION SET S3EnableVirtualAddressing=1;

COPY test.test(start,advertiser) FROM 's3://reports/*.csv' ON ANY NODE PARSER FCSVParser(type='traditional', reject_on_materialized_type_error='true', header='false', delimiter=E'\t') TRAILING NULLCOLS ABORT ON ERROR NO COMMIT;

this copy is failing with error 'Cannot expand glob pattern due to error, unable to connect to endpoint'

The debug log shows
CurlHttpClient [140639308084992] Making request to http://reports.localhost:4566?encoding-type=url&list-type=2&prefix=saf_fact_kvp_emr/fact_exchange_wins/

instead of request
http://localhost:4566/reports?encoding-type=url&list-type=2&prefix=saf_fact_kvp_emr/fact_exchange_wins/

can someone help me understand the issue and how to fix it?

Getting system information for cluster (this may take a while)... Error: Default shell on the following nodes are not bash. Default shell must be set to bash. 192.168.0.2 /sbin/nologin Exiting... Installation FAILED with errors.

sudouser from which I lunch installation have shell configured to /bin/bash, but disabled root account has shell configured to /sbin/nologin

I have read in install_vertica --help:

When the SUDO_USER environment variable is set, install-vertica attempts to ssh as that user. This is the case when invoked with 'sudo'. Otherwise, install-vertica will ssh as root. The credentials provided with these options must match the ssh user.

I have set SUDO_USER=sudouser but got the same error.

Any ideas?

Thanks, M

The documentation shows that it should work: link

But I get a Syntax error when I try it in vsql v11.0.1-0:

dbadmin=> SELECT listagg(t.col) FROM (SELECT 'b' AS col UNION ALL SELECT 'c' AS col UNION ALL SELECT 'a' AS col) t;
 listagg
---------
 b,c,a
(1 row)

dbadmin=> SELECT listagg(t.col) WITHIN GROUP (ORDER BY t.col) FROM (SELECT 'b' AS col UNION ALL SELECT 'c' AS col UNION ALL SELECT 'a' AS col) t;
ERROR 4856:  Syntax error at or near "FROM" at character 53
LINE 1: ...LECT listagg(t.col) WITHIN GROUP (ORDER BY t.col) FROM (SELE...
                                                             ^
dbadmin=> SELECT VERSION();
               VERSION
-------------------------------------
 Vertica Analytic Database v11.0.1-0
(1 row)

Can someone confirm this please? Or am I doing something wrong?

Thank you!

I'm adding and removing the same 2 AWS nodes to primary subcluster. Basically, i'm going from a single node to a 3 node and back down to 1 node (k-safe 0). When nodes 002 and 003 are not in the db i stop them in AWS to save $$. I get this error sometimes when i try to add the 002 and 003 nodes back in.

Failed to prepare a host for database participation.
See /opt/vertica/log/adminTools.log for details. Host hints follow.
10.20.xx.xx directory already exists: [Details - <ATResult> status=Error host=10.20.xx.xx error_type=<class 'vertica.engine.api.errors.ATDBPrepareError'> error_message=Catalog parent directory already exists: (/vertica/data/demo1_04)] 

I want to force recreate the directory if possible so i don't have to go to each of the two new nodes and delete the directory. This is for scripting purposes for auto scaling i'm working on.

I'm using this admin tools method

adminTools -t db_add_node -s 10.20.xx.xx,10.20.xx.xx -d demo1_04 -p 'pass'

When i look at the options i don't see a way to force recreate the directory. Here are the options i see

[dbadmin@ad2-demo1-04-node0001 root]$ admintools -t db_add_node -help
Usage: db_add_node [options]

Options:
  -h, --help            show this help message and exit
  -d DB, --database=DB  Name of the database
  -s HOSTS, --hosts=HOSTS
                        Comma separated list of hosts to add to database
  -p DBPASSWORD, --password=DBPASSWORD
                        Database password in single quotes
  -a AHOSTS, --add=AHOSTS
                        Comma separated list of hosts to add to database
  -c SCNAME, --subcluster=SCNAME
                        Name of subcluster for the new node
  --timeout=NONINTERACTIVE_TIMEOUT
                        set a timeout (in seconds) to wait for actions to
                        complete ('never') will wait forever (implicitly sets
                        -i)
  -i, --noprompts       do not stop and wait for user input(default false).
                        Setting this implies a timeout of 20 min.
  --compat21            (deprecated) Use Vertica 2.1 method using node names
                        instead of hostnames

Am i missing something? Do i need to fully remove the two nodes from the cluster so vertica drops the directory before i try to add them to db again? I want to be able to add and remove the same nodes from the db as smoothly as possible. This is the only error i'm running into right now.

When I try to load the parquet file, Vertica reports that 0 rows were loaded.
If I inspect the parquet with parquet-tools, I get a negative number of rows, see https://github.com/ktrueda/parquet-tools/issues/18

Output for a v10.1.1-7 dump:

~/.local/bin/parquet-tools inspect ./dump-1.parquet 

############ file meta data ############
created_by: parquet-cpp version 1.0.0-v10.1.1 (build Vertica Analytic Database)
num_columns: 3
num_rows: -1803805480
num_row_groups: 1
format_version: 1.0
serialized_size: 329

Output for a v11.0.0-0 dump:

~/.local/bin/parquet-tools inspect ./dump-2parquet 

############ file meta data ############
created_by: parquet-cpp version 1.0.0-v11.0.0 (build Vertica Analytic Database)
num_columns: 3
num_rows: -1766273362
num_row_groups: 1
format_version: 1.0
serialized_size: 328

Seems like you're using a really old parquet-cpp, maybe bump to a newer version? https://github.com/apache/parquet-cpp/releases

After building the connection following instructions here (https://www.vertica.com/kb/Vertica-Integration-with-DBeaver-Connection-Guide/Content/Partner/Vertica-Integration-with-DBeaver-Connection-Guide.htm), using the dbadmin user, I'm unable to connect.

The connection dialog has the following settings:
JDBC URL: jdbc:vertica://localhost:5433/VMart
Host: localhost Port: 5433
Database/Schema: VMart
User: dbadmin
Password: password
Save password locally is checked.

Here is the error message:

[Vertica]VJDBC Failed to connect to host localhost on port 5433. Reason: Failed to establish a connection to the primary server or any backup address.
Failed to establish a connection to the primary server or any backup address.
Failed to establish a connection to the primary server or any backup address.
Connection refused (Connection refused)
Connection refused (Connection refused)

I've also set the connection to throw debug level output to /tmp, but I'm unable to find any.

Are there known issues between these latest versions of DBeaver and V11?

Thanks.

• SQL Cookbook
• SQL Antipatterns
• The Art of SQL

but some features like TIMESERIES .. OVER and complex datatypes are very special.
Real world examples explained is something we need to get an idea what's possible.

If ORACLE published books why VERTICA shouldn't?

2021-05-23 09:01:47 localhost vbr Old restore points to be removed: 20210501_200009
2021-05-23 09:29:45 localhost vbr Approximate bytes to copy: ... of .... total.
2021-05-23 09:45:42 localhost vbr Copying backup metadata.
2021-05-23 09:46:01 localhost vbr Finalizing backup.
2021-05-23 09:46:01 localhost vbr Location s3://.....: putting updated backup manifest.
2021-05-23 09:46:12 localhost vbr Deleting old restore points.
2021-05-23 09:47:22 localhost vsql /opt/vertica/bin/vsql -q -t -X -ddb -p5433 -Udbadmin -h....
2021-05-23 09:47:24 localhost vbr Traceback (most recent call last):
    File "/opt/vertica/bin/vbr.py", line 10323, in main
      if vbr_task.run():
    File "/opt/vertica/bin/vbr.py", line 5150, in run
      result = self._run()
    File "/opt/vertica/bin/vbr.py", line 6559, in _run
      Parallel.foreach(delete_backup_objects, self._distinct_backup_locations)
    File "/opt/vertica/bin/vbr.py", line 10003, in foreach
      cls.map(func, iterable, threads_num=threads_num)
    File "/opt/vertica/bin/vbr.py", line 9997, in map
      raise exc_info[0](err_msg).with_traceback(exc_info[2])
    File "/opt/vertica/bin/vbr.py", line 9981, in map
      if not thr.join(Parallel.WAIT_QUANTUM):
    File "/opt/vertica/bin/vbr.py", line 9957, in join
      return self._thr.join(*args, **kwargs)
    File "/opt/vertica/bin/vbr.py", line 9932, in join
      raise self._exc_info[0](err_msg).with_traceback(self._exc_info[2])
    File "/opt/vertica/bin/vbr.py", line 9910, in run
      super(Parallel.CancellableThread, self).run()
    File "/opt/vertica/oss/python3/lib/python3.7/threading.py", line 870, in run
      self._target(*self._args, **self._kwargs)
    File "/opt/vertica/bin/vbr.py", line 9945, in do_run
      self._result = func(val)
    File "/opt/vertica/bin/vbr.py", line 6543, in delete_backup_objects
      self._is_data_from_shared_storage())
    File "/opt/vertica/bin/vbr.py", line 5664, in _delete_backup_objects
      delete_fanout_dir_objects, objs_by_fanout_dir, threads_num=delete_concurrency)
    File "/opt/vertica/bin/vbr.py", line 10003, in foreach
      cls.map(func, iterable, threads_num=threads_num)
    File "/opt/vertica/bin/vbr.py", line 9997, in map
      raise exc_info[0](err_msg).with_traceback(exc_info[2])
    File "/opt/vertica/bin/vbr.py", line 9981, in map
      if not thr.join(Parallel.WAIT_QUANTUM):
    File "/opt/vertica/bin/vbr.py", line 9957, in join
      return self._thr.join(*args, **kwargs)
    File "/opt/vertica/bin/vbr.py", line 9932, in join
      raise self._exc_info[0](err_msg).with_traceback(self._exc_info[2])
    File "/opt/vertica/bin/vbr.py", line 9910, in run
      super(Parallel.CancellableThread, self).run()
    File "/opt/vertica/oss/python3/lib/python3.7/threading.py", line 870, in run
      self._target(*self._args, **self._kwargs)
    File "/opt/vertica/bin/vbr.py", line 9945, in do_run
      self._result = func(val)
    File "/opt/vertica/bin/vbr.py", line 5661, in delete_fanout_dir_objects
      backup_access.delete_many('', obj_paths)
    File "/opt/vertica/bin/vbr.py", line 3536, in delete_many
      self._delete_many(remote_prefix, file_list)
    File "/opt/vertica/bin/vbr.py", line 3837, in _delete_many
      Parallel.map(delete_file_list, file_lists, threads_num=self.DELETE_THREADS_NUM)
    File "/opt/vertica/bin/vbr.py", line 9997, in map
      raise exc_info[0](err_msg).with_traceback(exc_info[2])
    File "/opt/vertica/bin/vbr.py", line 9981, in map
      if not thr.join(Parallel.WAIT_QUANTUM):
    File "/opt/vertica/bin/vbr.py", line 9957, in join
      return self._thr.join(*args, **kwargs)
    File "/opt/vertica/bin/vbr.py", line 9932, in join
      raise self._exc_info[0](err_msg).with_traceback(self._exc_info[2])
  TypeError: __init__() missing 1 required positional argument: 'operation_name'

Thank you.

While supplying our solution to a company using Vertica DB,
The following problems have occurred and we contact you.

== Base information ==
DB Server Version: Vertica Analytic Database v8.1.1-8
Vertica ODBC Client Version: 8.1.1.16, 9.2.1.2

Our solution uses ODBC to connect to Vertica DB.
By the way, when using 8.1.1.16 ODBC, the following error occurs about 3 out of 10 queries.

Error: # 20, [Vertica][VerticaDSII] (20) An error occurred during query execution: message do not agree with length in message type "T"
Error: # 10, [Vertica][VerticaDSII] (10) An error occurred during query preparation:

The above error may also appear upon initial connection,
It may also appear in the normal Select statement.

So, we change the ODBC version to 9.0.1, 8.0.1, etc..
And, when using 9.2.1.2, The above errors appear less.
but in the official Vertica compatibility table It is recommended to use version 8.1 or lower when connecting to 8.1 Server.
So, I would like to check if the 8.1.1 server can use 9.2.1 ODBC.
Or, Please tell me exactly what ODBC is right for the Vertica Analytic Database v8.1.1-8.

And, for a general query, (SELECT A INNER JOIN B ON A.a=B.b ... )
When executing the same SQL statement with Aqua Data Studio using JDBC, it takes 2 seconds,
Please tell us if there is a reason why it takes 80 seconds to use 8.1.1 ODBC or 9.2.1 ODBC or etc. .
The number of data in the table is 400 million for A and 30 million for B.

On our solution source, when I try to log before calling ODBC function SQLExecute (stmt) and log after call, the time difference is more than 80 seconds.
Please let me know why there is a time difference between JDBC and ODBC.

Thank you.

Thanks