search

TIBCOSoftware / be-contribution

This repository is to add various contributions across different modules within TIBCO BusinessEvents. It will include contributions by TIBCO BusinessEvents team as well external users/customers/fields teams.
BSD 3-Clause "New" or "Revised" License
0 stars 9 forks source link

Cassandra Store Catalog Function || Issue with ExecuteUpdate() function #88

Closed spingale-tibco closed 1 year ago

spingale-tibco commented 1 year ago

Version Information

Software Version(s)
BusinessEvents 6.3.0
OS Type? NA
OS Version? NA

What is the expected behavior?

ExecuteUpdate() should work with all type of supported queries like Insert, Update, Delete, Index, CreateTable, AlterTable, DropTable and return correct count. Also same should get reflect in cassandra store.

What is the actual behavior?

executeUpdate when ran with supported queries, returns count as -1, and also not getting reflecting in store.

Please provide log files.

ExecuteUpdateTest1.log ActiveSpaces_ExecuteUpdate.zip

rakulkar-tibco commented 1 year ago

Fixed, but it will still return -1 as there is no provision in Cassandra to get number of rows affected.

spingale-tibco commented 1 year ago

executeUpdate() is working with Insert, Update and Delete statement

While creating and deleting the Table/Index we are getting below exception
'Caused by: com.datastax.oss.driver.api.core.DriverTimeoutException: Query timed out after PT2S'

ExeuteUpdateFinal34.log

rakulkar-tibco commented 1 year ago

executeUpdate() is working with Insert, Update and Delete statement

While creating and deleting the Table/Index we are getting below exception 'Caused by: com.datastax.oss.driver.api.core.DriverTimeoutException: Query timed out after PT2S'

But on db side we can see the changes

spingale-tibco commented 1 year ago

Existing cluster had multiple keyspaces and tables. We were getting this server side warning Cluster already contains 397 tables in 124 keyspaces. Having a large number of tables will significantly slow down schema dependent cluster operations.

Hence, As discussed with Rashmi, tried to execute test with different cluster. table create/deletion and Index create/delete is working with another cluster.

ExecuteUpdateTable105.log