mismatch in decimals

tested sql/binarysigned.sql.log against sql/binarysigned.sql.log.ref
Failed. Check sql/binarysigned.sql.diff for differences.
tested sql/binaryunsigned.sql.log against sql/binaryunsigned.sql.log.ref
Failed. Check sql/binaryunsigned.sql.diff for differences.

[root@srvss2 srvswdev11]# diff test011/sql/binarysigned.sql.log test011/sql/binarysigned.sql.log.ref
8,9c8,9
< 0 1007 -126 -32766 -2147483646 -9223372036854775806 -9.9 -99.99 -99999.99 -9999999999.99 -3.40282e38 -1.7976931348623157e308
< 0 1008 127 32767 2147483647 9223372036854775807 9.9 99.99 99999.99 9999999999.99 3.40282e38 1.7976931348623157e308

hill Output in your above comment is cutoff - so I am putting it again here for completeness

diff test011/sql/binarysigned.sql.log test011/sql/binarysigned.sql.log.ref
8,9c8,9
< 0 1007 -126 -32766 -2147483646 -9223372036854775806 -9.9 -99.99 -99999.99 -9999999999.99 -3.40282e38 -1.7976931348623157e308
< 0 1008 127 32767 2147483647 9223372036854775807 9.9 99.99 99999.99 9999999999.99 3.40282e38 1.7976931348623157e308
—
> 0 1007 -126 -32766 -2147483646 -9223372036854775806 -9.9 -99.99 -99999.99 -9999999999.99 -3.40282e+38 -1.79769313486232e+308
> 0 1008 127 32767 2147483647 9223372036854775807 9.9 99.99 99999.99 9999999999.99 3.40282e+38 1.79769313486232e+308

As can be seen that the difference is because MariaDB ColumnStore is using e notation like this: 3.40282e38, where as the reference log is using 3.40383e+38

The value in the result shown by MariaDB ColumnStore and the reference are same, but the display format notation are different - so the reference log files and binaryunsigned.sql.log.ref and binarysigned.sql.log.ref need to be updated to use e38 notation instead of e+38 notation

After you update the reference log file - run this test script and if it passes please close the issue.

change made to ref logs

hill, Just to confirm ref log for both binarysigned.sql.log.ref and binaryunsigned.sql.log.ref needs to be updated

Not failing any more - so closing this