Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project Namespacing #393

Merged
merged 4 commits into from
Dec 27, 2019
Merged

Project Namespacing #393

merged 4 commits into from
Dec 27, 2019

Conversation

woop
Copy link
Member

@woop woop commented Dec 26, 2019

@feast-ci-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: woop

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@zhilingc
Copy link
Collaborator

/retest

3 similar comments
@zhilingc
Copy link
Collaborator

/retest

@zhilingc
Copy link
Collaborator

/retest

@zhilingc
Copy link
Collaborator

/retest

woop and others added 3 commits December 27, 2019 13:06
* Update Protos, Java SDK, Golang SDK to support namespacing
* Fixed Python SDK to support project namespacing protos
* Add integration with projects, update code to be compliant with new protos
* Move name, version and project back to spec
* Update Feast Core and Feast Ingestion to support project namespacing
* Update Core and Ingestion based on refactored FeatureSet proto
* Remove entity dataset validation
* Register feature sets first to speed up tests
@zhilingc zhilingc force-pushed the project-namespacing-squashed branch from de67d1f to f6c7ca0 Compare December 27, 2019 05:19
@davidheryanto
Copy link
Collaborator

/lgtm

@feast-ci-bot feast-ci-bot merged commit 5b69331 into master Dec 27, 2019
@woop woop deleted the project-namespacing-squashed branch December 30, 2019 02:05
}
// Version of the field
@Column(name = "version")
private int version;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just noticed this… Fields got a version in v0.4?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants