Qlik Community

Qlik Compose for Data Lakes

Discussion board for collaboration on Qlik Compose for Data Lakes.

Announcements
Qlik Insider: SaaS capabilities for Data Integration and Analytics, May 25th! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
varadharaj
Contributor II
Contributor II

Boolean datatype not available in Metadata mapping

Boolean datatype is not available for metadata mapping in attunity compose for data lakes.

Available datatypes,

Bigint,byte,date,datetimr,decimal,guid,integer,nvarchar,string,time,varchar

Version : 6.5.0.179

Kindly advise if there is any way to map boolean datatype.

1 Solution

Accepted Solutions
TimGarrod
Employee
Employee

If you use the Discovery process to define the storage metadata (and PK's from Replicate) then a BOOLEAN field will be mapped to an INTEGER in C4DL by default.       

If you are creating a BOOLEAN field manually and apply transformation or mapping logic to load it you have a choice depending on how you want to represent it in the lake.

If you want a binary (1/0) representation you can create the data domain as an INTEGER or BYTE.

IF you want a string (T/F, True, False) representation you can create the data domain as a VARCHAR/STRING and apply CASE WHEN ${source_field} =1 then 'TRUE' ELSE 'FALSE' END logic  to provide consumers with a more "consumer friendly" boolean field.

View solution in original post

1 Reply
TimGarrod
Employee
Employee

If you use the Discovery process to define the storage metadata (and PK's from Replicate) then a BOOLEAN field will be mapped to an INTEGER in C4DL by default.       

If you are creating a BOOLEAN field manually and apply transformation or mapping logic to load it you have a choice depending on how you want to represent it in the lake.

If you want a binary (1/0) representation you can create the data domain as an INTEGER or BYTE.

IF you want a string (T/F, True, False) representation you can create the data domain as a VARCHAR/STRING and apply CASE WHEN ${source_field} =1 then 'TRUE' ELSE 'FALSE' END logic  to provide consumers with a more "consumer friendly" boolean field.