Calcite has not implemented the syntax in that paper. I would support an effort
to add it (unsurprising, since I am a co-author of that paper).
EMIT STREAM is equivalent to the current SELECT STREAM syntax.
There is no equivalent in current Calcite of the EMIT AFTER WATERMARK, or EMIT
STREAM
Danny Chan created CALCITE-3269:
---
Summary: Returns integer for VARCHAR and INT division of
PostgreSql dialect
Key: CALCITE-3269
URL: https://issues.apache.org/jira/browse/CALCITE-3269
Project: Calcite
Hi Calcite community,
I have seen [1] is published, which proposes TVF style TUMBLE/HOP/SESSION
windowing and EMIT syntax for materialization control.
I tried to search dev@calcite and Calcite JIRA but didn't find those
support above. So is Calcite already support TVF windowing and EMIT syntax
Hey everyone,
Previously I mentioned that I was working on automated website builds
for the Calcite (and avatica and avatica-go subwebsite) Website [1] and
I wanted to give you guys some updates.
The initial attempt was to use the git-websites jenkins node to build
the site, however I ran
+1
I’ve poked Khai Tran re. 3122 (Pig).
> On Aug 16, 2019, at 11:20 PM, Stamatis Zampetakis wrote:
>
> Hi all,
>
> The release is advancing quite well, yet we have 22 issues marked for
> 1.21.0 [1].
>
> From those, the following 5 seem to be the most important:
>
>
One tricky aspect is to optimize a *batch* of requests.
The trick is to tie together the batch so that it is costed as one request. We
don’t have an operator specifically for that, but you could for instance use
UNION ALL. E.g. given Q1 and Q2, you could generate a plan for
select count(*)
The Apache Jenkins build system has built Calcite-Master (build #1304)
Status: Still Failing
Check console output at https://builds.apache.org/job/Calcite-Master/1304/ to
view the results.
Hi Danny,
thanks for the quick reply.
Cost calculation we can of course provide (but it could be a bit different as
we have not only CPU and Memory but also Network or something).
And also something like the RelNodes could be provided. In our case this would
be "Requests" which are at first
Hi Leon,
What do you mean recognize it as a raw table?
If you don't want to perform validation for a given query then you can
simply use the SqlParser who doesn't
care if the table exists or not.
Best,
Stamatis
On Sun, Aug 18, 2019 at 3:59 PM Leon Xu wrote:
> Thanks Julian, another
Cool idea ! Julian Feinauer ~
I think the volcano model can be used the base of the cost algorithm. As long
as you define all the metadata that you care about. Another thing is that you
should have a struct like RelNode and a method like #computeSelfCost.
Best,
Danny Chan
在 2019年8月19日 +0800
Hi Tino,
The ScanType is used by ColumnTypeScanType [1] which is a new interface
added in Go 1.8. The avatica-go implementation is here [2].
Therefore, we should not remove it as the database/sql can use this
interface.
I believe you are hitting the panic here in the generic driver [3].
Hi folks,
I’m here again with another PLC4X related question (https://plc4x.apache.org).
As we have more and more usecases we encounter situations where we send LOTS of
replies to PLCs which one could sometimes optimize.
This has multiple reasons upstream (like multiple different Services
12 matches
Mail list logo
