[jira] [Updated] (CALCITE-6181) Upgrade janino to 3.1.11
[ https://issues.apache.org/jira/browse/CALCITE-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaspati Krishnatri updated CALCITE-6181: -- Description: Upgrade Janino to 3.1.9+ due to CVE-2023-33546 janino 3.1.9 and earlier are subject to denial of service (DOS) attacks when using the expression evaluator.guess parameter name method. If the parser runs on user-supplied input, an attacker could supply content that causes the parser to crash due to a stack overflow. CVSSv3 Score:- 5.5(Medium) was: Upgrade Janino to 3.1.10 due to CVE-2023-33546 janino 3.1.9 and earlier are subject to denial of service (DOS) attacks when using the expression evaluator.guess parameter name method. If the parser runs on user-supplied input, an attacker could supply content that causes the parser to crash due to a stack overflow. CVSSv3 Score:- 5.5(Medium) > Upgrade janino to 3.1.11 > > > Key: CALCITE-6181 > URL: https://issues.apache.org/jira/browse/CALCITE-6181 > Project: Calcite > Issue Type: Task >Reporter: Devaspati Krishnatri >Priority: Major > Labels: pull-request-available > > Upgrade Janino to 3.1.9+ due to CVE-2023-33546 > janino 3.1.9 and earlier are subject to denial of service (DOS) attacks when > using the expression evaluator.guess parameter name method. If the parser > runs on user-supplied input, an attacker could supply content that causes the > parser to crash due to a stack overflow. > CVSSv3 Score:- 5.5(Medium) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CALCITE-6181) Upgrade janino to 3.1.11
[ https://issues.apache.org/jira/browse/CALCITE-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaspati Krishnatri updated CALCITE-6181: -- Summary: Upgrade janino to 3.1.11 (was: Upgrade janino to 3.1.10) > Upgrade janino to 3.1.11 > > > Key: CALCITE-6181 > URL: https://issues.apache.org/jira/browse/CALCITE-6181 > Project: Calcite > Issue Type: Task >Reporter: Devaspati Krishnatri >Priority: Major > Labels: pull-request-available > > Upgrade Janino to 3.1.10 due to CVE-2023-33546 > janino 3.1.9 and earlier are subject to denial of service (DOS) attacks when > using the expression evaluator.guess parameter name method. If the parser > runs on user-supplied input, an attacker could supply content that causes the > parser to crash due to a stack overflow. > CVSSv3 Score:- 5.5(Medium) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CALCITE-6116) Add EXISTS function (enabled in Spark library)
[
https://issues.apache.org/jira/browse/CALCITE-6116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17800926#comment-17800926
]
hongyu guo commented on CALCITE-6116:
-
Fixed in
[e877885|https://github.com/apache/calcite/commit/e877885ed90127a4cadb25f1b718f91375fe6164].
[~julianhyde] and [~mbudiu], thanks for your review!
> Add EXISTS function (enabled in Spark library)
> --
>
> Key: CALCITE-6116
> URL: https://issues.apache.org/jira/browse/CALCITE-6116
> Project: Calcite
> Issue Type: Improvement
> Components: core
>Affects Versions: 1.36.0
>Reporter: hongyu guo
>Assignee: hongyu guo
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.37.0
>
>
> exists(expr, pred) - Tests whether a predicate holds for one or more elements
> in the array.
> {code:sql}
> > SELECT `EXISTS`(array(1, 2, 3), x -> x % 2 == 0);
> true
> > SELECT `EXISTS`(array(1, 2, 3), x -> x % 2 == 10);
> false
> > SELECT `EXISTS`(array(1, null, 3), x -> x % 2 == 0);
> NULL
> > SELECT `EXISTS`(array(0, null, 2, 3, null), x -> x IS NULL);
> true
> > SELECT `EXISTS`(array(1, 2, 3), x -> x IS NULL);
> false
> {code}
> In Calcite, EXISTS is a keyword, so we need to specify the function with back
> quotes.
> Moreover, `EXISTS` is a higher-order function, and if we want to support
> higher-order functions in Calcite, we must first support lambda expressions
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CALCITE-6116) Add EXISTS function (enabled in Spark library)
[
https://issues.apache.org/jira/browse/CALCITE-6116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
hongyu guo resolved CALCITE-6116.
-
Resolution: Fixed
> Add EXISTS function (enabled in Spark library)
> --
>
> Key: CALCITE-6116
> URL: https://issues.apache.org/jira/browse/CALCITE-6116
> Project: Calcite
> Issue Type: Improvement
> Components: core
>Affects Versions: 1.36.0
>Reporter: hongyu guo
>Assignee: hongyu guo
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.37.0
>
>
> exists(expr, pred) - Tests whether a predicate holds for one or more elements
> in the array.
> {code:sql}
> > SELECT `EXISTS`(array(1, 2, 3), x -> x % 2 == 0);
> true
> > SELECT `EXISTS`(array(1, 2, 3), x -> x % 2 == 10);
> false
> > SELECT `EXISTS`(array(1, null, 3), x -> x % 2 == 0);
> NULL
> > SELECT `EXISTS`(array(0, null, 2, 3, null), x -> x IS NULL);
> true
> > SELECT `EXISTS`(array(1, 2, 3), x -> x IS NULL);
> false
> {code}
> In Calcite, EXISTS is a keyword, so we need to specify the function with back
> quotes.
> Moreover, `EXISTS` is a higher-order function, and if we want to support
> higher-order functions in Calcite, we must first support lambda expressions
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CALCITE-6182) Add LENGTH/LEN function (enabled in Snowflake library)
[ https://issues.apache.org/jira/browse/CALCITE-6182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CALCITE-6182: Labels: pull-request-available (was: ) > Add LENGTH/LEN function (enabled in Snowflake library) > -- > > Key: CALCITE-6182 > URL: https://issues.apache.org/jira/browse/CALCITE-6182 > Project: Calcite > Issue Type: Improvement >Reporter: Tanner Clary >Assignee: Tanner Clary >Priority: Major > Labels: pull-request-available > > Calcite already supports CHAR_LENGTH and LENGTH functions for the standard > library and BigQuery, respectively. > Snowflake also supports LENGTH and LEN as an alias as well. > The functions are identical aside from their names. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CALCITE-6182) Add LENGTH/LEN function (enabled in Snowflake library)
Tanner Clary created CALCITE-6182: - Summary: Add LENGTH/LEN function (enabled in Snowflake library) Key: CALCITE-6182 URL: https://issues.apache.org/jira/browse/CALCITE-6182 Project: Calcite Issue Type: Improvement Reporter: Tanner Clary Assignee: Tanner Clary Calcite already supports CHAR_LENGTH and LENGTH functions for the standard library and BigQuery, respectively. Snowflake also supports LENGTH and LEN as an alias as well. The functions are identical aside from their names. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CALCITE-6179) Support weekofmonth function format and add test
[ https://issues.apache.org/jira/browse/CALCITE-6179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CALCITE-6179: Labels: pull-request-available (was: ) > Support weekofmonth function format and add test > - > > Key: CALCITE-6179 > URL: https://issues.apache.org/jira/browse/CALCITE-6179 > Project: Calcite > Issue Type: Improvement > Components: core >Affects Versions: 1.36.0 >Reporter: Caican Cai >Assignee: Caican Cai >Priority: Minor > Labels: pull-request-available > Fix For: 1.37.0 > > > I found weekofmonth format missing in FormatElementEnum. > And I think I can add tests in FormatElementEnumTest to test the function of > each format -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CALCITE-6179) Support weekofmonth function format and add test
[ https://issues.apache.org/jira/browse/CALCITE-6179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caican Cai reassigned CALCITE-6179: --- Assignee: Caican Cai > Support weekofmonth function format and add test > - > > Key: CALCITE-6179 > URL: https://issues.apache.org/jira/browse/CALCITE-6179 > Project: Calcite > Issue Type: Improvement > Components: core >Affects Versions: 1.36.0 >Reporter: Caican Cai >Assignee: Caican Cai >Priority: Minor > Fix For: 1.37.0 > > > I found weekofmonth format missing in FormatElementEnum. > And I think I can add tests in FormatElementEnumTest to test the function of > each format -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CALCITE-6179) Support weekofmonth function format and add test
[ https://issues.apache.org/jira/browse/CALCITE-6179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17800674#comment-17800674 ] Caican Cai edited comment on CALCITE-6179 at 12/27/23 2:25 PM: --- And I found other bugs when formatting. Please see this PR for details. [https://github.com/apache/calcite/pull/3600] was (Author: JIRAUSER302115): And I found other bugs when formatting. Please see this PR for details. [[MINOR] Add FormatElementEnumTests and add weekofmonth format by caicancai · Pull Request #3600 · apache/calcite (github.com)|https://github.com/apache/calcite/pull/3600/files] > Support weekofmonth function format and add test > - > > Key: CALCITE-6179 > URL: https://issues.apache.org/jira/browse/CALCITE-6179 > Project: Calcite > Issue Type: Improvement > Components: core >Affects Versions: 1.36.0 >Reporter: Caican Cai >Priority: Minor > Fix For: 1.37.0 > > > I found weekofmonth format missing in FormatElementEnum. > And I think I can add tests in FormatElementEnumTest to test the function of > each format -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CALCITE-6181) Upgrade janino to 3.1.10
[ https://issues.apache.org/jira/browse/CALCITE-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CALCITE-6181: Labels: pull-request-available (was: ) > Upgrade janino to 3.1.10 > > > Key: CALCITE-6181 > URL: https://issues.apache.org/jira/browse/CALCITE-6181 > Project: Calcite > Issue Type: Task >Reporter: Devaspati Krishnatri >Priority: Major > Labels: pull-request-available > > Upgrade Janino to 3.1.10 due to CVE-2023-33546 > janino 3.1.9 and earlier are subject to denial of service (DOS) attacks when > using the expression evaluator.guess parameter name method. If the parser > runs on user-supplied input, an attacker could supply content that causes the > parser to crash due to a stack overflow. > CVSSv3 Score:- 5.5(Medium) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CALCITE-6181) Upgrade janino to 3.1.10
Devaspati Krishnatri created CALCITE-6181: - Summary: Upgrade janino to 3.1.10 Key: CALCITE-6181 URL: https://issues.apache.org/jira/browse/CALCITE-6181 Project: Calcite Issue Type: Task Reporter: Devaspati Krishnatri Upgrade Janino to 3.1.10 due to CVE-2023-33546 janino 3.1.9 and earlier are subject to denial of service (DOS) attacks when using the expression evaluator.guess parameter name method. If the parser runs on user-supplied input, an attacker could supply content that causes the parser to crash due to a stack overflow. CVSSv3 Score:- 5.5(Medium) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CALCITE-6180) Backslash cannot be escaped in LIKE ESCAPE operator
[
https://issues.apache.org/jira/browse/CALCITE-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated CALCITE-6180:
Labels: pull-request-available (was: pull)
> Backslash cannot be escaped in LIKE ESCAPE operator
> ---
>
> Key: CALCITE-6180
> URL: https://issues.apache.org/jira/browse/CALCITE-6180
> Project: Calcite
> Issue Type: Bug
> Components: core
>Affects Versions: 1.36.0
>Reporter: Evgeny Stanilovsky
>Assignee: Evgeny Stanilovsky
>Priority: Major
> Labels: pull-request-available
>
> The expression below must be processed correctly and return positive result
> {noformat}
> select 'Dev\ops' like 'Dev#\ops' escape '#';
> {noformat}
> Insted it returns :
> Invalid escape sequence exception.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CALCITE-6180) Backslash cannot be escaped in LIKE ESCAPE operator
[
https://issues.apache.org/jira/browse/CALCITE-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated CALCITE-6180:
Labels: pull (was: pull-request-available)
> Backslash cannot be escaped in LIKE ESCAPE operator
> ---
>
> Key: CALCITE-6180
> URL: https://issues.apache.org/jira/browse/CALCITE-6180
> Project: Calcite
> Issue Type: Bug
> Components: core
>Affects Versions: 1.36.0
>Reporter: Evgeny Stanilovsky
>Assignee: Evgeny Stanilovsky
>Priority: Major
> Labels: pull
>
> The expression below must be processed correctly and return positive result
> {noformat}
> select 'Dev\ops' like 'Dev#\ops' escape '#';
> {noformat}
> Insted it returns :
> Invalid escape sequence exception.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CALCITE-6180) Backslash cannot be escaped in LIKE ESCAPE operator
[
https://issues.apache.org/jira/browse/CALCITE-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CALCITE-6180:
Labels: pull-request-available (was: )
> Backslash cannot be escaped in LIKE ESCAPE operator
> ---
>
> Key: CALCITE-6180
> URL: https://issues.apache.org/jira/browse/CALCITE-6180
> Project: Calcite
> Issue Type: Bug
> Components: core
>Affects Versions: 1.36.0
>Reporter: Evgeny Stanilovsky
>Assignee: Evgeny Stanilovsky
>Priority: Major
> Labels: pull-request-available
>
> The expression below must be processed correctly and return positive result
> {noformat}
> select 'Dev\ops' like 'Dev#\ops' escape '#';
> {noformat}
> Insted it returns :
> Invalid escape sequence exception.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CALCITE-6180) Backslash cannot be escaped in LIKE ESCAPE operator
Evgeny Stanilovsky created CALCITE-6180:
---
Summary: Backslash cannot be escaped in LIKE ESCAPE operator
Key: CALCITE-6180
URL: https://issues.apache.org/jira/browse/CALCITE-6180
Project: Calcite
Issue Type: Bug
Components: core
Affects Versions: 1.36.0
Reporter: Evgeny Stanilovsky
Assignee: Evgeny Stanilovsky
The expression below must be processed correctly and return positive result
{noformat}
select 'Dev\ops' like 'Dev#\ops' escape '#';
{noformat}
Insted it returns :
Invalid escape sequence exception.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
