Hi,

Run this:

export NCURSES_NO_UTF8_ACS=1

And add the command to your .bashrc file so the change is applied every time you log on!

echo export NCURSES_NO_UTF8_ACS=1 >> ~/.bashrc

Hi, There is a maximum row size of 32,768,000 bytes... so if using all 32,000,000 bytes in a single LONG VARCHAR, that doesn't leave much room for a second LONG VARCHAR in the same table. You'd have to use separate tables. Question: What do you plan on doing with storing data of this size in Vertica?

Hi, The privileges on the ML functions must not be granted to PUBLIC. Have the admin user run the following script in vsql to reinstall the ML Package: vsql -f /opt/vertica/packages/MachineLearning/ddl/install.sql After re-installing you should see the EXECUTE privilege granted to PUBLIC: dbadmin=> ...

Review the reply here:

https://forum.vertica.com/discussion/23 ... -cascading

Vertica Community Blog post authored by Curtis Bennett Many clients who are new to Vertica are also new to big data. While Vertica’s reliance on industry-standard SQL can make the transition very easy, often the introduction of multiple nodes used in support of a database platform can take some get...

Vertica Community Blog post authored by Jim Knicely Vertica recognizes many time zones. However, there might come a time (zone) when you will need to reference one that is not available by default. Luckily it’s relatively easy to add a time zone to Vertica. See how here: https://my.vertica.com/blog...

Vertica Community Blog post authored by Jim Knicely You may find you want to set up resource pools before running queries to know how many resources a particular query needs. One way to do this is to create a small resource pool, profile the query, and note when the query is rejected. When the quer...