purple-printer-15193
05/02/2023, 3:34 PMsnowflake.account_usage.tag_references
table but I don’t see this table in the lineage. The snowflake.account_usage.tag_references
also never gets ingested by our Snowflake ingestion recipe. Lastly, when I try to just ingest the SNOWFLAKE
database I get an error like below:
"source": {
"type": "snowflake",
"report": {
"events_produced": 0,
"events_produced_per_sec": 0,
"entities": {},
"aspects": {},
"warnings": {},
"failures": {
"permission-error": [
"No tables/views found. Please check permissions."
]
},
I can definitely see and query the snowflake.account_usage.tag_references
table using the Snowflake UI though so I’m not sure if it’s really a permission error at all.
Thanks.lively-cat-88289
05/02/2023, 3:34 PMhigh-hospital-85984
05/02/2023, 3:48 PMpurple-printer-15193
05/02/2023, 3:50 PMsnowflake.account_usage.tag_references
table. So what I was expecting was thispurple-printer-15193
05/02/2023, 3:51 PMhigh-hospital-85984
05/02/2023, 3:57 PMastonishing-answer-96712
05/02/2023, 9:27 PMgray-shoe-75895
05/03/2023, 9:19 PMsnowflake.account_usage.tag_references
as a “system table” and hence automatically filter it out from both schema ingestion and lineage. I don’t think there’s a way to override that behavior, but cc @hundreds-photographer-13496 to confirmhundreds-photographer-13496
05/04/2023, 5:09 AMdatabase_pattern
config. If not specified in recipe explicitly it takes the form below. You can override this in recipe by explicitly setting the deny pattern and not including SNOWFLAKE in it.
database_pattern:
allow:
- .*
deny:
- ^UTIL_DB$
- ^SNOWFLAKE$
- ^SNOWFLAKE_SAMPLE_DATA$