MDEV-32753Spider engine does not load in ORACLE mode
Closed
MDEV-33706backport some spider fixes to 10.4 which was unlocked
Closed
split from
MDEV-33242SPIDER plugin initialization failed at 'create table if not exists mysql.spider_tables ... with 'Specified key was too long; max key length is 1000 bytes', Warning: Memory not freed: 10720
Closed
split to
MDEV-33584sql plugin init failure with traditional sql_mode
MDEV-33494 fix spider init with no_zero_date global sql mode
Like the fix for MDEV-32753 and MDEV-33242, spider init queries
creates new connections that use the global sql_mode of the existing
connection.
Yuchen Pei
added a comment - Hi holyfoot , ptal thanks
upstream/bb-10.5-ycp 3e494b1ea5a50a0769aab91af205284067f408b7
MDEV-33494 fix spider init with no_zero_date global sql mode
Like the fix for MDEV-32753 and MDEV-33242, spider init queries
creates new connections that use the global sql_mode of the existing
connection.
Roel Van de Paar
added a comment - Also found this one, same outcome. This one may be lightly sporadic.
SET @@sql_mode= 'TRADITIONAL' ;
SET GLOBAL sql_mode=( SELECT REPLACE (@@sql_mode, ',pipes_as_concat' , '' ));
INSTALL PLUGIN Spider SONAME 'ha_spider.so' ;
SHUTDOWN;
Roel Van de Paar
added a comment - And another one, this time again using old_mode alike to MDEV-33242
SET sql_mode= '' ;
SET GLOBAL old_mode= 'no_dup_key_warnings_with_ignore,no_progress_info' ;
INSTALL PLUGIN Spider SONAME 'ha_spider.so' ;
SHUTDOWN;
I am pushing this and opening a new ticket (MDEV-33584) from other examples from Roel (if not fixed already).
Yuchen Pei
added a comment - - edited Thanks for the review holyfoot .
I am pushing this and opening a new ticket ( MDEV-33584 ) from other examples from Roel (if not fixed already).
Roel, at which commit did you get the failure in the old_mode case in your comment[1]? I couldn't reproduce it at 10.6 5b8493ba34a4e5393ad9bdfe2803a11780ef3f52
Yuchen Pei
added a comment - Roel , at which commit did you get the failure in the old_mode case in your comment [1] ? I couldn't reproduce it at 10.6 5b8493ba34a4e5393ad9bdfe2803a11780ef3f52
[1] https://jira.mariadb.org/browse/MDEV-33494?focusedCommentId=280963&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-280963
Confirmed that the issue in this comment is no longer reproducible in 10.6 build today at rev 0df4651c13d68f1c228986f940d8ea4a226132f5
Roel Van de Paar
added a comment - Confirmed that the issue in this comment is no longer reproducible in 10.6 build today at rev 0df4651c13d68f1c228986f940d8ea4a226132f5
However, the original testcase in this ticket still causes an ERROR message in the error log (which is MDEV-31111). Info added here. A fix for that bug would be great, whenever possible (or is it perhaps fixed by the MDEV-33584 fix?).
Roel Van de Paar
added a comment - - edited However, the original testcase in this ticket still causes an ERROR message in the error log (which is MDEV-31111 ). Info added here . A fix for that bug would be great, whenever possible (or is it perhaps fixed by the MDEV-33584 fix?).
Update: here w/ thanks ycp
Hi holyfoot, ptal thanks
upstream/bb-10.5-ycp 3e494b1ea5a50a0769aab91af205284067f408b7
MDEV-33494 fix spider init with no_zero_date global sql mode
Like the fix for MDEV-32753 and MDEV-33242, spider init queries
creates new connections that use the global sql_mode of the existing
connection.