[jira] [Resolved] (CALCITE-3414) In calcite-core, use RexToLixTranslator.convert for type conversion code generation uniformly

[ https://issues.apache.org/jira/browse/CALCITE-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Danny Chen resolved CALCITE-3414. - Fix Version/s: 1.22.0 Resolution: Fixed Fixed in [429c0d0|https://github.com/apache/cal

[jira] [Resolved] (CALCITE-3416) SQL Dialects "DEFAULT"s should be more extensible

[ https://issues.apache.org/jira/browse/CALCITE-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Danny Chen resolved CALCITE-3416. - Fix Version/s: 1.22.0 Resolution: Fixed Fixed in [ff43dcb|https://github.com/apache/cal

[jira] [Commented] (CALCITE-3282) HiveSqlDialect should unparse INTEGER type as INT in order to be compatible with Hive1.x

[ https://issues.apache.org/jira/browse/CALCITE-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957480#comment-16957480 ] Danny Chen commented on CALCITE-3282: - Thanks for that, Julian ! > HiveSqlDialect

[jira] [Commented] (CALCITE-3362) Implementation for some empty tests of Lattice

[ https://issues.apache.org/jira/browse/CALCITE-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957467#comment-16957467 ] Julian Hyde commented on CALCITE-3362: -- Reviewing now. > Implementation for some

[jira] [Assigned] (CALCITE-3362) Implementation for some empty tests of Lattice

[ https://issues.apache.org/jira/browse/CALCITE-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde reassigned CALCITE-3362: Assignee: Julian Hyde (was: Wang Yanlin) > Implementation for some empty tests of Latti

[jira] [Created] (CALCITE-3438) Validator should disallow use of the GROUPING function inside a FILTER clause

Julian Hyde created CALCITE-3438: Summary: Validator should disallow use of the GROUPING function inside a FILTER clause Key: CALCITE-3438 URL: https://issues.apache.org/jira/browse/CALCITE-3438 Proje

[jira] [Commented] (CALCITE-3402) Allow RANGE with compoud ORDER BY clause

[ https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957245#comment-16957245 ] Julian Hyde commented on CALCITE-3402: -- We probably already support ROWS with comp

[jira] [Updated] (CALCITE-3282) HiveSqlDialect should unparse INTEGER type as INT in order to be compatible with Hive1.x

[ https://issues.apache.org/jira/browse/CALCITE-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde updated CALCITE-3282: - Summary: HiveSqlDialect should unparse INTEGER type as INT in order to be compatible with Hive1

[jira] [Updated] (CALCITE-3437) Elasticsearch Match query is not supported

[ https://issues.apache.org/jira/browse/CALCITE-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shikha Somani updated CALCITE-3437: --- Labels: QueryBuilder calcite elasticsearch match (was: ) > Elasticsearch Match query is no

[jira] [Commented] (CALCITE-2018) Queries failed with AssertionError: rel has lower cost than best cost of subset

[ https://issues.apache.org/jira/browse/CALCITE-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957203#comment-16957203 ] Xiening Dai commented on CALCITE-2018: -- Hi [~volodymyr], are you still working on

[jira] [Updated] (CALCITE-3437) Elasticsearch Match query is not supported

[ https://issues.apache.org/jira/browse/CALCITE-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shikha Somani updated CALCITE-3437: --- Description: Currently, Calcite only builds "text" queries on elasticsearch for text fields

[jira] [Created] (CALCITE-3437) Elasticsearch Match query is not supported

Shikha Somani created CALCITE-3437: -- Summary: Elasticsearch Match query is not supported Key: CALCITE-3437 URL: https://issues.apache.org/jira/browse/CALCITE-3437 Project: Calcite Issue Type

[jira] [Commented] (CALCITE-3402) Allow RANGE with compoud ORDER BY clause

[ https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16956993#comment-16956993 ] benj commented on CALCITE-3402: --- I Just check MSSQL 2017 and Oracle 11 that work like Pos

[jira] [Commented] (CALCITE-3402) Allow RANGE with compoud ORDER BY clause

[ https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16956862#comment-16956862 ] Danny Chen commented on CALCITE-3402: - It's not surprise the cases you gave for RAN

[jira] [Comment Edited] (CALCITE-3402) Allow RANGE with compoud ORDER BY clause

[ https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16956811#comment-16956811 ] benj edited comment on CALCITE-3402 at 10/22/19 9:13 AM: - Your

[jira] [Commented] (CALCITE-3402) Allow RANGE with compoud ORDER BY clause

[ https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16956811#comment-16956811 ] benj commented on CALCITE-3402: --- Your explanation make senses. I'm agree for the RANGE. B

[jira] [Commented] (CALCITE-3428) Refine RelMdColumnUniqueness for Filter by considering constant columns

[ https://issues.apache.org/jira/browse/CALCITE-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16956792#comment-16956792 ] jin xing commented on CALCITE-3428: --- Sorry [~julianhyde] ~ I will be careful next ti