Details
-
Type:
Story
-
Status: Won't Fix
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: Qserv
-
Labels:None
-
Story Points:4
-
Sprint:DB_W16_12
-
Team:Data Access and Database
Description
Sqlalchemy is generating some queries that are currently killing czar, the list is:
set autocommit=0
|
SHOW VARIABLES LIKE 'sql_mode'
|
SELECT DATABASE()
|
SELECT @@tx_isolation
|
show collation where `Charset` = 'utf8' and `Collation` = 'utf8_bin'
|
SELECT CAST('test plain returns' AS CHAR(60)) AS anon_1
|
SELECT CAST('test unicode returns' AS CHAR(60)) AS anon_1
|
SELECT CAST('test collated returns' AS CHAR CHARACTER SET utf8) COLLATE utf8_bin AS anon_1
|
SELECT 'x' AS some_label
|
select @@version_comment limit 1
|
Czar should survive unfriendly syntax, and this will be addressed through DM-3764.
In this story we will make sure that sqlalchemy-generated queries are properly handled (not just these particular queries, but all queries that do not involve any database and any table). We should run such queries on a local mysql instance (alternatively, perhaps redirect to one of the workers?)
Nice-to-have, but end-user support for client libraries other than the TAP service has been de-prioritized. Current query coverage is sufficient to support TAP service and administrative tooling; where not, specific individual issues have been or will be filed.