-
Notifications
You must be signed in to change notification settings - Fork 13.8k
[FLINK-22159][FLINK-22302][docs][table] Restructure SQL "Queries" pages and add docs for the new window TVF based operations #15642
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
Conversation
|
@leonardBang could you help to review this? cc @twalthr @sjwiesman , would be great if you can have a look too. |
|
Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community Automated ChecksLast check on commit 2870d23 (Sat Aug 28 11:16:36 UTC 2021) ✅no warnings Mention the bot in a comment to re-run the automated checks. Review Progress
Please see the Pull Request Review Guide for a full explanation of the review process. DetailsThe Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commandsThe @flinkbot bot supports the following commands:
|
leonardBang
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @wuchong for the great work, I left some comments about TVF pages
| > SELECT * FROM TABLE( | ||
| TUMBLE(TABLE Bid, DESCRIPTOR(bidtime), INTERVAL '10' MINUTES)); | ||
| -- or with the named params | ||
| -- note: the DATA param must be the first | ||
| > SELECT * FROM TABLE( | ||
| TUMBLE( | ||
| DATA => TABLE Bid, | ||
| TIMECOL => DESCRIPTOR(bidtime), | ||
| SIZE => INTERVAL '10' MINUTES)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add note that Note: Currently Flink doesn't support individual window table-valued function, window table-valued function should use with aggregate operation, here we just for explanation the data produced by table-valued function
| --+---------+-------+------+--------------+------------+--------------+ | ||
|
|
||
| -- apply aggregation on the tumbling windowed table | ||
| > SELECT window_start, window_end, SUM(price) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: we can use TIMESTAMP for bidtime and DECIMAL for price so that user can reproduce this case easily
|
Thanks @leonardBang for the reviewing, I have addressed your comments. |
sjwiesman
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for picking this up @wuchong , I have reviewed the English pages of this PR
Co-authored-by: Seth Wiesman <sjwiesman@gmail.com>
Co-authored-by: Seth Wiesman <sjwiesman@gmail.com>
|
Thanks @sjwiesman for polishing the docs, it looks much better now! I also applied the changes to Chinese docs. |
sjwiesman
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…ased operations This closes #15642
…to one page per operation This closes #15642
…ased operations This closes #15642
…to one page per operation This closes apache#15642
…ased operations This closes apache#15642
What is the purpose of the change
This add documentations for new introduced window TVF based operations and also restructure "Queries" page.
Currently, the "Queries" page has been very large and it's getting longger when we supporting more features. We already have separate pages for Joins and CEP. I would propose to separate "Queries" into one page per operation. This way we can easily add more detailed informations for the operations and more examples.
Brief change log
The "Queires" page is restructured into following pages:
I also refer some contents from https://docs.ververica.com/user_guide/sql_development/queries.html
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
@Public(Evolving): (yes / no)Documentation