You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the executeBatch method is executed and the process throws an exception, the InputBasedPreparedStatement.executeAny method clears the content of the generated preparedStatement by invoking the clearBatch() method. This makes it impossible to create a retry system when the exception is generated by a recoverable issue.
In implementations where batches of more than one million elements are being processed, the most efficient way to store the data is directly in the driver's preparedStatement. This way, the data is saved serialized, saving a large amount of memory. The execution of the clearBatch method prevents this possibility and forces redundant data storage.
Adding the ability to include a property to disable automatic clearBatch when an exception occurs would make the driver offer more flexible solutions when performing huge numbers of insertions on the server.
The text was updated successfully, but these errors were encountered:
Btw, what is initial format from which data is getting to prepared statement? Is it possible to use plain java client with one of supported formats (like JSONEachRow) to stream data from input to server by passing JDBC complexity?
Thank you for the quick response. The use of the JDBC client has been proposed as an additional abstraction layer. However, exploring the use of the Java client could be very interesting. Thank you for the suggestion!
When the executeBatch method is executed and the process throws an exception, the InputBasedPreparedStatement.executeAny method clears the content of the generated preparedStatement by invoking the clearBatch() method. This makes it impossible to create a retry system when the exception is generated by a recoverable issue.
In implementations where batches of more than one million elements are being processed, the most efficient way to store the data is directly in the driver's preparedStatement. This way, the data is saved serialized, saving a large amount of memory. The execution of the clearBatch method prevents this possibility and forces redundant data storage.
Adding the ability to include a property to disable automatic clearBatch when an exception occurs would make the driver offer more flexible solutions when performing huge numbers of insertions on the server.
The text was updated successfully, but these errors were encountered: