Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should TS Data Connections be rebuilt against the new Data Catalog tables? #7

Open
mcoles opened this issue Oct 31, 2019 · 0 comments
Labels
question Further information is requested

Comments

@mcoles
Copy link
Contributor

mcoles commented Oct 31, 2019

The new Data Catalog feature includes several new tables which can be useful for understanding underlying connections in Tableau Server. A non-exhaustive list:

column_assets
table_assets
database_assets
data_quality_indicators

There are also hist_* tables for each of these, along with *_events tables. These tables are all generated in the process of Data Catalog discovering and tracking what assets it has processed into the GraphQL database for Catalog.

On the database_assets table, the source_type and source_id can be used to join to the workbooks or datasources table. It's not clear that these can be linked to a data_connections record, though, which is what would be needed to determine which connection used the assets in question, though. There also seems to be no link between columns as found in databases in general, and how they're used in a given workbook or data source. Nor is there any link yet between a view and it's data connection(s).

On the whole, I tend to think we're probably better off just incorporating some basic fields from data_quality_indicators into this, and offloading the heavy lifting for what-uses-what logic to Data Catalog.

@mcoles mcoles added the question Further information is requested label Oct 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant