Skip to content

Conversation

@DylanGuedes
Copy link
Contributor

What changes were proposed in this pull request?

This PR ports window.sql from PostgreSQL regression tests https://github.com/postgres/postgres/blob/REL_12_STABLE/src/test/regress/sql/window.sql from lines 320~562

The expected results can be found in the link: https://github.com/postgres/postgres/blob/REL_12_STABLE/src/test/regress/expected/window.out

How was this patch tested?

Pass the Jenkins.

Why are the changes needed?

To ensure compatibility with PGSQL

Does this PR introduce any user-facing change?

No

How was this patch tested?

Comparison with PgSQL results.

Signed-off-by: DylanGuedes <[email protected]>
@HyukjinKwon
Copy link
Member

add to whitelist

@HyukjinKwon
Copy link
Member

cc @maropu, @dongjoon-hyun, @wangyum, @MaxGekk

@SparkQA
Copy link

SparkQA commented Oct 15, 2019

Test build #112097 has finished for PR 26121 at commit 2d86681.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@gengliangwang
Copy link
Member

@DylanGuedes Thanks for the work.
Please wait until #26107 is merged.

@dongjoon-hyun
Copy link
Member

#26107 is merged. Thanks, @gengliangwang .

@dongjoon-hyun
Copy link
Member

Retest this please.

@SparkQA
Copy link

SparkQA commented Oct 15, 2019

Test build #112122 has finished for PR 26121 at commit 2d86681.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

Copy link
Member

@HyukjinKwon HyukjinKwon left a comment

Choose a reason for hiding this comment

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

Seems fine. I'm going to merge this in few days.

-- nth_value(salary, 1) over(order by salary range between 1000 preceding and 1000 following),
-- salary from empsalary;

select last(salary) over(order by salary range between 1000 preceding and 1000 following),
Copy link
Member

Choose a reason for hiding this comment

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

Nit: It would be better if the SQL keywords are all in UPPERCASE.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I can make them uppercase, but, are you sure? I think that in PostgreSQL they are not always uppercase, such that the diff will be totally different.

@HyukjinKwon
Copy link
Member

I'm going to just merge this. It has been open so long and I am sure it has been exposed to reviewers enough time.

@HyukjinKwon
Copy link
Member

Merged to master.

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.

5 participants