Hi, > GDPR doesnt need milisecond realtime deletion right ?) right.
> since inbound FFs have > normally hundreds, thousands of records that will need to split, aggregate, > in complex flow file, implementing a clean It depends on your application. Not everyone uses NiFi for IoT and therefore a single record may be included. > In my opinion your answer to business/management gate keepers is that data > will be stored on data provenance for 24h (default) which can be > configured, and that This is not necessarily the point of the Data Lineage, that the information is deleted after 24 hours (or whatever is configured). If Data Lineage is needed (revision, legal requirements etc.), then deleting the data after a defined time is not an option. This is the reason why Atlas supports it. Best Regards, Uwe Am 30.01.2020 um 15:06 schrieb Emanuel Oliveira: > Hi, dont think makes sense an api for atomic records: > > 1. one configure retention od data provenance (default 24h is "good > enough" GDPR doesnt need milisecond realtime deletion right ?) > > https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#persistent-provenance-repository-properties > 2. even if there would be one api to delete FF's with an attribute = > <some id>, that would normally be useless as well, since inbound FFs have > normally hundreds, thousands of records that will need to split, aggregate, > in complex flow file, implementing a clean up an nano atomic level would be > to hard and extra effort not needed, since your target single record would > surely be part of multiple FF UUIDs, some only holding your record, but mot > surefly will have 100s, 100s of other records including your record > somewhere on the middle. > > > In my opinion your answer to business/management gate keepers is that data > will be stored on data provenance for 24h (default) which can be > configured, and that > > > Best Regards, > *Emanuel Oliveira* > > > > On Thu, Jan 30, 2020 at 1:54 PM [email protected] <[email protected]> > wrote: > >> Dear NiFi developer team, >> >> NiFi's Data Provenance and Data Lineage is perfectly adequate in the >> environment of NiFi, so there is often no need to use Atlas. >> >> When using NiFi with customer data a problem arises. >> The problem is the GDPR requirement that a user has the right to be >> forgotten. Unfortunately, I can't find any API call or information on >> how to delete individual user data from the NiFi Provenance Repository >> based on a user-defined attribute and its defined characteristics. >> >> A delete request like "delete all data and dependencies where the >> attribute XYZ has the value 123" is currently not possible to my knowledge. >> >> My questions are: >> Is this actually possible and how? And if not, is it planned? >> >> Thanks >> Uwe >>
