- 17.9K All Categories
- 3.3K Industry Applications
- 3.3K Intelligent Advisor
- 60 Insurance
- 534.5K On-Premises Infrastructure
- 137.7K Analytics Software
- 38.5K Application Development Software
- 5.3K Cloud Platform
- 109.1K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 70.8K Infrastructure Software
- 105.1K Integration
- 41.5K Security Software
Redaction Policies on ODI Integration Tables
I have data being loaded to a staging table where the staging table has a number of redacted fields. The ODI user is exempt from this policy so it can see the data.
The data is being transformed and loading into a dimension table which is redacted on the same fields, and the ODI user is exempt from this policy as well.
Moving data from staging to dimension works without any issue.
My concern is that the integration tables are not redacted. The integration tables are isolated in a schema that others don't have access to, the integration tables are dropped on completion and on error, but I am dealing with a large volume of identifiable information, but I at least need to make sure that I have explored all options before I rule out any possibilities.
The options I have considered:
- Avoid integration tables - easy enough to address, but performance is impacted when attempting to carry out the transformations in memory;
- Use static integration tables with a redaction policy on these - achievable, but does limit the executions to serial over parallel since I'm loading from multiple sources;
- Modify the knowledge module to add a redaction policy on table creation - Would require the ODI user having permissions to modify policies, and may be complex to incorporate in a knowledge module - also KM won't be supported which is a business concern.
I'm curious to know what your thoughts on the options above, or if you have an alternative approach.