Ben Cassell

@ktopcuoglu does the work around you provide work with Unity Catalog? My understanding was that external tables were mutually exclusive with managed...

Can you validate if this error is still present in 1.8.0b1? I suspect that it is, but since that release has many changes to how MVs work, would really appreciate...

As a workaround, you can just target a different profile with beefier compute when you run test. Otherwise, I think this is better raised with dbt-core.

> That's what I got in place. Though prevents me from running dbt build which is annoying. Understood. We're working on supporting compute per model, and maybe that will help...

We are taking it into consideration for planning. If you would like to expedite, consider submitting a PR with an implementation :).

Thanks for reporting. Does anything jump out if you look at the compiled version of the sql? Jinja is crazy...

@jeremyyeo does this still repro? If so, please remove the stale label, otherwise close :).

@eblanchi thanks for confirming so that we can prioritize.

For anyone who comes across this issue: I believe this is related to using seeds with a specified location_root/external locations. We will investigate ways to work around this limitation, but...

@mv1742 does this still repro on 1.6.x?