Vertica note: Before using a machine learning function, be aware that all the ongoing transactions m

It means that any in-progress transaction in the current session executing the machine learning function may be auto-committed. In this manner, very similar to the behavior of CREATE TABLE, which commits any existing transaction before proceeding to the table creation operation.

Thanks Ben. Meaning, this “Auto-Commit” would be restricted to the current session only – where the Machine Learning function is being executed – and as such may not affect any other sessions like the CREATE TABLE execution.

Correct. I'll put something in to adjust the documentation. It currently seems to apply to all transactions on the database, something which is not true.