[CASSSIDECAR-170] Prepared statements get stale once sidecar reconnects to Cassandra

• Type: Bug
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Component/s: Rest API
• Bug Category: Availability - Unavailable
• Severity: Normal
• Complexity: Normal
• Discovered By: Unit Test

Test and Documentation Plan

unit test; ci

• Assignee: Yifan Cai
• Reporter: Yifan Cai

Authors

Yifan Cai

• Created: 05/Dec/24 22:03
• Updated: 12/Dec/24 21:09

Description

When sidecar reconnects, the prepared statements were still associated with the previous session instance, causing all SidecarSchema related operations to fail. 
 

Tried to execute unknown prepared query : 0x38663cebc0a18b444860e0439a814e38. You may have used a PreparedStatement that was created with another Cluster instance.
com.datastax.driver.core.exceptions.InvalidQueryException: Tried to execute unknown prepared query : 0x38663cebc0a18b444860e0439a814e38. You may have used a PreparedStatement that was created with another Cluster instance.
	at com.datastax.driver.core.SessionManager.makeRequestMessage(SessionManager.java:640)
	at com.datastax.driver.core.SessionManager.executeAsync(SessionManager.java:141)
	at com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:58)
	at org.apache.cassandra.sidecar.db.DatabaseAccessor.execute(DatabaseAccessor.java:72)
	at org.apache.cassandra.sidecar.db.RestoreJobDatabaseAccessor.create(RestoreJobDatabaseAccessor.java:106)

Issue Links

• links to: GitHub Pull Request #156