[MDEV-26477] Spider-3.3.15 unstable on MariaDB 10.4.18 Created: 2021-08-25  Updated: 2021-09-27  Resolved: 2021-09-27

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - Spider
Affects Version/s: 10.4.18
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Kuijun Cui Assignee: Ian Gilfillan
Resolution: Fixed Votes: 0
Labels: Documentation
Environment:

LSB Version: :core-4.1-amd64:core-4.1-noarch
Distributor ID: CentOS
Description: CentOS Linux release 7.4.1708 (Core)
Release: 7.4.1708
Codename: Core

Attachments: PNG File screenshot-1.png    

 Description   

As official documents introduced, spider 3.3.15 should be appeared after mariadb 10.5.4, but appeared in 10.4.18, is it a bug?

Which version should I try to use for current highest 10.4 version?

(root@localhost) [sbtest] 18:51:42> select @@global.version, @@global.spider_version;
 
+---------------------+-------------------------+
 
| @@global.version    | @@global.spider_version |
 
+---------------------+-------------------------+
 
| 10.4.18-MariaDB-log | 3.3.15                  |
 
+---------------------+-------------------------+
 
1 row in set (0.00 sec)



 Comments   
Comment by Nayuta Yanagisawa (Inactive) [ 2021-08-25 ]

cui3093 Hi, Kuijun. Could you share the "official documents" you are referring to?

Comment by Kuijun Cui [ 2021-08-26 ]

The url: https://mariadb.com/kb/en/spider/

Comment by Nayuta Yanagisawa (Inactive) [ 2021-08-27 ]

cui3093 Please check INFORMATION_SCHEMA.PLUGINS. https://mariadb.com/kb/en/plugins-table-information-schema/

MariaDB [(none)]> SELECT PLUGIN_NAME, PLUGIN_AUTH_VERSION, PLUGIN_MATURITY FROM INFORMATION_SCHEMA.PLUGINS WHERE PLUGIN_NAME='SPIDER';
 
+-------------+---------------------+-----------------+
 
| PLUGIN_NAME | PLUGIN_AUTH_VERSION | PLUGIN_MATURITY |
 
+-------------+---------------------+-----------------+
 
| SPIDER      | 3.3.15              | Stable          |
 
+-------------+---------------------+-----------------+

If the doc contradicted the INFORMATION_SCHEMA.PLUGINS table, the table is true. We will fix the doc. Thank you for your report.

Comment by Kuijun Cui [ 2021-09-07 ]

Is it really a stable version?
Could you tell me why these kind alert coming?

20210907 12:06:17 [INFO SPIDER RESULT] from [172.36.249.16] 22625 to 113:  affected_rows: 18446744073709551615  id: 0  status: 16386  warning_count: 0
 
20210907 12:06:17 [ERROR SPIDER RESULT] to 113: 1305 FUNCTION sbtest.spider_ping_table does not exist
 
20210907 12:06:19 [INFO SPIDER RESULT] from [172.36.249.16] 23590 to 1083:  affected_rows: 18446744073709551615  id: 0  status: 16386  warning_count: 0
 
20210907 12:06:19 [INFO SPIDER RESULT] from [172.36.249.16] 23595 to 1088:  affected_rows: 18446744073709551615  id: 0  status: 16386  warning_count: 0
 
20210907 12:06:19 [ERROR SPIDER RESULT] to 1088: 1305 FUNCTION sbtest.spider_ping_table does not exist
 
20210907 12:06:19 [INFO SPIDER RESULT] from [172.36.249.16] 23594 to 1087:  affected_rows: 18446744073709551615  id: 0  status: 16386  warning_count: 0
 
20210907 12:06:19 [ERROR SPIDER RESULT] to 1087: 1305 FUNCTION sbtest.spider_ping_table does not exist
 
20210907 12:06:19 [INFO SPIDER RESULT] from [172.36.249.16] 23593 to 1086:  affected_rows: 18446744073709551615  id: 0  status: 16386  warning_count: 0
 
20210907 12:06:19 [ERROR SPIDER RESULT] to 1083: 1305 FUNCTION sbtest.spider_ping_table does not exist
 
20210907 12:06:19 [ERROR SPIDER RESULT] to 1086: 1305 FUNCTION sbtest.spider_ping_table does not exist
 
20210907 12:06:19 [INFO SPIDER RESULT] from [172.36.249.16] 23591 to 1084:  affected_rows: 18446744073709551615  id: 0  status: 16386  warning_count: 0
 
20210907 12:06:19 [ERROR SPIDER RESULT] to 1084: 1305 FUNCTION sbtest.spider_ping_table does not exist
 
20210907 12:06:19 [INFO SPIDER RESULT] from [172.36.249.16] 23589 to 1081:  affected_rows: 18446744073709551615  id: 0  status: 16386  warning_count: 0
 
20210907 12:06:19 [ERROR SPIDER RESULT] to 1081: 1305 FUNCTION sbtest.spider_ping_table does not exist
 
20210907 12:06:19 [INFO SPIDER RESULT] from [172.36.249.16] 23595 to 1088:  affected_rows: 18446744073709551615  id: 0  status: 16386  warning_count: 0
 
20210907 12:06:19 [ERROR SPIDER RESULT] to 1088: 1305 FUNCTION sbtest.spider_ping_table does not exist
 
20210907 12:06:19 [INFO SPIDER RESULT] from [172.36.249.16] 23594 to 1087:  affected_rows: 18446744073709551615  id: 0  status: 16386  warning_count: 0
 
20210907 12:06:19 [ERROR SPIDER RESULT] to 1087: 1305 FUNCTION sbtest.spider_ping_table does not exist
 
20210907 12:06:19 [INFO SPIDER RESULT] from [172.36.249.16] 23593 to 1086:  affected_rows: 18446744073709551615  id: 0  status: 16386  warning_count: 0
 
20210907 12:06:19 [ERROR SPIDER RESULT] to 1086: 1305 FUNCTION sbtest.spider_ping_table does not exist

Comment by Ian Gilfillan [ 2021-09-27 ]

The documentation issue has been fixed. As for the comment about errors appearing in the log, the issue tracker is not the best place for that. https://mariadb.com/kb/en/getting-help-with-mariadb/ suggests some places to try, and if it turns out to be a bug, another JIRA issue can be opened.

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