[MDEV-19648] Variable connect_conv_size doesn't change Created: 2019-05-30  Updated: 2020-09-08  Resolved: 2020-09-08

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - Connect
Affects Version/s: 10.2.24
Fix Version/s: 10.2.28, 10.1.42, 10.1.43, 10.1.44, 10.3.19, 10.4.9, 10.5.0, 10.1.45, 10.1.46

Type: Bug Priority: Minor
Reporter: Sebastian Cardona Osorio Assignee: Olivier Bertrand
Resolution: Fixed Votes: 0
Labels: connect-engine
Environment:

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=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.



 Comments   
Comment by Olivier Bertrand [ 2019-05-31 ]

Bug due to a misplaced parameter in the variable definition. It will be fixed in some future versions of MariaDB.

Meanwhile, a temporary tournaround is to specify the connect_conv_size variable value as a multiple of its default value 8192. For instance, specifying:

Set connect_conv_size=4;

will set it to 32,768. Unfortunately, this won't work for setting it to 1024 because only integer values are accepted.

Note that when fixed, the new default value will be 1024.

Comment by Anel Husakovic [ 2020-09-08 ]

Fixed with patch

Generated at Thu Feb 08 08:53:17 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.