I found today that I can't execute this:
UPSERT INTO loadtest.testing (id, firstname, lastname) SELECT NEXT VALUE
FOR loadtest.testing_id_seq, firstname, lastname FROM loadtest.testing
when the table has more than 500,000 rows in it ("MutationState size of
512000 is bigger than max allowed
Hi James,
Is it right to assume that with auto-commit set to true, the mutate maxSize
being exceeded error would not occur? This should be because now server side
does the commit automatically when the batch size is reached/ buffered.
Thanks,Sumit
From: James Taylor
That config setting (phoenix.mutate.maxSiize) is just a safety valve to
prevent out of memory errors and may be set to whatever you like. However,
if you're going to just turn around and do a commit after running your
upsert statement, performance will improve if you turn on auto commit
instead
