Add Feast CLI / python SDK documentation#199
Conversation
For Feast admins.
Using vendored protobuf, here are the new generated files
# Conflicts: # charts/feast/values.yaml # docs/install.md # protos/generated/go/feast/core/CoreService.pb.go # protos/generated/go/feast/core/DatasetService.pb.go # protos/generated/go/feast/core/JobService.pb.go # protos/generated/go/feast/core/UIService.pb.go # protos/generated/go/feast/serving/Serving.pb.go # protos/generated/go/feast/specs/EntitySpec.pb.go # protos/generated/go/feast/specs/FeatureGroupSpec.pb.go # protos/generated/go/feast/specs/FeatureSpec.pb.go # protos/generated/go/feast/specs/ImportJobSpecs.pb.go # protos/generated/go/feast/specs/ImportSpec.pb.go # protos/generated/go/feast/specs/StorageSpec.pb.go # protos/generated/go/feast/storage/BigTable.pb.go # protos/generated/go/feast/storage/Redis.pb.go # protos/generated/go/feast/types/Feature.pb.go # protos/generated/go/feast/types/FeatureRow.pb.go # protos/generated/go/feast/types/FeatureRowExtended.pb.go # protos/generated/go/feast/types/Value.pb.go
other fixes in the docs;
|
Hi @romanwozniak. Thanks for your PR. I'm waiting for a gojek member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/ok-to-test |
Use Feast image tag 0.1.1 because it fixes some templating in BigQuery https://github.com/gojek/feast/releases/tag/v0.1.1
|
/lgtm Thanks Roman! |
|
/lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: romanwozniak, zhilingc The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
In this PR:
granularityfrom the documentation / proto (because it was removed from the codebase in Remove feature "granularity" and relegate to metadata #17)