Re: DISTINCT ON clause

ANY_VALUE sounds good. There could instead/in addition be SAME_VALUE (which is similar, but asserts that all values are the same). > On Apr 4, 2018, at 3:33 PM, Aman Sinha wrote: > > Would the Calcite community be ok with having a new function called > 'ANY_VALUE()' which

Re: calcite git commit: Add Apache events image

I vote to remove it. But remember how the section looks, and the code to do it, and we can easily add it back in future for limited-time “promotions”. Julian > On Apr 9, 2018, at 10:16 AM, Michael Mior wrote: > > Good point. Do you suggest we update to 19th or just

Calcite-Master - Build # 245 - Still Failing

The Apache Jenkins build system has built Calcite-Master (build #245) Status: Still Failing Check console output at https://builds.apache.org/job/Calcite-Master/245/ to view the results.

JDK 8 syntax

Has anyone had any luck using JDK 8 syntax (e.g. “->” for lambdas) in Calcite? In core/pom.xml I changed source=1.7 target=1.7 to source=8 target=8 and it allowed the syntax but it seemed to break any tests that relied on janino. Related: https://issues.apache.org/jira/browse/CALCITE-2027

Re: calcite git commit: Add Apache events image

Good point. Do you suggest we update to 19th or just remove entirely? -- Michael Mior mm...@apache.org On Mon, Apr 9, 2018, 13:07 Julian Hyde, wrote: > Thanks for doing this, Michael. > > We should also remove the “Apache is celebrating its 18th anniversary” > section at the

Re: DISTINCT ON clause

The concept of a LIMIT per key as Julian suggested would actually be really useful for a couple of reasons: 1. It's a very common query in olap scenarios, and it would be nice to have a simpler way than window functions to express it in sql (and for us through the RelBuilder) 2. Not all databases

Re: calcite git commit: Add Apache events image

Thanks for doing this, Michael. We should also remove the “Apache is celebrating its 18th anniversary” section at the bottom of the page. Apache just celebrated its 19th anniversary. Julian > On Apr 9, 2018, at 8:33 AM, mm...@apache.org wrote: > > Repository: calcite > Updated Branches: >

[jira] [Created] (CALCITE-2245) Support for Postgres jsonb datatype

Ashirvad Gupta created CALCITE-2245: --- Summary: Support for Postgres jsonb datatype Key: CALCITE-2245 URL: https://issues.apache.org/jira/browse/CALCITE-2245 Project: Calcite Issue Type:

[jira] [Created] (CALCITE-2244) CTEs in DML: "WITH ... INSERT / UPDATE / DELETE / MERGE"

Julian Hyde created CALCITE-2244: Summary: CTEs in DML: "WITH ... INSERT / UPDATE / DELETE / MERGE" Key: CALCITE-2244 URL: https://issues.apache.org/jira/browse/CALCITE-2244 Project: Calcite

Towards Avatica-Go release ?.?

We have to make a release of Avatica Go soon (like, within the next month). As I’ve said previously, a tar-ball of the source (plus checksums/signatures and release notes) is sufficient. But we are an Apache project, and projects must make releases. Can someone please volunteer to be release

Re: calcite git commit: [CALCITE-2216] Improve extensibility of AggregateReduceFunctionsRule (Fabian Hueske)

Thanks Shuyi for taking on some of the load of reviewing/committing. Much appreciated! > On Apr 9, 2018, at 11:10 AM, shuyic...@apache.org wrote: > > Repository: calcite > Updated Branches: > refs/heads/master 5331bd2f8 -> 06080ff07 > > > [CALCITE-2216] Improve extensibility of

Re: JDK 8 syntax

Don’t have the error stack, but janino could not compile generated code because it said an “unwrap” method did not exist. There were no lambdas. I think perhaps that version of janino could not fully understand the Calcite class files. To reproduce, change 2 lines in core/pom.xml and run “mvn

Re: JDK 8 syntax

Il lun 9 apr 2018, 21:37 Julian Hyde ha scritto: > Don’t have the error stack, but janino could not compile generated code > because it said an “unwrap” method did not exist. > > There were no lambdas. I think perhaps that version of janino could not > fully understand the

Re: JDK 8 syntax

Il lun 9 apr 2018, 19:05 Julian Hyde ha scritto: > Has anyone had any luck using JDK 8 syntax (e.g. “->” for lambdas) in > Calcite? > > In core/pom.xml I changed source=1.7 target=1.7 to source=8 target=8 and > it allowed the syntax but it seemed to break any tests that relied

Re: JDK 8 syntax

Not sure if this is related, but it seems like Janino doesn't support Java8 lambdas under "Limitations" in http://janino-compiler.github.io/janino/ On Mon, Apr 9, 2018 at 12:54 PM Julian Hyde wrote: > I didn’t try. We’re on janino 2.7.6. The 2.x line only goes up to 2.7.8. >

Re: JDK 8 syntax

Awesome! On Mon, Apr 9, 2018 at 1:29 PM Enrico Olivelli wrote: > Il lun 9 apr 2018, 22:20 Cade Markegard ha > scritto: > > > Not sure if this is related, but it seems like Janino doesn't support > Java8 > > lambdas under "Limitations" in

Re: Use of CalciteSchema across Calcite

The policy that CalciteSchema should be private to Calcite hasn’t changed (it is a public interface only because… Java). It has never been private to the JDBC adapter. (The JDBC adapter readers from JDBC sources and is in org.apache.calcite.adapter.jdbc, whereas CalciteSchema is in

Re: Towards Avatica-Go release ?.?

I am wrapping up some things today and plan to test Avatica Go against the latest version of Avatica. I think we'll be able to make a release by the end of the week. I am happy to be the release manager for this one. The latest version of Avatica is 2.3.1 under Boostport/avatica, I think we

-jdk10 for Calcite on Jenkins (Re: Calcite-Master - Build # 246 - Still Failing)

I've disabled JDK10 builds for Calcite as these appear to be broken around maven-surefire-plugin. https://builds.apache.org/job/Calcite-Master/247/jdk=JDK%2010%20(latest),label_exp=ubuntu&&!cloud-slave&&!H31/console Trying to get the matrix job up and healthy again for Calcite. On 4/9/18 2:18

Calcite-Master - Build # 247 - Still Failing

The Apache Jenkins build system has built Calcite-Master (build #247) Status: Still Failing Check console output at https://builds.apache.org/job/Calcite-Master/247/ to view the results.

Re: Towards Avatica-Go release ?.?

Thanks, Francis. The most important step is to come up with a release vote email with the same items as [1]: release notes, git commit, artifacts to be voted on in dist.apache.org/repos/dist/dev , md5 and sha256 hashes. (The staged maven repository does

Re: -jdk10 for Calcite on Jenkins (Re: Calcite-Master - Build # 246 - Still Failing)

https://issues.apache.org/jira/browse/CALCITE-2237 I had created CALCITE-2237 to address this. There is a PR waiting for review :) Kevin Risden On Mon, Apr 9, 2018 at 5:28 PM, Josh Elser wrote: > I've disabled JDK10 builds for Calcite as these appear to be broken around

Re: -jdk10 for Calcite on Jenkins (Re: Calcite-Master - Build # 246 - Still Failing)

Also https://issues.apache.org/jira/browse/CALCITE-2063 has some linked tickets for Pig/Spark to try to get JDK 10 to completely pass. Kevin Risden On Mon, Apr 9, 2018 at 6:38 PM, Kevin Risden wrote: > https://issues.apache.org/jira/browse/CALCITE-2237 > > I had created

Re: Towards Avatica-Go release ?.?

Thanks Francis for taking this on! -- Michael Mior mm...@apache.org 2018-04-09 18:26 GMT-04:00 F21 : > I am wrapping up some things today and plan to test Avatica Go against the > latest version of Avatica. > > I think we'll be able to make a release by the end of the

Re: calcite git commit: Add Apache events image

How about just removing the sentence about the anniversary and keeping everything else as-is? -- Michael Mior mm...@apache.org 2018-04-09 13:21 GMT-04:00 Julian Hyde : > I vote to remove it. > > But remember how the section looks, and the code to do it, and we can > easily add

Re: JDK 8 syntax

I didn’t try. We’re on janino 2.7.6. The 2.x line only goes up to 2.7.8. I’m not eager to try upgrading to 3.x (latest release is 3.0.8) especially as they don’t explicitly mention fixing a JDK 8 issue. http://janino-compiler.github.io/janino/changelog.html

Calcite-Master - Build # 246 - Still Failing

The Apache Jenkins build system has built Calcite-Master (build #246) Status: Still Failing Check console output at https://builds.apache.org/job/Calcite-Master/246/ to view the results.

Calcite-Master - Build # 244 - Still Failing

The Apache Jenkins build system has built Calcite-Master (build #244) Status: Still Failing Check console output at https://builds.apache.org/job/Calcite-Master/244/ to view the results.

two avatica bugs

To whom concerns: when i use the avatica driver, found two bugs: one bug in protobuf serialization mode: 1.for org.apache.calcite.avatica.driver.remote.Service$CatalogsRequest,the response is org.apache.calcite.avatica.remote.Service$ResultSetResponse, and in Service$ResultSetResponse,

Re: Supporting named row construction in Calcite SQL

For what it’s worth, ROW is standard SQL. If it does what you need, we should use it. Reading your case quickly, I perceived that you needed a concise way to assign field names, and AS STRUCT seemed to do that. But staying within the standard is always preferred. BigQuery isn’t always good at

[jira] [Created] (CALCITE-2243) Timestamp values change with remote connection when the result set size exceeds 100 rows

Markku Vuorenmaa created CALCITE-2243: - Summary: Timestamp values change with remote connection when the result set size exceeds 100 rows Key: CALCITE-2243 URL:

Re: two avatica bugs

Hi Victor, I don't understand the first bug you are trying to describe. Please try to create a unit test which shows what you are seeing which is broken. The second does not surprise me -- I don't recall ever seeing the CLOB datatype implemented. Same for BLOB. You are very welcome to