[jira] [Commented] (CALCITE-2074) Simplification of AND/OR expressions yields wrong results

[ https://issues.apache.org/jira/browse/CALCITE-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16274064#comment-16274064 ] Jesus Camacho Rodriguez commented on CALCITE-2074: -- [~julianhyde], I think this is

[jira] [Created] (CALCITE-2074) Simplification of AND/OR expressions yields wrong results

Jesus Camacho Rodriguez created CALCITE-2074: Summary: Simplification of AND/OR expressions yields wrong results Key: CALCITE-2074 URL: https://issues.apache.org/jira/browse/CALCITE-2074

[jira] [Commented] (CALCITE-2069) RexSimplify.removeNullabilityCast() always removes cast for operand with ANY type

[ https://issues.apache.org/jira/browse/CALCITE-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273774#comment-16273774 ] Julian Hyde commented on CALCITE-2069: -- OK, thanks everyone; it sounds as if this won't break Drill

[jira] [Updated] (CALCITE-2069) RexSimplify.removeNullabilityCast() always removes cast for operand with ANY type

[ https://issues.apache.org/jira/browse/CALCITE-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde updated CALCITE-2069: - Fix Version/s: 1.16.0 > RexSimplify.removeNullabilityCast() always removes cast for operand

[jira] [Commented] (CALCITE-2069) RexSimplify.removeNullabilityCast() always removes cast for operand with ANY type

[ https://issues.apache.org/jira/browse/CALCITE-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273705#comment-16273705 ] Laurent Goujon commented on CALCITE-2069: - I did not observe any regression with our own test

[jira] [Commented] (CALCITE-2072) Allow specification of geospatial functions in connection string

[ https://issues.apache.org/jira/browse/CALCITE-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273667#comment-16273667 ] Julian Hyde commented on CALCITE-2072: -- We already support comma-separated lists, e.g.

[jira] [Resolved] (CALCITE-2073) Allow disabling of protobuf generation

[ https://issues.apache.org/jira/browse/CALCITE-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser resolved CALCITE-2073. - Resolution: Fixed Fixed in

[jira] [Commented] (CALCITE-2073) Allow disabling of protobuf generation

[ https://issues.apache.org/jira/browse/CALCITE-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273241#comment-16273241 ] ASF GitHub Bot commented on CALCITE-2073: - Github user asfgit closed the pull request at:

[jira] [Commented] (CALCITE-2073) Allow disabling of protobuf generation

[ https://issues.apache.org/jira/browse/CALCITE-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273097#comment-16273097 ] ASF GitHub Bot commented on CALCITE-2073: - GitHub user joshelser opened a pull request:

[jira] [Created] (CALCITE-2073) Allow disabling of protobuf generation

Josh Elser created CALCITE-2073: --- Summary: Allow disabling of protobuf generation Key: CALCITE-2073 URL: https://issues.apache.org/jira/browse/CALCITE-2073 Project: Calcite Issue Type: Task

[jira] [Created] (CALCITE-2072) Allow specification of geospatial functions in connection string

Michael Mior created CALCITE-2072: - Summary: Allow specification of geospatial functions in connection string Key: CALCITE-2072 URL: https://issues.apache.org/jira/browse/CALCITE-2072 Project:

[jira] [Updated] (CALCITE-2009) Possible bug in interpreting ( IN ) OR ( IN ) logic

[ https://issues.apache.org/jira/browse/CALCITE-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Bojko updated CALCITE-2009: - Affects Version/s: 1.15.0 > Possible bug in interpreting ( IN ) OR ( IN ) logic >

[jira] [Commented] (CALCITE-2009) Possible bug in interpreting ( IN ) OR ( IN ) logic

[ https://issues.apache.org/jira/browse/CALCITE-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272685#comment-16272685 ] Piotr Bojko commented on CALCITE-2009: -- 1.15.0-SNAPSHOT has the same issue. > Possible bug in

[jira] [Commented] (CALCITE-2009) Possible bug in interpreting ( IN ) OR ( IN ) logic

[ https://issues.apache.org/jira/browse/CALCITE-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272684#comment-16272684 ] Piotr Bojko commented on CALCITE-2009: -- I've discovered that when launching the followinf query