[jira] [Commented] (CALCITE-4035) Adapter for REST interface with query or path parameters

[ https://issues.apache.org/jira/browse/CALCITE-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121475#comment-17121475 ] David Hait commented on CALCITE-4035: - One limitation I see right away with the Fil

[jira] [Updated] (CALCITE-4033) SqlNode.toSqlString generates wrong query for syntax "literal(select * from unnest(...))"

[ https://issues.apache.org/jira/browse/CALCITE-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rui Wang updated CALCITE-4033: -- Description: Reported from: https://issues.apache.org/jira/browse/DRILL-7722 // Updated based on Jul

[jira] [Updated] (CALCITE-4033) SqlNode.toSqlString generates wrong query for syntax "literal(select * from unnest(...))"

[ https://issues.apache.org/jira/browse/CALCITE-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rui Wang updated CALCITE-4033: -- Description: Reported from: https://issues.apache.org/jira/browse/DRILL-7722 // Updated based on Jul

[jira] [Commented] (CALCITE-4033) SqlNode.toSqlString generates wrong query for syntax "literal(select * from unnest(...))"

[ https://issues.apache.org/jira/browse/CALCITE-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121439#comment-17121439 ] Rui Wang commented on CALCITE-4033: --- Thanks Julian for your clarification and sharing

[jira] [Updated] (CALCITE-4033) SqlNode.toSqlString generates wrong query for syntax "literal(select * from unnest(...))"

[ https://issues.apache.org/jira/browse/CALCITE-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rui Wang updated CALCITE-4033: -- Description: Reported from: https://issues.apache.org/jira/browse/DRILL-7722 // Updated based on Jul

[jira] [Commented] (CALCITE-4033) SqlNode.toSqlString generates wrong query for syntax "literal(select * from unnest(...))"

[ https://issues.apache.org/jira/browse/CALCITE-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121437#comment-17121437 ] Julian Hyde commented on CALCITE-4033: -- One problem is that SqlParserTest converts

[jira] [Commented] (CALCITE-3975) ProjectFilterTransposeRule should succeed for project that happens to reference all input columns

[ https://issues.apache.org/jira/browse/CALCITE-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121395#comment-17121395 ] Steven Talbot commented on CALCITE-3975: I see. That all makes sense. To me at

[jira] [Comment Edited] (CALCITE-3975) ProjectFilterTransposeRule should succeed for project that happens to reference all input columns

[ https://issues.apache.org/jira/browse/CALCITE-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121395#comment-17121395 ] Steven Talbot edited comment on CALCITE-3975 at 6/1/20, 11:13 PM: ---

[jira] [Comment Edited] (CALCITE-3975) ProjectFilterTransposeRule should succeed for project that happens to reference all input columns

[ https://issues.apache.org/jira/browse/CALCITE-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121395#comment-17121395 ] Steven Talbot edited comment on CALCITE-3975 at 6/1/20, 11:13 PM: ---

[jira] [Commented] (CALCITE-3975) ProjectFilterTransposeRule should succeed for project that happens to reference all input columns

[ https://issues.apache.org/jira/browse/CALCITE-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121388#comment-17121388 ] Julian Hyde commented on CALCITE-3975: -- I looked into this some more. It turns out

[jira] [Commented] (CALCITE-3951) Support different string comparison based on SqlCollation

[ https://issues.apache.org/jira/browse/CALCITE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121362#comment-17121362 ] Stamatis Zampetakis commented on CALCITE-3951: -- Hey [~rubenql] I am a bit

[jira] [Comment Edited] (CALCITE-4037) AggregateProjectMergeRule doesn't always respect column aliases

[ https://issues.apache.org/jira/browse/CALCITE-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121348#comment-17121348 ] Sylvain Crozon edited comment on CALCITE-4037 at 6/1/20, 9:25 PM: ---

[jira] [Commented] (CALCITE-4037) AggregateProjectMergeRule doesn't always respect column aliases

[ https://issues.apache.org/jira/browse/CALCITE-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121348#comment-17121348 ] Sylvain Crozon commented on CALCITE-4037: - I didn't want to submit a PR since w

[jira] [Commented] (CALCITE-4034) Implement a MySQL InnoDB adapter

[ https://issues.apache.org/jira/browse/CALCITE-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121318#comment-17121318 ] Julian Hyde commented on CALCITE-4034: -- A few quick points: * Fields that can be f

[jira] [Commented] (CALCITE-4036) Allow applying SemiJoinRule to join without aggregate below

[ https://issues.apache.org/jira/browse/CALCITE-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121236#comment-17121236 ] Haisheng Yuan commented on CALCITE-4036: Even AggregateRemoveRule is applied be

[jira] [Commented] (CALCITE-4035) Adapter for REST interface with query or path parameters

[ https://issues.apache.org/jira/browse/CALCITE-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121203#comment-17121203 ] Julian Hyde commented on CALCITE-4035: -- A good specification would be more useful,

[jira] [Resolved] (CALCITE-3946) Add parser support for MULTISET/SET and VOLATILE modifiers in CREATE TABLE statements

[ https://issues.apache.org/jira/browse/CALCITE-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde resolved CALCITE-3946. -- Resolution: Fixed Fixed in [8daba7|https://github.com/apache/calcite/commit/8daba770396193f9

[jira] [Resolved] (CALCITE-2997) Avoid pushing down join condition in SqlToRelConverter

[ https://issues.apache.org/jira/browse/CALCITE-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde resolved CALCITE-2997. -- Resolution: Fixed Fixed in [3fa29e17|https://github.com/apache/calcite/commit/3fa29e171d5ba4

[jira] [Commented] (CALCITE-3963) Maintain logical properties at RelSet (equivalent group) instead of RelNode

[ https://issues.apache.org/jira/browse/CALCITE-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121177#comment-17121177 ] Xiening Dai commented on CALCITE-3963: -- _*What's wrong with my suggestion to treat

[jira] [Commented] (CALCITE-4037) AggregateProjectMergeRule doesn't always respect column aliases

[ https://issues.apache.org/jira/browse/CALCITE-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121173#comment-17121173 ] Julian Hyde commented on CALCITE-4037: -- It would seem to make sense that the Aggre

[jira] [Commented] (CALCITE-4035) Adapter for REST interface with query or path parameters

[ https://issues.apache.org/jira/browse/CALCITE-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121122#comment-17121122 ] David Hait commented on CALCITE-4035: - The thing about the file adapter is that the

[jira] [Updated] (CALCITE-4037) AggregateProjectMergeRule doesn't always respect column aliases

[ https://issues.apache.org/jira/browse/CALCITE-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Crozon updated CALCITE-4037: Description: When columns aggregated over are given an alias, but not aggregated values,

[jira] [Updated] (CALCITE-4037) AggregateProjectMergeRule doesn't always respect column aliases

[ https://issues.apache.org/jira/browse/CALCITE-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Crozon updated CALCITE-4037: Description: When columns aggregated over are given an alias, but not aggregated values,

[jira] [Created] (CALCITE-4037) AggregateProjectMergeRule doesn't always respect column aliases

Sylvain Crozon created CALCITE-4037: --- Summary: AggregateProjectMergeRule doesn't always respect column aliases Key: CALCITE-4037 URL: https://issues.apache.org/jira/browse/CALCITE-4037 Project: Calc

[jira] [Commented] (CALCITE-4036) Allow applying SemiJoinRule to join without aggregate below

[ https://issues.apache.org/jira/browse/CALCITE-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121036#comment-17121036 ] Haisheng Yuan commented on CALCITE-4036: Hmm.. Because AggregateRemoveRule was

[jira] [Comment Edited] (CALCITE-4029) ProjectRemoveRule auto pruning may prevent rules from running if mixed conventions are used in a logical plan

[ https://issues.apache.org/jira/browse/CALCITE-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17120999#comment-17120999 ] Anton Haidai edited comment on CALCITE-4029 at 6/1/20, 1:06 PM: -

[jira] [Comment Edited] (CALCITE-4029) ProjectRemoveRule auto pruning may prevent rules from running if mixed conventions are used in a logical plan

[ https://issues.apache.org/jira/browse/CALCITE-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17120999#comment-17120999 ] Anton Haidai edited comment on CALCITE-4029 at 6/1/20, 1:06 PM: -

[jira] [Commented] (CALCITE-4029) ProjectRemoveRule auto pruning may prevent rules from running if mixed conventions are used in a logical plan

[ https://issues.apache.org/jira/browse/CALCITE-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17120999#comment-17120999 ] Anton Haidai commented on CALCITE-4029: --- [~botong] I agree, for example, even af

[jira] [Commented] (CALCITE-4036) Allow applying SemiJoinRule to join without aggregate below

[ https://issues.apache.org/jira/browse/CALCITE-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17120830#comment-17120830 ] Vova Vysotskyi commented on CALCITE-4036: - Such plan was obtained because Aggre

[jira] [Commented] (CALCITE-4034) Implement a MySQL InnoDB adapter

[ https://issues.apache.org/jira/browse/CALCITE-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17120822#comment-17120822 ] neoremind commented on CALCITE-4034: Hi Julian, Thanks for your response and suppo

[jira] [Updated] (CALCITE-4034) Implement a MySQL InnoDB adapter

[ https://issues.apache.org/jira/browse/CALCITE-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] neoremind updated CALCITE-4034: --- Attachment: (was: module_structure.png) > Implement a MySQL InnoDB adapter > --

[jira] [Updated] (CALCITE-4034) Implement a MySQL InnoDB adapter

[ https://issues.apache.org/jira/browse/CALCITE-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] neoremind updated CALCITE-4034: --- Attachment: module_structure.png > Implement a MySQL InnoDB adapter > -

[jira] [Updated] (CALCITE-4034) Implement a MySQL InnoDB adapter

[ https://issues.apache.org/jira/browse/CALCITE-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] neoremind updated CALCITE-4034: --- Attachment: (was: 屏幕快照 2020-06-01 下午3.38.30.png) > Implement a MySQL InnoDB adapter > -

[jira] [Updated] (CALCITE-4034) Implement a MySQL InnoDB adapter

[ https://issues.apache.org/jira/browse/CALCITE-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] neoremind updated CALCITE-4034: --- Attachment: 屏幕快照 2020-06-01 下午3.38.30.png > Implement a MySQL InnoDB adapter >