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

Add job identifier to FeatureRow #147

Merged
merged 3 commits into from
Mar 3, 2019
Merged

Conversation

mansiib
Copy link
Contributor

@mansiib mansiib commented Mar 1, 2019

Issue #145

@zhilingc
Copy link
Collaborator

zhilingc commented Mar 1, 2019

/approve

@feast-ci-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: zhilingc

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

@tims
Copy link
Contributor

tims commented Mar 1, 2019

Does the job id get set by core when it starts the job? if not it wont match Beam's notion of a job name.

@zhilingc
Copy link
Collaborator

zhilingc commented Mar 1, 2019

@tims It's slightly confusing, but the Feast definition of job id is actually the job name (not the job id) and is what we return to the user when they run a job; we map it to the runner's job id internally. Since this will be written to BQ, which is external, it makes sense to use this instead of the runner job id.

@tims
Copy link
Contributor

tims commented Mar 2, 2019

I meant, is the jobId being set as the job name in when you start the runner? I thought it wasn't based on conversations, but it seems that it is:

https://github.com/gojek/feast/blob/c525845b05d73e8ec10511b93c34f3105ae438b8/core/src/main/java/feast/core/job/direct/DirectRunnerJobManager.java#L81

@tims
Copy link
Contributor

tims commented Mar 2, 2019

/lgtm

@zhilingc
Copy link
Collaborator

zhilingc commented Mar 2, 2019

@tims If the user sets it from the API it will be the user provided value, if not ingestion will generate one.

@zhilingc
Copy link
Collaborator

zhilingc commented Mar 2, 2019

@mansiib you probably want to merge in the changes you made in PR #146

@tims
Copy link
Contributor

tims commented Mar 2, 2019

@tims If the user sets it from the API it will be the user provided value, if not ingestion will generate one.

That's why I asked

@zhilingc
Copy link
Collaborator

zhilingc commented Mar 2, 2019

@tims If the user sets it from the API it will be the user provided value, if not ingestion will generate one.

That's why I asked

Oh right. Sorry, I can't read apparently. haha. It does, as you've already found out.

@feast-ci-bot feast-ci-bot removed the lgtm label Mar 2, 2019
@zhilingc
Copy link
Collaborator

zhilingc commented Mar 2, 2019

/retest

@zhilingc
Copy link
Collaborator

zhilingc commented Mar 3, 2019

/lgtm

@feast-ci-bot feast-ci-bot merged commit 0a89bd6 into feast-dev:master Mar 3, 2019
@feast-ci-bot
Copy link
Collaborator

@mansiib: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
presubmit-unit-tests 21db33c link /test presubmit-unit-tests

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.

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.

4 participants