You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@calcite.apache.org by Julian Hyde <jh...@apache.org> on 2016/10/12 00:28:29 UTC
Towards Avatica 1.9
Over 20 commits and 4 months since the last Avatica release. Is it about time we had another?
Does anyone have any time constraints (must be done before X; or must be done after Y; or please wait until I’ve had chance to fix bugs Z1 and Z2)?
See the tracking JIRA case, https://issues.apache.org/jira/browse/CALCITE-1354 <https://issues.apache.org/jira/browse/CALCITE-1354>, and the corresponding Calcite issue https://issues.apache.org/jira/browse/CALCITE-1270 <https://issues.apache.org/jira/browse/CALCITE-1270>.
Julian
Re: Towards Avatica 1.9
Posted by Josh Elser <jo...@gmail.com>.
s/We now include shaded artifacts/We now included non-shaded and shaded
artifacts/
For historical accuracy, the issues were actually filed by people who
wanted non-shaded artifacts when we only published shaded artifacts for
some modules (e.g the introduction of
org.apache.calcite.avatica:avatica-core:1.9.0).
I can expand a little bit to document the protocol compatibility testing
I did (will do, rather) against 1.7.0, 1.8.0, and 1.8.1.
Calling out the protobuf-3.1.0 dependency upgrade (from the previous
beta version) is also likely good.
I think all of these can be tweaked after the fact, assuming rc0 passes.
- Josh
Julian Hyde wrote:
> Can someone review my draft release notes for accuracy?
>
> https://github.com/julianhyde/calcite/blob/branch-avatica-1.9/avatica/site/_docs/history.md
>
> I'll be cutting the the first release candidate (RC0) shortly.
>
> Julian
>
>
> On Sun, Oct 23, 2016 at 1:38 PM, Julian Hyde<jh...@apache.org> wrote:
>> Josh has fixed everything marked fixVersion = avatica-1.9.0. So, I think
>> we\u2019re good to go for an RC0 as early as tomorrow evening (~30 hours from
>> now). Please speak up if you have something you\u2019d like to put in.
>>
>> One question: I see that https://issues.apache.org/jira/browse/CALCITE-1353
>> is slated for avatica-1.10. But is there any reason it couldn\u2019t be done for
>> avatica-1.9? If someone wants to fix it, please speak up (and submit a PR)
>> ASAP.
>>
>> Julian
>>
>>
>>
>> On Oct 23, 2016, at 1:08 PM, Josh Elser<jo...@gmail.com> wrote:
>>
>> One last thing: I just closed out CALCITE-1255 (already done) and moved the
>> rest of the unresolved issues in fixVersion=avatica-1.9.0 to avatica-1.10.0.
>>
>> Josh Elser wrote:
>>
>> Alright, just made a whirlwind-pass through issues:
>>
>> 2ee0e35 [CALCITE-1464] Upgrade Jetty version to 9.2.19v20160908
>> 2438d53 [CALCITE-1463] standalone-server needs to relocate dependencies
>> itself
>> 221d180 [CALCITE-1355] Upgrade to protobuf-java 3.1.0
>> 483b9f9 [CALCITE-1462] Remove Avatica pom cruft
>>
>> Let me clean up the fixVersion=avatica-1.9.0 to reflect this (and we can
>> use that to track any further action before we make this release).
>>
>> - Josh
>>
>> Josh Elser wrote:
>>
>> First off, thanks for volunteering, Julian!
>>
>> Let me get in the stable protobuf-3 patch today. I've just been ignoring
>> this.
>>
>> I was hoping to get ARRAY support done, but it was trickier than I
>> anticipated and I'm still working on it. I think I should not hold up
>> the release more. I can finish it in 1.10.
>>
>> I see a few dependencies which only exist in depMgmt (hadoop and
>> findbugs, so far). I'll clean these up now as well. [1]
>>
>> * Updating jetty to 9.2.19.v20160908 is probably safe/good to do.
>> * Updating to jodatime 2.9.4 also sounds good[2]
>>
>> - Josh
>>
>> [1] https://issues.apache.org/jira/browse/CALCITE-1462
>> [2] http://www.joda.org/joda-time/upgradeto294.html
>>
>> Julian Hyde wrote:
>>
>> With
>> https://issues.apache.org/jira/browse/CALCITE-1458<https://issues.apache.org/jira/browse/CALCITE-1458>
>>
>> I think we need an avatica-1.9 fairly soon. Say, first RC on Wednesday
>> (he says, pulling a date out of the air).
>>
>> I volunteer to be release manager (unless someone would *love* to be
>> RM).
>>
>> What do you all think?
>>
>> Are there any dependencies we should upgrade? Here\u2019s the full list:
>>
>> <airlift-tpch.version>0.1</airlift-tpch.version>
>> <avatica.version>1.8.0</avatica.version>
>> <build-helper-maven-plugin.version>1.9</build-helper-maven-plugin.version>
>>
>>
>> <cassandra-driver-core.version>3.0.0</cassandra-driver-core.version>
>> <checksum-maven-plugin.version>1.2</checksum-maven-plugin.version>
>> <commons-dbcp.version>1.4</commons-dbcp.version>
>> <commons-lang3.version>3.2</commons-lang3.version>
>> <commons-logging.version>1.1.3</commons-logging.version>
>> <eigenbase-properties.version>1.1.5</eigenbase-properties.version>
>> <elasticsearch-java-driver.version>2.3.2</elasticsearch-java-driver.version>
>>
>>
>> <findbugs.version>1.3.9</findbugs.version>
>> <fmpp-maven-plugin.version>1.0</fmpp-maven-plugin.version>
>> <foodmart-data-hsqldb.version>0.3</foodmart-data-hsqldb.version>
>> <foodmart-queries.version>0.4.1</foodmart-queries.version>
>> <freemarker.version>2.3.19</freemarker.version>
>> <git-commit-id-plugin.version>2.1.9</git-commit-id-plugin.version>
>> <!-- We support (and test against) Guava versions between
>> 14.0.1 (Hive) and 19.0 (most recent).
>> Override with your preferred version and it should work. -->
>> <guava.version>18.0</guava.version>
>> <joda.version>2.8.1</joda.version>
>> <h2.version>1.4.185</h2.version>
>> <hadoop.version>2.6.0</hadoop.version>
>> <hamcrest.version>1.3</hamcrest.version>
>> <hppc.version>0.7.1</hppc.version>
>> <hsqldb.version>2.3.1</hsqldb.version>
>> <httpclient.version>4.5.2</httpclient.version>
>> <httpcore.version>4.4.4</httpcore.version>
>> <hydromatic-resource.version>0.5.1</hydromatic-resource.version>
>> <hydromatic-toolbox.version>0.3</hydromatic-toolbox.version>
>> <hydromatic-tpcds.version>0.4</hydromatic-tpcds.version>
>> <jackson.version>2.6.3</jackson.version>
>> <janino.version>2.7.6</janino.version>
>> <java-diff.version>1.1</java-diff.version>
>> <javacc-maven-plugin.version>2.4</javacc-maven-plugin.version>
>> <jcip-annotations.version>1.0-1</jcip-annotations.version>
>> <jetty.version>9.2.15.v20160210</jetty.version>
>> <jmh.version>1.11.2</jmh.version>
>> <junit.version>4.12</junit.version>
>> <maven-checkstyle-plugin.version>2.12.1</maven-checkstyle-plugin.version>
>>
>> <maven-dependency-plugin.version>2.10</maven-dependency-plugin.version>
>> <maven-failsafe-plugin.version>2.7.2</maven-failsafe-plugin.version>
>> <maven-scm-provider.version>1.9.1</maven-scm-provider.version>
>> <maven-shade-plugin.version>2.1</maven-shade-plugin.version>
>> <maven-source-plugin.version>2.4</maven-source-plugin.version>
>> <mockito-all.version>1.10.19</mockito-all.version>
>> <mongo-java-driver.version>2.12.3</mongo-java-driver.version>
>> <mysql-driver.version>5.1.20</mysql-driver.version>
>> <opencsv.version>2.3</opencsv.version>
>> <oracle-jdbc6-driver.version>11.2.0.2.0</oracle-jdbc6-driver.version>
>> <pentaho-aggdesigner.version>5.1.5-jhyde</pentaho-aggdesigner.version>
>> <postgresql.version>9.3-1102-jdbc3</postgresql.version>
>> <protobuf.version>3.0.0-beta-1</protobuf.version>
>> <quidem.version>0.7</quidem.version>
>> <scala.version>2.10.3</scala.version>
>> <scott-data-hsqldb.version>0.1</scott-data-hsqldb.version>
>> <servlet.version>3.0.1</servlet.version>
>> <slf4j.version>1.7.13</slf4j.version>
>> <spark.version>1.6.1</spark.version>
>> <sqlline.version>1.1.9</sqlline.version>
>> <xalan.version>2.7.1</xalan.version>
>> <xerces.version>2.9.1</xerces.version>
>>
>>
>>
>> Julian
>>
>>
>>
>>
>> On Oct 11, 2016, at 8:06 PM, Josh Elser<jo...@gmail.com> wrote:
>>
>> I'd like to finish up two issues:
>>
>> https://issues.apache.org/jira/browse/CALCITE-1050 ARRAY support. I
>> think this one is close. I need to write more tests. I am aiming to
>> commit this week.
>>
>> https://issues.apache.org/jira/browse/CALCITE-1355 Protobuf-java
>> upgrade. Since there is a stable release, we should get on to one of
>> those instead of the alpha/beta we presently have.
>>
>> There are few others in the pipeline that I need to revisit, but I
>> don't think they should block avatica-1.9
>>
>> Julian Hyde wrote:
>>
>> Over 20 commits and 4 months since the last Avatica release. Is it
>> about time we had another?
>>
>> Does anyone have any time constraints (must be done before X; or
>> must be done after Y; or please wait until I\u2019ve had chance to fix
>> bugs Z1 and Z2)?
>>
>> See the tracking JIRA case,
>> https://issues.apache.org/jira/browse/CALCITE-1354<https://issues.apache.org/jira/browse/CALCITE-1354>,
>>
>> and the corresponding Calcite issue
>> https://issues.apache.org/jira/browse/CALCITE-1270<https://issues.apache.org/jira/browse/CALCITE-1270>.
>>
>>
>>
>> Julian
>>
>>
>>
>>
>>
>
Re: Towards Avatica 1.9
Posted by Julian Hyde <jh...@apache.org>.
Can someone review my draft release notes for accuracy?
https://github.com/julianhyde/calcite/blob/branch-avatica-1.9/avatica/site/_docs/history.md
I'll be cutting the the first release candidate (RC0) shortly.
Julian
On Sun, Oct 23, 2016 at 1:38 PM, Julian Hyde <jh...@apache.org> wrote:
> Josh has fixed everything marked fixVersion = avatica-1.9.0. So, I think
> we’re good to go for an RC0 as early as tomorrow evening (~30 hours from
> now). Please speak up if you have something you’d like to put in.
>
> One question: I see that https://issues.apache.org/jira/browse/CALCITE-1353
> is slated for avatica-1.10. But is there any reason it couldn’t be done for
> avatica-1.9? If someone wants to fix it, please speak up (and submit a PR)
> ASAP.
>
> Julian
>
>
>
> On Oct 23, 2016, at 1:08 PM, Josh Elser <jo...@gmail.com> wrote:
>
> One last thing: I just closed out CALCITE-1255 (already done) and moved the
> rest of the unresolved issues in fixVersion=avatica-1.9.0 to avatica-1.10.0.
>
> Josh Elser wrote:
>
> Alright, just made a whirlwind-pass through issues:
>
> 2ee0e35 [CALCITE-1464] Upgrade Jetty version to 9.2.19v20160908
> 2438d53 [CALCITE-1463] standalone-server needs to relocate dependencies
> itself
> 221d180 [CALCITE-1355] Upgrade to protobuf-java 3.1.0
> 483b9f9 [CALCITE-1462] Remove Avatica pom cruft
>
> Let me clean up the fixVersion=avatica-1.9.0 to reflect this (and we can
> use that to track any further action before we make this release).
>
> - Josh
>
> Josh Elser wrote:
>
> First off, thanks for volunteering, Julian!
>
> Let me get in the stable protobuf-3 patch today. I've just been ignoring
> this.
>
> I was hoping to get ARRAY support done, but it was trickier than I
> anticipated and I'm still working on it. I think I should not hold up
> the release more. I can finish it in 1.10.
>
> I see a few dependencies which only exist in depMgmt (hadoop and
> findbugs, so far). I'll clean these up now as well. [1]
>
> * Updating jetty to 9.2.19.v20160908 is probably safe/good to do.
> * Updating to jodatime 2.9.4 also sounds good[2]
>
> - Josh
>
> [1] https://issues.apache.org/jira/browse/CALCITE-1462
> [2] http://www.joda.org/joda-time/upgradeto294.html
>
> Julian Hyde wrote:
>
> With
> https://issues.apache.org/jira/browse/CALCITE-1458<https://issues.apache.org/jira/browse/CALCITE-1458>
>
> I think we need an avatica-1.9 fairly soon. Say, first RC on Wednesday
> (he says, pulling a date out of the air).
>
> I volunteer to be release manager (unless someone would *love* to be
> RM).
>
> What do you all think?
>
> Are there any dependencies we should upgrade? Here’s the full list:
>
> <airlift-tpch.version>0.1</airlift-tpch.version>
> <avatica.version>1.8.0</avatica.version>
> <build-helper-maven-plugin.version>1.9</build-helper-maven-plugin.version>
>
>
> <cassandra-driver-core.version>3.0.0</cassandra-driver-core.version>
> <checksum-maven-plugin.version>1.2</checksum-maven-plugin.version>
> <commons-dbcp.version>1.4</commons-dbcp.version>
> <commons-lang3.version>3.2</commons-lang3.version>
> <commons-logging.version>1.1.3</commons-logging.version>
> <eigenbase-properties.version>1.1.5</eigenbase-properties.version>
> <elasticsearch-java-driver.version>2.3.2</elasticsearch-java-driver.version>
>
>
> <findbugs.version>1.3.9</findbugs.version>
> <fmpp-maven-plugin.version>1.0</fmpp-maven-plugin.version>
> <foodmart-data-hsqldb.version>0.3</foodmart-data-hsqldb.version>
> <foodmart-queries.version>0.4.1</foodmart-queries.version>
> <freemarker.version>2.3.19</freemarker.version>
> <git-commit-id-plugin.version>2.1.9</git-commit-id-plugin.version>
> <!-- We support (and test against) Guava versions between
> 14.0.1 (Hive) and 19.0 (most recent).
> Override with your preferred version and it should work. -->
> <guava.version>18.0</guava.version>
> <joda.version>2.8.1</joda.version>
> <h2.version>1.4.185</h2.version>
> <hadoop.version>2.6.0</hadoop.version>
> <hamcrest.version>1.3</hamcrest.version>
> <hppc.version>0.7.1</hppc.version>
> <hsqldb.version>2.3.1</hsqldb.version>
> <httpclient.version>4.5.2</httpclient.version>
> <httpcore.version>4.4.4</httpcore.version>
> <hydromatic-resource.version>0.5.1</hydromatic-resource.version>
> <hydromatic-toolbox.version>0.3</hydromatic-toolbox.version>
> <hydromatic-tpcds.version>0.4</hydromatic-tpcds.version>
> <jackson.version>2.6.3</jackson.version>
> <janino.version>2.7.6</janino.version>
> <java-diff.version>1.1</java-diff.version>
> <javacc-maven-plugin.version>2.4</javacc-maven-plugin.version>
> <jcip-annotations.version>1.0-1</jcip-annotations.version>
> <jetty.version>9.2.15.v20160210</jetty.version>
> <jmh.version>1.11.2</jmh.version>
> <junit.version>4.12</junit.version>
> <maven-checkstyle-plugin.version>2.12.1</maven-checkstyle-plugin.version>
>
> <maven-dependency-plugin.version>2.10</maven-dependency-plugin.version>
> <maven-failsafe-plugin.version>2.7.2</maven-failsafe-plugin.version>
> <maven-scm-provider.version>1.9.1</maven-scm-provider.version>
> <maven-shade-plugin.version>2.1</maven-shade-plugin.version>
> <maven-source-plugin.version>2.4</maven-source-plugin.version>
> <mockito-all.version>1.10.19</mockito-all.version>
> <mongo-java-driver.version>2.12.3</mongo-java-driver.version>
> <mysql-driver.version>5.1.20</mysql-driver.version>
> <opencsv.version>2.3</opencsv.version>
> <oracle-jdbc6-driver.version>11.2.0.2.0</oracle-jdbc6-driver.version>
> <pentaho-aggdesigner.version>5.1.5-jhyde</pentaho-aggdesigner.version>
> <postgresql.version>9.3-1102-jdbc3</postgresql.version>
> <protobuf.version>3.0.0-beta-1</protobuf.version>
> <quidem.version>0.7</quidem.version>
> <scala.version>2.10.3</scala.version>
> <scott-data-hsqldb.version>0.1</scott-data-hsqldb.version>
> <servlet.version>3.0.1</servlet.version>
> <slf4j.version>1.7.13</slf4j.version>
> <spark.version>1.6.1</spark.version>
> <sqlline.version>1.1.9</sqlline.version>
> <xalan.version>2.7.1</xalan.version>
> <xerces.version>2.9.1</xerces.version>
>
>
>
> Julian
>
>
>
>
> On Oct 11, 2016, at 8:06 PM, Josh Elser<jo...@gmail.com> wrote:
>
> I'd like to finish up two issues:
>
> https://issues.apache.org/jira/browse/CALCITE-1050 ARRAY support. I
> think this one is close. I need to write more tests. I am aiming to
> commit this week.
>
> https://issues.apache.org/jira/browse/CALCITE-1355 Protobuf-java
> upgrade. Since there is a stable release, we should get on to one of
> those instead of the alpha/beta we presently have.
>
> There are few others in the pipeline that I need to revisit, but I
> don't think they should block avatica-1.9
>
> Julian Hyde wrote:
>
> Over 20 commits and 4 months since the last Avatica release. Is it
> about time we had another?
>
> Does anyone have any time constraints (must be done before X; or
> must be done after Y; or please wait until I’ve had chance to fix
> bugs Z1 and Z2)?
>
> See the tracking JIRA case,
> https://issues.apache.org/jira/browse/CALCITE-1354<https://issues.apache.org/jira/browse/CALCITE-1354>,
>
> and the corresponding Calcite issue
> https://issues.apache.org/jira/browse/CALCITE-1270<https://issues.apache.org/jira/browse/CALCITE-1270>.
>
>
>
> Julian
>
>
>
>
>
RE: window questions
Posted by Radu Tudoran <ra...@huawei.com>.
Hi,
I tried to change the type of the field to TIMESTAMP as you suggested. Nevertheless, I get a similar error. It seems that when validating the expression ("INTERVAL '1' HOUR") this gets converted in the SqlWindow class in the validateFrameBoundary() into a INTERVAL_DAY_TIME and it seems that this is not supported. It is a bit surprising that it is not converted to TIMESTAMP. I guess this is part of the error?
Any thoughts to work around?
Best regards,
-----Original Message-----
From: Julian Hyde [mailto:jhyde@apache.org]
Sent: Monday, October 24, 2016 5:55 PM
To: dev@calcite.apache.org
Subject: Re: window questions
Usually people use a column of type TIMESTAMP.
I guess TIME makes sense, if you know your stream will stop before midnight. If you really want to use TIME, please log a JIRA case for it. But things will work more smoothly if you convert your column to TIMESTAMP.
On Mon, Oct 24, 2016 at 7:16 AM, Radu Tudoran <ra...@huawei.com> wrote:
> Hi,
>
> I am trying to parse a simple query over a window. Basically the query follows the examples on the website of using the "OVER" clause. Nevertheless I have 2 questions about this:
>
>
> 1) if the "time_event" field over which I want to create the window is of type TIME, I get an error when parsing the query (see below) that the RANGE clause is not acceptable. How is this the case as most of the example on the website are like this ?
>
>
> The query example:
> SELECT STREAM user, SUM(value) OVER (ORDER BY time_event RANGE
> INTERVAL '1' HOUR PRECEDING) AS recent_sum FROM data
>
> Exception in thread "main" 16:01:38,146 ERROR org.apache.calcite.runtime.CalciteException - org.apache.calcite.runtime.CalciteContextException: From line 1, column 85 to line 1, column 101: Data type of ORDER BY prohibits use of RANGE clause
> org.apache.calcite.tools.ValidationException:
> org.apache.calcite.runtime.CalciteContextException: From line 1,
> column 85 to line 1, column 101: Data type of ORDER BY prohibits use
> of RANGE clause
>
>
> 2) if I change the type of the field to do the ordering in type long and write the same query and replace " RANGE INTERVAL '1' HOUR PRECEDING " with "RANGE 3600 PRECEDING " - then I get the query parsed and the logical graph looks like the one below. What is surprising is that there is not LogicalWindow. I do not understand the logic of the parsing if the inner part of "OVER" is not converted to window...then how can it be possible to create a rule to map this over some window implementation?
>
> LogicalDelta
> LogicalProject(user=[$3], recent_sum=[CASE(>(COUNT($11) OVER (ORDER BY $10 RANGE BETWEEN 3600 PRECEDING AND CURRENT ROW), 0), CAST($SUM0($11) OVER (ORDER BY $10 RANGE BETWEEN 3600 PRECEDING AND CURRENT ROW)):DOUBLE, null)])
> LogicalTableScan(table=[[data]])
Re: window questions
Posted by Julian Hyde <jh...@apache.org>.
Usually people use a column of type TIMESTAMP.
I guess TIME makes sense, if you know your stream will stop before
midnight. If you really want to use TIME, please log a JIRA case for
it. But things will work more smoothly if you convert your column to
TIMESTAMP.
On Mon, Oct 24, 2016 at 7:16 AM, Radu Tudoran <ra...@huawei.com> wrote:
> Hi,
>
> I am trying to parse a simple query over a window. Basically the query follows the examples on the website of using the "OVER" clause. Nevertheless I have 2 questions about this:
>
>
> 1) if the "time_event" field over which I want to create the window is of type TIME, I get an error when parsing the query (see below) that the RANGE clause is not acceptable. How is this the case as most of the example on the website are like this ?
>
>
> The query example:
> SELECT STREAM user, SUM(value) OVER (ORDER BY time_event RANGE INTERVAL '1' HOUR PRECEDING) AS recent_sum FROM data
>
> Exception in thread "main" 16:01:38,146 ERROR org.apache.calcite.runtime.CalciteException - org.apache.calcite.runtime.CalciteContextException: From line 1, column 85 to line 1, column 101: Data type of ORDER BY prohibits use of RANGE clause
> org.apache.calcite.tools.ValidationException: org.apache.calcite.runtime.CalciteContextException: From line 1, column 85 to line 1, column 101: Data type of ORDER BY prohibits use of RANGE clause
>
>
> 2) if I change the type of the field to do the ordering in type long and write the same query and replace " RANGE INTERVAL '1' HOUR PRECEDING " with "RANGE 3600 PRECEDING " - then I get the query parsed and the logical graph looks like the one below. What is surprising is that there is not LogicalWindow. I do not understand the logic of the parsing if the inner part of "OVER" is not converted to window...then how can it be possible to create a rule to map this over some window implementation?
>
> LogicalDelta
> LogicalProject(user=[$3], recent_sum=[CASE(>(COUNT($11) OVER (ORDER BY $10 RANGE BETWEEN 3600 PRECEDING AND CURRENT ROW), 0), CAST($SUM0($11) OVER (ORDER BY $10 RANGE BETWEEN 3600 PRECEDING AND CURRENT ROW)):DOUBLE, null)])
> LogicalTableScan(table=[[data]])
window questions
Posted by Radu Tudoran <ra...@huawei.com>.
Hi,
I am trying to parse a simple query over a window. Basically the query follows the examples on the website of using the "OVER" clause. Nevertheless I have 2 questions about this:
1) if the "time_event" field over which I want to create the window is of type TIME, I get an error when parsing the query (see below) that the RANGE clause is not acceptable. How is this the case as most of the example on the website are like this ?
The query example:
SELECT STREAM user, SUM(value) OVER (ORDER BY time_event RANGE INTERVAL '1' HOUR PRECEDING) AS recent_sum FROM data
Exception in thread "main" 16:01:38,146 ERROR org.apache.calcite.runtime.CalciteException - org.apache.calcite.runtime.CalciteContextException: From line 1, column 85 to line 1, column 101: Data type of ORDER BY prohibits use of RANGE clause
org.apache.calcite.tools.ValidationException: org.apache.calcite.runtime.CalciteContextException: From line 1, column 85 to line 1, column 101: Data type of ORDER BY prohibits use of RANGE clause
2) if I change the type of the field to do the ordering in type long and write the same query and replace " RANGE INTERVAL '1' HOUR PRECEDING " with "RANGE 3600 PRECEDING " - then I get the query parsed and the logical graph looks like the one below. What is surprising is that there is not LogicalWindow. I do not understand the logic of the parsing if the inner part of "OVER" is not converted to window...then how can it be possible to create a rule to map this over some window implementation?
LogicalDelta
LogicalProject(user=[$3], recent_sum=[CASE(>(COUNT($11) OVER (ORDER BY $10 RANGE BETWEEN 3600 PRECEDING AND CURRENT ROW), 0), CAST($SUM0($11) OVER (ORDER BY $10 RANGE BETWEEN 3600 PRECEDING AND CURRENT ROW)):DOUBLE, null)])
LogicalTableScan(table=[[data]])
Re: Towards Avatica 1.9
Posted by Julian Hyde <jh...@apache.org>.
Josh has fixed everything marked fixVersion = avatica-1.9.0. So, I think we’re good to go for an RC0 as early as tomorrow evening (~30 hours from now). Please speak up if you have something you’d like to put in.
One question: I see that https://issues.apache.org/jira/browse/CALCITE-1353 <https://issues.apache.org/jira/browse/CALCITE-1353> is slated for avatica-1.10. But is there any reason it couldn’t be done for avatica-1.9? If someone wants to fix it, please speak up (and submit a PR) ASAP.
Julian
> On Oct 23, 2016, at 1:08 PM, Josh Elser <jo...@gmail.com> wrote:
>
> One last thing: I just closed out CALCITE-1255 (already done) and moved the rest of the unresolved issues in fixVersion=avatica-1.9.0 to avatica-1.10.0.
>
> Josh Elser wrote:
>> Alright, just made a whirlwind-pass through issues:
>>
>> 2ee0e35 [CALCITE-1464] Upgrade Jetty version to 9.2.19v20160908
>> 2438d53 [CALCITE-1463] standalone-server needs to relocate dependencies
>> itself
>> 221d180 [CALCITE-1355] Upgrade to protobuf-java 3.1.0
>> 483b9f9 [CALCITE-1462] Remove Avatica pom cruft
>>
>> Let me clean up the fixVersion=avatica-1.9.0 to reflect this (and we can
>> use that to track any further action before we make this release).
>>
>> - Josh
>>
>> Josh Elser wrote:
>>> First off, thanks for volunteering, Julian!
>>>
>>> Let me get in the stable protobuf-3 patch today. I've just been ignoring
>>> this.
>>>
>>> I was hoping to get ARRAY support done, but it was trickier than I
>>> anticipated and I'm still working on it. I think I should not hold up
>>> the release more. I can finish it in 1.10.
>>>
>>> I see a few dependencies which only exist in depMgmt (hadoop and
>>> findbugs, so far). I'll clean these up now as well. [1]
>>>
>>> * Updating jetty to 9.2.19.v20160908 is probably safe/good to do.
>>> * Updating to jodatime 2.9.4 also sounds good[2]
>>>
>>> - Josh
>>>
>>> [1] https://issues.apache.org/jira/browse/CALCITE-1462
>>> [2] http://www.joda.org/joda-time/upgradeto294.html
>>>
>>> Julian Hyde wrote:
>>>> With
>>>> https://issues.apache.org/jira/browse/CALCITE-1458<https://issues.apache.org/jira/browse/CALCITE-1458>
>>>>
>>>> I think we need an avatica-1.9 fairly soon. Say, first RC on Wednesday
>>>> (he says, pulling a date out of the air).
>>>>
>>>> I volunteer to be release manager (unless someone would *love* to be
>>>> RM).
>>>>
>>>> What do you all think?
>>>>
>>>> Are there any dependencies we should upgrade? Here’s the full list:
>>>>
>>>> <airlift-tpch.version>0.1</airlift-tpch.version>
>>>> <avatica.version>1.8.0</avatica.version>
>>>> <build-helper-maven-plugin.version>1.9</build-helper-maven-plugin.version>
>>>>
>>>>
>>>> <cassandra-driver-core.version>3.0.0</cassandra-driver-core.version>
>>>> <checksum-maven-plugin.version>1.2</checksum-maven-plugin.version>
>>>> <commons-dbcp.version>1.4</commons-dbcp.version>
>>>> <commons-lang3.version>3.2</commons-lang3.version>
>>>> <commons-logging.version>1.1.3</commons-logging.version>
>>>> <eigenbase-properties.version>1.1.5</eigenbase-properties.version>
>>>> <elasticsearch-java-driver.version>2.3.2</elasticsearch-java-driver.version>
>>>>
>>>>
>>>> <findbugs.version>1.3.9</findbugs.version>
>>>> <fmpp-maven-plugin.version>1.0</fmpp-maven-plugin.version>
>>>> <foodmart-data-hsqldb.version>0.3</foodmart-data-hsqldb.version>
>>>> <foodmart-queries.version>0.4.1</foodmart-queries.version>
>>>> <freemarker.version>2.3.19</freemarker.version>
>>>> <git-commit-id-plugin.version>2.1.9</git-commit-id-plugin.version>
>>>> <!-- We support (and test against) Guava versions between
>>>> 14.0.1 (Hive) and 19.0 (most recent).
>>>> Override with your preferred version and it should work. -->
>>>> <guava.version>18.0</guava.version>
>>>> <joda.version>2.8.1</joda.version>
>>>> <h2.version>1.4.185</h2.version>
>>>> <hadoop.version>2.6.0</hadoop.version>
>>>> <hamcrest.version>1.3</hamcrest.version>
>>>> <hppc.version>0.7.1</hppc.version>
>>>> <hsqldb.version>2.3.1</hsqldb.version>
>>>> <httpclient.version>4.5.2</httpclient.version>
>>>> <httpcore.version>4.4.4</httpcore.version>
>>>> <hydromatic-resource.version>0.5.1</hydromatic-resource.version>
>>>> <hydromatic-toolbox.version>0.3</hydromatic-toolbox.version>
>>>> <hydromatic-tpcds.version>0.4</hydromatic-tpcds.version>
>>>> <jackson.version>2.6.3</jackson.version>
>>>> <janino.version>2.7.6</janino.version>
>>>> <java-diff.version>1.1</java-diff.version>
>>>> <javacc-maven-plugin.version>2.4</javacc-maven-plugin.version>
>>>> <jcip-annotations.version>1.0-1</jcip-annotations.version>
>>>> <jetty.version>9.2.15.v20160210</jetty.version>
>>>> <jmh.version>1.11.2</jmh.version>
>>>> <junit.version>4.12</junit.version>
>>>> <maven-checkstyle-plugin.version>2.12.1</maven-checkstyle-plugin.version>
>>>>
>>>> <maven-dependency-plugin.version>2.10</maven-dependency-plugin.version>
>>>> <maven-failsafe-plugin.version>2.7.2</maven-failsafe-plugin.version>
>>>> <maven-scm-provider.version>1.9.1</maven-scm-provider.version>
>>>> <maven-shade-plugin.version>2.1</maven-shade-plugin.version>
>>>> <maven-source-plugin.version>2.4</maven-source-plugin.version>
>>>> <mockito-all.version>1.10.19</mockito-all.version>
>>>> <mongo-java-driver.version>2.12.3</mongo-java-driver.version>
>>>> <mysql-driver.version>5.1.20</mysql-driver.version>
>>>> <opencsv.version>2.3</opencsv.version>
>>>> <oracle-jdbc6-driver.version>11.2.0.2.0</oracle-jdbc6-driver.version>
>>>> <pentaho-aggdesigner.version>5.1.5-jhyde</pentaho-aggdesigner.version>
>>>> <postgresql.version>9.3-1102-jdbc3</postgresql.version>
>>>> <protobuf.version>3.0.0-beta-1</protobuf.version>
>>>> <quidem.version>0.7</quidem.version>
>>>> <scala.version>2.10.3</scala.version>
>>>> <scott-data-hsqldb.version>0.1</scott-data-hsqldb.version>
>>>> <servlet.version>3.0.1</servlet.version>
>>>> <slf4j.version>1.7.13</slf4j.version>
>>>> <spark.version>1.6.1</spark.version>
>>>> <sqlline.version>1.1.9</sqlline.version>
>>>> <xalan.version>2.7.1</xalan.version>
>>>> <xerces.version>2.9.1</xerces.version>
>>>>
>>>>
>>>>
>>>> Julian
>>>>
>>>>
>>>>
>>>>
>>>>> On Oct 11, 2016, at 8:06 PM, Josh Elser<jo...@gmail.com> wrote:
>>>>>
>>>>> I'd like to finish up two issues:
>>>>>
>>>>> https://issues.apache.org/jira/browse/CALCITE-1050 ARRAY support. I
>>>>> think this one is close. I need to write more tests. I am aiming to
>>>>> commit this week.
>>>>>
>>>>> https://issues.apache.org/jira/browse/CALCITE-1355 Protobuf-java
>>>>> upgrade. Since there is a stable release, we should get on to one of
>>>>> those instead of the alpha/beta we presently have.
>>>>>
>>>>> There are few others in the pipeline that I need to revisit, but I
>>>>> don't think they should block avatica-1.9
>>>>>
>>>>> Julian Hyde wrote:
>>>>>> Over 20 commits and 4 months since the last Avatica release. Is it
>>>>>> about time we had another?
>>>>>>
>>>>>> Does anyone have any time constraints (must be done before X; or
>>>>>> must be done after Y; or please wait until I’ve had chance to fix
>>>>>> bugs Z1 and Z2)?
>>>>>>
>>>>>> See the tracking JIRA case,
>>>>>> https://issues.apache.org/jira/browse/CALCITE-1354<https://issues.apache.org/jira/browse/CALCITE-1354>,
>>>>>>
>>>>>> and the corresponding Calcite issue
>>>>>> https://issues.apache.org/jira/browse/CALCITE-1270<https://issues.apache.org/jira/browse/CALCITE-1270>.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Julian
>>>>>>
>>>>>>
>>>>
>>>>
Re: Towards Avatica 1.9
Posted by Josh Elser <jo...@gmail.com>.
One last thing: I just closed out CALCITE-1255 (already done) and moved
the rest of the unresolved issues in fixVersion=avatica-1.9.0 to
avatica-1.10.0.
Josh Elser wrote:
> Alright, just made a whirlwind-pass through issues:
>
> 2ee0e35 [CALCITE-1464] Upgrade Jetty version to 9.2.19v20160908
> 2438d53 [CALCITE-1463] standalone-server needs to relocate dependencies
> itself
> 221d180 [CALCITE-1355] Upgrade to protobuf-java 3.1.0
> 483b9f9 [CALCITE-1462] Remove Avatica pom cruft
>
> Let me clean up the fixVersion=avatica-1.9.0 to reflect this (and we can
> use that to track any further action before we make this release).
>
> - Josh
>
> Josh Elser wrote:
>> First off, thanks for volunteering, Julian!
>>
>> Let me get in the stable protobuf-3 patch today. I've just been ignoring
>> this.
>>
>> I was hoping to get ARRAY support done, but it was trickier than I
>> anticipated and I'm still working on it. I think I should not hold up
>> the release more. I can finish it in 1.10.
>>
>> I see a few dependencies which only exist in depMgmt (hadoop and
>> findbugs, so far). I'll clean these up now as well. [1]
>>
>> * Updating jetty to 9.2.19.v20160908 is probably safe/good to do.
>> * Updating to jodatime 2.9.4 also sounds good[2]
>>
>> - Josh
>>
>> [1] https://issues.apache.org/jira/browse/CALCITE-1462
>> [2] http://www.joda.org/joda-time/upgradeto294.html
>>
>> Julian Hyde wrote:
>>> With
>>> https://issues.apache.org/jira/browse/CALCITE-1458<https://issues.apache.org/jira/browse/CALCITE-1458>
>>>
>>> I think we need an avatica-1.9 fairly soon. Say, first RC on Wednesday
>>> (he says, pulling a date out of the air).
>>>
>>> I volunteer to be release manager (unless someone would *love* to be
>>> RM).
>>>
>>> What do you all think?
>>>
>>> Are there any dependencies we should upgrade? Here\u2019s the full list:
>>>
>>> <airlift-tpch.version>0.1</airlift-tpch.version>
>>> <avatica.version>1.8.0</avatica.version>
>>> <build-helper-maven-plugin.version>1.9</build-helper-maven-plugin.version>
>>>
>>>
>>> <cassandra-driver-core.version>3.0.0</cassandra-driver-core.version>
>>> <checksum-maven-plugin.version>1.2</checksum-maven-plugin.version>
>>> <commons-dbcp.version>1.4</commons-dbcp.version>
>>> <commons-lang3.version>3.2</commons-lang3.version>
>>> <commons-logging.version>1.1.3</commons-logging.version>
>>> <eigenbase-properties.version>1.1.5</eigenbase-properties.version>
>>> <elasticsearch-java-driver.version>2.3.2</elasticsearch-java-driver.version>
>>>
>>>
>>> <findbugs.version>1.3.9</findbugs.version>
>>> <fmpp-maven-plugin.version>1.0</fmpp-maven-plugin.version>
>>> <foodmart-data-hsqldb.version>0.3</foodmart-data-hsqldb.version>
>>> <foodmart-queries.version>0.4.1</foodmart-queries.version>
>>> <freemarker.version>2.3.19</freemarker.version>
>>> <git-commit-id-plugin.version>2.1.9</git-commit-id-plugin.version>
>>> <!-- We support (and test against) Guava versions between
>>> 14.0.1 (Hive) and 19.0 (most recent).
>>> Override with your preferred version and it should work. -->
>>> <guava.version>18.0</guava.version>
>>> <joda.version>2.8.1</joda.version>
>>> <h2.version>1.4.185</h2.version>
>>> <hadoop.version>2.6.0</hadoop.version>
>>> <hamcrest.version>1.3</hamcrest.version>
>>> <hppc.version>0.7.1</hppc.version>
>>> <hsqldb.version>2.3.1</hsqldb.version>
>>> <httpclient.version>4.5.2</httpclient.version>
>>> <httpcore.version>4.4.4</httpcore.version>
>>> <hydromatic-resource.version>0.5.1</hydromatic-resource.version>
>>> <hydromatic-toolbox.version>0.3</hydromatic-toolbox.version>
>>> <hydromatic-tpcds.version>0.4</hydromatic-tpcds.version>
>>> <jackson.version>2.6.3</jackson.version>
>>> <janino.version>2.7.6</janino.version>
>>> <java-diff.version>1.1</java-diff.version>
>>> <javacc-maven-plugin.version>2.4</javacc-maven-plugin.version>
>>> <jcip-annotations.version>1.0-1</jcip-annotations.version>
>>> <jetty.version>9.2.15.v20160210</jetty.version>
>>> <jmh.version>1.11.2</jmh.version>
>>> <junit.version>4.12</junit.version>
>>> <maven-checkstyle-plugin.version>2.12.1</maven-checkstyle-plugin.version>
>>>
>>> <maven-dependency-plugin.version>2.10</maven-dependency-plugin.version>
>>> <maven-failsafe-plugin.version>2.7.2</maven-failsafe-plugin.version>
>>> <maven-scm-provider.version>1.9.1</maven-scm-provider.version>
>>> <maven-shade-plugin.version>2.1</maven-shade-plugin.version>
>>> <maven-source-plugin.version>2.4</maven-source-plugin.version>
>>> <mockito-all.version>1.10.19</mockito-all.version>
>>> <mongo-java-driver.version>2.12.3</mongo-java-driver.version>
>>> <mysql-driver.version>5.1.20</mysql-driver.version>
>>> <opencsv.version>2.3</opencsv.version>
>>> <oracle-jdbc6-driver.version>11.2.0.2.0</oracle-jdbc6-driver.version>
>>> <pentaho-aggdesigner.version>5.1.5-jhyde</pentaho-aggdesigner.version>
>>> <postgresql.version>9.3-1102-jdbc3</postgresql.version>
>>> <protobuf.version>3.0.0-beta-1</protobuf.version>
>>> <quidem.version>0.7</quidem.version>
>>> <scala.version>2.10.3</scala.version>
>>> <scott-data-hsqldb.version>0.1</scott-data-hsqldb.version>
>>> <servlet.version>3.0.1</servlet.version>
>>> <slf4j.version>1.7.13</slf4j.version>
>>> <spark.version>1.6.1</spark.version>
>>> <sqlline.version>1.1.9</sqlline.version>
>>> <xalan.version>2.7.1</xalan.version>
>>> <xerces.version>2.9.1</xerces.version>
>>>
>>>
>>>
>>> Julian
>>>
>>>
>>>
>>>
>>>> On Oct 11, 2016, at 8:06 PM, Josh Elser<jo...@gmail.com> wrote:
>>>>
>>>> I'd like to finish up two issues:
>>>>
>>>> https://issues.apache.org/jira/browse/CALCITE-1050 ARRAY support. I
>>>> think this one is close. I need to write more tests. I am aiming to
>>>> commit this week.
>>>>
>>>> https://issues.apache.org/jira/browse/CALCITE-1355 Protobuf-java
>>>> upgrade. Since there is a stable release, we should get on to one of
>>>> those instead of the alpha/beta we presently have.
>>>>
>>>> There are few others in the pipeline that I need to revisit, but I
>>>> don't think they should block avatica-1.9
>>>>
>>>> Julian Hyde wrote:
>>>>> Over 20 commits and 4 months since the last Avatica release. Is it
>>>>> about time we had another?
>>>>>
>>>>> Does anyone have any time constraints (must be done before X; or
>>>>> must be done after Y; or please wait until I\u2019ve had chance to fix
>>>>> bugs Z1 and Z2)?
>>>>>
>>>>> See the tracking JIRA case,
>>>>> https://issues.apache.org/jira/browse/CALCITE-1354<https://issues.apache.org/jira/browse/CALCITE-1354>,
>>>>>
>>>>> and the corresponding Calcite issue
>>>>> https://issues.apache.org/jira/browse/CALCITE-1270<https://issues.apache.org/jira/browse/CALCITE-1270>.
>>>>>
>>>>>
>>>>>
>>>>> Julian
>>>>>
>>>>>
>>>
>>>
Re: Towards Avatica 1.9
Posted by Josh Elser <jo...@gmail.com>.
Alright, just made a whirlwind-pass through issues:
2ee0e35 [CALCITE-1464] Upgrade Jetty version to 9.2.19v20160908
2438d53 [CALCITE-1463] standalone-server needs to relocate dependencies
itself
221d180 [CALCITE-1355] Upgrade to protobuf-java 3.1.0
483b9f9 [CALCITE-1462] Remove Avatica pom cruft
Let me clean up the fixVersion=avatica-1.9.0 to reflect this (and we can
use that to track any further action before we make this release).
- Josh
Josh Elser wrote:
> First off, thanks for volunteering, Julian!
>
> Let me get in the stable protobuf-3 patch today. I've just been ignoring
> this.
>
> I was hoping to get ARRAY support done, but it was trickier than I
> anticipated and I'm still working on it. I think I should not hold up
> the release more. I can finish it in 1.10.
>
> I see a few dependencies which only exist in depMgmt (hadoop and
> findbugs, so far). I'll clean these up now as well. [1]
>
> * Updating jetty to 9.2.19.v20160908 is probably safe/good to do.
> * Updating to jodatime 2.9.4 also sounds good[2]
>
> - Josh
>
> [1] https://issues.apache.org/jira/browse/CALCITE-1462
> [2] http://www.joda.org/joda-time/upgradeto294.html
>
> Julian Hyde wrote:
>> With
>> https://issues.apache.org/jira/browse/CALCITE-1458<https://issues.apache.org/jira/browse/CALCITE-1458>
>> I think we need an avatica-1.9 fairly soon. Say, first RC on Wednesday
>> (he says, pulling a date out of the air).
>>
>> I volunteer to be release manager (unless someone would *love* to be RM).
>>
>> What do you all think?
>>
>> Are there any dependencies we should upgrade? Here\u2019s the full list:
>>
>> <airlift-tpch.version>0.1</airlift-tpch.version>
>> <avatica.version>1.8.0</avatica.version>
>> <build-helper-maven-plugin.version>1.9</build-helper-maven-plugin.version>
>>
>> <cassandra-driver-core.version>3.0.0</cassandra-driver-core.version>
>> <checksum-maven-plugin.version>1.2</checksum-maven-plugin.version>
>> <commons-dbcp.version>1.4</commons-dbcp.version>
>> <commons-lang3.version>3.2</commons-lang3.version>
>> <commons-logging.version>1.1.3</commons-logging.version>
>> <eigenbase-properties.version>1.1.5</eigenbase-properties.version>
>> <elasticsearch-java-driver.version>2.3.2</elasticsearch-java-driver.version>
>>
>> <findbugs.version>1.3.9</findbugs.version>
>> <fmpp-maven-plugin.version>1.0</fmpp-maven-plugin.version>
>> <foodmart-data-hsqldb.version>0.3</foodmart-data-hsqldb.version>
>> <foodmart-queries.version>0.4.1</foodmart-queries.version>
>> <freemarker.version>2.3.19</freemarker.version>
>> <git-commit-id-plugin.version>2.1.9</git-commit-id-plugin.version>
>> <!-- We support (and test against) Guava versions between
>> 14.0.1 (Hive) and 19.0 (most recent).
>> Override with your preferred version and it should work. -->
>> <guava.version>18.0</guava.version>
>> <joda.version>2.8.1</joda.version>
>> <h2.version>1.4.185</h2.version>
>> <hadoop.version>2.6.0</hadoop.version>
>> <hamcrest.version>1.3</hamcrest.version>
>> <hppc.version>0.7.1</hppc.version>
>> <hsqldb.version>2.3.1</hsqldb.version>
>> <httpclient.version>4.5.2</httpclient.version>
>> <httpcore.version>4.4.4</httpcore.version>
>> <hydromatic-resource.version>0.5.1</hydromatic-resource.version>
>> <hydromatic-toolbox.version>0.3</hydromatic-toolbox.version>
>> <hydromatic-tpcds.version>0.4</hydromatic-tpcds.version>
>> <jackson.version>2.6.3</jackson.version>
>> <janino.version>2.7.6</janino.version>
>> <java-diff.version>1.1</java-diff.version>
>> <javacc-maven-plugin.version>2.4</javacc-maven-plugin.version>
>> <jcip-annotations.version>1.0-1</jcip-annotations.version>
>> <jetty.version>9.2.15.v20160210</jetty.version>
>> <jmh.version>1.11.2</jmh.version>
>> <junit.version>4.12</junit.version>
>> <maven-checkstyle-plugin.version>2.12.1</maven-checkstyle-plugin.version>
>> <maven-dependency-plugin.version>2.10</maven-dependency-plugin.version>
>> <maven-failsafe-plugin.version>2.7.2</maven-failsafe-plugin.version>
>> <maven-scm-provider.version>1.9.1</maven-scm-provider.version>
>> <maven-shade-plugin.version>2.1</maven-shade-plugin.version>
>> <maven-source-plugin.version>2.4</maven-source-plugin.version>
>> <mockito-all.version>1.10.19</mockito-all.version>
>> <mongo-java-driver.version>2.12.3</mongo-java-driver.version>
>> <mysql-driver.version>5.1.20</mysql-driver.version>
>> <opencsv.version>2.3</opencsv.version>
>> <oracle-jdbc6-driver.version>11.2.0.2.0</oracle-jdbc6-driver.version>
>> <pentaho-aggdesigner.version>5.1.5-jhyde</pentaho-aggdesigner.version>
>> <postgresql.version>9.3-1102-jdbc3</postgresql.version>
>> <protobuf.version>3.0.0-beta-1</protobuf.version>
>> <quidem.version>0.7</quidem.version>
>> <scala.version>2.10.3</scala.version>
>> <scott-data-hsqldb.version>0.1</scott-data-hsqldb.version>
>> <servlet.version>3.0.1</servlet.version>
>> <slf4j.version>1.7.13</slf4j.version>
>> <spark.version>1.6.1</spark.version>
>> <sqlline.version>1.1.9</sqlline.version>
>> <xalan.version>2.7.1</xalan.version>
>> <xerces.version>2.9.1</xerces.version>
>>
>>
>>
>> Julian
>>
>>
>>
>>
>>> On Oct 11, 2016, at 8:06 PM, Josh Elser<jo...@gmail.com> wrote:
>>>
>>> I'd like to finish up two issues:
>>>
>>> https://issues.apache.org/jira/browse/CALCITE-1050 ARRAY support. I
>>> think this one is close. I need to write more tests. I am aiming to
>>> commit this week.
>>>
>>> https://issues.apache.org/jira/browse/CALCITE-1355 Protobuf-java
>>> upgrade. Since there is a stable release, we should get on to one of
>>> those instead of the alpha/beta we presently have.
>>>
>>> There are few others in the pipeline that I need to revisit, but I
>>> don't think they should block avatica-1.9
>>>
>>> Julian Hyde wrote:
>>>> Over 20 commits and 4 months since the last Avatica release. Is it
>>>> about time we had another?
>>>>
>>>> Does anyone have any time constraints (must be done before X; or
>>>> must be done after Y; or please wait until I\u2019ve had chance to fix
>>>> bugs Z1 and Z2)?
>>>>
>>>> See the tracking JIRA case,
>>>> https://issues.apache.org/jira/browse/CALCITE-1354<https://issues.apache.org/jira/browse/CALCITE-1354>,
>>>> and the corresponding Calcite issue
>>>> https://issues.apache.org/jira/browse/CALCITE-1270<https://issues.apache.org/jira/browse/CALCITE-1270>.
>>>>
>>>>
>>>> Julian
>>>>
>>>>
>>
>>
Re: Towards Avatica 1.9
Posted by Josh Elser <jo...@gmail.com>.
First off, thanks for volunteering, Julian!
Let me get in the stable protobuf-3 patch today. I've just been ignoring
this.
I was hoping to get ARRAY support done, but it was trickier than I
anticipated and I'm still working on it. I think I should not hold up
the release more. I can finish it in 1.10.
I see a few dependencies which only exist in depMgmt (hadoop and
findbugs, so far). I'll clean these up now as well. [1]
* Updating jetty to 9.2.19.v20160908 is probably safe/good to do.
* Updating to jodatime 2.9.4 also sounds good[2]
- Josh
[1] https://issues.apache.org/jira/browse/CALCITE-1462
[2] http://www.joda.org/joda-time/upgradeto294.html
Julian Hyde wrote:
> With https://issues.apache.org/jira/browse/CALCITE-1458<https://issues.apache.org/jira/browse/CALCITE-1458> I think we need an avatica-1.9 fairly soon. Say, first RC on Wednesday (he says, pulling a date out of the air).
>
> I volunteer to be release manager (unless someone would *love* to be RM).
>
> What do you all think?
>
> Are there any dependencies we should upgrade? Here\u2019s the full list:
>
> <airlift-tpch.version>0.1</airlift-tpch.version>
> <avatica.version>1.8.0</avatica.version>
> <build-helper-maven-plugin.version>1.9</build-helper-maven-plugin.version>
> <cassandra-driver-core.version>3.0.0</cassandra-driver-core.version>
> <checksum-maven-plugin.version>1.2</checksum-maven-plugin.version>
> <commons-dbcp.version>1.4</commons-dbcp.version>
> <commons-lang3.version>3.2</commons-lang3.version>
> <commons-logging.version>1.1.3</commons-logging.version>
> <eigenbase-properties.version>1.1.5</eigenbase-properties.version>
> <elasticsearch-java-driver.version>2.3.2</elasticsearch-java-driver.version>
> <findbugs.version>1.3.9</findbugs.version>
> <fmpp-maven-plugin.version>1.0</fmpp-maven-plugin.version>
> <foodmart-data-hsqldb.version>0.3</foodmart-data-hsqldb.version>
> <foodmart-queries.version>0.4.1</foodmart-queries.version>
> <freemarker.version>2.3.19</freemarker.version>
> <git-commit-id-plugin.version>2.1.9</git-commit-id-plugin.version>
> <!-- We support (and test against) Guava versions between
> 14.0.1 (Hive) and 19.0 (most recent).
> Override with your preferred version and it should work. -->
> <guava.version>18.0</guava.version>
> <joda.version>2.8.1</joda.version>
> <h2.version>1.4.185</h2.version>
> <hadoop.version>2.6.0</hadoop.version>
> <hamcrest.version>1.3</hamcrest.version>
> <hppc.version>0.7.1</hppc.version>
> <hsqldb.version>2.3.1</hsqldb.version>
> <httpclient.version>4.5.2</httpclient.version>
> <httpcore.version>4.4.4</httpcore.version>
> <hydromatic-resource.version>0.5.1</hydromatic-resource.version>
> <hydromatic-toolbox.version>0.3</hydromatic-toolbox.version>
> <hydromatic-tpcds.version>0.4</hydromatic-tpcds.version>
> <jackson.version>2.6.3</jackson.version>
> <janino.version>2.7.6</janino.version>
> <java-diff.version>1.1</java-diff.version>
> <javacc-maven-plugin.version>2.4</javacc-maven-plugin.version>
> <jcip-annotations.version>1.0-1</jcip-annotations.version>
> <jetty.version>9.2.15.v20160210</jetty.version>
> <jmh.version>1.11.2</jmh.version>
> <junit.version>4.12</junit.version>
> <maven-checkstyle-plugin.version>2.12.1</maven-checkstyle-plugin.version>
> <maven-dependency-plugin.version>2.10</maven-dependency-plugin.version>
> <maven-failsafe-plugin.version>2.7.2</maven-failsafe-plugin.version>
> <maven-scm-provider.version>1.9.1</maven-scm-provider.version>
> <maven-shade-plugin.version>2.1</maven-shade-plugin.version>
> <maven-source-plugin.version>2.4</maven-source-plugin.version>
> <mockito-all.version>1.10.19</mockito-all.version>
> <mongo-java-driver.version>2.12.3</mongo-java-driver.version>
> <mysql-driver.version>5.1.20</mysql-driver.version>
> <opencsv.version>2.3</opencsv.version>
> <oracle-jdbc6-driver.version>11.2.0.2.0</oracle-jdbc6-driver.version>
> <pentaho-aggdesigner.version>5.1.5-jhyde</pentaho-aggdesigner.version>
> <postgresql.version>9.3-1102-jdbc3</postgresql.version>
> <protobuf.version>3.0.0-beta-1</protobuf.version>
> <quidem.version>0.7</quidem.version>
> <scala.version>2.10.3</scala.version>
> <scott-data-hsqldb.version>0.1</scott-data-hsqldb.version>
> <servlet.version>3.0.1</servlet.version>
> <slf4j.version>1.7.13</slf4j.version>
> <spark.version>1.6.1</spark.version>
> <sqlline.version>1.1.9</sqlline.version>
> <xalan.version>2.7.1</xalan.version>
> <xerces.version>2.9.1</xerces.version>
>
>
>
> Julian
>
>
>
>
>> On Oct 11, 2016, at 8:06 PM, Josh Elser<jo...@gmail.com> wrote:
>>
>> I'd like to finish up two issues:
>>
>> https://issues.apache.org/jira/browse/CALCITE-1050 ARRAY support. I think this one is close. I need to write more tests. I am aiming to commit this week.
>>
>> https://issues.apache.org/jira/browse/CALCITE-1355 Protobuf-java upgrade. Since there is a stable release, we should get on to one of those instead of the alpha/beta we presently have.
>>
>> There are few others in the pipeline that I need to revisit, but I don't think they should block avatica-1.9
>>
>> Julian Hyde wrote:
>>> Over 20 commits and 4 months since the last Avatica release. Is it about time we had another?
>>>
>>> Does anyone have any time constraints (must be done before X; or must be done after Y; or please wait until I\u2019ve had chance to fix bugs Z1 and Z2)?
>>>
>>> See the tracking JIRA case, https://issues.apache.org/jira/browse/CALCITE-1354<https://issues.apache.org/jira/browse/CALCITE-1354>, and the corresponding Calcite issue https://issues.apache.org/jira/browse/CALCITE-1270<https://issues.apache.org/jira/browse/CALCITE-1270>.
>>>
>>> Julian
>>>
>>>
>
>
Re: Towards Avatica 1.9
Posted by Julian Hyde <jh...@apache.org>.
With https://issues.apache.org/jira/browse/CALCITE-1458 <https://issues.apache.org/jira/browse/CALCITE-1458> I think we need an avatica-1.9 fairly soon. Say, first RC on Wednesday (he says, pulling a date out of the air).
I volunteer to be release manager (unless someone would *love* to be RM).
What do you all think?
Are there any dependencies we should upgrade? Here’s the full list:
<airlift-tpch.version>0.1</airlift-tpch.version>
<avatica.version>1.8.0</avatica.version>
<build-helper-maven-plugin.version>1.9</build-helper-maven-plugin.version>
<cassandra-driver-core.version>3.0.0</cassandra-driver-core.version>
<checksum-maven-plugin.version>1.2</checksum-maven-plugin.version>
<commons-dbcp.version>1.4</commons-dbcp.version>
<commons-lang3.version>3.2</commons-lang3.version>
<commons-logging.version>1.1.3</commons-logging.version>
<eigenbase-properties.version>1.1.5</eigenbase-properties.version>
<elasticsearch-java-driver.version>2.3.2</elasticsearch-java-driver.version>
<findbugs.version>1.3.9</findbugs.version>
<fmpp-maven-plugin.version>1.0</fmpp-maven-plugin.version>
<foodmart-data-hsqldb.version>0.3</foodmart-data-hsqldb.version>
<foodmart-queries.version>0.4.1</foodmart-queries.version>
<freemarker.version>2.3.19</freemarker.version>
<git-commit-id-plugin.version>2.1.9</git-commit-id-plugin.version>
<!-- We support (and test against) Guava versions between
14.0.1 (Hive) and 19.0 (most recent).
Override with your preferred version and it should work. -->
<guava.version>18.0</guava.version>
<joda.version>2.8.1</joda.version>
<h2.version>1.4.185</h2.version>
<hadoop.version>2.6.0</hadoop.version>
<hamcrest.version>1.3</hamcrest.version>
<hppc.version>0.7.1</hppc.version>
<hsqldb.version>2.3.1</hsqldb.version>
<httpclient.version>4.5.2</httpclient.version>
<httpcore.version>4.4.4</httpcore.version>
<hydromatic-resource.version>0.5.1</hydromatic-resource.version>
<hydromatic-toolbox.version>0.3</hydromatic-toolbox.version>
<hydromatic-tpcds.version>0.4</hydromatic-tpcds.version>
<jackson.version>2.6.3</jackson.version>
<janino.version>2.7.6</janino.version>
<java-diff.version>1.1</java-diff.version>
<javacc-maven-plugin.version>2.4</javacc-maven-plugin.version>
<jcip-annotations.version>1.0-1</jcip-annotations.version>
<jetty.version>9.2.15.v20160210</jetty.version>
<jmh.version>1.11.2</jmh.version>
<junit.version>4.12</junit.version>
<maven-checkstyle-plugin.version>2.12.1</maven-checkstyle-plugin.version>
<maven-dependency-plugin.version>2.10</maven-dependency-plugin.version>
<maven-failsafe-plugin.version>2.7.2</maven-failsafe-plugin.version>
<maven-scm-provider.version>1.9.1</maven-scm-provider.version>
<maven-shade-plugin.version>2.1</maven-shade-plugin.version>
<maven-source-plugin.version>2.4</maven-source-plugin.version>
<mockito-all.version>1.10.19</mockito-all.version>
<mongo-java-driver.version>2.12.3</mongo-java-driver.version>
<mysql-driver.version>5.1.20</mysql-driver.version>
<opencsv.version>2.3</opencsv.version>
<oracle-jdbc6-driver.version>11.2.0.2.0</oracle-jdbc6-driver.version>
<pentaho-aggdesigner.version>5.1.5-jhyde</pentaho-aggdesigner.version>
<postgresql.version>9.3-1102-jdbc3</postgresql.version>
<protobuf.version>3.0.0-beta-1</protobuf.version>
<quidem.version>0.7</quidem.version>
<scala.version>2.10.3</scala.version>
<scott-data-hsqldb.version>0.1</scott-data-hsqldb.version>
<servlet.version>3.0.1</servlet.version>
<slf4j.version>1.7.13</slf4j.version>
<spark.version>1.6.1</spark.version>
<sqlline.version>1.1.9</sqlline.version>
<xalan.version>2.7.1</xalan.version>
<xerces.version>2.9.1</xerces.version>
Julian
> On Oct 11, 2016, at 8:06 PM, Josh Elser <jo...@gmail.com> wrote:
>
> I'd like to finish up two issues:
>
> https://issues.apache.org/jira/browse/CALCITE-1050 ARRAY support. I think this one is close. I need to write more tests. I am aiming to commit this week.
>
> https://issues.apache.org/jira/browse/CALCITE-1355 Protobuf-java upgrade. Since there is a stable release, we should get on to one of those instead of the alpha/beta we presently have.
>
> There are few others in the pipeline that I need to revisit, but I don't think they should block avatica-1.9
>
> Julian Hyde wrote:
>> Over 20 commits and 4 months since the last Avatica release. Is it about time we had another?
>>
>> Does anyone have any time constraints (must be done before X; or must be done after Y; or please wait until I’ve had chance to fix bugs Z1 and Z2)?
>>
>> See the tracking JIRA case, https://issues.apache.org/jira/browse/CALCITE-1354<https://issues.apache.org/jira/browse/CALCITE-1354>, and the corresponding Calcite issue https://issues.apache.org/jira/browse/CALCITE-1270<https://issues.apache.org/jira/browse/CALCITE-1270>.
>>
>> Julian
>>
>>
Re: Towards Avatica 1.9
Posted by Josh Elser <jo...@gmail.com>.
I'd like to finish up two issues:
https://issues.apache.org/jira/browse/CALCITE-1050 ARRAY support. I
think this one is close. I need to write more tests. I am aiming to
commit this week.
https://issues.apache.org/jira/browse/CALCITE-1355 Protobuf-java
upgrade. Since there is a stable release, we should get on to one of
those instead of the alpha/beta we presently have.
There are few others in the pipeline that I need to revisit, but I don't
think they should block avatica-1.9
Julian Hyde wrote:
> Over 20 commits and 4 months since the last Avatica release. Is it about time we had another?
>
> Does anyone have any time constraints (must be done before X; or must be done after Y; or please wait until I\u2019ve had chance to fix bugs Z1 and Z2)?
>
> See the tracking JIRA case, https://issues.apache.org/jira/browse/CALCITE-1354<https://issues.apache.org/jira/browse/CALCITE-1354>, and the corresponding Calcite issue https://issues.apache.org/jira/browse/CALCITE-1270<https://issues.apache.org/jira/browse/CALCITE-1270>.
>
> Julian
>
>