[MXS-3184] COM_STMT_EXECUTE with FOUND_ROWS not routed to previous target Created: 2020-09-15  Updated: 2020-11-16  Resolved: 2020-11-16

Status: Closed
Project: MariaDB MaxScale
Component/s: QueryClassifier
Affects Version/s: 2.3.20, 2.4.12, 2.5.3
Fix Version/s: 6.0.0

Type: Bug Priority: Minor
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Sprint: MXS-SPRINT-119

 Description   

With MXS-3143 fixed, COM_QUERY packets will be routed to the server where the last command was executed. This does not cover COM_STMT_EXECUTE packets which means that a prepared statement with FOUND_ROWS will not be handled the same way a COM_QUERY packet with FOUND_ROWS is.

The fix to this is to classify queries like this as a special type which should be routed to the previous target, if it is still available.

 Comments   
Comment by markus makela [ 2020-10-26 ]

This could be solved by storing a reference to the buffer instead of the type it contains. This would allow all query classification results to be exposed for COM_STMT_EXECUTE as well.

Generated at Thu Feb 08 04:19:34 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.