[jira] [Created] (CALCITE-4272) Incorrect sub-query to JDBC driver

Roman Churganov created CALCITE-4272: Summary: Incorrect sub-query to JDBC driver Key: CALCITE-4272 URL: https://issues.apache.org/jira/browse/CALCITE-4272 Project: Calcite Issue Type: Bu

[jira] [Comment Edited] (CALCITE-4240) SqlTypeUtil#getMaxPrecisionScaleDecimal will create decimal that has the same precision and scale

[ https://issues.apache.org/jira/browse/CALCITE-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199876#comment-17199876 ] Jiatao Tao edited comment on CALCITE-4240 at 9/22/20, 6:51 AM: --

[jira] [Comment Edited] (CALCITE-4240) SqlTypeUtil#getMaxPrecisionScaleDecimal will create decimal that has the same precision and scale

[ https://issues.apache.org/jira/browse/CALCITE-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199876#comment-17199876 ] Jiatao Tao edited comment on CALCITE-4240 at 9/22/20, 6:51 AM: --

[jira] [Commented] (CALCITE-4240) SqlTypeUtil#getMaxPrecisionScaleDecimal will create decimal that has the same precision and scale

[ https://issues.apache.org/jira/browse/CALCITE-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199876#comment-17199876 ] Jiatao Tao commented on CALCITE-4240: - If you execute `{{create table test (a decim

[jira] [Comment Edited] (CALCITE-4240) SqlTypeUtil#getMaxPrecisionScaleDecimal will create decimal that has the same precision and scale

[ https://issues.apache.org/jira/browse/CALCITE-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199876#comment-17199876 ] Jiatao Tao edited comment on CALCITE-4240 at 9/22/20, 6:50 AM: --

[jira] [Commented] (CALCITE-4176) Key descriptor can be optional in SESSION table function

[ https://issues.apache.org/jira/browse/CALCITE-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199831#comment-17199831 ] Rui Wang commented on CALCITE-4176: --- [~liupengcheng] seems like I don't have the perm

[jira] [Commented] (CALCITE-4176) Key descriptor can be optional in SESSION table function

[ https://issues.apache.org/jira/browse/CALCITE-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199823#comment-17199823 ] liupengcheng commented on CALCITE-4176: --- hi, [~amaliujia] Please assign this task

[jira] [Resolved] (CALCITE-4209) In RelBuilder, add an option to not simplify LIMIT 0 to an empty relation

[ https://issues.apache.org/jira/browse/CALCITE-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde resolved CALCITE-4209. -- Fix Version/s: 1.26.0 Resolution: Fixed Fixed in [02904822|https://github.com/apache/

[jira] [Resolved] (CALCITE-4271) RelBuilder.in should allow duplicate values

[ https://issues.apache.org/jira/browse/CALCITE-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde resolved CALCITE-4271. -- Fix Version/s: 1.26.0 Resolution: Fixed Fixed in [2acf3426e|https://github.com/apache

[jira] [Assigned] (CALCITE-4271) RelBuilder.in should allow duplicate values

[ https://issues.apache.org/jira/browse/CALCITE-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde reassigned CALCITE-4271: Assignee: Julian Hyde > RelBuilder.in should allow duplicate values > --

[jira] [Updated] (CALCITE-4209) In RelBuilder, add an option to not simplify LIMIT 0 to an empty relation

[ https://issues.apache.org/jira/browse/CALCITE-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde updated CALCITE-4209: - Description: When you call {{relBuilder.limit(0, 0)}} it triggers a call to {{RelBuilder.empty

[jira] [Updated] (CALCITE-4209) In RelBuilder, add an option to not simplify LIMIT 0 to an empty relation

[ https://issues.apache.org/jira/browse/CALCITE-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde updated CALCITE-4209: - Summary: In RelBuilder, add an option to not simplify LIMIT 0 to an empty relation (was: RelBu

[jira] [Assigned] (CALCITE-4209) RelBuilder: ability to avoid generating empty() on limit 0

[ https://issues.apache.org/jira/browse/CALCITE-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde reassigned CALCITE-4209: Assignee: Julian Hyde > RelBuilder: ability to avoid generating empty() on limit 0 > ---

[jira] [Created] (CALCITE-4271) RelBuilder.in should allow duplicate values

Julian Hyde created CALCITE-4271: Summary: RelBuilder.in should allow duplicate values Key: CALCITE-4271 URL: https://issues.apache.org/jira/browse/CALCITE-4271 Project: Calcite Issue Type: B

[jira] [Assigned] (CALCITE-4176) Key descriptor can be optional in SESSION table function

[ https://issues.apache.org/jira/browse/CALCITE-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rui Wang reassigned CALCITE-4176: - Assignee: (was: Rui Wang) > Key descriptor can be optional in SESSION table function > ---

[jira] [Commented] (CALCITE-4176) Key descriptor can be optional in SESSION table function

[ https://issues.apache.org/jira/browse/CALCITE-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199632#comment-17199632 ] Rui Wang commented on CALCITE-4176: --- [~duli] [~liupengcheng] I became crazily busy r

[jira] [Comment Edited] (CALCITE-4242) Wrong plan for nested NOT EXISTS subqueries

[ https://issues.apache.org/jira/browse/CALCITE-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199548#comment-17199548 ] James Starr edited comment on CALCITE-4242 at 9/21/20, 5:40 PM: -

[jira] [Commented] (CALCITE-4242) Wrong plan for nested NOT EXISTS subqueries

[ https://issues.apache.org/jira/browse/CALCITE-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199548#comment-17199548 ] James Starr commented on CALCITE-4242: -- One nit for your example, what if the resu

[jira] [Commented] (CALCITE-4223) Introducing column statistics to RelOptTable

[ https://issues.apache.org/jira/browse/CALCITE-4223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199349#comment-17199349 ] Liya Fan commented on CALCITE-4223: --- IMHO, I like the idea of a quick path for some i

[jira] [Resolved] (CALCITE-4241) Some improvements to metadata query

[ https://issues.apache.org/jira/browse/CALCITE-4241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liya Fan resolved CALCITE-4241. --- Resolution: Fixed > Some improvements to metadata query > --- > >

[jira] [Commented] (CALCITE-4264) The query planner should take CPU cost into account

[ https://issues.apache.org/jira/browse/CALCITE-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199258#comment-17199258 ] Ruben Q L commented on CALCITE-4264: I agree it is worth a try. Some simple real-li

[jira] [Commented] (CALCITE-4267) Add filed "output" for RelJsonWriter.

[ https://issues.apache.org/jira/browse/CALCITE-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199229#comment-17199229 ] Stamatis Zampetakis commented on CALCITE-4267: -- I am not sure I understand

[jira] [Resolved] (CALCITE-4261) Join with three tables causes IllegalArgumentException in EnumerableBatchNestedLoopJoinRule

[ https://issues.apache.org/jira/browse/CALCITE-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruben Q L resolved CALCITE-4261. Resolution: Fixed Fixed via https://github.com/apache/calcite/commit/43cf101576e3108f94aa51ffe42

[jira] [Created] (CALCITE-4270) Elasticsearch Collapse Query is not supported

Shlok Srivastava created CALCITE-4270: - Summary: Elasticsearch Collapse Query is not supported Key: CALCITE-4270 URL: https://issues.apache.org/jira/browse/CALCITE-4270 Project: Calcite