Hello @hello_knime. This bug probably occurs when you provide the anonymization conditions that are not possible to fulfil. I may suggest you to try to make your anonymization requirements a bit loose. One of the most simple way to do that is to set up the suppression limit more than 0. It means that you would allow the algorithm to produce completely anonymized records (with *-values for quasi-identifiers) for some outliers in your data set.
Also you can try to set up a wider range of hierarchy levels in case you restricted them, or maybe you should revise your hierarchies.
Please let me know if this advice is helpful for you, and if it helped to get rid of this error message.
Otherwise please provide more details about the settings that you are using, or maybe you could share a workflow.
Thank you very much for your kind reply. I have tried your suggestion; but unfortunately, I still get the same error (please see the attached screenshot).
Could you please suggest me a list of literature to understand this Hierarchical Anonymization better?
Hello Sharif. I have just downloaded the workflow and ran it from scratch, and I did not find any issues.
Have you changed settings of any other nodes in the workflow? The Hierarchical Anonymization node might be sensitive to the data set it is processing. Maybe you could share you workflow in an executed state, so I will also have this error as you do?
In order to learn more about hierarchies you can watch the webinar, where I have explained how to work with the anonymization nodes:
I think I have found a found a problem, and it was easy fortunately. Some hierarchies, necessary for the anonymization were missing since you have deleted the connection between Create Hierarchy and Hierarchy Reader nodes. This should solve your problem.