Open dmartinol opened 3 days ago
right, makes sense. this is similar to #4186. Basically, we need to move all DataSource
methods that actually need to touch the datasets from DataSource
to OfflineStore
. I did this only for valiadate
before, now we need to do the same for get_table_column_names_and_types
.
I see that validate_data_source
is a static method in OfflineStore
interface. I assume we want to make it an instance method and re-implement if in the OfflineServer class, right? together with the other new method get_table_column_names_and_types
, of course.
This should not require a big effort, even if the Arrow Flight server was not exactly design to serve such purposes but rather suited for "efficient data transport". Shouldn't we make it a multi-protocol application instead and delegate some endpoints unrelated to data-transport to a traditional REST or grpc server?
This should not require a big effort, even if the Arrow Flight server was not exactly design to serve such purposes but rather suited for "efficient data transport". Shouldn't we make it a multi-protocol application instead and delegate some endpoints unrelated to data-transport to a traditional REST or grpc server?
imho that would end up being more complicated than adding a couple of non-data "endpoints" to a flight server,
I will start evaluating this one.
I think we can start by requiring data source read permissions for both.
Expected Behavior
Running
feast apply
from a client connected using remote proxies should apply the python definitions.Current Behavior
The apply fails. With a project using the
postgres
template and a deployment onkind
using #4528 it throws the following error:Reference to local
feature_store.yaml
:Forwarded ports for all remote services to local ports 8001-8003 (see working example of
feast feature-views list
).Steps to reproduce
Follow steps of PR #4528 and then run
feast apply
from theclient
folder (after copying theexample_repo.py
)