working on a different query (not the one from above), but the arn (or guid or hash or whatever you want to call it) that is the first that you see, may not be traceable; but in the SQL (at least in this complex SQL with multiple with clauses aka CTE), there is an ARN in the SQL that maps back to something in the dataset. The SQL in redshift in the QS built portion of the SQL (that wraps our custom SQL), there is an arn that maps back to a PhyscialTableMap component as per the CLI. I used the following CLI command to generate the file datasetoutput.txt:
aws quicksight describe-data-set --aws-account-id 150970770365 --data-set-id f8f5ec22-a01b-44a8-90dc-c030a2f1af1b >datasetoutput.txt
I need confirm that dataset built without custom SQL (what I call the visual approach) also follow this pattern.
If this holds true, then one step is dump all of datasets via cli using python and cross reference dataset to physical table map ARN’s, and then step two is to interrogate redshift sql history and parse the SQL looking for ARNs and match those to the ones found in the first step.