You need to
SELECT * from public. Sample_Data_1_view;
Columnar format is in the view.
Please check out the native Python driver at https://github.com/vertica/vertica-python
This driver is available using pip (PyPI) and works with all Python 3.x versions.
You can also use pyodbc with the Vertica ODBC driver.
See this link for some ideas: https://forum.vertica.com/discussion/216053/flextable-udfs-broken-failure-in-udx-rpc-call-invokesetexeccontext-failed-to-map-segment-from-s
Most likely due to the user you're using has insufficient privileges to your catalog directory, or your catalog directory is on a disk with noexec enabled.
I would recommend you consult with support on this topic. I've anecdotally heard of clients successfully upgrading in this manner, but I'm sure there are specific scenarios which make this difficult.
In general, you should be OK to have mixed operating systems within a cluster, but we certainly don't recommend that long-term. It also matters which flavors they are, but if you're sticking with the same flavor, you should be OK. Again - in general.
You can have one node down in a 3 node cluster and still be operational. You may notice a slight performance degrade, and there are certainly other factors at play internally which could cause this to be worse, depending on the physical layout of your data, and some network considerations. But you shouldn't have to take an application outage to do this.
I don't believe a backup cares what Vertica version you are using. But again, consult with support. I'm not qualified to answer #4, as I'm not a Linux admin. Bottom line, you should reach out to support for guidance on this process. They have a lot more experience and use-cases to draw upon for this kind of situation.
Hi, I've worked on a similar situation where a customer needed to upgrade from RHEL 6.x to 7.x in a larger cluster. Two comments:
You are correct that as long as Vertica version is the same, cluster should stay up.
Other customer found that by preserving Vertica files and directories (e.g., /opt/vertica, init scripts in /etc, along with catalog, data folders) that they were able to restart Vertica and sync a bit faster.
Yes, that is what I meant. I don't believe the Vertica backup cares too much about the OS version. Thanks.
Try to run the admintools command install_package with the option --force-reinstall like shown here:
But please note that currently Vertica (9.2.x) support Debian Linux versions 8.5, 8.9