[jira] [Created] (CALCITE-4671) Allow Avatica connect-string properties in any case (lowerCamel, UPPER_SNAKE, etc.)
Julian Hyde created CALCITE-4671:
Summary: Allow Avatica connect-string properties in any case
(lowerCamel, UPPER_SNAKE, etc.)
Key: CALCITE-4671
URL: https://issues.apache.org/jira/browse/CALCITE-4671
Project: Calcite
Issue Type: Bug
Components: avatica
Reporter: Julian Hyde
Avatica's built-in properties are mostly lower_snake case (e.g.
{{truststore_password}}; the one exception being {{timeZone}} in lowerCamel;
see [client
reference|https://calcite.apache.org/avatica/docs/client_reference.html]);
Calcite's built-in properties are lowerCamel case (e.g.
[approximateTopN|https://calcite.apache.org/javadocAggregate/org/apache/calcite/config/CalciteConnectionProperty.html#APPROXIMATE_TOP_N];
see [Calcite JDBC driver
reference|https://calcite.apache.org/docs/adapter.html#jdbc-connect-string-parameters%C2%A0]).
Avatica's properties are inherited by Calcite, so there is bound to be
confusion.
Avatica's connect string parser (also used in Calcite) should allow any case.
Thus {{truststore_password}}, {{truststorePassword}}, {{TRUSTSTORE_PASSWORD}},
{{TruststorePassword}} are all acceptable. {{trustStorePassword}} is not
acceptable, because "truststore" is one word.
In Calcite and Avatica doc, add a note that properties can are accepted in any
case.
Change Avatica's properties to lowerCamel case in both doc and code. (The old
forms, e.g. "truststore_password", will continue to work.)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CALCITE-4670) Support PERCENTILE_DISC for any sortable type and PERCENTILE_CONT for interval types
Rafay A created CALCITE-4670: Summary: Support PERCENTILE_DISC for any sortable type and PERCENTILE_CONT for interval types Key: CALCITE-4670 URL: https://issues.apache.org/jira/browse/CALCITE-4670 Project: Calcite Issue Type: Improvement Components: core Reporter: Rafay A With the current implementation (CALCITE-4644), percentile functions are only supported for numeric types. We want to add support for any sortable type for PERCENTILE_DISC as Postgres supports, and also add support for interval types for PERCENTILE_CONT. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CALCITE-4669) Allow empty MAP[] constructors
Jiefan Li created CALCITE-4669:
--
Summary: Allow empty MAP[] constructors
Key: CALCITE-4669
URL: https://issues.apache.org/jira/browse/CALCITE-4669
Project: Calcite
Issue Type: Wish
Reporter: Jiefan Li
Similar ticket: https://issues.apache.org/jira/browse/CALCITE-3504
Currently an MAP expression requires at least 2 element. However, Hive supports
empty MAP() syntax.
Please allow empty MAP expressions:
{code:sql}
SELECT MAP[] FROM foo;
{code}
cc: [~wmoustafa]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [ANNOUNCE] New committer: Vladimir Ozerov
Congratulations, Vladimir! Best, Chunwei On Sat, Jun 26, 2021 at 3:03 AM Vladimir Sitnikov < sitnikov.vladi...@gmail.com> wrote: > Vladimir, welcome! > > >consistent signal from the "field" - lack of documentation blocks > > I wonder if logging "missing sections" would help. > The catch here is if you work with Calcite for some time the missing docs > become a blind spot. > > For instance, once I heard that if one wants to add a test case, then it is > not clear which class/approach is appropriate. > If you think about it, we do have multiple ways to create tests at > different levels, however, we do not suggest entry points or something like > that. > > It might probably help if there was a layered diagram with pointers to the > test class samples. > > Vladimir >
