You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
measurement-lab only has views to production tables managed by mlab-oti.
Up to this point, the "canonical" locations for tables did not intersect with real tables in all projects. This was because real tables were in "base_tables" dataset, and we wanted canonical views in the experiment named dataset, e.g. "ndt".
Now the universal gardener creates and writes to tables in the "raw_ndt" dataset for sandbox, staging, and oti. However, we need only views in measurement-lab. The current deployment process does not yet support this.
The text was updated successfully, but these errors were encountered:
It is not resolved. An example of the essential issue: gardener creates ndt.ndt7 in mlab-oti. Something else creates a view for ndt.ndt7 in measurement-lab.
Right but both are expected to change. I would expect something like mlab-oti.ndt_raw.ndt7_x20210401 for the gardner output and *.raw_ndt.ndt7 for views in all projects. at the moment we can exploit raw_ndt vs ndt_raw to sitestep the problem.
BTW this might be a nice motif for all tables (versioned) and views (unversioned) in the same dataset. e.g. also ndt_joined
measurement-lab only has views to production tables managed by mlab-oti.
Up to this point, the "canonical" locations for tables did not intersect with real tables in all projects. This was because real tables were in "base_tables" dataset, and we wanted canonical views in the experiment named dataset, e.g. "ndt".
Now the universal gardener creates and writes to tables in the "raw_ndt" dataset for sandbox, staging, and oti. However, we need only views in measurement-lab. The current deployment process does not yet support this.
The text was updated successfully, but these errors were encountered: