-
Notifications
You must be signed in to change notification settings - Fork 12
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
Document structure design #63
Comments
Current structure SQLFlow
Proposed structure SQLFlow
Team, please review and comment. |
@llxxxll any suggestion? |
Looks good. |
Test model -> model validation |
This part means adding some definitions for some terminologies we use in SQLFlow, e.g. executer, SQLFlow server, RPC server, etc...For sure the less terms we created, the better. |
Thanks for the review, Any suggestion for the structure I proposed? |
I updated the structure following the latest SQLFlow repo:
|
Document structure design
- The principle of gradual progress.
- Users at different stages of learning can find the corresponding guide.
- Each model should have a corresponding application example.
The text was updated successfully, but these errors were encountered: