Julian,
Can you please review PR #22[1] for calcite-avatica-go?
I also have some documentation fixes in a PR #20[2], and since we are
going to cancel the vote for rc0 and roll rc1, I think it would be a
good idea to merge that PR in too.
Francis
[1] https://github.com/apache/calcite-avatica-
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/22
Check files for Apache license header in make-release-artifacts script
cc @julianhyde
One quick question:
In cb2d4cb4596d5850bd0eb10c9c7697b679aabc2d, the script was updated
Kevin Risden created CALCITE-2272:
-
Summary: Avatica - Apache POM 19 and JDK 10 javadoc
Key: CALCITE-2272
URL: https://issues.apache.org/jira/browse/CALCITE-2272
Project: Calcite
Issue Type:
The vote for Apache Calcite Avatica Go 3.0.0-rc0 has been canceled.
I will make a rc1 and start a new vote.
Francis
On 18/04/2018 6:43 PM, Francis Chuang wrote:
Hi all,
I have created a release for Apache Calcite Avatica Go, release
candidate 0.
The release notes are available here:
http
Hi Julian,
That make sense. I'll update the script in a PR.
Regarding the gopher.png file, I removed it and replaced it with the
Calcite logo (you should be able to see the commit on master).
Are there any other changes that we need to make?
I am going to cancel the vote and tag 3.0.0-rc1 fo
Yes, I’ve ignored that change for a couple of months (sorry Shuyi) but I
reviewed it yesterday and am currently testing, so it should be committed to
master shortly.
> On Apr 20, 2018, at 5:41 PM, Shuyi Chen wrote:
>
> Currently, user defined type is not supported in Calcite. But it's WIP,
> p
While running this query
SELECT COUNTRY_REGION, SUM(CUST_ID) OVER (PARTITION BY COUNTRY_REGION) FROM
SALES.COUNTRIES LEFT JOIN SALES.CUSTOMERS ON CUSTOMERS.COUNTRY_ID =
COUNTRIES.COUNTRY_ID
The following error is thrown
java.lang.AssertionError
at
org.apache.calcite.rel.metadata.RelMdDistrib
Currently, user defined type is not supported in Calcite. But it's WIP,
please see https://issues.apache.org/jira/browse/CALCITE-2045. With this
PR, you can either use CREATE TYPE statement to define your own type or
define your new type in the JSON schema.
Thanks
Shuyi
On Fri, Apr 20, 2018 at 4
I want to parse a query having 'text' in place of 'varchar'. For
example, select
cast(ps_comment as text) from part While parsing calcite is showing,
Unknown data type name 'TEXT'.
How can I make calcite to parse the above query successfully having
user-defined data type 'text'?
Thanks in advanc
For optimized query plans, I have given rowCount of the table to calcite.
But still I want to add more column informations like column type/size and
so, to the metadata, so that calcite will use that also to give more
optimized plan. But how can I give those details to calcite planner?
Thanks in a
Alexey Makhmutov created CALCITE-2271:
-
Summary: Join of two views with window aggregates produce
incorrect results or NPE
Key: CALCITE-2271
URL: https://issues.apache.org/jira/browse/CALCITE-2271
I agree that the script to build the release should be part of the
source code. And the script that checks for headers is part of that.
The "case" statement is actually important, because it gives us a
place to document (and justify) files without headers, and other files
of interesting provenance.
12 matches
Mail list logo