[MCOL-1783] cpimport is not handling BOOLEAN data type correctly Created: 2018-10-08  Updated: 2021-01-15

Status: Closed
Project: MariaDB ColumnStore
Component/s: cpimport
Affects Version/s: 1.2
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Daniel Lee (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None


 Description   

Build tested: 1.2 source
/root/columnstore/mariadb-columnstore-server
commit 6b44f0d9c453ede53024f525b7ddf32b5323171b
Merge: 7db44a7 853a0f7
Author: Andrew Hutchings <andrew@linuxjedi.co.uk>
Date: Thu Sep 27 20:37:03 2018 +0100
Merge pull request #134 from mariadb-corporation/versionCmakeFix
port changes for mysql_version cmake to fix columnstore RPM packaging
/root/columnstore/mariadb-columnstore-server/mariadb-columnstore-engine
commit 6ee12248b8764569ca7e965b5cc35746b25d816c
Merge: 068b168 47fbf62
Author: Roman Nozdrin <drrtuy@gmail.com>
Date: Mon Oct 8 11:22:42 2018 +0300
Merge pull request #586 from mariadb-corporation/MCOL-1775
MCOL-1775 Fix addtime/subtime for WHERE

1. For a column is of BOOLEAN data type and the data value is the word true or false (not case sensitive) , value load 0. It should be 1 for true or 0 for false. It looks like it is doing a value saturation, string gets change to a 0.

2) When the data value is NULL,

a) cpimport without -n or with "-n 0" switch

Value of 0 is loaded. This is correct as NULL is treated as a value string, saturation should occurred.

b) cpimort with "-n 1"
Value of 1 is loaded. This is incorrect as NULL should be loaded as a null value.



 Comments   
Comment by Andrew Hutchings (Inactive) [ 2018-10-10 ]

Please provide your CSV file so we can reproduce 2 since there are several ways of representing NULL.

Generated at Thu Feb 08 02:31:21 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.