[CANCEL][VOTE] Release apache-calcite-1.12.0 (release candidate 0)

Canceling the vote, due Michael’s -1. Many thanks to all who downloaded and voted on the release. I’ll have an RC1 up for vote shortly. Julian > On Mar 20, 2017, at 1:49 PM, Julian Hyde wrote: > > Thanks for testing this, Michael. I think this is a show-stopper, and I’m >

Re: Why do I get a fixed length type from literals in CASE

Per the SQL standard: * Character literals have type CHAR (not VARCHAR) * The type of a CASE statement is the most general type of any of its branches. * Spaces are trimmed from CHAR values before comparing them. So, if I compare the CHAR(8) value ‘non_aero ‘ with the CHAR(7) value ‘non_aero’ the

RE: Commits during release vote

You can use git subtree split to extract the Avatica commits into a new repository. This would maintain the history but would generate new commit IDs. Alternatively the history could start with the entire Calcite history with the first commit being one which deletes all non-Avatica files. --

[jira] [Created] (CALCITE-1717) Move Avatica into its own git repository

Julian Hyde created CALCITE-1717: Summary: Move Avatica into its own git repository Key: CALCITE-1717 URL: https://issues.apache.org/jira/browse/CALCITE-1717 Project: Calcite Issue Type: Bug

[jira] [Created] (CALCITE-1716) Cassandra integration tests broken due to change in CAST behavior

Michael Mior created CALCITE-1716: - Summary: Cassandra integration tests broken due to change in CAST behavior Key: CALCITE-1716 URL: https://issues.apache.org/jira/browse/CALCITE-1716 Project:

Re: Commits during release vote

How fitting :) It should be fairly simple -- let me put in a request to infra. Once we have a repo, it should be self-service for us to move the stuff over there. Julian Hyde wrote: Thanks - I’ll rebase after the release. I’m sitting in a cafe right now and there’s a guy right outside the

Re: [VOTE] Release apache-calcite-1.12.0 (release candidate 0)

I'm going to have to change my vote to -1. I just ran the Cassandra integration tests and there's currently a failure which seems to be due to a Guava change incompatible with the Cassandra driver. I'm currently investigating how to resolve this. Suggestions welcome.

[jira] [Created] (CALCITE-1715) Cassandra adapter is broken by Guava change

Michael Mior created CALCITE-1715: - Summary: Cassandra adapter is broken by Guava change Key: CALCITE-1715 URL: https://issues.apache.org/jira/browse/CALCITE-1715 Project: Calcite Issue

[jira] [Created] (CALCITE-1714) Do not push group by on druid metrics fields

slim bouguerra created CALCITE-1714: --- Summary: Do not push group by on druid metrics fields Key: CALCITE-1714 URL: https://issues.apache.org/jira/browse/CALCITE-1714 Project: Calcite Issue

Re: [VOTE] Release apache-calcite-1.12.0 (release candidate 0)

+1 (binding) Downloaded the tarball, checked hashes, compiled, ran testsuite. Integrated with Hive + HIVE-15708 and ran some q tests. Thanks Julian! Jesús On 3/20/17, 6:26 PM, "Kevin Risden" wrote: >I tested Apache Solr integration with the Apache Calcite 1.12.0

[jira] [Created] (CALCITE-1713) elasticsearch adapter does not support elastic 5 & above versions

Rani Yaroshinsky created CALCITE-1713: - Summary: elasticsearch adapter does not support elastic 5 & above versions Key: CALCITE-1713 URL: https://issues.apache.org/jira/browse/CALCITE-1713

[jira] [Created] (CALCITE-1712) elasticsearch adapter is very slow, and does not support many of the operators

Rani Yaroshinsky created CALCITE-1712: - Summary: elasticsearch adapter is very slow, and does not support many of the operators Key: CALCITE-1712 URL: https://issues.apache.org/jira/browse/CALCITE-1712

[jira] [Created] (CALCITE-1711) Expose elasticsearch as jdbc type rather than custom

Rani Yaroshinsky created CALCITE-1711: - Summary: Expose elasticsearch as jdbc type rather than custom Key: CALCITE-1711 URL: https://issues.apache.org/jira/browse/CALCITE-1711 Project: Calcite

Re: [VOTE] Release apache-calcite-1.12.0 (release candidate 0)

I tested Apache Solr integration with the Apache Calcite 1.12.0 RC0 maven snapshot and saw no issues. +1 (non binding) https://github.com/risdenk/lucene-solr/tree/calcite112rc https://travis-ci.org/risdenk/lucene-solr/builds/212498804 Kevin Risden On Mon, Mar 20, 2017 at 1:17 PM, Maryann Xue

Re: [VOTE] Release apache-calcite-1.12.0 (release candidate 0)

+1 On Mon, Mar 20, 2017 at 9:37 AM, Michael Mior wrote: > +1 (non-binding) > > Checked hashes and signature of the tarball and compiled and ran tests. > > -- > Michael Mior > michael.m...@gmail.com > > 2017-03-17 17:30 GMT-04:00 Julian Hyde : > > > Hi all,

Re: Documentation around writing a custom cost factory

> On Mar 20, 2017, at 12:14 AM, Hussain Pirosha > wrote: > > Thanks Julian. > > Spending more time with calcite code on computing cost, I have few questions. > > 1. The cost of the plan is the sum of all the converted (datasource > specific) RelNodes ? Yes.

Re: Commits during release vote

Thanks - I’ll rebase after the release. I’m sitting in a cafe right now and there’s a guy right outside the window re-potting the plant pots: pull up each plant individually, pull its roots apart from other plants, and put into a new pot with more room around it to grow. We should definitely

Re: [VOTE] Release apache-calcite-1.12.0 (release candidate 0)

+1 (non-binding) Checked hashes and signature of the tarball and compiled and ran tests. -- Michael Mior michael.m...@gmail.com 2017-03-17 17:30 GMT-04:00 Julian Hyde : > Hi all, > > I have created a build for Apache Calcite 1.12.0, release candidate 0. > > Thanks to everyone

Re: Commits during release vote

Oops, sorry for causing some pain, Julian. I'm ok with a rebase/force-push. It completely slipped my mind that I should have held off on those commits :) I still think separating out Avatica from the Calcite repo would be better long term (Shi had gotten confused over this, recently), but,

RE: Documentation around writing a custom cost factory

Thanks Julian. Spending more time with calcite code on computing cost, I have few questions. 1. The cost of the plan is the sum of all the converted (datasource specific) RelNodes ? 2. the computeSelfCost method shall calculate the cost by using the RelMetaDataQuery. Can you point to some