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
If I have two columns that are both assigned to AnonymizedFaker (eg. for uuid4), then the reverse transform always produces the same exact values for both columns. This is unexpected, as I'd want each uuid column to have different values.
We should change the behavior for the AnonymizedFaker and PseudoAnonymizedFaker transformers.
When first initializing the HyperTransformer, we should set a different seed for each of these transformers. (The seed values should be deterministic. Eg. The transformer for column1 is always set to seed=37.) As a result, these transformers will have a different seed. Each transformer should separately store its seed.
When resetting the HyperTransformer, these transformer should set their own individual seeds to what was stored in step (1)
The text was updated successfully, but these errors were encountered:
@fealho Another suggestion: Instead of just using the column name, create a hash using a combination of the column name and some value(s) in the data itself.
Rationale: Different tables may have the same column name. Eg. there can be an address column in table vendors and also customers. The seed should not be the same for both columns -- that would lead to some unexpected results of vendors and customers having the same addresses!
Problem Description
If I have two columns that are both assigned to
AnonymizedFaker
(eg. foruuid4
), then the reverse transform always produces the same exact values for both columns. This is unexpected, as I'd want each uuid column to have different values.See SDV issue 1303.
Expected behavior
We should change the behavior for the
AnonymizedFaker
andPseudoAnonymizedFaker
transformers.column1
is always set to seed=37.) As a result, these transformers will have a different seed. Each transformer should separately store its seed.The text was updated successfully, but these errors were encountered: