How to compare null values in Data Profiling - Cross Table Analysis

[Edith1]

Hello all,

I am using the Cross Table Analysis to compare all the columns between two tables. I discovered the # of rows not matched can have rows that have null values for any of the columns. These rows are in fact the same because the null value exists on both tables for the same column. 

Is there a setting I can change to incorporate null values? 

Here's an example, this row was included to the total for # NotMatch when in fact both rows in both tables match because the null value exists in the same column. 

TABLE A = 1000404677;Pat;Love;<null>;

TABLE B = 1000404677;Pat;Love;<null>;    

[Anonymous]

@Edith Murillo​ I have checked with our developers and we confirmed the issue, there is no a workaround now, however, we have found a way to fix it, we will add an option to handle the null value on the component.

https://jira.talendforge.org/browse/TDQ-19030

You can watch the jira issue and follow the status.

Regards

Shong