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

[improve](function) the offset params in lead/lag function could use 0 #33174

Merged
merged 1 commit into from
Apr 4, 2024

Conversation

zhangstar333
Copy link
Contributor

@zhangstar333 zhangstar333 commented Apr 2, 2024

Proposed changes

before limit the offset param must > 0,
could follow mysql behavior >=0, so offset could equal to 0.

Issue Number: close #xxx

Further comments

If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...

@doris-robot
Copy link

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR

Since 2024-03-18, the Document has been moved to doris-website.
See Doris Document.

@zhangstar333
Copy link
Contributor Author

run buildall

@doris-robot
Copy link

TPC-H: Total hot run time: 38550 ms
machine: 'aliyun_ecs.c7a.8xlarge_32C64G'
scripts: https://github.com/apache/doris/tree/master/tools/tpch-tools
Tpch sf100 test result on commit 6be624828f5db85f3a9db167df34d64c80a6a793, data reload: false

------ Round 1 ----------------------------------
q1	17659	4229	4052	4052
q2	2007	205	182	182
q3	10596	1236	1398	1236
q4	10302	849	956	849
q5	7502	2957	2935	2935
q6	219	136	135	135
q7	1098	637	615	615
q8	9420	2080	2031	2031
q9	6587	6158	6120	6120
q10	8438	3496	3481	3481
q11	413	247	245	245
q12	378	216	214	214
q13	17763	2893	2865	2865
q14	266	245	240	240
q15	522	488	486	486
q16	498	399	385	385
q17	958	904	894	894
q18	7121	6420	6397	6397
q19	1606	1529	1529	1529
q20	597	316	306	306
q21	3540	3069	3047	3047
q22	367	306	315	306
Total cold run time: 107857 ms
Total hot run time: 38550 ms

----- Round 2, with runtime_filter_mode=off -----
q1	4059	4048	4010	4010
q2	330	219	219	219
q3	2948	2921	2945	2921
q4	1855	1798	1855	1798
q5	5213	5188	5191	5188
q6	206	126	127	126
q7	2251	1801	1803	1801
q8	3207	3265	3263	3263
q9	8483	8453	8465	8453
q10	3740	3946	3988	3946
q11	559	467	470	467
q12	753	595	585	585
q13	14660	3153	3220	3153
q14	327	300	293	293
q15	543	492	478	478
q16	474	440	423	423
q17	1778	1728	1703	1703
q18	8248	7728	7294	7294
q19	1672	1668	1666	1666
q20	2026	1793	1813	1793
q21	5211	4951	4960	4951
q22	479	430	448	430
Total cold run time: 69022 ms
Total hot run time: 54961 ms

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Apr 3, 2024
Copy link
Contributor

github-actions bot commented Apr 3, 2024

PR approved by at least one committer and no changes requested.

Copy link
Contributor

github-actions bot commented Apr 3, 2024

PR approved by anyone and no changes requested.

@xiaokang xiaokang added dev/2.0.x usercase Important user case type label and removed dev/2.0.x labels Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by one committer. dev/2.0.9-merged dev/2.1.2-merged reviewed usercase Important user case type label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants