Option to create a resource without overwriting existing records about feast HOT 4 CLOSED

@zhilingc can you highlight the method you are referring to (for extension)?

from feast.

From:

rpc ApplyFeature(feast.specs.FeatureSpec) returns (CoreServiceTypes.ApplyFeatureResponse) {};

To:

rpc ApplyFeature(CoreServiceTypes.ApplyFeatureRequest) returns (CoreServiceTypes.ApplyFeatureResponse) {};

message ApplyFeatureRequest {
  feast.specs.FeatureSpec spec = 1;
  bool update = 2;
}

I'm not sure if i prefer this solution actually.

from feast.

Well, multiple things:

• A better abstraction would be ApplyResource or UpdateResource, otherwise we will reinvent this for all resource types. But if we take that logic further...
• If we eventually intend to move to Kubernetes for managing our resources, then we are basically reinventing the resources management within it. It might be easier to just move all of this into CRDs, and then Feast just becomes a proxy to these requests.

from feast.

This issue isn't relevant any more due to changes in Feast 0.3.0

from feast.