[jira] [Commented] (CALCITE-6284) Invalid conversion triggers ClassCastException

[ https://issues.apache.org/jira/browse/CALCITE-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17824169#comment-17824169 ] Julian Hyde commented on CALCITE-6284: -- Thank you! > Invalid conversion triggers

[jira] [Commented] (CALCITE-6293) Support OR condition in arrow adapter

[ https://issues.apache.org/jira/browse/CALCITE-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17824168#comment-17824168 ] Julian Hyde commented on CALCITE-6293: -- [~asolimando], +1 on merging what we have. The new tickets

[jira] [Updated] (CALCITE-6302) Release Calcite 1.37.0

[ https://issues.apache.org/jira/browse/CALCITE-6302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde updated CALCITE-6302: - Fix Version/s: 1.37.0 > Release Calcite 1.37.0 > -- > >

[jira] [Commented] (CALCITE-6248) Illegal dates are accepted by casts

[ https://issues.apache.org/jira/browse/CALCITE-6248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823772#comment-17823772 ] Julian Hyde commented on CALCITE-6248: -- Postel's law applies: "be conservative in what you send,

[jira] [Commented] (CALCITE-6284) Invalid conversion triggers ClassCastException

[ https://issues.apache.org/jira/browse/CALCITE-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823770#comment-17823770 ] Julian Hyde commented on CALCITE-6284: -- Can you fill out the description? Describe what's going on

[jira] [Commented] (CALCITE-6239) Add a PostGIS dialect that supports ST_ functions

[ https://issues.apache.org/jira/browse/CALCITE-6239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823753#comment-17823753 ] Julian Hyde commented on CALCITE-6239: -- [~bchapuis], In my

[jira] [Commented] (CALCITE-6292) Support more arrow type

[ https://issues.apache.org/jira/browse/CALCITE-6292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823745#comment-17823745 ] Julian Hyde commented on CALCITE-6292: -- Arrow types are very similar to SQL and JDBC types. You

[jira] [Commented] (CALCITE-6293) Support OR condition in arrow adapter

[ https://issues.apache.org/jira/browse/CALCITE-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823744#comment-17823744 ] Julian Hyde commented on CALCITE-6293: -- Can you provide more details? This case (and others you

[jira] [Commented] (CALCITE-6297) Support sub-queries in arrow adapter

[ https://issues.apache.org/jira/browse/CALCITE-6297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823468#comment-17823468 ] Julian Hyde commented on CALCITE-6297: -- I don’t understand what this means. Add description.  >

[jira] [Commented] (CALCITE-6278) Add REGEXP、REGEXP_LIKE function (enabled in Spark library)

[ https://issues.apache.org/jira/browse/CALCITE-6278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823342#comment-17823342 ] Julian Hyde commented on CALCITE-6278: -- Use a real comma in the subject, please. Does RLIKE have

[jira] [Resolved] (CALCITE-6288) Error while compiling LIKE function after update to 1.36

[ https://issues.apache.org/jira/browse/CALCITE-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde resolved CALCITE-6288. -- Resolution: Not A Problem Make sure that the column has SQL type {{{}MAP{}}}. Add some test

[jira] [Commented] (CALCITE-6289) View in union cannot be reused

[ https://issues.apache.org/jira/browse/CALCITE-6289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823332#comment-17823332 ] Julian Hyde commented on CALCITE-6289: -- What would the plan look like if reuse was occurring?

[jira] [Commented] (CALCITE-6288) Error while compiling LIKE function after update to 1.36

[ https://issues.apache.org/jira/browse/CALCITE-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823070#comment-17823070 ] Julian Hyde commented on CALCITE-6288: -- The SQL doesn’t seem to have a valid type. An item in

[jira] [Commented] (CALCITE-6281) Add test infrastructure to ensure that Calcite is consistent with the SQL dialects it is trying to emulate

[ https://issues.apache.org/jira/browse/CALCITE-6281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820939#comment-17820939 ] Julian Hyde commented on CALCITE-6281: -- Work in progress, based on Stamatis' [PR

[jira] [Assigned] (CALCITE-6281) Add test infrastructure to ensure that Calcite is consistent with the SQL dialects it is trying to emulate

[ https://issues.apache.org/jira/browse/CALCITE-6281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde reassigned CALCITE-6281: Assignee: Julian Hyde > Add test infrastructure to ensure that Calcite is consistent

[jira] [Resolved] (CALCITE-6219) Support SQL Validation for Tables with columns tagged as 'filter required'

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

[jira] [Commented] (CALCITE-6281) Add test infrastructure to ensure that Calcite is consistent with the SQL dialects it is trying to emulate

[ https://issues.apache.org/jira/browse/CALCITE-6281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820926#comment-17820926 ] Julian Hyde commented on CALCITE-6281: -- The only goal is to compare specifications: given an

[jira] [Commented] (CALCITE-6219) Support SQL Validation for Tables with columns tagged as 'filter required'

[ https://issues.apache.org/jira/browse/CALCITE-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820898#comment-17820898 ] Julian Hyde commented on CALCITE-6219: -- [~oliverlee], Looks like we've resolved your comment

[jira] [Created] (CALCITE-6281) Add test infrastructure to ensure that Calcite is consistent with the SQL dialects it is trying to emulate

Julian Hyde created CALCITE-6281: Summary: Add test infrastructure to ensure that Calcite is consistent with the SQL dialects it is trying to emulate Key: CALCITE-6281 URL:

[jira] [Commented] (CALCITE-6275) Parser for data types ignores element nullability in collections

[ https://issues.apache.org/jira/browse/CALCITE-6275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820199#comment-17820199 ] Julian Hyde commented on CALCITE-6275: -- In standard SQL, I don't think that NOT NULL is strictly

[jira] [Commented] (CALCITE-5638) Assertion Failure during planning correlated query with orderby

[ https://issues.apache.org/jira/browse/CALCITE-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820172#comment-17820172 ] Julian Hyde commented on CALCITE-5638: -- The problem still occurs if I remove the {{{}ORDER BY{}}}.

[jira] [Commented] (CALCITE-6279) Use Null to replace the results of some Math functions that return NaN.

[ https://issues.apache.org/jira/browse/CALCITE-6279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820166#comment-17820166 ] Julian Hyde commented on CALCITE-6279: -- Also, do not talk about what Java does. Calcite users do

[jira] [Commented] (CALCITE-6279) Use Null to replace the results of some Math functions that return NaN.

[ https://issues.apache.org/jira/browse/CALCITE-6279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820164#comment-17820164 ] Julian Hyde commented on CALCITE-6279: -- What you mean by “SQL rules”? Imprecise specifications

[jira] [Comment Edited] (CALCITE-6210) Cast to VARBINARY causes an assertion failure

[ https://issues.apache.org/jira/browse/CALCITE-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819856#comment-17819856 ] Julian Hyde edited comment on CALCITE-6210 at 2/23/24 12:14 AM: {quote}

[jira] [Commented] (CALCITE-6210) Cast to VARBINARY causes an assertion failure

[ https://issues.apache.org/jira/browse/CALCITE-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819856#comment-17819856 ] Julian Hyde commented on CALCITE-6210: -- {quote}The problem with my approach is that other dialects

[jira] [Commented] (CALCITE-6261) RelBuilder.aggregate() field pruning does not use permuted field indices when used with force project and duplicate agg calls

[ https://issues.apache.org/jira/browse/CALCITE-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819849#comment-17819849 ] Julian Hyde commented on CALCITE-6261: -- [~zrlpar] and [~phanimahidhar], Thanks for figuring it

[jira] [Commented] (CALCITE-6272) Improved LogicalPlan representation of distinct keyword

[ https://issues.apache.org/jira/browse/CALCITE-6272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818595#comment-17818595 ] Julian Hyde commented on CALCITE-6272: -- I think you’re saying the current behavior is fine, and

[jira] [Commented] (CALCITE-6259) The implementation of the Log library operator does not match the actual dialect behavior.

[ https://issues.apache.org/jira/browse/CALCITE-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818583#comment-17818583 ] Julian Hyde commented on CALCITE-6259: -- Go with [~mbudiu]'s method (separate SQL functions). But

[jira] [Commented] (CALCITE-6120) Add MATCHES_FILTER function, to match on Looker-style filter expressions

[ https://issues.apache.org/jira/browse/CALCITE-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818221#comment-17818221 ] Julian Hyde commented on CALCITE-6120: -- I've started work. Dev branch:

[jira] [Assigned] (CALCITE-6120) Add MATCHES_FILTER function, to match on Looker-style filter expressions

[ https://issues.apache.org/jira/browse/CALCITE-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde reassigned CALCITE-6120: Assignee: Julian Hyde > Add MATCHES_FILTER function, to match on Looker-style filter

[jira] [Commented] (CALCITE-6219) Support SQL Validation for Tables with columns tagged as 'filter required'

[ https://issues.apache.org/jira/browse/CALCITE-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818121#comment-17818121 ] Julian Hyde commented on CALCITE-6219: -- [~oliverlee], I have added a few more cleanup commits in

[jira] [Commented] (CALCITE-6268) Support implementing custom JdbcSchema

[ https://issues.apache.org/jira/browse/CALCITE-6268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818011#comment-17818011 ] Julian Hyde commented on CALCITE-6268: -- Why should we allow this? What is the problem you’re

[jira] [Commented] (CALCITE-6266) SqlValidatorException with LATERAL TABLE and JOIN

[ https://issues.apache.org/jira/browse/CALCITE-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817803#comment-17817803 ] Julian Hyde commented on CALCITE-6266: -- That makes sense. I had the same hypothesis. But if the

[jira] [Commented] (CALCITE-6266) SqlValidatorException with LATERAL TABLE and JOIN

[ https://issues.apache.org/jira/browse/CALCITE-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817764#comment-17817764 ] Julian Hyde commented on CALCITE-6266: -- It's quite possible that the new behavior is correct, and

[jira] [Commented] (CALCITE-6259) The implementation of the Log library operator does not match the actual dialect behavior.

[ https://issues.apache.org/jira/browse/CALCITE-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817763#comment-17817763 ] Julian Hyde commented on CALCITE-6259: -- As I said above, the behavior of LOGx functions should be

[jira] [Commented] (CALCITE-6263) Discuss the coupling of Calcite with JTS

[ https://issues.apache.org/jira/browse/CALCITE-6263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817762#comment-17817762 ] Julian Hyde commented on CALCITE-6263: -- I used string (WKT) as a simple example; binary (WKB)

[jira] [Updated] (CALCITE-6239) Add a postgis dialect that supports ST functions

[ https://issues.apache.org/jira/browse/CALCITE-6239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde updated CALCITE-6239: - Component/s: spatial > Add a postgis dialect that supports ST functions >

[jira] [Updated] (CALCITE-6239) Add a PostGIS dialect that supports ST_ functions

[ https://issues.apache.org/jira/browse/CALCITE-6239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde updated CALCITE-6239: - Summary: Add a PostGIS dialect that supports ST_ functions (was: Add a postgis dialect that

[jira] [Commented] (CALCITE-6265) Cannot provide different numeric type as placeholder

[ https://issues.apache.org/jira/browse/CALCITE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817759#comment-17817759 ] Julian Hyde commented on CALCITE-6265: -- Sure, it shows up in Calcite, but it's due to Avatica not

[jira] [Commented] (CALCITE-6252) BigQuery FORMAT_DATE uses the wrong calendar for Julian dates

[ https://issues.apache.org/jira/browse/CALCITE-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817721#comment-17817721 ] Julian Hyde commented on CALCITE-6252: -- It's OK to change the summary, but it might be OK to keep

[jira] [Commented] (CALCITE-6248) Illegal dates are accepted by casts

[ https://issues.apache.org/jira/browse/CALCITE-6248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817552#comment-17817552 ] Julian Hyde commented on CALCITE-6248: -- I understand your chain of reasoning. But it is flawed,

[jira] [Commented] (CALCITE-6263) Discuss the coupling of Calcite with JTS

[ https://issues.apache.org/jira/browse/CALCITE-6263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817551#comment-17817551 ] Julian Hyde commented on CALCITE-6263: -- I don't mind Calcite having *some* coupling to JTS, but

[jira] [Commented] (CALCITE-6265) Cannot provide different numeric type as placeholder

[ https://issues.apache.org/jira/browse/CALCITE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817548#comment-17817548 ] Julian Hyde commented on CALCITE-6265: -- I think the bug is in Avatica - or at any rate, Avatica is

[jira] [Commented] (CALCITE-6248) Illegal dates are accepted by casts

[ https://issues.apache.org/jira/browse/CALCITE-6248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817544#comment-17817544 ] Julian Hyde commented on CALCITE-6248: -- I think we should remain reasonably liberal in the format

[jira] [Commented] (CALCITE-6261) RelBuilder.aggregate() field pruning does not use permuted field indices when used with force project and duplicate agg calls

[ https://issues.apache.org/jira/browse/CALCITE-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817542#comment-17817542 ] Julian Hyde commented on CALCITE-6261: -- [~zrlpar], No hurry. I know how corporate lawyers can be.

[jira] [Commented] (CALCITE-6261) RelBuilder.aggregate() field pruning does not use permuted field indices when used with force project and duplicate agg calls

[ https://issues.apache.org/jira/browse/CALCITE-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817432#comment-17817432 ] Julian Hyde commented on CALCITE-6261: -- [~zrlpar], Thanks for taking this on. I have set

[jira] [Updated] (CALCITE-6261) RelBuilder.aggregate() field pruning does not use permuted field indices when used with force project and duplicate agg calls

[ https://issues.apache.org/jira/browse/CALCITE-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde updated CALCITE-6261: - Fix Version/s: 1.37.0 > RelBuilder.aggregate() field pruning does not use permuted field

[jira] [Resolved] (CALCITE-5888) Assertion error in aggregate

[ https://issues.apache.org/jira/browse/CALCITE-5888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde resolved CALCITE-5888. -- Fix Version/s: 1.37.0 Resolution: Duplicate Marking resolved as a duplicate; all work

[jira] [Commented] (CALCITE-6239) Add a postgis dialect that supports ST functions

[ https://issues.apache.org/jira/browse/CALCITE-6239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816823#comment-17816823 ] Julian Hyde commented on CALCITE-6239: -- I reviewed the PR, looks pretty good. However, the change

[jira] [Commented] (CALCITE-6259) Return the result with the log10 and log functions of argument 0

[ https://issues.apache.org/jira/browse/CALCITE-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816776#comment-17816776 ] Julian Hyde commented on CALCITE-6259: -- 1. Whatever behavior we choose, let's make sure the

[jira] [Commented] (CALCITE-6261) RelBuilder.aggregate() field pruning does not use permuted field indices when used with force project and duplicate agg calls

[ https://issues.apache.org/jira/browse/CALCITE-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816710#comment-17816710 ] Julian Hyde commented on CALCITE-6261: -- Thanks for logging this; and I agree that it looks like a

[jira] [Commented] (CALCITE-6219) Support SQL Validation for Tables with columns tagged as 'filter required'

[ https://issues.apache.org/jira/browse/CALCITE-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816265#comment-17816265 ] Julian Hyde commented on CALCITE-6219: -- [~oliverlee], In my

[jira] [Commented] (CALCITE-6244) Improve `Expressions#constant` to allow passing models with non-public fields

[ https://issues.apache.org/jira/browse/CALCITE-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816218#comment-17816218 ] Julian Hyde commented on CALCITE-6244: -- Can you link the PR? (If you use CALCITE-6244 in the

[jira] [Commented] (CALCITE-6252) BigQuery FORMAT_DATE uses the wrong calendar for Julian dates

[ https://issues.apache.org/jira/browse/CALCITE-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816211#comment-17816211 ] Julian Hyde commented on CALCITE-6252: -- [~mbudiu], In your PR, you deal with "" (full weekday

[jira] [Resolved] (CALCITE-6256) Incorrect rendering of HTML on InnoDB adapter page

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

[jira] [Commented] (CALCITE-6256) Incorrect rendering of HTML on InnoDB adapter page

[ https://issues.apache.org/jira/browse/CALCITE-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815870#comment-17815870 ] Julian Hyde commented on CALCITE-6256: -- The problems seem to start much earlier in the document,

[jira] [Commented] (CALCITE-2980) Implement the FORMAT clause of the CAST operator

[ https://issues.apache.org/jira/browse/CALCITE-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815855#comment-17815855 ] Julian Hyde commented on CALCITE-2980: -- No apology needed. It's just good to state your goals

[jira] [Commented] (CALCITE-2980) Implement the FORMAT clause of the CAST operator

[ https://issues.apache.org/jira/browse/CALCITE-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815849#comment-17815849 ] Julian Hyde commented on CALCITE-2980: -- [~jerin_john], In this PR do you intend to support

[jira] [Commented] (CALCITE-6252) BigQuery FORMAT_DATE uses the wrong calendar for Julian dates

[ https://issues.apache.org/jira/browse/CALCITE-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815818#comment-17815818 ] Julian Hyde commented on CALCITE-6252: -- Ah, thanks [~mbudiu], sounds like we're on the same page.

[jira] [Commented] (CALCITE-6252) BigQuery FORMAT_DATE uses the wrong calendar for Julian dates

[ https://issues.apache.org/jira/browse/CALCITE-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815809#comment-17815809 ] Julian Hyde commented on CALCITE-6252: -- My understanding is that SQL date values (e.g. {{DATE

[jira] [Commented] (CALCITE-6252) BigQuery FORMAT_DATE uses the wrong calendar for Julian dates

[ https://issues.apache.org/jira/browse/CALCITE-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815808#comment-17815808 ] Julian Hyde commented on CALCITE-6252: -- Is this related to (or caused by) CALCITE-1884 or

[jira] [Comment Edited] (CALCITE-6254) Enable calling table functions without requiring TABLE() wrapper

[ https://issues.apache.org/jira/browse/CALCITE-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815804#comment-17815804 ] Julian Hyde edited comment on CALCITE-6254 at 2/8/24 7:08 PM: -- Also note

[jira] [Commented] (CALCITE-6254) Enable calling table functions without requiring TABLE() wrapper

[ https://issues.apache.org/jira/browse/CALCITE-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815804#comment-17815804 ] Julian Hyde commented on CALCITE-6254: -- Also note that {{TABLE tableName}} is a separate syntax

[jira] [Resolved] (CALCITE-1490) Allow table functions without explicit TABLE

[ https://issues.apache.org/jira/browse/CALCITE-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde resolved CALCITE-1490. -- Fix Version/s: 1.37.0 Resolution: Duplicate > Allow table functions without explicit

[jira] [Commented] (CALCITE-6254) Enable calling table functions without requiring TABLE() wrapper

[ https://issues.apache.org/jira/browse/CALCITE-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815801#comment-17815801 ] Julian Hyde commented on CALCITE-6254: -- Thanks for this. The subject arose when we implemented

[jira] [Comment Edited] (CALCITE-6252) BigQuery FORMAT_DATE seems to use the wrong calendar for Julian dates

[ https://issues.apache.org/jira/browse/CALCITE-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815479#comment-17815479 ] Julian Hyde edited comment on CALCITE-6252 at 2/8/24 2:30 AM: -- Do you know

[jira] [Commented] (CALCITE-6252) BigQuery FORMAT_DATE seems to use the wrong calendar for Julian dates

[ https://issues.apache.org/jira/browse/CALCITE-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815479#comment-17815479 ] Julian Hyde commented on CALCITE-6252: -- Do you know what date BigQuery diverges from Calcite? Is

[jira] [Commented] (CALCITE-6240) Remove ROW_NUMBER if OVER PARTITION BY unique key

[ https://issues.apache.org/jira/browse/CALCITE-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814506#comment-17814506 ] Julian Hyde commented on CALCITE-6240: -- Also related to CALCITE-5406, because {code:java} SELECT

[jira] [Commented] (CALCITE-6237) Using fractions in LOG function does not return correct results

[ https://issues.apache.org/jira/browse/CALCITE-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814503#comment-17814503 ] Julian Hyde commented on CALCITE-6237: -- +1 [~asolimando] [~caicancai], Often the hardest problem

[jira] [Comment Edited] (CALCITE-6240) Remove ROW_NUMBER if OVER PARTITION BY unique key

[ https://issues.apache.org/jira/browse/CALCITE-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814498#comment-17814498 ] Julian Hyde edited comment on CALCITE-6240 at 2/5/24 8:02 PM: -- Regarding

[jira] [Commented] (CALCITE-6240) Remove ROW_NUMBER if OVER PARTITION BY unique key

[ https://issues.apache.org/jira/browse/CALCITE-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814498#comment-17814498 ] Julian Hyde commented on CALCITE-6240: -- Can this behavior be described by an algebraic property?

[jira] [Commented] (CALCITE-6244) Improve `Expressions#constant` to allow passing models with non-public fields

[ https://issues.apache.org/jira/browse/CALCITE-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814429#comment-17814429 ] Julian Hyde commented on CALCITE-6244: -- Do you propose to allow any class with public fields? I’d

[jira] [Updated] (CALCITE-6244) Improve `Expressions#constant` to allow passing models with non-public fields

[ https://issues.apache.org/jira/browse/CALCITE-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde updated CALCITE-6244: - Component/s: linq4j (was: avatica) > Improve `Expressions#constant` to

[jira] [Commented] (CALCITE-1317) Rewrite "MAX" as "ORDER BY ... LIMIT ..."

[ https://issues.apache.org/jira/browse/CALCITE-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814003#comment-17814003 ] Julian Hyde commented on CALCITE-1317: -- [~jiajunbernoulli], I agree that those optimizations make

[jira] [Commented] (CALCITE-6238) Exception while evaluating ROUND function

[ https://issues.apache.org/jira/browse/CALCITE-6238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813822#comment-17813822 ] Julian Hyde commented on CALCITE-6238: -- Our operator tests already spot that a function has

[jira] [Commented] (CALCITE-6238) Exception while evaluating ROUND function

[ https://issues.apache.org/jira/browse/CALCITE-6238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813820#comment-17813820 ] Julian Hyde commented on CALCITE-6238: -- Ideal would be a variation of the second: check that the

[jira] [Commented] (CALCITE-6237) Using fractions in LOG function does not return correct results

[ https://issues.apache.org/jira/browse/CALCITE-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813815#comment-17813815 ] Julian Hyde commented on CALCITE-6237: -- [~caicancai], Do you understand why I closed CALCITE-6232

[jira] [Comment Edited] (CALCITE-6214) Remove DISTINCT in aggregate function if field is unique

[ https://issues.apache.org/jira/browse/CALCITE-6214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813752#comment-17813752 ] Julian Hyde edited comment on CALCITE-6214 at 2/2/24 4:29 PM: -- That’s not

[jira] [Commented] (CALCITE-6214) Remove DISTINCT in aggregate function if field is unique

[ https://issues.apache.org/jira/browse/CALCITE-6214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813752#comment-17813752 ] Julian Hyde commented on CALCITE-6214: -- That’s not what I said. In my example the combined columns

[jira] [Commented] (CALCITE-6232) Using fractions and 0 in LOG function does not return correct results

[ https://issues.apache.org/jira/browse/CALCITE-6232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813358#comment-17813358 ] Julian Hyde commented on CALCITE-6232: -- Please open a new case. This case is closed. > Using

[jira] [Commented] (CALCITE-6232) Using fractions and 0 in LOG function does not return correct results

[ https://issues.apache.org/jira/browse/CALCITE-6232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813356#comment-17813356 ] Julian Hyde commented on CALCITE-6232: -- Please open a new case. This one is closed. > Using

[jira] [Comment Edited] (CALCITE-6232) Using fractions and 0 in LOG function does not return correct results

[ https://issues.apache.org/jira/browse/CALCITE-6232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813352#comment-17813352 ] Julian Hyde edited comment on CALCITE-6232 at 2/1/24 5:40 PM: -- The summary

[jira] [Commented] (CALCITE-6232) Using fractions and 0 in LOG function does not return correct results

[ https://issues.apache.org/jira/browse/CALCITE-6232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813352#comment-17813352 ] Julian Hyde commented on CALCITE-6232: -- The summary is extremely unhelpful. It might as well say

[jira] [Comment Edited] (CALCITE-6221) JDBC adapter generates invalid query when the same table is joined multiple times

[ https://issues.apache.org/jira/browse/CALCITE-6221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812425#comment-17812425 ] Julian Hyde edited comment on CALCITE-6221 at 1/30/24 5:39 PM: --- Thank you

[jira] [Commented] (CALCITE-6221) JDBC adapter generates invalid query when the same table is joined multiple times

[ https://issues.apache.org/jira/browse/CALCITE-6221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812425#comment-17812425 ] Julian Hyde commented on CALCITE-6221: -- I agree that the subselect is necessary for the outer join

[jira] [Commented] (CALCITE-6235) MAP_CONTAINS_KEY function results correspond to Spark results

[ https://issues.apache.org/jira/browse/CALCITE-6235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812415#comment-17812415 ] Julian Hyde commented on CALCITE-6235: -- That expression doesn't have a valid type. You can't use a

[jira] [Commented] (CALCITE-6219) Support SQL Validation for Tables with columns tagged as 'filter required'

[ https://issues.apache.org/jira/browse/CALCITE-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812082#comment-17812082 ] Julian Hyde commented on CALCITE-6219: -- If a 'filter required' column is not filtered but it is in

[jira] [Commented] (CALCITE-6231) JDBC adapter generates "UNNEST" when it should generate "UNNEST ... WITH ORDINALITY"

[ https://issues.apache.org/jira/browse/CALCITE-6231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812039#comment-17812039 ] Julian Hyde commented on CALCITE-6231: -- My concern was that end-users have not heard about

[jira] [Updated] (CALCITE-6231) JDBC adapter generates "UNNEST" when it should generate "UNNEST ... WITH ORDINALITY"

[ https://issues.apache.org/jira/browse/CALCITE-6231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde updated CALCITE-6231: - Summary: JDBC adapter generates "UNNEST" when it should generate "UNNEST ... WITH ORDINALITY"

[jira] [Commented] (CALCITE-6214) Remove DISTINCT in aggregate function if field is unique

[ https://issues.apache.org/jira/browse/CALCITE-6214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812038#comment-17812038 ] Julian Hyde commented on CALCITE-6214: -- Does this change take into account GROUP BY keys? For

[jira] [Commented] (CALCITE-6221) JDBC adapter generates invalid query when the same table is joined multiple times

[ https://issues.apache.org/jira/browse/CALCITE-6221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812036#comment-17812036 ] Julian Hyde commented on CALCITE-6221: -- There are too many changes in RelToSqlConverterTest (too

[jira] [Closed] (CALCITE-2031) Implement more OpenGIS functions

[ https://issues.apache.org/jira/browse/CALCITE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde closed CALCITE-2031. > Implement more OpenGIS functions > > > Key:

[jira] [Resolved] (CALCITE-2031) Implement more OpenGIS functions

[ https://issues.apache.org/jira/browse/CALCITE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde resolved CALCITE-2031. -- Fix Version/s: 1.35.0 Resolution: Fixed Agreed. All of the core ST_ functions are

[jira] [Commented] (CALCITE-6231) ORDINALITY is omitted during the RelToSql stage

[ https://issues.apache.org/jira/browse/CALCITE-6231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811544#comment-17811544 ] Julian Hyde commented on CALCITE-6231: -- Can you improve the summary? Readers of the release notes

[jira] [Commented] (CALCITE-6232) Using fractions and 0 in LOG function does not return correct results

[ https://issues.apache.org/jira/browse/CALCITE-6232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811543#comment-17811543 ] Julian Hyde commented on CALCITE-6232: -- Why would you expect fractions to have a special behavior

[jira] [Resolved] (CALCITE-6232) Using fractions and 0 in LOG function does not return correct results

[ https://issues.apache.org/jira/browse/CALCITE-6232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde resolved CALCITE-6232. -- Resolution: Invalid > Using fractions and 0 in LOG function does not return correct results

[jira] [Commented] (CALCITE-6063) If ARRAY subquery has ORDER BY (without LIMIT), rows are not sorted

[ https://issues.apache.org/jira/browse/CALCITE-6063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811392#comment-17811392 ] Julian Hyde commented on CALCITE-6063: -- Looks good. I asked for validator test but I see you added

[jira] [Resolved] (CALCITE-6222) Mysql does not have to_char function

[ https://issues.apache.org/jira/browse/CALCITE-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde resolved CALCITE-6222. -- Resolution: Invalid > Mysql does not have to_char function >

[jira] [Reopened] (CALCITE-6222) Mysql does not have to_char function

[ https://issues.apache.org/jira/browse/CALCITE-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde reopened CALCITE-6222: -- > Mysql does not have to_char function > > >

[jira] [Commented] (CALCITE-6222) Mysql does not have to_char function

[ https://issues.apache.org/jira/browse/CALCITE-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811389#comment-17811389 ] Julian Hyde commented on CALCITE-6222: -- The first step in this case should have been to contact

<    1   2   3   4   5   6   7   8   9   10   >