`Unknown sysvar` error

[Nick-S-2018]

Bug Description:

It looks that Manticore has stopped handling requests for some MySQL system variables which makes MySQL tools like DBeaver fail on connect.

SELECT  @@session.auto_increment_increment AS auto_increment_increment, @@character_set_client AS character_set_client, @@character_set_connection AS character_set_connection, @@character_set_results AS character_set_results, @@character_set_server AS character_set_server, @@collation_server AS collation_server, @@collation_connection AS collation_connection, @@init_connect AS init_connect, @@interactive_timeout AS interactive_timeout, @@license AS license, @@lower_case_table_names AS lower_case_table_names, @@max_allowed_packet AS max_allowed_packet, @@net_write_timeout AS net_write_timeout, @@performance_schema AS performance_schema, @@sql_mode AS sql_mode, @@system_time_zone AS system_time_zone, @@time_zone AS time_zone, @@transaction_isolation AS transaction_isolation, @@wait_timeout AS wait_timeout

Which produces the following error:

"unknown sysvar @@character_set_results; unknown sysvar @@character_set_server; unknown sysvar @@collation_server; unknown sysvar @@collation_connection; unknown sysvar @@init_connect; unknown sysvar @@interactive_timeout; unknown sysvar @@license; unknown sysvar @@net_write_timeout; unknown sysvar @@performance_schema; unknown sysvar @@sql_mode; unknown sysvar @@system_time_zone; unknown sysvar @@time_zone; unknown sysvar @@transaction_isolation; unknown sysvar @@wait_timeout"

Manticore Search Version:

Manticore 10.1.0 c10e1563b@25060414 dev

Operating System Version:

Ubuntu 22.04

Have you tried the latest development version?

Yes

Internal Checklist:

^{To be completed by the assignee. Check off tasks that have been completed or are not applicable.}

Details

• Implementation completed
• Tests developed (DBeaver integration test)
• Documentation updated
• Documentation reviewed

[pakud]

i've noticed that when using this set of packages:

manticore-buddy 3.29.0+25060414-beb1b320
manticore-columnar-lib 5.0.1+25060311-59c70926
manticore-common 10.1.0-25060608-c63706038
manticore-executor 1.3.2-25012408-1856ac9
manticore-extra 1.3.2-25012408-1856ac9
manticore-galera 3.37
manticore-load 1.18.2+25050118-8537968a
manticore-server 10.1.0-25060608-c63706038
manticore-server-core 10.1.0-25060608-c63706038
manticore-tzdata 1.0.0-240522-a8aa66e

under Debian 12 on amd64 i can connect usind dbeaver with this /etc/manticoresearch/manticore.conf:

searchd {
    listen = 0.0.0.0:9306:mysql41
    log = /var/log/manticore/searchd.log
    query_log = /var/log/manticore/query.log
    pid_file = /var/run/manticore/searchd.pid
    data_dir = /var/lib/manticore/data


pseudo_sharding =1
threads=64
max_packet_size         = 8M
max_filters             = 256
max_filter_values       = 8192
}

but as soon as i activate buddy - i start to get errors as above when connecting from dbeaver:

searchd {
    listen = 0.0.0.0:9306:mysql41
    listen = 0.0.0.0:9308:http
    log = /var/log/manticore/searchd.log
    query_log = /var/log/manticore/query.log
    pid_file = /var/run/manticore/searchd.pid
    data_dir = /var/lib/manticore/data


pseudo_sharding =1
threads=64
max_packet_size         = 8M
max_filters             = 256
max_filter_values       = 8192

}

[giovanichaves]

@Nick-S-2018 Any updates in this matter?
Would be nice being able to connect to it from intelliJ using the MySQL 5.1 driver back again

[Nick-S-2018]

We're going to work on this issue in the nearest future.

[giovanichaves]

Nearest future = couple weeks? next month?

[Nick-S-2018]

Yes, I believe, in the next couple of weeks or sooner.

[sanikolaev]

Related issues:

• Always 0 for unexisting @@variables #3109
• Rust client consider "<empty>" as non-valid response. #1273