-
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
Add job identifier to FeatureRow #147
Conversation
/approve |
[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 |
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. |
@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. |
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: |
/lgtm |
@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. |
/retest |
/lgtm |
@mansiib: The following test failed, say
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. |
Issue #145