Skip to content

[CALCITE-3724] Presto dialect implementation#1776

Closed
XuQianJin-Stars wants to merge 2 commits intoapache:masterfrom
XuQianJin-Stars:CALCITE-3724
Closed

[CALCITE-3724] Presto dialect implementation#1776
XuQianJin-Stars wants to merge 2 commits intoapache:masterfrom
XuQianJin-Stars:CALCITE-3724

Conversation

@XuQianJin-Stars
Copy link
Contributor

As illustrated in CALCITE-3724

@XuQianJin-Stars XuQianJin-Stars requested review from danny0405 and hsyuan and removed request for hsyuan January 31, 2020 07:43
@XuQianJin-Stars XuQianJin-Stars changed the title [CALCITE-3724] Implement PrestoSqlDialect [CALCITE-3724] Implement Presto Dialect Feb 4, 2020
@XuQianJin-Stars XuQianJin-Stars changed the title [CALCITE-3724] Implement Presto Dialect [CALCITE-3724] Presto dialect implementation Feb 4, 2020
Copy link
Contributor

@danny0405 danny0405 left a comment

Choose a reason for hiding this comment

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

Thanks for the PR, can you explain why we need a Presto dialect ? Which unparse logic do you want to customize ?

@XuQianJin-Stars
Copy link
Contributor Author

XuQianJin-Stars commented Feb 7, 2020

Thanks for the PR, can you explain why we need a Presto dialect ? Which unparse logic do you want to customize ?

hi @danny0405 The previous discussion is here [1]
[1] https://mail-archives.apache.org/mod_mbox/calcite-dev/202001.mbox/%3cCAPSgeETHa88DN7Bwqd+qez-i1=3XDa2LN3+wQdk7x_QfEXm8Ew@mail.gmail.com%3e

@danny0405
Copy link
Contributor

danny0405 commented Feb 12, 2020

Thanks for the PR, can you explain why we need a Presto dialect ? Which unparse logic do you want to customize ?

hi @danny0405 The previous discussion is here [1]
[1] https://mail-archives.apache.org/mod_mbox/calcite-dev/202001.mbox/%3cCAPSgeETHa88DN7Bwqd+qez-i1=3XDa2LN3+wQdk7x_QfEXm8Ew@mail.gmail.com%3e

Thanks, you can paste the conclusion/the background to the JIRA issue or the link is okey.

@DonnyZone
Copy link
Contributor

Hi, @XuQianJin-Stars, could you please rebase the PR? It will be nice if you can provide presto's doc and highlight the unparse logic in Jira/PR's description.

@XuQianJin-Stars
Copy link
Contributor Author

Hi, @XuQianJin-Stars, could you please rebase the PR? It will be nice if you can provide presto's doc and highlight the unparse logic in Jira/PR's description.

well, but I am a bit busy lately, I will take time to deal with this later.

}

@Test void testCubeInSpark() {
@Test public void testCubeWithGroupBy() {
Copy link
Contributor

Choose a reason for hiding this comment

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

I remember that there was a PR that removed public. We'd better follow this style.

Copy link
Contributor Author

@XuQianJin-Stars XuQianJin-Stars Jun 2, 2020

Choose a reason for hiding this comment

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

I remember that there was a PR that removed public. We'd better follow this style.

well, I have changed it.

@DonnyZone
Copy link
Contributor

LGTM

Copy link
Contributor

@danny0405 danny0405 left a comment

Choose a reason for hiding this comment

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

+1, but needs some refactoring.

@danny0405 danny0405 added the accepted-and-would-rework-soon This patch is overall ok, but need some refactoring by the committers. label Jun 8, 2020
@XuQianJin-Stars
Copy link
Contributor Author

+1, but needs some refactoring.

hi @danny0405 What are the main contents of rework?

@danny0405 danny0405 closed this Jun 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

accepted-and-would-rework-soon This patch is overall ok, but need some refactoring by the committers.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants