I am very glad to see the patch has been accepted，and many thanks to all of you
(Michael, Julian, Vladimir, ...) for continuously paying attention to this
thread, and for the great review work.
Thank you again!
Hongze
At 2018-11-10 02:30:31, "Julian Hyde" wrote:
>Hongze has also just
Hi Julian,
If I remember right, Calcite does not support Postgres's json and jsonb
datatype in current version (1.18).
Calcite has built-in JSON support (see CALCITE-2266[1]) similar to what has
been implemented in Oracle and MS SQL, It is a earlier version of the whole
JSON things described
n the builds might take a bit longer.
Kevin Risden
On Mon, Mar 25, 2019 at 1:36 PM Hongze Zhang wrote:
Hi all,
This is caused by a known problem which is analyzed in mail thread[1], and
it seems that the problem keeps failing our Jenkins build for a period of
time. I had tried cleani
Chuang <
> francischu...@apache.org> έγραψε:
>
>> (Note: This was supposed to be sent last month, but I've somehow
>> forgotten. Please accept my apologies.)
>>
>> Apache Calcite's Project Management Committee (PMC) has invited Hongze
>> Zhang
ltan Haindrich as committer
d d561dba0e Site: Add commit message guidelines for contributors (Stamatis
Zampetakis)
d a96db9117 Site: [CALCITE-2734] Update mongo documentation to reflect
filename changes
pick 27706dd07 Site: News item for release 1.19.0
pick 07fcedb42 Site: Add new committers (Haishe
Firstly, thank you very much for sharing the case, Rui!
I have run a test with the SQL you provided and also run into the same
exception (under a global LOOKAHEAD 3). After debugging the generated
parser code, I think the problem is probably in the generated LOOKAHEAD
method
Ops, correct a typo:
"... after uncommenting a line ..." -> "... after commenting a line
...".
Best,
Hongze
-- Original Message ------
From: "Hongze Zhang"
To: dev@calcite.apache.org
Sent: 2019/3/26 19:28:08
Subject: Re: Calcite doesn't work with LOOKA
I see the CI of the last commit is passed now:
https://travis-ci.org/apache/calcite/builds/512347766?utm_source=github_status_medium=notification
But the build status of GitHub commit (the yellow point after "committed
xx days ago") is still now being synced.
Hongze
-- Original Message
Should I open a Jira to upgrade that plugin version ?
>
> Thanks,
> Gelbana
>
>
> On Thu, Mar 28, 2019 at 4:18 AM Rui Li wrote:
>
>> Thanks Hongze, that's good to know.
>>
>> On Thu, Mar 28, 2019 at 8:43 AM Hongze Zhang wrote:
>>
>>>> Besides, i
guess we'd better get rid of these warnings if we want to stick
> to lookahead(2).
>
> On Wed, Mar 27, 2019 at 8:54 AM Hongze Zhang wrote:
>
>> Thanks, Yuzhao.
>>
>> Since the more generic problem is that the production "E()"[1] causes the
>> paren
As far as you can see, the rule doesn't currently support non-equal
join.
While you execute a SQL with non-equal join conditions, the rule can
only handle the equal join generated by JoinExtractFilterRule[1]. So
AFAIK you are not able to receive performance benefits by this rule so
far
L61
-- Original Message --
From: "Hongze Zhang"
To: dev@calcite.apache.org
Sent: 2019/4/1 12:00:04
Subject: Re: Is sort-merge join rule supports a non-equi join?
As far as you can see, the rule doesn't currently support non-equal
join.
While you execute a SQL with n
Hi all,
This is caused by a known problem which is analyzed in mail thread[1], and it
seems that the problem keeps failing our Jenkins build for a period of time. I
had tried cleaning Calcite's workspaces on several slave nodes but it could not
prevent the same error happening on other
o Chen wrote:
>
> Maybe we should fire a jira if it is a bug.
>
> Best,
> Danny Chan
> 在 2019年3月26日 +0800 PM8:33，Hongze Zhang ，写道：
>> Ops, correct a typo:
>>
>> "... after uncommenting a line ..." -> "... after commenting a line
>> ...".
Just forced this push to change the commit message from
"[CALCITE-2787] Json aggregate calls with different null clause get incorrectly
merged during converting from SQL to relational algebra”
to
"[CALCITE-2787] JSON aggregate calls with different null clause get incorrectly
merged during
Hi Anton,
Following code works to me:
final RexNode shiftedDateField =
relBuilder.call(
SqlStdOperatorTable.TIMESTAMP_ADD,
relBuilder.getRexBuilder().makeFlag(TimeUnitRange.MONTH),
relBuilder.literal(1),
relBuilder.getRexBuilder().makeDateLiteral(new
Correct the flag:
TimeUnitRange.MONTH -> TimeUnit.MONTH
Best,
Hongze
At 2019-02-22 22:07:11, "Hongze Zhang" wrote:
Hi Anton,
Following code works to me:
final RexNode shiftedDateField =
relBuilder.call(
SqlStdOperatorTable.
t;>
>> EnumerableCalc(expr#0..26=[{inputs}], expr#27=[1], expr#28=[1],
>> expr#29=[*($t27, $t28)], expr#30=[+($t0, $t29)], EXPR$0=[$t30])
>>
>> And Calcite is able to execute it. So now I'm trying to replicate it
>> using a RelBuilder (usin
,
rexBuilder.makeIntervalLiteral(
TimeUnit.MONTH.multiplier,
new SqlIntervalQualifier(TimeUnit.MONTH, null, SqlParserPos.ZERO)
),
relBuilder.literal(1)
)
);
> On Feb 23, 2019, at 00:03, Hongze Zhang wrote:
>
>> RexNode shiftedDateField =
>
Thanks for your help on this topic, Qianjin! It would be great if you are
willing to contribute more. Be free to file JIRA issues / open PRs at the time
when you think is right.
Best,
Hongze
Hongze
From: ForwardXu
Date: 2019-02-25 09:43
To: Hongze Zhang
Subject: Integrating MySQL's JSON
Sorry for making the wrong operation, Zoltan. I’ve reassigned the issue to you.
Hongze
> On Feb 25, 2019, at 23:09, Hongze Zhang (JIRA) wrote:
>
>
> [
> https://issues.apache.org/jira/browse/CALCITE-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
&
There is a Github robot "Stale"[1][2] for closing inactive PRs automatically.
Below are some Apache projects already using it:
1. https://github.com/apache/incubator-druid/blob/master/.github/stale.yml
2. https://github.com/apache/airflow/blob/master/.github/stale.yml
3.
as renamed.
Can you please have a look Hongze Zhang?
Best,
Stamatis
Στις Δευ, 11 Μαρ 2019 στις 9:27 π.μ., ο/η Apache Jenkins Server <
jenk...@builds.apache.org> έγραψε:
The Apache Jenkins build system has built Calcite-Master (build #1070)
Status: Still Failing
Check console
://builds.apache.org/job/Calcite-Master/1072/
-- Original Message --
From: "Hongze Zhang"
To: dev@calcite.apache.org
Sent: 2019/3/11 17:42:43
Subject: Re: Calcite-Master - Build # 1070 - Still Failing
Stamatis,
Thank you for reminding me, working on finding a reason.
Be
If the function TIMESTAMPADD is not supported in Oracle, in general the
OracleSqlDialect should translate it to some other expressions or calls. But it
seems that currently the dialect does not provide the translation[1].
It would be great if you can log a JIRA case to describe your issue, or
Hi RamKrishna,
As you said:
> So, basically I need to add 2 Hours to CurrentTime.
I think the generated function call "TIMESTAMPADD(HOUR, 2,
CURRENT_TIMESTAMP)" already did that.
If what you want is to compare it's value with a MySQL's Date (with
format -xx-xx), based on Christopher's
Hi all,
Recently I have spent some time on playing with Calcite's built-in SQL parsers.
And now I'm interested with the reason why the global LOOKAHEAD is set to 2[1]
by default.
I run a comparative benchmark using the ParserBenchmark util class, and the
output log shows visible parsing
Thank you very much for managing the release, Kevin.
If the community have enough reviewing resource I would hope the fix of
CALCITE-2785[1] and CALCITE-2787[2] could be bring to Calcite 1.19.0. Besides I
think I can try my best helping review PRs with which I have enough knowledge
too.
t away with, but
>maybe we were wrong.
>
>> On Feb 12, 2019, at 8:24 AM, Hongze Zhang wrote:
>>
>> Hi all,
>>
>>
>> Recently I have spent some time on playing with Calcite's built-in SQL
>> parsers. And now I'm interested with the reason why the
SQL parser
The performance improvements are impressive - basically the parser got 10x
faster.
However, the parser is now more difficult to develop. Is this worth the speedup?
Julian
> On Feb 13, 2019, at 5:30 AM, Hongze Zhang wrote:
>
> Thank you very much for the qui
erator tables at a higher level using the
>> connection property FUN [1].
>>
>> Best,
>> Stamatis
>>
>> [1]
>> https://calcite.apache.org/apidocs/org/apache/calcite/config/CalciteConnectionProperty.html#FUN
>>
>>
>> Στις Παρ, 1 Φεβ 201
y to have that tester check error messages if the test is defined in
BabelParserTest? (Perhaps you could inspect the stack and see whether
“BabelParserTest.test” appears in the top few entries.)
Julian
> On Feb 14, 2019, at 12:36 AM, Hongze Zhang wrote:
>
> I think it's not something unacc
Hi,
We used to face the same problem overriding the default behavior including
operand type checker of a standard operator. If you are using Calcite as an
individual planner (or other circumstances you are not taking the Calcite's
default planner tool org.apache.calcite.prepare.PlannerImpl)
Hi all,
There is a PR CALCITE-2791[1] from xuqianjin about adding a MySQL function
JSON_TYPE[2], and I want to know what do you think about it.
JSON_TYPE is not a standard JSON function defined by SQL:2016. In MySQL the use
of this function is to get the type of a JSON doc. The similar
Congratulations, Stamatis!
Hongze
From: Andrei Sereda
Date: 2019-02-01 11:13
To: dev
Subject: Re: [ANNOUNCE] New committer: Stamatis Zampetakis
Welcome, Stamatis, and thanks for your help.
On Thu, Jan 31, 2019 at 6:22 PM Stamatis Zampetakis
wrote:
> Thank you all for the warm welcome!
>
Congratulations, Zoltan!
Hongze
From: Andrei Sereda
Date: 2019-02-01 11:14
To: dev
Subject: Re: [ANNOUNCE] New committer: Zoltan Haindrich
Welcome, Zoltan!
On Wed, Jan 30, 2019 at 4:39 PM Francis Chuang
wrote:
> Congrats, Zoltan!
>
> Francis
>
> On 31/01/2019 7:05 am, Kevin Risden wrote:
έγραψε:
> +1
>
> In the reference doc, let’s make it clear that these are in MySQL but not
> in the standard. (Unlike some of their other extensions to standard SQL,
> MySQL seem to have done a good job - they are well-designed and
> well-documented.)
>
> > On Jan 31, 2019
Rajesh,
I am not very familiar with Snowflake but I think you need to extend
Babel parser[1] to support Teradata Database's syntax first (also don't
forget to specify Calcite JDBC property
"parserFactory=org.apache.calcite.sql.parser.babel.SqlBabelParserImpl#FACTORY"
to make sure the Babel
e is, might still encounter the same issue
> with Values.
>
>
> Thanks ~
> Haisheng Yuan
> ----------
> 发件人：Hongze Zhang
> 日 期：2019年04月16日 18:10:17
> 收件人：
> 主 题：Re: [DISCUSS] RelCompositeTrait
>
> If we m
Hi Andrew,
My feeling is that maybe what you actually need is the util class
RelToSqlConverter[1]. But if you are using JdbcAdapter, it does not always
translate the whole SQL you executed as you want. For example in this case[2],
the logical plan is only partially pushed down to the source
I didn't take look on the PR in detail so far, but it seems that a topic about
backward compatibility would be worth to discuss anyway.
Regarding the Enumerable's API, I don't think there are many use cases of them
from Calcite users. Although users may create instances in some custom rules,
Although requirement of such functionality is not usual but there is actually a
method
"org.apache.calcite.prepare.CalcitePrepareImpl.EmptyScalarTranslator.toRex(Expression
expression)" which intended to do translation from linq4j expressions to rex
nodes. But since the method is currently
Hi Andrew,
If you are focusing parsing only, I believe you can just use the babel parser -
in babel we have added support for DATE function via CALCITE-3022. The thing is
you need to compile Calcite's code by yourself - 1.20.0 hasn't been released
yet.
Hongze
> On Jun 6, 2019, at 19:06,
+1
On macOS 10.14.5, openjdk 11.0.2:
- Built and ran unit tests from tarball OK
- Built and ran unit tests from target commit 3979b460c OK
- Checked signatures and hashes OK
Thanks Michael!
Hongze
> On Jun 21, 2019, at 06:42, Michael Mior wrote:
>
> Thanks for noting the issue in the
Congratulations, Danny!
Best,
Hongze
-- Original Message --
From: "Jark Wu"
To: dev@calcite.apache.org
Sent: 2019/5/14 10:04:44
Subject: Re: [ANNOUNCE] New committer: Danny Chan
Congratulations Danny!
Best,
Jark
On Tue, 14 May 2019 at 09:57, Yuzhao Chen wrote:
Thank you
+1
(OpenJDK 1.8, Fedora 29)
* Built and run tests from tarball [OK]
* Built and run tests from Git commit 95e154 [OK]
* Run Calcite tests with the RC [OK]
* Run some smoke tests with SQLLine, DBeaver [OK]
* Checked signatures and hashes [OK]
Thanks Francis!
Hongze
-- Original Message
Hi all,
As I have suggested on a related thread[1] started by Stamatis, I am planning
to close the JIRA tickets that are marked as status "RESOLVED" but bound with
an earlier fix version. Say, if a ticket is marked "RESOLVED", and its fix
version is provided but not one of our unreleased
Congratulations, Stamatis! And thank you so much for your thoughtful
suggestions and kindly help on different aspects and discussions.
> On Apr 27, 2019, at 10:44, Francis Chuang wrote:
>
> I'm pleased to announce that Stamatis has accepted an invitation to
> join the Calcite PMC. Stamatis has
I slightly prefer "function set" (should be "FunctionSet"?), as long as
starting with "fun", which names the existing connection property.
Hongze
> On Apr 27, 2019, at 06:45, Yuzhao Chen wrote:
>
> Thx for the discussing, Julian
>
> I’m also confused about the difference between
Thanks for the summing up, Stamatis. That helps a lot, and I am convinced by
the advantages.
Also, I've re-checked the original definition[1] of the status flags CLOSED,
RESOLVED, etc. Following is what "RESOLVED" is for:
> RESOLVED: The issue is considered finished, the resolution is correct.
Congratulations, Ruben!
> On Apr 27, 2019, at 10:39, Francis Chuang wrote:
>
>
> Apache Calcite's Project Management Committee (PMC) has invited Ruben Quesada
> Lopez to become a committer, and we are pleased to announce that he has
> accepted.
>
> In just a few months, Ruben has
Congratulations, Zhiwei!
> On Apr 27, 2019, at 10:37, Francis Chuang wrote:
>
> Zhiwei Peng
t;Tools" -> "Bulk change".
>
> Kevin Risden
>
>
> On Mon, Apr 29, 2019 at 10:46 AM Hongze Zhang wrote:
>
>> Hi all,
>>
>> As I have suggested on a related thread[1] started by Stamatis, I am
>> planning to close the JIRA tickets that
id emailing everyone of the
>> change. If you select "Tools" -> "Bulk change".
>> Kevin Risden
>> On Mon, Apr 29, 2019 at 10:46 AM Hongze Zhang wrote:
>>> Hi all,
>>>
>>> As I have suggested on a related thread[1] started by
apache.org/thread.html/216c7fc441509f9da8c63937f30d5458a1222f475da89a4ec4417ece@%3Cdev.calcite.apache.org%3E
Francis
On 30/04/2019 3:58 am, Hongze Zhang wrote:
Thanks Josh, I noticed that the mails are sent, apologize to everyone being
annoyed.
Maybe I missed something but I re-checked the who
t seems
> that field values are configured globally per JIRA instance (and not per
> project) so I guess we cannot remove some values without affecting all
> Apache projects. I'm not so familiar with JIRA so if somebody else knows
> how to remove "Resolved" from the values of
Hi Vishwas,
The way to access elements from array or map is documented[1] on Calcite
website. Is that what you need?
By the way, the ordinal you use to access an array should start from 1 rather
than 0. For instance, if you execute SQL:
> select x[2]['key2'] as v from
Thank you very much for the summarizing, Stamatis! And +1 to documenting them
to website.
But still one thing I'm not pretty much sure:
> There are cases where the JIRA issue may be solved in the discussion (or
> some other reason) without necessitating a change. In such cases, the
>
If we minimize the issue scope to Calcite itself, I think the 3 JIRA
tickets: CALCITE-2010, CALCITE-2593, CALCITE-2764 that Haisheng has
listed (thanks, Haisheng!) are all related to the multi-sorted
EnumerableValue more or less. An it looks like if we want to get these
problems fixed quickly
+1 for 5B
Hongze
> On Jul 1, 2019, at 12:01, Danny Chan wrote:
>
> +1 for 5B, but using the font of 2C.
>
> Best,
> Danny Chan
> 在 2019年6月29日 +0800 PM4:48，Ivan Grgurina ，写道：
>> +1 for 5B, but using the font from 2C.
>>
>>
>> From: Yuva raj
>> Sent: Saturday,
Congratulations, Stamatis!
Hongze
At 2019-12-20 18:38:12, "Jesus Camacho Rodriguez" wrote:
>Congrats Stamatis! Well deserved!
>
>-Jesús
>
>On Thu, Dec 19, 2019 at 8:51 PM Julian Hyde wrote:
>
>> Glad to have you as the new chair, Stamatis! You have been a mature,
>> helpful and moderating
I think '=' is being shown because by "format json" the statement produced a
JSON value expression rather than a regular
JSON string. Ideally "format json" should not be at the rhs of a select item
and the validator should complain about
that. So there could be a missing check rule in validator.
Hongze Zhang created CALCITE-2530:
-
Summary: Reasonable behavior of TRIM function when the length of
trim character is not 1(one)
Key: CALCITE-2530
URL: https://issues.apache.org/jira/browse/CALCITE-2530
Hongze Zhang created CALCITE-2535:
-
Summary: Runtime failure check not working in SqlTesterImpl.java
Key: CALCITE-2535
URL: https://issues.apache.org/jira/browse/CALCITE-2535
Project: Calcite
Hongze Zhang created CALCITE-2539:
-
Summary: Several test case not passed in
CalciteSqlOperatorTest.java
Key: CALCITE-2539
URL: https://issues.apache.org/jira/browse/CALCITE-2539
Project: Calcite
Hongze Zhang created CALCITE-2648:
-
Summary: Implementation of EnumerableWindow does not preserve
input collation
Key: CALCITE-2648
URL: https://issues.apache.org/jira/browse/CALCITE-2648
Project
Hongze Zhang created CALCITE-2670:
-
Summary: Combine similar JSON aggregate functions in operator table
Key: CALCITE-2670
URL: https://issues.apache.org/jira/browse/CALCITE-2670
Project: Calcite
Hongze Zhang created CALCITE-2593:
-
Summary: Failed to plan when SQL is like "sum(X + 1) filter (where
Y)"
Key: CALCITE-2593
URL: https://issues.apache.org/jira/browse/CALCITE-2593
Projec
Hongze Zhang created CALCITE-2787:
-
Summary: Json aggregate calls with different null clause get
incorrectly merged during converting from sql to rel
Key: CALCITE-2787
URL: https://issues.apache.org/jira/browse
Hongze Zhang created CALCITE-2786:
-
Summary: Add order by clause support for JSON_ARRAYAGG
Key: CALCITE-2786
URL: https://issues.apache.org/jira/browse/CALCITE-2786
Project: Calcite
Issue
Hongze Zhang created CALCITE-2785:
-
Summary: In EnumerableAggregate, wrong result produced If there
are sorted aggregates and non-sorted aggregates at the same time.
Key: CALCITE-2785
URL: https
Hongze Zhang created CALCITE-2956:
-
Summary: Jenkins failure caused by cached classes generated by
previous build
Key: CALCITE-2956
URL: https://issues.apache.org/jira/browse/CALCITE-2956
Project
Hongze Zhang created CALCITE-2876:
-
Summary: Add MySQLSqlOperatorTable
Key: CALCITE-2876
URL: https://issues.apache.org/jira/browse/CALCITE-2876
Project: Calcite
Issue Type: Improvement
Hongze Zhang created CALCITE-2866:
-
Summary: Allow passing custom SqlValidator / SqlToRelConverter
implementations into FrameworkConfig
Key: CALCITE-2866
URL: https://issues.apache.org/jira/browse/CALCITE-2866
Hongze Zhang created CALCITE-2867:
-
Summary: JSON support
Key: CALCITE-2867
URL: https://issues.apache.org/jira/browse/CALCITE-2867
Project: Calcite
Issue Type: Task
Components
Hongze Zhang created CALCITE-2868:
-
Summary: Support for JSON key uniqueness constraint
Key: CALCITE-2868
URL: https://issues.apache.org/jira/browse/CALCITE-2868
Project: Calcite
Issue Type
Hongze Zhang created CALCITE-2870:
-
Summary: Support for JSON query quotes behavior
Key: CALCITE-2870
URL: https://issues.apache.org/jira/browse/CALCITE-2870
Project: Calcite
Issue Type: Sub
Hongze Zhang created CALCITE-2872:
-
Summary: Support for specifying encoding in JSON representation
clause
Key: CALCITE-2872
URL: https://issues.apache.org/jira/browse/CALCITE-2872
Project: Calcite
Hongze Zhang created CALCITE-2871:
-
Summary: Implement JSON_TABLE function
Key: CALCITE-2871
URL: https://issues.apache.org/jira/browse/CALCITE-2871
Project: Calcite
Issue Type: Sub-task
Hongze Zhang created CALCITE-2933:
-
Summary: In Druid adapter, expression like
"cast(cast(\"timestamp\" as timestamp) as varchar)" returns as epoch millisecond
Key: CALCITE-2933
URL: https
Hongze Zhang created CALCITE-2847:
-
Summary: Optimize global LOOKAHEAD for SQL parsers
Key: CALCITE-2847
URL: https://issues.apache.org/jira/browse/CALCITE-2847
Project: Calcite
Issue Type
Hongze Zhang created CALCITE-2993:
-
Summary: ParseException may be thrown for legal SQL queries due to
incorrect "LOOKAHEAD(1)" hints
Key: CALCITE-2993
URL: https://issues.apache.org/jira/browse/CA
Hongze Zhang created CALCITE-3095:
-
Summary: Add several system properties to control rules and traits
Key: CALCITE-3095
URL: https://issues.apache.org/jira/browse/CALCITE-3095
Project: Calcite
Hongze Zhang created CALCITE-3093:
-
Summary: Decouple JDBC connection calls from PlannerImpl
Key: CALCITE-3093
URL: https://issues.apache.org/jira/browse/CALCITE-3093
Project: Calcite
Issue
Hongze Zhang created CALCITE-3074:
-
Summary: Move MySQL's JSON operators to SqlLibraryOperators
Key: CALCITE-3074
URL: https://issues.apache.org/jira/browse/CALCITE-3074
Project: Calcite
Hongze Zhang created CALCITE-3075:
-
Summary: Evaluate Travis CI for Windows build
Key: CALCITE-3075
URL: https://issues.apache.org/jira/browse/CALCITE-3075
Project: Calcite
Issue Type
Hongze Zhang created CALCITE-3045:
-
Summary: NullPointerException when casting null literal to user
defined type
Key: CALCITE-3045
URL: https://issues.apache.org/jira/browse/CALCITE-3045
Project
Hongze Zhang created CALCITE-3046:
-
Summary: CompileException when inserting casted value of
composited user defined type
Key: CALCITE-3046
URL: https://issues.apache.org/jira/browse/CALCITE-3046
Hongze Zhang created CALCITE-3029:
-
Summary: Java-oriented field type is wrongly forced to be NOT NULL
after being converted to SQL-oriented
Key: CALCITE-3029
URL: https://issues.apache.org/jira/browse/CALCITE
89 matches
Mail list logo
