xiaoshan1213 commented on issue #30256: URL: https://github.com/apache/superset/issues/30256#issuecomment-2532966221
Hi thanks for the response, I opened a email thread to discuss, but haven't got any response from there yet. And to answer the questions above • Where are the results being stored/cached to avoid re-running the query -- Superset has backend preserve feature, and in our case we configure to store in S3. • How do we deal with things like the data changing since the query was run (i.e. cache invalidation) -- For this case, we can bring up some notification on UI about this result is retrieved at what date and time, customers can choose to rerun the query. • How do we address security implications, e.g. row level security, PII leakage, etc. -- For now, we are not considering this, since once customers within query_lab role, they should be able to access the query results or shared results. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
