Skip to content

Create empty Job Service - #1059

Merged
feast-ci-bot merged 2 commits into
feast-dev:masterfrom
tsotnet:job-service-creation
Oct 21, 2020
Merged

Create empty Job Service#1059
feast-ci-bot merged 2 commits into
feast-dev:masterfrom
tsotnet:job-service-creation

Conversation

@tsotnet

@tsotnet tsotnet commented Oct 15, 2020

Copy link
Copy Markdown
Collaborator

What this PR does / why we need it: This PR creates an empty Job Service with and the Docker image creation step.

@feast-ci-bot

Copy link
Copy Markdown
Collaborator

Hi @tsotnet. Thanks for your PR.

I'm waiting for a feast-dev member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

@woop

woop commented Oct 15, 2020

Copy link
Copy Markdown
Member

/ok-to-test

@woop

woop commented Oct 15, 2020

Copy link
Copy Markdown
Member

/kind housekeeping

Comment thread infra/docker/jobservice/Dockerfile Outdated

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Do we need the tests?

Comment thread protos/feast/core/JobService.proto Outdated

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We can probably just remove this.

Comment thread protos/feast/core/JobService.proto Outdated

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

we should make this a struct for consistency with the ingestion job parameter format

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actually lets just drop it from here for now. The only way this entire Job proto is used is to list jobs, i think it is fine if you just get the basic info like job type and table name there, but not redis connection details.

We can always add more stuff later.

@terryyylim terryyylim left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I think we should standardize the naming to created_timestamp, stop_timestamp since those are use eg in FeatureTable proto as well.

Comment thread protos/feast/core/JobService.proto Outdated

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Maybe standardize to project here?

Comment thread sdk/python/feast/job_service.py Outdated

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I recommend we follow pep8 style guide as stated here, to utilize lowercase separated by underscores for function names.

@tsotnet tsotnet Oct 21, 2020

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

JobService_pb2_grpc module name is autogenerated by grpc, I don't think we have a control to modify it.

Comment thread infra/charts/feast/charts/feast-jobservice/templates/deployment.yaml Outdated
@tsotnet
tsotnet force-pushed the job-service-creation branch from ec84828 to 92ef175 Compare October 21, 2020 09:13
Signed-off-by: Tsotne Tabidze <tsotnet@gmail.com>
@tsotnet
tsotnet force-pushed the job-service-creation branch from 92ef175 to 97f70be Compare October 21, 2020 14:25
Signed-off-by: Tsotne Tabidze <tsotnet@gmail.com>
@tsotnet
tsotnet force-pushed the job-service-creation branch from bde318a to 653160e Compare October 21, 2020 14:35
RUN make compile-protos-python

# Install Feast SDK
COPY .git .git

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Is there a reason why we copy git into the docker file?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Looks like git is used by sdk/python/setup.py here https://github.com/feast-dev/feast/blob/master/sdk/python/setup.py#L52. If I remove this line docker build step errors out.

Also I copied this mostly from the jupyter dockerfile, which contains the similar build step. We could improve docker build files by removing the dependency on git (seems like it's only used to copy the readme file from the git repo root), but I think that's probably better handled by another PR.

@feast-ci-bot

Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tsotnet, woop

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

The pull request process is described here

Details 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

@woop

woop commented Oct 21, 2020

Copy link
Copy Markdown
Member

/lgtm

@feast-ci-bot
feast-ci-bot merged commit 473e0af into feast-dev:master Oct 21, 2020
@tsotnet
tsotnet deleted the job-service-creation branch October 21, 2020 16:12
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.

7 participants