Fair point, the ID joins do get heavy in a federated model. Two things that help:
For Predictive Optimization specifically, you can skip the billing join entirely. system.storage.predictive_optimization_operations_history already reports catalog, sch...
@srikanthp24 ,
To your core question: multiple gateway pipelines against the same source database don't interfere with each other. Each gateway keeps its own independent state, its own staging volume, and its own CDC/change-tracking cursor, so a sepa...
Hi @data_pulse ,
Short answer: no, that propagation isn't supported. Unity Catalog catalog/schema/table tags do not flow into system.billing.usage.custom_tags for Predictive Optimization, Data Quality Monitoring, or Lakehouse Monitoring. This is by...
Hi @tcranoratmcgee ,
This is likely a NetSuite API limitation rather than a Lakeflow bug, set expectations that full scans may be unavoidable for this table, and I recommend confirming whether snapshot mode offers a viable alternative.
SuiteAnalytics...
Hi @POCUSER ,
Yes, the Lakebase Data API can be used privately with Public Network Access disabled. Because the Data API is a REST endpoint (Lakebase Data API), it goes through your workspace’s standard inbound (front-end) Private Link, the databrick...
