[jira] [Commented] (CALCITE-6414) Snowflake JDBC adapter should generate BOOLOR_AGG, BOOLAND_AGG for MAX, MIN on BOOLEAN values

[ https://issues.apache.org/jira/browse/CALCITE-6414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848714#comment-17848714 ] Justin Swett commented on CALCITE-6414: --- My apologies, Snowflake does , however the aggregate

[jira] [Updated] (CALCITE-6414) Resolve Snoflake SQL generation of BOOL_OR, BOOL_AND

[ https://issues.apache.org/jira/browse/CALCITE-6414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Swett updated CALCITE-6414: -- Description: The rewriteMacMInExpr is generating incorrect SQL for Snowflake. Instead of

[jira] [Updated] (CALCITE-6414) Resolve Snoflake SQL generation of BOOL_OR, BOOL_AND

[ https://issues.apache.org/jira/browse/CALCITE-6414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Swett updated CALCITE-6414: -- Description: The rewriteMacMInExpr is generating incorrect SQL for Snowflake. Instead of

[jira] [Updated] (CALCITE-6414) Resolve Snoflake SQL generation of BOOL_OR, BOOL_AND

[ https://issues.apache.org/jira/browse/CALCITE-6414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Swett updated CALCITE-6414: -- Description: The rewriteMacMInExpr is generating incorrect SQL for Snowflake. Instead of

[jira] [Created] (CALCITE-6414) Resolve Snoflake SQL generation of BOOL_OR, BOOL_AND

Justin Swett created CALCITE-6414: - Summary: Resolve Snoflake SQL generation of BOOL_OR, BOOL_AND Key: CALCITE-6414 URL: https://issues.apache.org/jira/browse/CALCITE-6414 Project: Calcite

[jira] [Commented] (CALCITE-5155) Extensible time units

[ https://issues.apache.org/jira/browse/CALCITE-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17603224#comment-17603224 ] Justin Swett commented on CALCITE-5155: --- Re 5: Do we need an offset parameter to derive a useful

[jira] [Comment Edited] (CALCITE-4276) Rewriting for materialized view will project wrong input

[ https://issues.apache.org/jira/browse/CALCITE-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17293888#comment-17293888 ] Justin Swett edited comment on CALCITE-4276 at 3/2/21, 6:06 PM: Hmmm..

[jira] [Commented] (CALCITE-4276) Rewriting for materialized view will project wrong input

[ https://issues.apache.org/jira/browse/CALCITE-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17293888#comment-17293888 ] Justin Swett commented on CALCITE-4276: --- Hmmm.. I think I have the SQL's ported to the test

[jira] [Comment Edited] (CALCITE-4361) BigQuery comments starting with # cause SqlParseException

[ https://issues.apache.org/jira/browse/CALCITE-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223834#comment-17223834 ] Justin Swett edited comment on CALCITE-4361 at 10/30/20, 6:26 PM: -- '#'

[jira] [Commented] (CALCITE-4361) BigQuery comments starting with # cause SqlParseException

[ https://issues.apache.org/jira/browse/CALCITE-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223834#comment-17223834 ] Justin Swett commented on CALCITE-4361: --- # starts a comment. Your query return [1, 2, 3] >

[jira] [Created] (CALCITE-4362) Unable to parse queries that use BigQuery pseudo columns _PARTITIONDATE/_PARTITIONTIME

Justin Swett created CALCITE-4362: - Summary: Unable to parse queries that use BigQuery pseudo columns _PARTITIONDATE/_PARTITIONTIME Key: CALCITE-4362 URL: https://issues.apache.org/jira/browse/CALCITE-4362

[jira] [Commented] (CALCITE-4361) BigQuery comments starting with # cause SqlParseException

[ https://issues.apache.org/jira/browse/CALCITE-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17222450#comment-17222450 ] Justin Swett commented on CALCITE-4361: --- Should also add a # inside "" scenario too {code:java}

[jira] [Created] (CALCITE-4361) BigQuery comments starting with # cause SqlParseException

Justin Swett created CALCITE-4361: - Summary: BigQuery comments starting with # cause SqlParseException Key: CALCITE-4361 URL: https://issues.apache.org/jira/browse/CALCITE-4361 Project: Calcite

[jira] [Commented] (CALCITE-4297) Babel should accept CURRENT_DATE and CURRENT_DATETIME, with and without parentheses

[ https://issues.apache.org/jira/browse/CALCITE-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210260#comment-17210260 ] Justin Swett commented on CALCITE-4297: --- PR posted,

[jira] [Commented] (CALCITE-4297) Babel should accept CURRENT_DATE and CURRENT_DATETIME, with and without parentheses

[ https://issues.apache.org/jira/browse/CALCITE-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210248#comment-17210248 ] Justin Swett commented on CALCITE-4297: --- Adding a new SqlFunction parses and validates

[jira] [Comment Edited] (CALCITE-4297) Babel should accept CURRENT_DATE and CURRENT_DATETIME, with and without parentheses

[ https://issues.apache.org/jira/browse/CALCITE-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210227#comment-17210227 ] Justin Swett edited comment on CALCITE-4297 at 10/8/20, 2:13 PM: - Ok,

[jira] [Commented] (CALCITE-4297) Babel should accept CURRENT_DATE and CURRENT_DATETIME, with and without parentheses

[ https://issues.apache.org/jira/browse/CALCITE-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210227#comment-17210227 ] Justin Swett commented on CALCITE-4297: --- Ok, adding BIG_QUERY to SqlConformanceEnum's

[jira] [Created] (CALCITE-4297) Babel should accept CURRENT_DATE and CURRENT_DATETIME

Justin Swett created CALCITE-4297: - Summary: Babel should accept CURRENT_DATE and CURRENT_DATETIME Key: CALCITE-4297 URL: https://issues.apache.org/jira/browse/CALCITE-4297 Project: Calcite

[jira] [Updated] (CALCITE-4276) Rewriting for materialized view will project wrong input

[ https://issues.apache.org/jira/browse/CALCITE-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Swett updated CALCITE-4276: -- Description: When MaterializedViewOnlyAggregateRule does its rewrite it will sometimes

[jira] [Created] (CALCITE-4276) Rewriting for materialized view will project wrong input

Justin Swett created CALCITE-4276: - Summary: Rewriting for materialized view will project wrong input Key: CALCITE-4276 URL: https://issues.apache.org/jira/browse/CALCITE-4276 Project: Calcite

[jira] [Comment Edited] (CALCITE-3874) SqlImplementor builder uses wrong context for sub-selects

[jira] [Commented] (CALCITE-3874) SqlImplementor builder uses wrong context for sub-selects

[ https://issues.apache.org/jira/browse/CALCITE-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073286#comment-17073286 ] Justin Swett commented on CALCITE-3874: --- I missed your request... I'll try to look at this week

[jira] [Commented] (CALCITE-3875) Create visitor to emit java code that would reproduce the visited rel

[ https://issues.apache.org/jira/browse/CALCITE-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17066959#comment-17066959 ] Justin Swett commented on CALCITE-3875: --- Definitely more useful if it can be called from an IDE

[jira] [Created] (CALCITE-3875) Create visitor to emit java code that would reproduce the visited rel

Justin Swett created CALCITE-3875: - Summary: Create visitor to emit java code that would reproduce the visited rel Key: CALCITE-3875 URL: https://issues.apache.org/jira/browse/CALCITE-3875 Project:

[jira] [Updated] (CALCITE-3874) SqlImplementor builder uses wrong context for sub-selects

[ https://issues.apache.org/jira/browse/CALCITE-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Swett updated CALCITE-3874: -- Description: When a sub-query is detected, via RelToSqlConverter visit on Project and in

[jira] [Commented] (CALCITE-3874) SqlImplementor builder uses wrong context for sub-selects

[ https://issues.apache.org/jira/browse/CALCITE-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17066822#comment-17066822 ] Justin Swett commented on CALCITE-3874: --- In the environment I've listed the before and after rel

[jira] [Created] (CALCITE-3874) SqlImplementor builder uses wrong context for sub-selects

Justin Swett created CALCITE-3874: - Summary: SqlImplementor builder uses wrong context for sub-selects Key: CALCITE-3874 URL: https://issues.apache.org/jira/browse/CALCITE-3874 Project: Calcite

[jira] [Created] (CALCITE-3370) Emulate NULL direction for MSSQL

Justin Swett created CALCITE-3370: - Summary: Emulate NULL direction for MSSQL Key: CALCITE-3370 URL: https://issues.apache.org/jira/browse/CALCITE-3370 Project: Calcite Issue Type: Task

[jira] [Comment Edited] (CALCITE-3308) RelBuilder.literal with a string argument should create a character literal with appropriate character set

[ https://issues.apache.org/jira/browse/CALCITE-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16921718#comment-16921718 ] Justin Swett edited comment on CALCITE-3308 at 9/3/19 9:01 PM: --- FWIW,

[jira] [Commented] (CALCITE-3308) RelBuilder.literal with a string argument should create a character literal with appropriate character set

[ https://issues.apache.org/jira/browse/CALCITE-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16921718#comment-16921718 ] Justin Swett commented on CALCITE-3308: --- FWIW, using makeCharLiteral with a NlsString and UTF-8