Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.2.24
-
I saw that behavior on Windows and Linux, in the case of Windows this my information:
Operating System: Windows 10 Pro 64-bit (10.0, Build 17763)(17763.rs5_release.180914-1434)
Language: English (Regional Setting: English)
Processor: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8 CPUs), ~2.6GHz
Memory: 16384MB RAM
And for Centos 7:
Linux 3.10.0-693.el7.x86_64 #1 SMP Tue Aug 22 21:09:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
CentOS Linux release 7.4.1708 (Core)
Information from mysqld --print-defaults:
mysqld would have been started with the following arguments:
--datadir=C:/Program Files/MariaDB 10.2/data --port=3308 --innodb_buffer_pool_size=2036M --max_allowed_packet=96M --connect_type_conv=YES --connect_conv_size=1024 --event_scheduler=ONI saw that behavior on Windows and Linux, in the case of Windows this my information: Operating System: Windows 10 Pro 64-bit (10.0, Build 17763)(17763.rs5_release.180914-1434) Language: English (Regional Setting: English) Processor: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8 CPUs), ~2.6GHz Memory: 16384MB RAM And for Centos 7: Linux 3.10.0-693.el7.x86_64 #1 SMP Tue Aug 22 21:09:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux CentOS Linux release 7.4.1708 (Core) Information from mysqld --print-defaults: mysqld would have been started with the following arguments: --datadir=C:/Program Files/MariaDB 10.2/data --port=3308 --innodb_buffer_pool_size=2036M --max_allowed_packet=96M --connect_type_conv=YES --connect_conv_size=1024 --event_scheduler=ON
Description
I was trying to sync information from a server with MySQL 5.6. The schema that I wanted to sync has so many text type columns, so I needed to set connect_conv_size and connect_type_conv variables, and I didn't have any problem to do that in MariaDB version 10.2.14 but I couldn't do it with version 10.2.24, connect_type_conv it could set to YES but connect_conv_size it couldn't set to another value that the default value.
I tried to put the value with --connect-conv-size=1024 and in the configuration file. In both case I got that when I used show variables command:
mariadb> SHOW VARIABLES LIKE 'connect%';
|
+-----------------------+------------------------+
|
| Variable_name | Value |
|
+-----------------------+------------------------+
|
| connect_class_path | |
|
| connect_cond_push | ON |
|
| connect_conv_size | 0 |
|
| connect_enable_mongo | ON |
|
| connect_exact_info | OFF |
|
| connect_indx_map | OFF |
|
| connect_java_wrapper | wrappers/JdbcInterface |
|
| connect_json_grp_size | 10 |
|
| connect_json_null | <null> |
|
| connect_jvm_path | |
|
| connect_timeout | 10 |
|
| connect_type_conv | YES |
|
| connect_use_tempfile | AUTO |
|
| connect_work_size | 67108864 |
|
| connect_xtrace | |
|
+-----------------------+------------------------+
|
15 rows in set (0.03 sec)
|
That thing avoid that "discovery method" could get the real size of varchar column, I fixed manually column size and it worked. I think that's a bug in configuration file or I missed something. Thanks in advance.