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

Deduplicate example notebooks #456

Merged
merged 2 commits into from
Feb 2, 2020

Conversation

woop
Copy link
Member

@woop woop commented Feb 2, 2020

What this PR does / why we need it:

This PR removes the duplication of example notebooks between the docker-compose section and the root of the project. The docker compose file now spins up a complete Feast with the Feast repository mounted into it, and asks users to use the the examples in the feast/examples/ directory.

Which issue(s) this PR fixes:

Fixes #415

Does this PR introduce a user-facing change?:

NONE

@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

@khorshuheng
Copy link
Collaborator

https://docs.feast.dev/getting-started/installing-feast needs to be updated to direct the user to use the basic notebook instead of quickstart.

@@ -4,9 +4,9 @@ services:
batch-serving:
image: ${FEAST_SERVING_IMAGE}:${FEAST_VERSION}
Copy link
Collaborator

Choose a reason for hiding this comment

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

Previously, i separated the docker compose file into two because i thought there will be use cases where users would only want to start online serving and not batch serving. Now that i am more familiar with Feast i think that doesn't make much sense any more, especially after the change in this PR, where the basic example assumes that both online and batch serving must be present. Do you think we should have one single docker compose file instead, or keep the current setup?

Copy link
Member Author

Choose a reason for hiding this comment

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

I like the idea of merging. I'll do that.

Copy link
Member Author

Choose a reason for hiding this comment

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

Done.

@woop
Copy link
Member Author

woop commented Feb 2, 2020

https://docs.feast.dev/getting-started/installing-feast needs to be updated to direct the user to use the basic notebook instead of quickstart.

Done.

@khorshuheng
Copy link
Collaborator

/lgtm

@feast-ci-bot feast-ci-bot merged commit 361cbd1 into feast-dev:master Feb 2, 2020
khorshuheng pushed a commit to khorshuheng/feast that referenced this pull request Feb 14, 2020
* Deduplicate example notebooks

* Merge docker-compose.yml for both batch and online serving.
@khorshuheng khorshuheng mentioned this pull request Feb 14, 2020
khorshuheng pushed a commit that referenced this pull request Feb 14, 2020
* Deduplicate example notebooks

* Merge docker-compose.yml for both batch and online serving.
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.

Deduplicate example notebooks
4 participants