-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Moving Feast Java back into main repo under java/ package #1997
Conversation
Skipping CI for Draft Pull Request. |
/test all |
@adchia: No jobs can be run with
In response to this:
Instructions 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. |
/test test-core-and-ingestion |
/test test-serving |
/test test-java-sdk |
Codecov Report
@@ Coverage Diff @@
## master #1997 +/- ##
===========================================
- Coverage 82.21% 58.88% -23.34%
===========================================
Files 100 101 +1
Lines 8052 8106 +54
===========================================
- Hits 6620 4773 -1847
- Misses 1432 3333 +1901
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
/retest |
/test test-serving |
/test test-core-and-ingestion |
/test test-java-sdk |
@adchia: The following test failed, say
Full PR test history. Your PR dashboard. Instructions 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. I understand the commands that are listed here. |
/test test-java-sdk |
/test test-serving |
.github/workflows/java_mirror.yml
Outdated
@@ -0,0 +1,25 @@ | |||
name: mirror |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this part is obsolete. It used to mirror to internal repo in Gojek, but that repo is on 0.9-branch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
<version>5.6.2</version> | ||
</dependency> | ||
<dependency> | ||
<groupId>org.springframework.kafka</groupId> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it seems like we bringing back too much
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ingestion part was supposed to be deleted from feast-java long time ago, but it's possible that not everything was deleted
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed, will in a followup PR remove obsolete sections
Are we gonna support 0.9 registry? I'm confused by the goal of this resurrection. IMO, big part of it should die for good |
As an extension to this question and our conversation yesterday. Would it make sense to list out the exact functionality that will not be supported (and is slated for deletion) after this PR is merged? Overall the PR looks good to me, as long as we agree a lot of the code will be deleted after merge. In terms of GitHub Actions: We should probably merge the different tests by category ( |
Signed-off-by: Danny Chiao <[email protected]>
Signed-off-by: Danny Chiao <[email protected]>
Signed-off-by: Danny Chiao <[email protected]>
Signed-off-by: Danny Chiao <[email protected]>
65c2ad7
to
fa66cf5
Compare
Signed-off-by: Danny Chiao <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adchia, pyalex 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 |
/lgtm |
@pyalex will fix some tests very soon |
What this PR does / why we need it:
This is almost a verbatim copy of feast java logic back into feast under java/. A couple of key changes:
In followup PRs, we intend to remove:
We also will consolidate GitHub actions into master vs release vs PR actions (though we need to verify the actions work first).
As far as releases will go. We will switch back to having one consistent version for Feast Java + Feast Python components. This will require we deprecate the old maven + DockerHub package names (e.g. on https://hub.docker.com/u/feastdev and https://mvnrepository.com/artifact/dev.feast) for Feast Java (since Feast Java is on 0.25.2 whereas the main repo is on 0.15) and update tutorials to reflect this.
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: