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