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
Right now every time we want to open the telescope picker, we have to run the dbt cli.
We could make use of some kind of caching strategy to speed up the process.
We would store the state of the output, using the state of files inside the dbt project, we would redirect to the cached result when none had changed.
Even better we could attached the function responsible to generate the model state when a buffer is saved, to try to avoid cold start to a maximum.
I'm up to looking into such a thing, but do you have another view on how to reason about this thing ?
The text was updated successfully, but these errors were encountered:
There's not a lot of great options at the moment. dbt-rpc which would have been perfect, has been deprecated. dbt-server is not really in a state where I can develop against.
Caching is definitely possible, if you'd like to contribute I'd be happy to accept a PR. Happy to assist with that.
Right now every time we want to open the telescope picker, we have to run the dbt cli.
We could make use of some kind of caching strategy to speed up the process.
We would store the state of the output, using the state of files inside the dbt project, we would redirect to the cached result when none had changed.
Even better we could attached the function responsible to generate the model state when a buffer is saved, to try to avoid cold start to a maximum.
I'm up to looking into such a thing, but do you have another view on how to reason about this thing ?
The text was updated successfully, but these errors were encountered: