Any design recommendations for Pinot setups that need to deal with data protection requirements of different locations where certain personal data should remain in location boundaries (e.g. GDPR)? Do people try to setup global tables and use Server and Segment definitions to limit scope? Or do people create separate tables?
03/22/2021, 3:16 AM
I am unsure if there is a way for you to force (moreover guarantee) a segment be on a certain server (in a certain geo location).
Which leaves option 2 I guess.
For your case, would you end up with too many tables (one per geo location boundary)? Perhaps something that can be explored as a feature request (in which case, do you mind opening an issue?).
03/23/2021, 12:14 AM
Ah okay. Good to know. It’s fine if we have multiple tables. I’d imagine this number will grow with time.
I’m curious to see what other companies do. I imagine this is a common issue.
03/23/2021, 12:18 AM
For us, the GDPR requirements have been more around purging PII data when needed. And for that, we have setup a Minion job to perform the purging. I haven't personally run into the requirements you mentioned, although it makes sense to me, which is why I was exploring if more folks need it, perhaps we can open a request for the same.