[MXS-1771] Can't route COM_QUERY:QUERY_TYPE_READ|QUERY_TYPE_USERVAR_WRITE|QUERY_TYPE_USERVAR_READ Created: 2018-04-10  Updated: 2018-04-11  Resolved: 2018-04-11

Status: Closed
Project: MariaDB MaxScale
Component/s: N/A
Affects Version/s: None
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Wagner Bianchi (Inactive) Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None


 Description   

Folks,

After upgrading a running maxscale with no issues from 2.2.1 to 2.2.4, I started getting this below error on the maxscale error log and the query wasn't being routed:

2018-04-10 10:14:02   error  : (1036) [readwritesplit] Can't route COM_QUERY:QUERY_TYPE_READ|QUERY_TYPE_USERVAR_WRITE|QUERY_TYPE_USERVAR_READ:"SELECT @RowNum:=@RowNum+1 AS pmt_num,tpp.id,tpp.company_id,tpp.pmt_plan_id,tpp.chk_num,tpp.pmt_amount,tpp.pmt_amount AS pmt_amt,tpp.pmt_date,tpp.pmt_date AS end_date,tpp.pmt_date AS eff_end_date,tpp.trans_id,tpp.trans_id AS paid_ti_id,CASE @RowNum     WHEN 1 THEN d.create_date     ELSE (SELECT DATE_ADD(pmt_date,INTERVAL 1 DAY) FROM trans_pmt_plan_pmts AS tpp2 WHERE tpp2.id<tpp.id AND tpp2.pmt_plan_id=tpp.pmt_plan_id ORDER BY tpp2.id DESC LIMIT 1) END AS start_date,tpp.paid_date,NULL AS deferred_date,tpp.trans_clear_id,tpp.trans_return_id,tpp.scan_id,SUM(IFNULL(IF(ti_paid.id IS NULL,0,IF(ach_ti.type_id IN (57,65),0,tpp_paid.amt_applied)),0)) AS amt_applied,tp.paid_in_full FROM trans_pmt_plan_pmts AS tpp INNER JOIN trans_pmt_plan AS tp ON tpp.pmt_plan_id=tp.id LEFT JOIN trans_pmt_plan_pmts_paid tpp_paid ON tpp.id=tpp_paid.pmt_id LEFT JOIN trans_item ti_paid ON tpp_paid.trans_id=ti_paid.id AND ti_paid.is_void=0 LEFT JOIN ach_sched AS ach ON ti_paid.id=ach.trans_item_id LEFT JOIN trans_item ach_ti ON ach.created_trans_item_id=ach_ti.id LEFT OUTER JOIN (         SELECT id,hdr_id,create_date FROM trans_pmt_plan WHERE hdr_id=18533439 ) AS d ON tpp.`pmt_plan_id`=d.id WHERE tpp.company_id=279 AND tp.hdr_id=18533439 AND tp.is_deleted=0 GROUP BY tpp.id ". SELECT with session data modification is not supported if configuration parameter use_sql_variables_in=all .



 Comments   
Comment by markus makela [ 2018-04-11 ]

This is expected behavior if use_sql_variables_in=master is not defined.

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