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

docs: Credit-risk-end-to-end example #4630

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

dandawg
Copy link
Contributor

@dandawg dandawg commented Oct 16, 2024

What this PR does / why we need it:

This PR presents a clear step-by-step guide aimed at data science teams who need a basic hands-on introduction to Feast. I use the AI modeling workflow to demonstrate Feast in-context. In this example, the data doesn't randomly appear with feast init, and it's not randomly generated (except for timestamps and IDs). The example data comes from a popular OpenML dataset, and the reader progresses through data preparation, model training, and model serving. The example walks through the basic steps of the AI modeling process, and Feast solutions are brought in where they naturally provide value.

As people of different roles (data scientists, data engineers, DevOps, AppDevs, etc.) need introductions to Feast and how it fits in the AI/ML flow, I've kept the example approachable, so that someone who doesn't know all of the technical disciplines can follow along and get an idea of the full picture.

Which issue(s) this PR fixes:

The quickstart documentation and other examples are great for describing Feast functionality, but they use randomly generated data with no real patterns, and they are not as clear on where things fit in the process of doing AI/ML.

Misc

@dandawg dandawg changed the title docs: credit-risk-end-to-end example docs: Credit-risk-end-to-end example Oct 16, 2024
@dmartinol
Copy link
Contributor

👏 👏 👏

@dandawg dandawg force-pushed the feast-sklearn-example branch 2 times, most recently from 2b08cdb to 2dc651c Compare October 21, 2024 01:53
Copy link
Member

@franciscojavierarceo franciscojavierarceo left a comment

Choose a reason for hiding this comment

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

Let's adjust based on the feedback provided

@dandawg dandawg requested a review from a team as a code owner October 28, 2024 02:24
@dandawg
Copy link
Contributor Author

dandawg commented Nov 21, 2024

@franciscojavierarceo I've adjusted this PR based on the feedback given. I believe it's ready to merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants