You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When working on #142, I noticed that in hlink/linking/matching/link_step_explode.py, if expand_length is not set for a blocking column, we run the following code:
However, the rest of the code treats exploding_column_name as the output column name and derived_from_column as the input column name. So I think there is a bug here. This should be
instead unless I am misunderstanding something. This is probably a low-impact bug as you need to be blocking on an input column that is an array type to hit it. I believe that most exploded columns are integer columns with expand_length set.
The text was updated successfully, but these errors were encountered:
When working on #142, I noticed that in hlink/linking/matching/link_step_explode.py, if
expand_length
is not set for a blocking column, we run the following code:However, the rest of the code treats
exploding_column_name
as the output column name andderived_from_column
as the input column name. So I think there is a bug here. This should beinstead unless I am misunderstanding something. This is probably a low-impact bug as you need to be blocking on an input column that is an array type to hit it. I believe that most exploded columns are integer columns with
expand_length
set.The text was updated successfully, but these errors were encountered: