Re: [VOTE] Release calcite-avatica-go-3.0.0 (release candidate 0)

Regarding the gopher.png file: I have removed it and replaced it with the Calcite logo (calcite.png) this should avoid any licensing issues. Francis On 19/04/2018 11:47 AM, Julian Hyde wrote: Thanks for starting the vote. A few questions/comments before I cast my vote. Not all of them are

[GitHub] calcite-avatica-go pull request #21: Replace gopher.png with Calcite logo an...

Github user asfgit closed the pull request at: https://github.com/apache/calcite-avatica-go/pull/21 ---

[GitHub] calcite-avatica-go pull request #21: Replace gopher.png with Calcite logo an...

GitHub user F21 opened a pull request: https://github.com/apache/calcite-avatica-go/pull/21 Replace gopher.png with Calcite logo and uncomment HSQLDB transaction tests You can merge this pull request into a Git repository by running: $ git pull

Re: SQL:2016

Glad to see that we are discussing JSON features in latest SQL standard and Michael already worked on one JSON function. I think we Drill community is interested in polymorphic table function feature and I just filed CALCITE-2270 for that. From: Julian Hyde

[jira] [Created] (CALCITE-2270) [SQL:2016] Polymorphic table functions

Chunhui Shi created CALCITE-2270: Summary: [SQL:2016] Polymorphic table functions Key: CALCITE-2270 URL: https://issues.apache.org/jira/browse/CALCITE-2270 Project: Calcite Issue Type: Bug

Druid Adapter - Error Prone checking result

I was looking into Error Prone [1] checking for Calcite and it found what looks like a bug in Druid Adapter. The output is as follows DruidJsonFilter.java:[324,9] [IdentityBinaryExpression] A binary expression > where both operands are the same is usually incorrect; the value of this > expression

[jira] [Created] (CALCITE-2269) Enable errorprone checking

Kevin Risden created CALCITE-2269: - Summary: Enable errorprone checking Key: CALCITE-2269 URL: https://issues.apache.org/jira/browse/CALCITE-2269 Project: Calcite Issue Type: Improvement

[jira] [Created] (CALCITE-2268) Avatica HSQLDB Dockerfile should be bumped to 2.4.0

Kevin Risden created CALCITE-2268: - Summary: Avatica HSQLDB Dockerfile should be bumped to 2.4.0 Key: CALCITE-2268 URL: https://issues.apache.org/jira/browse/CALCITE-2268 Project: Calcite

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

JDK 10 is now passing with Travis CI (tracked in CALCITE-2063). Should be able to turn back on the Apache Jenkins Calcite JDK 10 builds :) Kevin Risden On Thu, Apr 12, 2018 at 7:42 PM, Kevin Risden wrote: > I just put up a PR to fix the remaining JDK 10 failures for

Re: SQL:2016

Yes. Apache has representation in the W3C and Open Geospatial Consortium. Much database innovation these days is coming out of open source, and these open source projects tend to join Apache, so it makes a lot of sense that we have a voice. > On Apr 19, 2018, at 1:30 PM, Edmon Begoli

Re: SQL:2016

I will certainly ask. I noticed that most members are big vendors, but that might have to do with a $2200 membership fee. It would probably be good to have ASF represented more broadly by the projects that use SQL as an API. On Thursday, April 19, 2018, Julian Hyde wrote: >

Re: SQL:2016

Do you think you could help bring a little more openness to the process? I’d love to know what areas are being considered, and what is the target date for the next standard. Even if the information flow is only one way, it would help counter some perceptions that the process is dominated by

Re: SQL:2016

I’ve actually joined the standard to be, in addition to representing my lab, an advocate for Calcite and ASF, so I could represent these needs, and bring anything else up. Just let me know. Thank you, Edmon On Thursday, April 19, 2018, Julian Hyde wrote: > I’d love to know

Re: SQL:2016

I’d love to know whether/when you guys intend to standardize streaming SQL. I have come to the conclusion that extensions to SQL’s existing temporal support (i.e. being able to join each row to a different temporal snapshot of a table) would be extremely useful to support streaming. Also,

Re: SQL:2016

I am on the SQL standards committee and I will ask. Are there any other things anyone would like to know? On Thu, Apr 19, 2018 at 5:54 PM Michael Mior wrote: > Thanks for the review. I have most of these changes sorted out. Is there > any good resource for the SQL standard

Re: SQL:2016

I usually search for "committee draft iso 9075” and easily find drafts of the standard. An ASF-wide copy of the standard is worth exploring. We would need to keep it private. Julian > On Apr 19, 2018, at 8:54 AM, Michael Mior wrote: > > Thanks for the review. I have

Re: Bug Report! Help! Calcite TUMBLE! I have tried many times, many ways, but the tutorial for streaming is not working!

I ignore emails that have “HELP” and exclamation points in the title. > On Apr 19, 2018, at 10:02 AM, Gia Thuan Lam wrote: > > To honorable Calcite developers, > > thank you for creating Calcite. I find Calcite very interesting and if > working, it will be very

Bug Report! Help! Calcite TUMBLE! I have tried many times, many ways, but the tutorial for streaming is not working!

To honorable Calcite developers, thank you for creating Calcite. I find Calcite very interesting and if working, it will be very suitable for my job. However, in the middle of my learning, the tutorial for Calcite streaming does not seem to work. Therefore, I am writing to you with the hope that

Re: SQL:2016

Thanks for the review. I have most of these changes sorted out. Is there any good resource for the SQL standard aside from purchasing a copy of the standard itself. If not, do you think that this is something the ASF would be willing to do? Assuming it could be shared between projects, I think