[jira] [Commented] (CALCITE-2374) Add instructions for building source releases to README
[ https://issues.apache.org/jira/browse/CALCITE-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16520010#comment-16520010 ] Francis Chuang commented on CALCITE-2374: - The readmes for Calcite and Avatica seem to be almost identical: [https://github.com/apache/calcite-avatica/blob/master/README] [https://github.com/apache/calcite/blob/master/README] > Add instructions for building source releases to README > --- > > Key: CALCITE-2374 > URL: https://issues.apache.org/jira/browse/CALCITE-2374 > Project: Calcite > Issue Type: Improvement > Components: avatica, core >Reporter: Francis Chuang >Priority: Trivial > > I think this should be pretty trivial for calcite and avatica. We just need > to say: `run: mvn install from the root of the extracted source`, right? > [~julianhyde] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CALCITE-2374) Add instructions for building source releases to README
[ https://issues.apache.org/jira/browse/CALCITE-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16519985#comment-16519985 ] Julian Hyde commented on CALCITE-2374: -- IIRC, Calcite already has it covered. The README references the document with the build instructions, or something like that. > Add instructions for building source releases to README > --- > > Key: CALCITE-2374 > URL: https://issues.apache.org/jira/browse/CALCITE-2374 > Project: Calcite > Issue Type: Improvement > Components: avatica, core >Reporter: Francis Chuang >Priority: Trivial > > I think this should be pretty trivial for calcite and avatica. We just need > to say: `run: mvn install from the root of the extracted source`, right? > [~julianhyde] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CALCITE-2374) Add instructions for building source releases to README
Francis Chuang created CALCITE-2374: --- Summary: Add instructions for building source releases to README Key: CALCITE-2374 URL: https://issues.apache.org/jira/browse/CALCITE-2374 Project: Calcite Issue Type: Improvement Components: avatica, core Reporter: Francis Chuang I think this should be pretty trivial for calcite and avatica. We just need to say: `run: mvn install from the root of the extracted source`, right? [~julianhyde] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CALCITE-2373) Fix Javadoc deprecation warnings under JDK 9
[
https://issues.apache.org/jira/browse/CALCITE-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francis Chuang updated CALCITE-2373:
Description:
Copied from the mailing list from [~julianhyde]'s post:
I just noticed the following deprecation warnings given by javadoc under JDK 9:
{code:java}
[WARNING]
/home/jhyde/regress/calcite-avatica/core/src/main/java/org/apache/calcite/avatica/AvaticaResultSet.java:[360,22]
getUnicodeStream(java.lang.String) in java.sql.ResultSet has been deprecated
[WARNING]
/home/jhyde/regress/calcite-avatica/core/src/main/java/org/apache/calcite/avatica/AvaticaResultSet.java:[335,21]
getBigDecimal(java.lang.String,int) in java.sql.ResultSet has been deprecated
[WARNING]
/home/jhyde/regress/calcite-avatica/core/src/main/java/org/apache/calcite/avatica/AvaticaResultSet.java:[295,22]
getUnicodeStream(int) in java.sql.ResultSet has been deprecated
[WARNING]
/home/jhyde/regress/calcite-avatica/core/src/main/java/org/apache/calcite/avatica/AvaticaResultSet.java:[270,21]
getBigDecimal(int,int) in java.sql.ResultSet has been deprecated
[WARNING]
/home/jhyde/regress/calcite-avatica/server/src/test/java/org/apache/calcite/avatica/SslDriverTest.java:[36,37]
org.bouncycastle.jce.provider.X509CertificateObject in
org.bouncycastle.jce.provider has been deprecated [WARNING]
/home/jhyde/regress/calcite-avatica/server/src/test/java/org/apache/calcite/avatica/SslDriverTest.java:[173,9]
org.bouncycastle.jce.provider.X509CertificateObject in
org.bouncycastle.jce.provider has been deprecated [WARNING]
/home/jhyde/regress/calcite-avatica/server/src/test/java/org/apache/calcite/avatica/SslDriverTest.java:[195,13]
org.bouncycastle.jce.provider.X509CertificateObject in
org.bouncycastle.jce.provider has been deprecated [WARNING]
/home/jhyde/regress/calcite-avatica/server/src/test/java/org/apache/calcite/avatica/SslDriverTest.java:[220,18]
org.bouncycastle.jce.provider.X509CertificateObject in
org.bouncycastle.jce.provider has been deprecated{code}
was:
Copied from the mailing list from [~julianhyde]'s post:
I just noticed the following deprecation warnings given by javadoc under JDK 9:
{code:java}
[WARNING]
/home/jhyde/regress/calcite-avatica/core/src/main/java/org/apache/calcite/avatica/AvaticaResultSet.java:[360,22]
getUnicodeStream(java.lang.String) in java.sql.ResultSet has been deprecated
[WARNING]
/home/jhyde/regress/calcite-avatica/core/src/main/java/org/apache/calcite/avatica/AvaticaResultSet.java:[335,21]
getBigDecimal(java.lang.String,int) in java.sql.ResultSet has been deprecated
[WARNING]
/home/jhyde/regress/calcite-avatica/core/src/main/java/org/apache/calcite/avatica/AvaticaResultSet.java:[295,22]
getUnicodeStream(int) in java.sql.ResultSet has been deprecated [WARNING]
/home/jhyde/regress/calcite-avatica/core/src/main/java/org/apache/calcite/avatica/AvaticaResultSet.java:[270,21]
getBigDecimal(int,int) in java.sql.ResultSet has been deprecated [WARNING]
/home/jhyde/regress/calcite-avatica/server/src/test/java/org/apache/calcite/avatica/SslDriverTest.java:[36,37]
org.bouncycastle.jce.provider.X509CertificateObject in
org.bouncycastle.jce.provider has been deprecated [WARNING]
/home/jhyde/regress/calcite-avatica/server/src/test/java/org/apache/calcite/avatica/SslDriverTest.java:[173,9]
org.bouncycastle.jce.provider.X509CertificateObject in
org.bouncycastle.jce.provider has been deprecated [WARNING]
/home/jhyde/regress/calcite-avatica/server/src/test/java/org/apache/calcite/avatica/SslDriverTest.java:[195,13]
org.bouncycastle.jce.provider.X509CertificateObject in
org.bouncycastle.jce.provider has been deprecated [WARNING]
/home/jhyde/regress/calcite-avatica/server/src/test/java/org/apache/calcite/avatica/SslDriverTest.java:[220,18]
org.bouncycastle.jce.provider.X509CertificateObject in
org.bouncycastle.jce.provider has been deprecated{code}
> Fix Javadoc deprecation warnings under JDK 9
>
>
> Key: CALCITE-2373
> URL: https://issues.apache.org/jira/browse/CALCITE-2373
> Project: Calcite
> Issue Type: Bug
> Components: avatica
>Reporter: Francis Chuang
>Priority: Minor
>
> Copied from the mailing list from [~julianhyde]'s post:
> I just noticed the following deprecation warnings given by javadoc under JDK
> 9:
> {code:java}
> [WARNING]
> /home/jhyde/regress/calcite-avatica/core/src/main/java/org/apache/calcite/avatica/AvaticaResultSet.java:[360,22]
> getUnicodeStream(java.lang.String) in java.sql.ResultSet has been deprecated
> [WARNING]
> /home/jhyde/regress/calcite-avatica/core/src/main/java/org/apache/calcite/avatica/AvaticaResultSet.java:[335,21]
> getBigDecimal(java.lang.String,int) in java.sql.ResultSet has been
> deprecated
> [WARNING]
> /home/jhyde/regress/calcite-avatica/core/src/main/java/org/apache/calcite/avatica/Avatic
[jira] [Created] (CALCITE-2373) Fix Javadoc deprecation warnings under JDK 9
Francis Chuang created CALCITE-2373:
---
Summary: Fix Javadoc deprecation warnings under JDK 9
Key: CALCITE-2373
URL: https://issues.apache.org/jira/browse/CALCITE-2373
Project: Calcite
Issue Type: Bug
Components: avatica
Reporter: Francis Chuang
Copied from the mailing list from [~julianhyde]'s post:
I just noticed the following deprecation warnings given by javadoc under JDK 9:
{code:java}
[WARNING]
/home/jhyde/regress/calcite-avatica/core/src/main/java/org/apache/calcite/avatica/AvaticaResultSet.java:[360,22]
getUnicodeStream(java.lang.String) in java.sql.ResultSet has been deprecated
[WARNING]
/home/jhyde/regress/calcite-avatica/core/src/main/java/org/apache/calcite/avatica/AvaticaResultSet.java:[335,21]
getBigDecimal(java.lang.String,int) in java.sql.ResultSet has been deprecated
[WARNING]
/home/jhyde/regress/calcite-avatica/core/src/main/java/org/apache/calcite/avatica/AvaticaResultSet.java:[295,22]
getUnicodeStream(int) in java.sql.ResultSet has been deprecated [WARNING]
/home/jhyde/regress/calcite-avatica/core/src/main/java/org/apache/calcite/avatica/AvaticaResultSet.java:[270,21]
getBigDecimal(int,int) in java.sql.ResultSet has been deprecated [WARNING]
/home/jhyde/regress/calcite-avatica/server/src/test/java/org/apache/calcite/avatica/SslDriverTest.java:[36,37]
org.bouncycastle.jce.provider.X509CertificateObject in
org.bouncycastle.jce.provider has been deprecated [WARNING]
/home/jhyde/regress/calcite-avatica/server/src/test/java/org/apache/calcite/avatica/SslDriverTest.java:[173,9]
org.bouncycastle.jce.provider.X509CertificateObject in
org.bouncycastle.jce.provider has been deprecated [WARNING]
/home/jhyde/regress/calcite-avatica/server/src/test/java/org/apache/calcite/avatica/SslDriverTest.java:[195,13]
org.bouncycastle.jce.provider.X509CertificateObject in
org.bouncycastle.jce.provider has been deprecated [WARNING]
/home/jhyde/regress/calcite-avatica/server/src/test/java/org/apache/calcite/avatica/SslDriverTest.java:[220,18]
org.bouncycastle.jce.provider.X509CertificateObject in
org.bouncycastle.jce.provider has been deprecated{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CALCITE-2372) Add Phoenix 4.14 to Avatica-Go integration tests
[ https://issues.apache.org/jira/browse/CALCITE-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Chuang resolved CALCITE-2372. - Resolution: Fixed > Add Phoenix 4.14 to Avatica-Go integration tests > > > Key: CALCITE-2372 > URL: https://issues.apache.org/jira/browse/CALCITE-2372 > Project: Calcite > Issue Type: Task > Components: avatica-go >Reporter: Francis Chuang >Assignee: Francis Chuang >Priority: Major > Fix For: avatica-go-3.1.0 > > > The > [HBase-Phoenix-all-in-one|https://github.com/Boostport/hbase-phoenix-all-in-one] > docker image has been updated to HBase 1.4.5 and Phoenix 4.14.0. > We should test Avatica-Go against this new version of Phoenix when running > the Phoenix tests. > We should also turn the travis configuration into a build matrix so that we > are still testing against older versions of Phoenix + Avatica. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CALCITE-2372) Add Phoenix 4.14 to Avatica-Go integration tests
[ https://issues.apache.org/jira/browse/CALCITE-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16519872#comment-16519872 ] ASF GitHub Bot commented on CALCITE-2372: - Github user asfgit closed the pull request at: https://github.com/apache/calcite-avatica-go/pull/25 > Add Phoenix 4.14 to Avatica-Go integration tests > > > Key: CALCITE-2372 > URL: https://issues.apache.org/jira/browse/CALCITE-2372 > Project: Calcite > Issue Type: Task > Components: avatica-go >Reporter: Francis Chuang >Assignee: Francis Chuang >Priority: Major > Fix For: avatica-go-3.1.0 > > > The > [HBase-Phoenix-all-in-one|https://github.com/Boostport/hbase-phoenix-all-in-one] > docker image has been updated to HBase 1.4.5 and Phoenix 4.14.0. > We should test Avatica-Go against this new version of Phoenix when running > the Phoenix tests. > We should also turn the travis configuration into a build matrix so that we > are still testing against older versions of Phoenix + Avatica. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CALCITE-2372) Add Phoenix 4.14 to Avatica-Go integration tests
[ https://issues.apache.org/jira/browse/CALCITE-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16519862#comment-16519862 ] ASF GitHub Bot commented on CALCITE-2372: - GitHub user F21 opened a pull request: https://github.com/apache/calcite-avatica-go/pull/25 [CALCITE-2372] Add Phoenix 4.14.0 for testing and turn travis.yml into a build matrix You can merge this pull request into a Git repository by running: $ git pull https://github.com/Boostport/calcite-avatica-go add-phoenix-4.14.0-for-testing Alternatively you can review and apply these changes as the patch at: https://github.com/apache/calcite-avatica-go/pull/25.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #25 commit d661be75564d5dd89e4687d54659ecdbd28b574b Author: Francis Chuang Date: 2018-06-22T00:12:45Z [CALCITE-2372] Add Phoenix 4.14.0 for testing and turn travis.yml into a build matrix > Add Phoenix 4.14 to Avatica-Go integration tests > > > Key: CALCITE-2372 > URL: https://issues.apache.org/jira/browse/CALCITE-2372 > Project: Calcite > Issue Type: Task > Components: avatica-go >Reporter: Francis Chuang >Assignee: Francis Chuang >Priority: Major > Fix For: avatica-go-3.1.0 > > > The > [HBase-Phoenix-all-in-one|https://github.com/Boostport/hbase-phoenix-all-in-one] > docker image has been updated to HBase 1.4.5 and Phoenix 4.14.0. > We should test Avatica-Go against this new version of Phoenix when running > the Phoenix tests. > We should also turn the travis configuration into a build matrix so that we > are still testing against older versions of Phoenix + Avatica. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CALCITE-2372) Add Phoenix 4.14 to Avatica-Go integration tests
Francis Chuang created CALCITE-2372: --- Summary: Add Phoenix 4.14 to Avatica-Go integration tests Key: CALCITE-2372 URL: https://issues.apache.org/jira/browse/CALCITE-2372 Project: Calcite Issue Type: Task Components: avatica-go Reporter: Francis Chuang Assignee: Francis Chuang Fix For: avatica-go-3.1.0 The [HBase-Phoenix-all-in-one|https://github.com/Boostport/hbase-phoenix-all-in-one] docker image has been updated to HBase 1.4.5 and Phoenix 4.14.0. We should test Avatica-Go against this new version of Phoenix when running the Phoenix tests. We should also turn the travis configuration into a build matrix so that we are still testing against older versions of Phoenix + Avatica. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CALCITE-2268) Avatica HSQLDB Dockerfile should be bumped to 2.4.0
[ https://issues.apache.org/jira/browse/CALCITE-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden reassigned CALCITE-2268: - Assignee: Francis Chuang (was: Kevin Risden) > Avatica HSQLDB Dockerfile should be bumped to 2.4.0 > --- > > Key: CALCITE-2268 > URL: https://issues.apache.org/jira/browse/CALCITE-2268 > Project: Calcite > Issue Type: Improvement > Components: avatica >Reporter: Kevin Risden >Assignee: Francis Chuang >Priority: Trivial > Fix For: avatica-1.12.0 > > > CALCITE-2013 bumped the HSQLDB version to 2.4.0. Looks like the Dockerfile > was not updated at the same time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CALCITE-2215) Avatica - Remove unused shaded jar
[ https://issues.apache.org/jira/browse/CALCITE-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volodymyr Vysotskyi updated CALCITE-2215: - Fix Version/s: 1.17.0 > Avatica - Remove unused shaded jar > -- > > Key: CALCITE-2215 > URL: https://issues.apache.org/jira/browse/CALCITE-2215 > Project: Calcite > Issue Type: Task >Reporter: Volodymyr Vysotskyi >Assignee: Julian Hyde >Priority: Minor > Fix For: 1.17.0 > > > Currently shaded/core/pom.xml and standalone-server/pom.xml files shade jar > which was not declared in the pom files: > - org.apache.commons > It may cause problems for projects which shade Avatica and have dependencies > to the specified library. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CALCITE-1362) Filter aboved Join should consider the join key equivalence to push through
[ https://issues.apache.org/jira/browse/CALCITE-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volodymyr Vysotskyi updated CALCITE-1362: - Fix Version/s: 1.17.0 > Filter aboved Join should consider the join key equivalence to push through > > > Key: CALCITE-1362 > URL: https://issues.apache.org/jira/browse/CALCITE-1362 > Project: Calcite > Issue Type: Improvement >Reporter: wei lin >Assignee: Vitalii Diravka >Priority: Major > Fix For: 1.17.0 > > Original Estimate: 168h > Remaining Estimate: 168h > > currently the FilterIntoJoinRule does not consider the join key equivalence. > we should consider that and push more condition into children. i will do it > and provide the patch later. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CALCITE-1711) Expose elasticsearch as jdbc type rather than custom
[ https://issues.apache.org/jira/browse/CALCITE-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volodymyr Vysotskyi updated CALCITE-1711: - Fix Version/s: 1.17.0 > Expose elasticsearch as jdbc type rather than custom > > > Key: CALCITE-1711 > URL: https://issues.apache.org/jira/browse/CALCITE-1711 > Project: Calcite > Issue Type: Bug > Components: avatica >Reporter: Rani Yaroshinsky >Priority: Major > Fix For: 1.17.0 > > > I cannot figure out how to add specific schema to elasticsearch adapter, or > how to expose is as the relevant fields with types rather than this weird > _MAP, which does not expose correctly for any tool. > An example or documentation, would help with this issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CALCITE-1958) Cannot create Schema objects when using Avatica with HSQLDB
[
https://issues.apache.org/jira/browse/CALCITE-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volodymyr Vysotskyi updated CALCITE-1958:
-
Fix Version/s: 1.17.0
> Cannot create Schema objects when using Avatica with HSQLDB
> ---
>
> Key: CALCITE-1958
> URL: https://issues.apache.org/jira/browse/CALCITE-1958
> Project: Calcite
> Issue Type: Bug
> Components: avatica
>Reporter: Francis Chuang
>Priority: Major
> Fix For: 1.17.0
>
>
> Encountered this one while porting a test from Phoenix to Avatica with HSQLDB
> for the Go client.
> This happens whether I open the connection with or without a default schema
> to Avatica.
> I then create a schema: `CREATE SCHEMA IF NOT EXISTS avaticatest`.
> I then attempt to create a table:
> {code}
> CREATE TABLE avaticatest.some_table (
> int INTEGER PRIMARY KEY
> )
> {code}
> Avatica fails with this message:
> {code}
> An error was encountered while processing your request: RuntimeException:
> java.sql.SQLException: invalid schema name: avaticatest in statement [CREATE
> TABLE avaticatest.some_table (
> int INTEGER PRIMARY KEY
> )] -> SQLException: invalid
> schema name: avaticatest in statement [CREATE TABLE avaticatest.some_table (
> int INTEGER PRIMARY KEY
> )] -> HsqlException: invalid
> schema name: avaticatest
> {code}
> I have tried a few things that did not work:
> - Making the schema name uppercase `AVATICATEST` everywhere
> - Making the table name also uppercase everywhere: `SOME_TABLE`.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CALCITE-2319) Druid Expressions - Output Type of Boolean expressions should be set to LONG.
[
https://issues.apache.org/jira/browse/CALCITE-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volodymyr Vysotskyi updated CALCITE-2319:
-
Fix Version/s: 1.17.0
> Druid Expressions - Output Type of Boolean expressions should be set to LONG.
> -
>
> Key: CALCITE-2319
> URL: https://issues.apache.org/jira/browse/CALCITE-2319
> Project: Calcite
> Issue Type: Bug
> Components: druid
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
>Priority: Major
> Fix For: 1.17.0
>
>
> Sample Query -
> {code}
> SELECT \"product_id\" > 1000 as pid_category, COUNT(\"store_sales\") FROM
> FOODMART_TABLE GROUP BY \"product_id\" > 1000";
> {code}
> For the above query output type of virtual column is set to string whereas it
> should be set to float as druid expression return type is float.
> {code}
> "{"queryType":"groupBy","dataSource":"foodmart","granularity":"all","dimensions":[{"type":"default","dimension":"vc","outputName":"vc","outputType":"STRING"}],"virtualColumns":[{"type":"expression","name":"vc","expression":"(CAST(\"product_id\",
> 'LONG') >
> 1000)","outputType":"FLOAT"}],"limitSpec":{"type":"default"},"aggregations":[{"type":"filtered","filter":{"type":"not","field":{"type":"selector","dimension":"store_sales","value":null}},"aggregator":{"type":"count","name":"EXPR$1","fieldName":"store_sales"}}],"intervals":["1900-01-09T00:00:00.000Z/2992-01-10T00:00:00.000Z"]}"
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CALCITE-2319) Druid Expressions - Output Type of Boolean expressions should be set to LONG.
[
https://issues.apache.org/jira/browse/CALCITE-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volodymyr Vysotskyi updated CALCITE-2319:
-
Component/s: druid
> Druid Expressions - Output Type of Boolean expressions should be set to LONG.
> -
>
> Key: CALCITE-2319
> URL: https://issues.apache.org/jira/browse/CALCITE-2319
> Project: Calcite
> Issue Type: Bug
> Components: druid
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
>Priority: Major
> Fix For: 1.17.0
>
>
> Sample Query -
> {code}
> SELECT \"product_id\" > 1000 as pid_category, COUNT(\"store_sales\") FROM
> FOODMART_TABLE GROUP BY \"product_id\" > 1000";
> {code}
> For the above query output type of virtual column is set to string whereas it
> should be set to float as druid expression return type is float.
> {code}
> "{"queryType":"groupBy","dataSource":"foodmart","granularity":"all","dimensions":[{"type":"default","dimension":"vc","outputName":"vc","outputType":"STRING"}],"virtualColumns":[{"type":"expression","name":"vc","expression":"(CAST(\"product_id\",
> 'LONG') >
> 1000)","outputType":"FLOAT"}],"limitSpec":{"type":"default"},"aggregations":[{"type":"filtered","filter":{"type":"not","field":{"type":"selector","dimension":"store_sales","value":null}},"aggregator":{"type":"count","name":"EXPR$1","fieldName":"store_sales"}}],"intervals":["1900-01-09T00:00:00.000Z/2992-01-10T00:00:00.000Z"]}"
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CALCITE-2345) add tests using Fongo to Mongo Adapter
[ https://issues.apache.org/jira/browse/CALCITE-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volodymyr Vysotskyi updated CALCITE-2345: - Fix Version/s: 1.17.0 > add tests using Fongo to Mongo Adapter > -- > > Key: CALCITE-2345 > URL: https://issues.apache.org/jira/browse/CALCITE-2345 > Project: Calcite > Issue Type: Improvement > Components: mongodb >Reporter: Andrei Sereda >Assignee: Michael Mior >Priority: Major > Fix For: 1.17.0 > > > Better test coverage for unit tests using > [Fongo|https://github.com/fakemongo/fongo] which is in-memory implementation > of Mongo API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CALCITE-2345) add tests using Fongo to Mongo Adapter
[ https://issues.apache.org/jira/browse/CALCITE-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volodymyr Vysotskyi updated CALCITE-2345: - Component/s: mongodb > add tests using Fongo to Mongo Adapter > -- > > Key: CALCITE-2345 > URL: https://issues.apache.org/jira/browse/CALCITE-2345 > Project: Calcite > Issue Type: Improvement > Components: mongodb >Reporter: Andrei Sereda >Assignee: Michael Mior >Priority: Major > Fix For: 1.17.0 > > > Better test coverage for unit tests using > [Fongo|https://github.com/fakemongo/fongo] which is in-memory implementation > of Mongo API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CALCITE-2358) Use null literal instead of empty string as argument for timestamp_parse Druid expression
[
https://issues.apache.org/jira/browse/CALCITE-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volodymyr Vysotskyi updated CALCITE-2358:
-
Fix Version/s: 1.17.0
> Use null literal instead of empty string as argument for timestamp_parse
> Druid expression
> -
>
> Key: CALCITE-2358
> URL: https://issues.apache.org/jira/browse/CALCITE-2358
> Project: Calcite
> Issue Type: Bug
> Components: druid
>Reporter: slim bouguerra
>Assignee: slim bouguerra
>Priority: Major
> Fix For: 1.17.0
>
>
> With the new ability to support null values in Druid, empty string is not
> equal to null anymore.
> To enable auto format parser {code}timestamp_parse{code} Druid function
> expects null literal as format argument.
> I have added a connection config parameter to allow smooth transition from
> old Druid version to version 0.13.0 and above.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CALCITE-2337) Release Calcite 1.17.0
[ https://issues.apache.org/jira/browse/CALCITE-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volodymyr Vysotskyi reassigned CALCITE-2337: Assignee: Volodymyr Vysotskyi (was: Julian Hyde) > Release Calcite 1.17.0 > -- > > Key: CALCITE-2337 > URL: https://issues.apache.org/jira/browse/CALCITE-2337 > Project: Calcite > Issue Type: Task >Reporter: Volodymyr Vysotskyi >Assignee: Volodymyr Vysotskyi >Priority: Major > Fix For: 1.17.0 > > > Release Calcite 1.17.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CALCITE-2347) embedded ElasticSearch node for ES adapter unit tests
[ https://issues.apache.org/jira/browse/CALCITE-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Mior resolved CALCITE-2347. --- Resolution: Fixed Fix Version/s: 1.17.0 > embedded ElasticSearch node for ES adapter unit tests > - > > Key: CALCITE-2347 > URL: https://issues.apache.org/jira/browse/CALCITE-2347 > Project: Calcite > Issue Type: Improvement > Components: elasticsearch-adapter >Reporter: Andrei Sereda >Assignee: Michael Mior >Priority: Major > Fix For: 1.17.0 > > > Currently ES adapter integration tests require manual startup of elastic > cluster. Elastic node can also be started programmatically and embedded in a > java application. Init costs are small enough to be run as part of unit test. > The plan is to migrate (re-use) exiting IT to be executed as part of unit > test as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CALCITE-2347) embedded ElasticSearch node for ES adapter unit tests
[ https://issues.apache.org/jira/browse/CALCITE-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16519215#comment-16519215 ] Michael Mior commented on CALCITE-2347: --- Fixed in [c12cb4b0d|https://github.com/apache/calcite/commit/c12cb4b0de1baa3f7cbb9952ee350fdd1701662d] > embedded ElasticSearch node for ES adapter unit tests > - > > Key: CALCITE-2347 > URL: https://issues.apache.org/jira/browse/CALCITE-2347 > Project: Calcite > Issue Type: Improvement > Components: elasticsearch-adapter >Reporter: Andrei Sereda >Assignee: Michael Mior >Priority: Major > Fix For: 1.17.0 > > > Currently ES adapter integration tests require manual startup of elastic > cluster. Elastic node can also be started programmatically and embedded in a > java application. Init costs are small enough to be run as part of unit test. > The plan is to migrate (re-use) exiting IT to be executed as part of unit > test as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CALCITE-2347) embedded ElasticSearch node for ES adapter unit tests
[ https://issues.apache.org/jira/browse/CALCITE-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Mior reassigned CALCITE-2347: - Assignee: Michael Mior (was: Julian Hyde) > embedded ElasticSearch node for ES adapter unit tests > - > > Key: CALCITE-2347 > URL: https://issues.apache.org/jira/browse/CALCITE-2347 > Project: Calcite > Issue Type: Improvement > Components: elasticsearch-adapter >Reporter: Andrei Sereda >Assignee: Michael Mior >Priority: Major > > Currently ES adapter integration tests require manual startup of elastic > cluster. Elastic node can also be started programmatically and embedded in a > java application. Init costs are small enough to be run as part of unit test. > The plan is to migrate (re-use) exiting IT to be executed as part of unit > test as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
