[jira] [Updated] (CALCITE-6319) Add negative test to POW and POWER functions
[ https://issues.apache.org/jira/browse/CALCITE-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] hongyu guo updated CALCITE-6319: Fix Version/s: (was: 1.37.0) > Add negative test to POW and POWER functions > > > Key: CALCITE-6319 > URL: https://issues.apache.org/jira/browse/CALCITE-6319 > Project: Calcite > Issue Type: Test >Affects Versions: 1.36.0 >Reporter: Caican Cai >Priority: Minor > Labels: pull-request-available > > Add negative test to pow and power functions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CALCITE-6332) Optimization CoreRules.AGGREGATE_EXPAND_DISTINCT_AGGREGATES_TO_JOIN produces incorrect results for aggregates with groupSets
Mihai Budiu created CALCITE-6332:
Summary: Optimization
CoreRules.AGGREGATE_EXPAND_DISTINCT_AGGREGATES_TO_JOIN produces incorrect
results for aggregates with groupSets
Key: CALCITE-6332
URL: https://issues.apache.org/jira/browse/CALCITE-6332
Project: Calcite
Issue Type: Bug
Components: core
Affects Versions: 1.36.0
Reporter: Mihai Budiu
The optimization rule does not seem to consider the groupSets at all.
The following two queries produce the same resulting plan:
{code:sql}
select count(distinct deptno) as cd, count(*) as c
from emp
group by cube(deptno)
{code}
{code:sql}
select count(distinct deptno) as cd, count(*) as c
from emp
group by deptno
{code}
(Notice that one query has a cube, while the other one doesn't)
The produced plan is:
{code}
LogicalProject(CD=[$1], C=[$2]), id = 196
LogicalAggregate(group=[{0}], CD=[COUNT($0)], C=[$SUM0($1)]), id = 201
LogicalAggregate(group=[{0}], C=[COUNT()]), id = 198
LogicalProject(DEPTNO=[$8]), id = 192
LogicalTableScan(table=[[schema, EMP]]), id = 163
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CALCITE-6138) Parser does not accept TIMESTAMP WITH TIME ZONE as a data type
[ https://issues.apache.org/jira/browse/CALCITE-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mihai Budiu resolved CALCITE-6138. -- Resolution: Fixed > Parser does not accept TIMESTAMP WITH TIME ZONE as a data type > -- > > Key: CALCITE-6138 > URL: https://issues.apache.org/jira/browse/CALCITE-6138 > Project: Calcite > Issue Type: Bug > Components: core >Affects Versions: 1.36.0 >Reporter: Mihai Budiu >Assignee: Mihai Budiu >Priority: Minor > Labels: pull-request-available > Fix For: 1.37.0 > > > The current SQL grammar accepts either TIMESTAMP WITHOUT TIME ZONE or > TIMESTAMP WITH LOCAL TIME ZONE. It does not accept the version without LOCAL: > TIMESTAMP WITH TIME ZONE. This is a legal type in other SQL dialects, and it > appears in the SQL 92 standard. > The Calcite documentation also lists the rejected type as a legal scalar > type: [https://calcite.apache.org/docs/reference.html#scalar-types] > So there is a bug: either the compiler is wrong, or the documentation is > wrong. The main question is "which one?" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CALCITE-6319) Add negative test to POW and POWER functions
[ https://issues.apache.org/jira/browse/CALCITE-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827317#comment-17827317 ] hongyu guo commented on CALCITE-6319: - Hi [~caicancai]. Are you still working on this jira? If not, can you remove 1.37.0 of fix version? > Add negative test to POW and POWER functions > > > Key: CALCITE-6319 > URL: https://issues.apache.org/jira/browse/CALCITE-6319 > Project: Calcite > Issue Type: Test >Affects Versions: 1.36.0 >Reporter: Caican Cai >Priority: Minor > Labels: pull-request-available > Fix For: 1.37.0 > > > Add negative test to pow and power functions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CALCITE-6138) Parser does not accept TIMESTAMP WITH TIME ZONE as a data type
[ https://issues.apache.org/jira/browse/CALCITE-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827316#comment-17827316 ] hongyu guo commented on CALCITE-6138: - Has this bug been fixed? we should mark this ticket as `Fixed` status if does > Parser does not accept TIMESTAMP WITH TIME ZONE as a data type > -- > > Key: CALCITE-6138 > URL: https://issues.apache.org/jira/browse/CALCITE-6138 > Project: Calcite > Issue Type: Bug > Components: core >Affects Versions: 1.36.0 >Reporter: Mihai Budiu >Assignee: Mihai Budiu >Priority: Minor > Labels: pull-request-available > Fix For: 1.37.0 > > > The current SQL grammar accepts either TIMESTAMP WITHOUT TIME ZONE or > TIMESTAMP WITH LOCAL TIME ZONE. It does not accept the version without LOCAL: > TIMESTAMP WITH TIME ZONE. This is a legal type in other SQL dialects, and it > appears in the SQL 92 standard. > The Calcite documentation also lists the rejected type as a legal scalar > type: [https://calcite.apache.org/docs/reference.html#scalar-types] > So there is a bug: either the compiler is wrong, or the documentation is > wrong. The main question is "which one?" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CALCITE-6310) Add REGEXP_LIKE function (enabled in PostgreSQL library)
[ https://issues.apache.org/jira/browse/CALCITE-6310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Duong updated CALCITE-6310: - Summary: Add REGEXP_LIKE function (enabled in PostgreSQL library) (was: Support PostgreSQL REGEXP_REPLACE) > Add REGEXP_LIKE function (enabled in PostgreSQL library) > > > Key: CALCITE-6310 > URL: https://issues.apache.org/jira/browse/CALCITE-6310 > Project: Calcite > Issue Type: Sub-task >Reporter: James Duong >Assignee: James Duong >Priority: Minor > > * There is an existing implementation. > * PostgreSQL requires supporting an optional extra flags argument -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CALCITE-6310) Support PostgreSQL REGEXP_REPLACE
[ https://issues.apache.org/jira/browse/CALCITE-6310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Duong reassigned CALCITE-6310: Assignee: James Duong > Support PostgreSQL REGEXP_REPLACE > - > > Key: CALCITE-6310 > URL: https://issues.apache.org/jira/browse/CALCITE-6310 > Project: Calcite > Issue Type: Sub-task >Reporter: James Duong >Assignee: James Duong >Priority: Minor > > * There is an existing implementation. > * PostgreSQL requires supporting an optional extra flags argument -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CALCITE-6309) Add REGEXP_LIKE function (enabled in MySQL, Oracle, PostgreSQL and Spark libraries)
[ https://issues.apache.org/jira/browse/CALCITE-6309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Duong reassigned CALCITE-6309: Assignee: James Duong > Add REGEXP_LIKE function (enabled in MySQL, Oracle, PostgreSQL and Spark > libraries) > --- > > Key: CALCITE-6309 > URL: https://issues.apache.org/jira/browse/CALCITE-6309 > Project: Calcite > Issue Type: Sub-task >Reporter: James Duong >Assignee: James Duong >Priority: Minor > Labels: pull-request-available > > * The Spark version of this is being implemented in CALCITE-6278 > * The PostgreSQL version requires supporting a 3-arg version that takes in > flags. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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&focusedCommentId=17827231#comment-17827231
]
Tanner Clary commented on CALCITE-2980:
---
[~jerin_john]I see no problem with this. In my mind, incremental commits are
perfectly fine and as such not all tests are going to pass at first. As long as
we have some showing that the new additions add some functionality and don't
break existing functionality, I think that's ok.
> Implement the FORMAT clause of the CAST operator
>
>
> Key: CALCITE-2980
> URL: https://issues.apache.org/jira/browse/CALCITE-2980
> Project: Calcite
> Issue Type: Bug
>Reporter: Julian Hyde
>Assignee: Jerin John
>Priority: Major
> Labels: pull-request-available
>
> SQL:2016 adds an optional {{FORMAT format}} clause to the {{CAST}} operator.
> It is a standard way to do what functions like {{TO_DATE}}, {{TO_NUMBER}},
> {{TO_CHAR}}, {{TO_TIMESTAMP}} have done in an ad hoc way (and with differing
> specifications among databases).
> Here is an example:
> {code:java}
> cast('01-05-2017' as date format 'DD-MM-')
> {code}
> The following paragraphs are copied from IMPALA-4018, which describes
> implementing this in Impala. (That case also describes cases where the
> implementations of {{TO_TIMESTAMP}} etc. in Hive, Impala, Oracle and
> PostgreSQL are not consistent with each other. We should take note as we
> implement these functions in Calcite.)
> SQL:2016 defines the following datetime templates
> {noformat}
> ::=
> { }...
> ::=
>
> |
> ::=
>
> |
> |
> |
> |
> |
> |
> |
> |
> |
> |
> |
> |
> |
> ::=
>
> |
> |
> |
> |
> |
> |
> |
> ::=
> | YYY | YY | Y
> ::=
> | RR
> ::=
> MM
> ::=
> DD
> ::=
> DDD
> ::=
> HH | HH12
> ::=
> HH24
> ::=
> MI
> ::=
> SS
> ::=
> S
> ::=
> FF1 | FF2 | FF3 | FF4 | FF5 | FF6 | FF7 | FF8 | FF9
> ::=
> A.M. | P.M.
> ::=
> TZH
> ::=
> TZM
> {noformat}
> SQL:2016 also introduced the {{FORMAT}} clause for {{CAST}} which is the
> standard way to do string <> datetime conversions
> {noformat}
> ::=
> CAST
>AS
> [ FORMAT ]
>
> ::=
>
> |
> ::=
>
> |
> ::=
>
> {noformat}
> For example:
> {noformat}
> CAST( AS [FORMAT ])
> CAST( AS [FORMAT ])
> cast(dt as string format 'DD-MM-')
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[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&focusedCommentId=17827222#comment-17827222
]
Jerin John commented on CALCITE-2980:
-
Team, I wanted to discuss about the timeline to enable the quidem tests
[cast-with-format.iq|https://github.com/apache/calcite/blob/main/core/src/test/resources/sql/cast-with-format.iq]
which were imported from Impala by [~julianhyde].
Based on the observations from my previous comment, there are certain
FormatElements not available in the current implementation of Calcite's
[FormatModels|https://github.com/apache/calcite/blob/main/core/src/main/java/org/apache/calcite/util/format/FormatModels.java]
and would hence be failing many of those quidem tests. While this
[PR|https://github.com/apache/calcite/pull/3677] I created adds support for the
{{FORMAT}} Clause with {{{}CAST{}}}, it'll take a while to comb through the
3000 lines of quidem tests to selectively disable the failing ones for now.
My question is can we merge this PR first and then enable these tests in a
subsequent change once the FormatElements are fixed? I could create an
additional JIRA case for tracking it or can be done as part of one of the JIRA
issues linked above. Would appreciate your feedback on this and the PR as well,
thanks!
cc: [~julianhyde] [~tanclary]
> Implement the FORMAT clause of the CAST operator
>
>
> Key: CALCITE-2980
> URL: https://issues.apache.org/jira/browse/CALCITE-2980
> Project: Calcite
> Issue Type: Bug
>Reporter: Julian Hyde
>Assignee: Jerin John
>Priority: Major
> Labels: pull-request-available
>
> SQL:2016 adds an optional {{FORMAT format}} clause to the {{CAST}} operator.
> It is a standard way to do what functions like {{TO_DATE}}, {{TO_NUMBER}},
> {{TO_CHAR}}, {{TO_TIMESTAMP}} have done in an ad hoc way (and with differing
> specifications among databases).
> Here is an example:
> {code:java}
> cast('01-05-2017' as date format 'DD-MM-')
> {code}
> The following paragraphs are copied from IMPALA-4018, which describes
> implementing this in Impala. (That case also describes cases where the
> implementations of {{TO_TIMESTAMP}} etc. in Hive, Impala, Oracle and
> PostgreSQL are not consistent with each other. We should take note as we
> implement these functions in Calcite.)
> SQL:2016 defines the following datetime templates
> {noformat}
> ::=
> { }...
> ::=
>
> |
> ::=
>
> |
> |
> |
> |
> |
> |
> |
> |
> |
> |
> |
> |
> |
> ::=
>
> |
> |
> |
> |
> |
> |
> |
> ::=
> | YYY | YY | Y
> ::=
> | RR
> ::=
> MM
> ::=
> DD
> ::=
> DDD
> ::=
> HH | HH12
> ::=
> HH24
> ::=
> MI
> ::=
> SS
> ::=
> S
> ::=
> FF1 | FF2 | FF3 | FF4 | FF5 | FF6 | FF7 | FF8 | FF9
> ::=
> A.M. | P.M.
> ::=
> TZH
> ::=
> TZM
> {noformat}
> SQL:2016 also introduced the {{FORMAT}} clause for {{CAST}} which is the
> standard way to do string <> datetime conversions
> {noformat}
> ::=
> CAST
>AS
> [ FORMAT ]
>
> ::=
>
> |
> ::=
>
> |
> ::=
>
> {noformat}
> For example:
> {noformat}
> CAST( AS [FORMAT ])
> CAST( AS [FORMAT ])
> cast(dt as string format 'DD-MM-')
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CALCITE-6314) Add RANDOM function (enabled in Postgres library)
[ https://issues.apache.org/jira/browse/CALCITE-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827197#comment-17827197 ] James Duong edited comment on CALCITE-6314 at 3/14/24 6:15 PM: --- I worked with ASF infra to get Contributor permissions to this board now. was (Author: jduong): I worked with ASF infra to get Contributor permissions to this board. > Add RANDOM function (enabled in Postgres library) > - > > Key: CALCITE-6314 > URL: https://issues.apache.org/jira/browse/CALCITE-6314 > Project: Calcite > Issue Type: Sub-task >Reporter: James Duong >Assignee: James Duong >Priority: Major > Labels: pull-request-available > Fix For: 1.37.0 > > > This is an alias for RAND(), except it should not support passing in a seed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CALCITE-6314) Add RANDOM function (enabled in Postgres library)
[ https://issues.apache.org/jira/browse/CALCITE-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827197#comment-17827197 ] James Duong commented on CALCITE-6314: -- I worked with ASF infra to get Contributor permissions to this board. > Add RANDOM function (enabled in Postgres library) > - > > Key: CALCITE-6314 > URL: https://issues.apache.org/jira/browse/CALCITE-6314 > Project: Calcite > Issue Type: Sub-task >Reporter: James Duong >Assignee: James Duong >Priority: Major > Labels: pull-request-available > Fix For: 1.37.0 > > > This is an alias for RAND(), except it should not support passing in a seed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CALCITE-6314) Add RANDOM function (enabled in Postgres library)
[ https://issues.apache.org/jira/browse/CALCITE-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Duong reassigned CALCITE-6314: Assignee: James Duong (was: Tanner Clary) > Add RANDOM function (enabled in Postgres library) > - > > Key: CALCITE-6314 > URL: https://issues.apache.org/jira/browse/CALCITE-6314 > Project: Calcite > Issue Type: Sub-task >Reporter: James Duong >Assignee: James Duong >Priority: Major > Labels: pull-request-available > Fix For: 1.37.0 > > > This is an alias for RAND(), except it should not support passing in a seed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CALCITE-6328) The BigQuery functions SAFE_* do not match the BigQuery specification
[
https://issues.apache.org/jira/browse/CALCITE-6328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827192#comment-17827192
]
Mihai Budiu edited comment on CALCITE-6328 at 3/14/24 5:49 PM:
---
They differ in several respects.
The simplest way to see what the problems are is to look at the tests I had to
disable in the fix for [CALCITE-6322]
https://github.com/apache/calcite/pull/3733
There is a new Bug.CALCITE_6328_FIXED covering all of them.
was (Author: JIRAUSER295926):
They differ in several respects.
The simplest way to see what the problems are is to look at the tests I had to
disable in the fix for [CALCITE-6324]
https://github.com/apache/calcite/pull/3733
There is a new Bug.CALCITE_6328_FIXED covering all of them.
> The BigQuery functions SAFE_* do not match the BigQuery specification
> -
>
> Key: CALCITE-6328
> URL: https://issues.apache.org/jira/browse/CALCITE-6328
> Project: Calcite
> Issue Type: Bug
> Components: core
>Affects Versions: 1.36.0
>Reporter: Mihai Budiu
>Priority: Minor
>
> The BigQuery dialect does not support DECIMAL values with arbitrary types: it
> only supports two fixed types: NUMERIC and BIGNUMERIC, both with fixed
> precision and scale.
> The runtime implementation of the SAFE_* functions uses the following helper
> in SqlFunctions:
> {code:java}
> /** Returns whether a BigDecimal value is safe (that is, has not
> overflowed).
>* According to BigQuery, BigDecimal overflow occurs if the precision is
> greater
>* than 76 or the scale is greater than 38. */
> private static boolean safeDecimal(BigDecimal b) {
> return b.scale() <= 38 && b.precision() <= 76;
> }
> {code}
> This helper does not handle correctly NUMERIC value, only BIGNUMERIC.
> Moreover, all the tests in SqlOperatorTests use a type system which doesn't
> even support DECIMAL values wider than 38 digits. So a test like the
> following:
> {code:java}
> f.checkNull("safe_add(cast(-9.9e75 as DECIMAL(76, 0)), "
> + "cast(-9.9e75 as DECIMAL(76, 0)))");
> {code}
> cannot even create the expected BigDecimal value correctly.
> This surfaced during the attempt to fix [CALCITE-6322]: once the casts to
> DECIMAL are implemented, some of these tests break.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CALCITE-6314) Add RANDOM function (enabled in Postgres library)
[ https://issues.apache.org/jira/browse/CALCITE-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827186#comment-17827186 ] Mihai Budiu commented on CALCITE-6314: -- I can't assign James either, it says that the user name does not exist. > Add RANDOM function (enabled in Postgres library) > - > > Key: CALCITE-6314 > URL: https://issues.apache.org/jira/browse/CALCITE-6314 > Project: Calcite > Issue Type: Sub-task >Reporter: James Duong >Assignee: Tanner Clary >Priority: Major > Labels: pull-request-available > Fix For: 1.37.0 > > > This is an alias for RAND(), except it should not support passing in a seed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CALCITE-6314) Add RANDOM function (enabled in Postgres library)
[ https://issues.apache.org/jira/browse/CALCITE-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827174#comment-17827174 ] Tanner Clary commented on CALCITE-6314: --- [~julianhyde] do you know how to switch? I want to make sure [~jduong] gets his credit > Add RANDOM function (enabled in Postgres library) > - > > Key: CALCITE-6314 > URL: https://issues.apache.org/jira/browse/CALCITE-6314 > Project: Calcite > Issue Type: Sub-task >Reporter: James Duong >Assignee: Tanner Clary >Priority: Major > Labels: pull-request-available > Fix For: 1.37.0 > > > This is an alias for RAND(), except it should not support passing in a seed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CALCITE-6314) Add RANDOM function (enabled in Postgres library)
[ https://issues.apache.org/jira/browse/CALCITE-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827173#comment-17827173 ] James Duong commented on CALCITE-6314: -- I wonder if this is an issue with my account. This is an old account that had been inactive for a bit, then got linked to my Apache credentials when I received them. > Add RANDOM function (enabled in Postgres library) > - > > Key: CALCITE-6314 > URL: https://issues.apache.org/jira/browse/CALCITE-6314 > Project: Calcite > Issue Type: Sub-task >Reporter: James Duong >Assignee: Tanner Clary >Priority: Major > Labels: pull-request-available > Fix For: 1.37.0 > > > This is an alias for RAND(), except it should not support passing in a seed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CALCITE-6330) Print the average row size when when explaining an operator
[
https://issues.apache.org/jira/browse/CALCITE-6330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827167#comment-17827167
]
mengdou commented on CALCITE-6330:
--
[~zabetak] Thanks for your explanation. I agree with you about the fine line
that how many things we can put in the explanation of any operator. Because the
average row size is related to the cost estimation, it makes sense to put it in
there.
> Print the average row size when when explaining an operator
> ---
>
> Key: CALCITE-6330
> URL: https://issues.apache.org/jira/browse/CALCITE-6330
> Project: Calcite
> Issue Type: Improvement
> Components: core
>Reporter: mengdou
>Assignee: mengdou
>Priority: Minor
>
> In this time, when we dump the plan of a RelNode Tree, there is no average
> row size exported in the output string, even if
> SqlExplainLevel.ALL_ATTRIBUTES is specified.
> Because the implementation in explain_() in class RelWriterImpl doesn't
> include the metric average_row_size:
>
> {code:java}
> switch (detailLevel) {
> case ALL_ATTRIBUTES:
> s.append(": rowcount = ")
> .append(mq.getRowCount(rel))
> .append(", cumulative cost = ")
> .append(mq.getCumulativeCost(rel));
> }
> switch (detailLevel) {
> case NON_COST_ATTRIBUTES:
> case ALL_ATTRIBUTES:
> if (!withIdPrefix) {
> // If we didn't print the rel id at the start of the line, print
> // it at the end.
> s.append(", id = ").append(rel.getId());
> }
> break;
> } {code}
>
> So I'd like to add this metric by calling md.getAverageRowSize(rel)
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CALCITE-6314) Add RANDOM function (enabled in Postgres library)
[ https://issues.apache.org/jira/browse/CALCITE-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanner Clary resolved CALCITE-6314. --- Fix Version/s: 1.37.0 Assignee: Tanner Clary Resolution: Fixed Merged via [9c0d690|https://github.com/apache/calcite/commit/9c0d690439920fff5120250e5f1899f857a5b1ec], thanks for the fix, [~jduong] I'm not sure why it won't let me assign [~jduong] as the assignee. Do you know, [~mbudiu]? > Add RANDOM function (enabled in Postgres library) > - > > Key: CALCITE-6314 > URL: https://issues.apache.org/jira/browse/CALCITE-6314 > Project: Calcite > Issue Type: Sub-task >Reporter: James Duong >Assignee: Tanner Clary >Priority: Major > Labels: pull-request-available > Fix For: 1.37.0 > > > This is an alias for RAND(), except it should not support passing in a seed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CALCITE-6331) The third-party source code file doesn't have a License file.
[ https://issues.apache.org/jira/browse/CALCITE-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827126#comment-17827126 ] Stamatis Zampetakis commented on CALCITE-6331: -- I don't remember the motivation behind this packaging structure but I remember various discussions on the topic. If you look into the git/JIRA history or the archives of dev@calcite you may find something relevant. > The third-party source code file doesn't have a License file. > - > > Key: CALCITE-6331 > URL: https://issues.apache.org/jira/browse/CALCITE-6331 > Project: Calcite > Issue Type: Improvement >Reporter: Calvin Kirs >Priority: Major > Labels: pull-request-available > > [https://github.com/apache/calcite/blob/main/LICENSE#L184-L196] > We reference these third-party source code files but don't provide the > corresponding LICENSE files. > FYI : [https://www.apache.org/legal/release-policy.html#license-file] > > Here is the MIT license: > > Permission is hereby granted, free of charge, to any person obtaining a copy > of this software and associated documentation files (the "Software"), to deal > in the Software without restriction, including without limitation the rights > to use, copy, modify, merge, publish, distribute, sublicense, and/or sell > copies of the Software, and to permit persons to whom the Software is > furnished to do so, subject to the following conditions: The above copyright > notice and this permission notice shall be included in all copies or > substantial portions of the Software. > > > > > > > > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CALCITE-6331) The third-party source code file doesn't have a License file.
[ https://issues.apache.org/jira/browse/CALCITE-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Calvin Kirs resolved CALCITE-6331. -- Resolution: Invalid > The third-party source code file doesn't have a License file. > - > > Key: CALCITE-6331 > URL: https://issues.apache.org/jira/browse/CALCITE-6331 > Project: Calcite > Issue Type: Improvement >Reporter: Calvin Kirs >Priority: Major > Labels: pull-request-available > > [https://github.com/apache/calcite/blob/main/LICENSE#L184-L196] > We reference these third-party source code files but don't provide the > corresponding LICENSE files. > FYI : [https://www.apache.org/legal/release-policy.html#license-file] > > Here is the MIT license: > > Permission is hereby granted, free of charge, to any person obtaining a copy > of this software and associated documentation files (the "Software"), to deal > in the Software without restriction, including without limitation the rights > to use, copy, modify, merge, publish, distribute, sublicense, and/or sell > copies of the Software, and to permit persons to whom the Software is > furnished to do so, subject to the following conditions: The above copyright > notice and this permission notice shall be included in all copies or > substantial portions of the Software. > > > > > > > > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CALCITE-6331) The third-party source code file doesn't have a License file.
[ https://issues.apache.org/jira/browse/CALCITE-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827109#comment-17827109 ] Calvin Kirs commented on CALCITE-6331: -- It looks like we used a script to organize the license files under https://github.com/apache/calcite/tree/f0dc2b0aea46b1fd3f37e0cc126edaf82ade2344/src/main/config/licenses. This is consistent with the pointers in the LICENSE file in the root directory.（Additional License files can be found in the 'licenses' folder located in the same directory as the LICENSE file (i.e. this file)) I'm curious to ask, why not put it directly in the correct location, but instead use a script to do it when packaging? > The third-party source code file doesn't have a License file. > - > > Key: CALCITE-6331 > URL: https://issues.apache.org/jira/browse/CALCITE-6331 > Project: Calcite > Issue Type: Improvement >Reporter: Calvin Kirs >Priority: Major > Labels: pull-request-available > > [https://github.com/apache/calcite/blob/main/LICENSE#L184-L196] > We reference these third-party source code files but don't provide the > corresponding LICENSE files. > FYI : [https://www.apache.org/legal/release-policy.html#license-file] > > Here is the MIT license: > > Permission is hereby granted, free of charge, to any person obtaining a copy > of this software and associated documentation files (the "Software"), to deal > in the Software without restriction, including without limitation the rights > to use, copy, modify, merge, publish, distribute, sublicense, and/or sell > copies of the Software, and to permit persons to whom the Software is > furnished to do so, subject to the following conditions: The above copyright > notice and this permission notice shall be included in all copies or > substantial portions of the Software. > > > > > > > > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CALCITE-6330) Print the average row size when when explaining an operator
[
https://issues.apache.org/jira/browse/CALCITE-6330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827073#comment-17827073
]
Stamatis Zampetakis commented on CALCITE-6330:
--
Based on the SqlExplainLevel specification I am not sure if it was ever
intended to bring anything else except the cost. The average row size may be a
nice thing to have but others would possibly find other metadata useful as
well. Every new thing that we add increases the serialization cost so there is
a fine line with how many things we can put in there.
Usually people who need to add more metadata tend to extend or implement their
own RelWriter.
> Print the average row size when when explaining an operator
> ---
>
> Key: CALCITE-6330
> URL: https://issues.apache.org/jira/browse/CALCITE-6330
> Project: Calcite
> Issue Type: Improvement
> Components: core
>Reporter: mengdou
>Assignee: mengdou
>Priority: Minor
>
> In this time, when we dump the plan of a RelNode Tree, there is no average
> row size exported in the output string, even if
> SqlExplainLevel.ALL_ATTRIBUTES is specified.
> Because the implementation in explain_() in class RelWriterImpl doesn't
> include the metric average_row_size:
>
> {code:java}
> switch (detailLevel) {
> case ALL_ATTRIBUTES:
> s.append(": rowcount = ")
> .append(mq.getRowCount(rel))
> .append(", cumulative cost = ")
> .append(mq.getCumulativeCost(rel));
> }
> switch (detailLevel) {
> case NON_COST_ATTRIBUTES:
> case ALL_ATTRIBUTES:
> if (!withIdPrefix) {
> // If we didn't print the rel id at the start of the line, print
> // it at the end.
> s.append(", id = ").append(rel.getId());
> }
> break;
> } {code}
>
> So I'd like to add this metric by calling md.getAverageRowSize(rel)
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CALCITE-6331) The third-party source code file doesn't have a License file.
[ https://issues.apache.org/jira/browse/CALCITE-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827068#comment-17827068 ] Stamatis Zampetakis commented on CALCITE-6331: -- The licenses can be found here: [https://github.com/apache/calcite/tree/f0dc2b0aea46b1fd3f37e0cc126edaf82ade2344/src/main/config/licenses] Are you sure that there is something missing? > The third-party source code file doesn't have a License file. > - > > Key: CALCITE-6331 > URL: https://issues.apache.org/jira/browse/CALCITE-6331 > Project: Calcite > Issue Type: Improvement >Reporter: Calvin Kirs >Priority: Major > Labels: pull-request-available > > [https://github.com/apache/calcite/blob/main/LICENSE#L184-L196] > We reference these third-party source code files but don't provide the > corresponding LICENSE files. > FYI : [https://www.apache.org/legal/release-policy.html#license-file] > > Here is the MIT license: > > Permission is hereby granted, free of charge, to any person obtaining a copy > of this software and associated documentation files (the "Software"), to deal > in the Software without restriction, including without limitation the rights > to use, copy, modify, merge, publish, distribute, sublicense, and/or sell > copies of the Software, and to permit persons to whom the Software is > furnished to do so, subject to the following conditions: The above copyright > notice and this permission notice shall be included in all copies or > substantial portions of the Software. > > > > > > > > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CALCITE-6331) The third-party source code file doesn't have a License file.
[ https://issues.apache.org/jira/browse/CALCITE-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Calvin Kirs updated CALCITE-6331: - Description: [https://github.com/apache/calcite/blob/main/LICENSE#L184-L196] We reference these third-party source code files but don't provide the corresponding LICENSE files. FYI : [https://www.apache.org/legal/release-policy.html#license-file] Here is the MIT license: Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. was: [https://github.com/apache/calcite/blob/main/LICENSE#L184-L196] We reference these third-party source code files but don't provide the corresponding LICENSE files. FYI : [https://www.apache.org/legal/release-policy.html#license-file] Here is MIT license: Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. > The third-party source code file doesn't have a License file. > - > > Key: CALCITE-6331 > URL: https://issues.apache.org/jira/browse/CALCITE-6331 > Project: Calcite > Issue Type: Improvement >Reporter: Calvin Kirs >Priority: Major > Labels: pull-request-available > > [https://github.com/apache/calcite/blob/main/LICENSE#L184-L196] > We reference these third-party source code files but don't provide the > corresponding LICENSE files. > FYI : [https://www.apache.org/legal/release-policy.html#license-file] > > Here is the MIT license: > > Permission is hereby granted, free of charge, to any person obtaining a copy > of this software and associated documentation files (the "Software"), to deal > in the Software without restriction, including without limitation the rights > to use, copy, modify, merge, publish, distribute, sublicense, and/or sell > copies of the Software, and to permit persons to whom the Software is > furnished to do so, subject to the following conditions: The above copyright > notice and this permission notice shall be included in all copies or > substantial portions of the Software. > > > > > > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CALCITE-6331) The third-party source code file doesn't have a License file.
[ https://issues.apache.org/jira/browse/CALCITE-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Calvin Kirs updated CALCITE-6331: - Description: [https://github.com/apache/calcite/blob/main/LICENSE#L184-L196] We reference these third-party source code files but don't provide the corresponding LICENSE files. FYI : [https://www.apache.org/legal/release-policy.html#license-file] Here is MIT license: Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. was: [https://github.com/apache/calcite/blob/main/LICENSE#L184-L196] We reference these third-party source code files but don't provide the corresponding LICENSE files. FYI : [https://www.apache.org/legal/release-policy.html#license-file] Here is MIT license: Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. > The third-party source code file doesn't have a License file. > - > > Key: CALCITE-6331 > URL: https://issues.apache.org/jira/browse/CALCITE-6331 > Project: Calcite > Issue Type: Improvement >Reporter: Calvin Kirs >Priority: Major > Labels: pull-request-available > > [https://github.com/apache/calcite/blob/main/LICENSE#L184-L196] > We reference these third-party source code files but don't provide the > corresponding LICENSE files. > FYI : [https://www.apache.org/legal/release-policy.html#license-file] > > Here is MIT license: > > Permission is hereby granted, free of charge, to any person obtaining a copy > of this software and associated documentation files (the "Software"), to deal > in the Software without restriction, including without limitation the rights > to use, copy, modify, merge, publish, distribute, sublicense, and/or sell > copies of the Software, and to permit persons to whom the Software is > furnished to do so, subject to the following conditions: The above copyright > notice and this permission notice shall be included in all copies or > substantial portions of the Software. > > > > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CALCITE-6331) The third-party source code file doesn't have a License file.
[ https://issues.apache.org/jira/browse/CALCITE-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Calvin Kirs updated CALCITE-6331: - Description: [https://github.com/apache/calcite/blob/main/LICENSE#L184-L196] We reference these third-party source code files but don't provide the corresponding LICENSE files. FYI : [https://www.apache.org/legal/release-policy.html#license-file] Here is the MIT license: Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. was: [https://github.com/apache/calcite/blob/main/LICENSE#L184-L196] We reference these third-party source code files but don't provide the corresponding LICENSE files. FYI : [https://www.apache.org/legal/release-policy.html#license-file] Here is the MIT license: Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. > The third-party source code file doesn't have a License file. > - > > Key: CALCITE-6331 > URL: https://issues.apache.org/jira/browse/CALCITE-6331 > Project: Calcite > Issue Type: Improvement >Reporter: Calvin Kirs >Priority: Major > Labels: pull-request-available > > [https://github.com/apache/calcite/blob/main/LICENSE#L184-L196] > We reference these third-party source code files but don't provide the > corresponding LICENSE files. > FYI : [https://www.apache.org/legal/release-policy.html#license-file] > > Here is the MIT license: > > Permission is hereby granted, free of charge, to any person obtaining a copy > of this software and associated documentation files (the "Software"), to deal > in the Software without restriction, including without limitation the rights > to use, copy, modify, merge, publish, distribute, sublicense, and/or sell > copies of the Software, and to permit persons to whom the Software is > furnished to do so, subject to the following conditions: The above copyright > notice and this permission notice shall be included in all copies or > substantial portions of the Software. > > > > > > > > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CALCITE-6331) The third-party source code file doesn't have a License file.
[ https://issues.apache.org/jira/browse/CALCITE-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Calvin Kirs updated CALCITE-6331: - Description: [https://github.com/apache/calcite/blob/main/LICENSE#L184-L196] We reference these third-party source code files but don't provide the corresponding LICENSE files. FYI : [https://www.apache.org/legal/release-policy.html#license-file] Here is MIT license: Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. was: [https://github.com/apache/calcite/blob/main/LICENSE#L184-L196] We reference these third-party source code files but don't provide the corresponding LICENSE files. FYI : https://www.apache.org/legal/release-policy.html#license-file > The third-party source code file doesn't have a License file. > - > > Key: CALCITE-6331 > URL: https://issues.apache.org/jira/browse/CALCITE-6331 > Project: Calcite > Issue Type: Improvement >Reporter: Calvin Kirs >Priority: Major > Labels: pull-request-available > > [https://github.com/apache/calcite/blob/main/LICENSE#L184-L196] > We reference these third-party source code files but don't provide the > corresponding LICENSE files. > FYI : [https://www.apache.org/legal/release-policy.html#license-file] > > Here is MIT license: > > Permission is hereby granted, free of charge, to any person obtaining a copy > of this software and associated documentation files (the "Software"), to deal > in the Software without restriction, including without limitation the rights > to use, copy, modify, merge, publish, distribute, sublicense, and/or sell > copies of the Software, and to permit persons to whom the Software is > furnished to do so, subject to the following conditions: The above copyright > notice and this permission notice shall be included in all copies or > substantial portions of the Software. > > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CALCITE-6331) The third-party source code file doesn't have a License file.
[ https://issues.apache.org/jira/browse/CALCITE-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CALCITE-6331: Labels: pull-request-available (was: ) > The third-party source code file doesn't have a License file. > - > > Key: CALCITE-6331 > URL: https://issues.apache.org/jira/browse/CALCITE-6331 > Project: Calcite > Issue Type: Improvement >Reporter: Calvin Kirs >Priority: Major > Labels: pull-request-available > > [https://github.com/apache/calcite/blob/main/LICENSE#L184-L196] > We reference these third-party source code files but don't provide the > corresponding LICENSE files. > FYI : https://www.apache.org/legal/release-policy.html#license-file > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CALCITE-6331) The third-party source code file doesn't have a License file.
Calvin Kirs created CALCITE-6331: Summary: The third-party source code file doesn't have a License file. Key: CALCITE-6331 URL: https://issues.apache.org/jira/browse/CALCITE-6331 Project: Calcite Issue Type: Improvement Reporter: Calvin Kirs [https://github.com/apache/calcite/blob/main/LICENSE#L184-L196] We reference these third-party source code files but don't provide the corresponding LICENSE files. FYI : https://www.apache.org/legal/release-policy.html#license-file -- This message was sent by Atlassian Jira (v8.20.10#820010)
