Hub
NodeNode / Manipulator

Hierarchical Anonymization

Community Nodes Privacy
Drag & drop
Like
Copy short link

Node details

Input ports
  1. Type: Table
    Input data table
    Input data table
  2. Type: Arx Config
    Hierarchy Configuration
    Hierarchy Configuration
Output ports
  1. Type: Table
    Result table with anonymized data
    Result table with anonymized data
  2. Type: Table
    Statistics table
    Statistics table
  3. Type: Table
    Suppressed records
    Suppressed records
  4. Type: Table
    Attribute Risks
    Attribute Risks
  5. Type: Flow Variable
    Statistics converted to flow variables
    Statistics converted to flow variables. If partitioning is enabled only first row of statistic table is used

Extension

The Hierarchical Anonymization node is part of this extension:

Related workflows & nodes

  1. Redfield_Privacy_extension_example
    Privacy Anonymization Redfield
    +1
    The workflow gives an example of how the Privacy extension nodes are used for data anonym…
    redfield > Public > Redfield_Privacy_extension_example
  2. Redfield_Privacy_extension_example
    Privacy Anonymization Redfield
    +1
    The workflow gives an example of how the Privacy extension nodes are used for data anonym…
    jwienstroeer > Public > Redfield_Privacy_extension_example
  3. Anonymization workshop by Redfield
    redfield > Public > Anonymization workshop by Redfield
  4. 02.1_Data_Anonymization
    Best practices Data engineer Data engineering
    +1
    The company has two branches: one in the United States and another one in Europe. New US …
    knime > Education > Courses > L4-DE Best Practices for Data Engineering > solutions > Session_2_ETL_Processing_II > 02.1_Data_Anonymization
  5. 02.2 Database update
    Best practices Data engineer Data engineering
    +1
    The company has two branches: one in the United States and another one in Europe. New US …
    knime > Education > Courses > L4-DE Best Practices for Data Engineering > exercises > Session_2_ETL_Processing_II > 02.2_Database_update
  6. 02.2 Database update
    Best practices Data engineer Data engineering
    +1
    The company has two branches: one in the United States and another one in Europe. New US …
    knime > Education > Courses > L4-DE Best Practices for Data Engineering > solutions > Session_2_ETL_Processing_II > 02.2_Database_update
  7. 04.1_ETL_Customers
    Best practices Data engineer Data engineering
    +1
    The company has two branches: one in the United States and another one in Europe. New US …
    knime > Education > Courses > L4-DE Best Practices for Data Engineering > exercises > Session_4_Orchestration > 04.1_ETL_Customers
  8. 04.1_ETL_Customers
    Best practices Data engineer Data engineering
    +1
    The company has two branches: one in the United States and another one in Europe. New US …
    knime > Education > Courses > L4-DE Best Practices for Data Engineering > solutions > Session_4_Orchestration > 04.1_ETL_Customers