Dear All -
I'm personally not a Python programmer, but our customers and prospects, and some of us, are fond of the Vertica Python Client.
One of our prospects wants to test a multi-threaded data retrieval of small to medium sized result sets using Python from Vertica .
We get connection load balancing:
- setting the -c switch while calling vsql
- by default in JDBC and ODBC if we use the external IP address and the connection load balance policy of the database is set to its default "roundrobin"
Question is, how is that with the Vertica Python Client? A test by the customer with 4 parallel threads connecting always returned node 1 when calling "select node_name from current_session".
Can we specify something to change that while connecting at all?
Thanks and cheers -
Marco
