Jark Wu created CALCITE-4545:
Summary: Unparse a new function of FUNCTION_ID syntax will be
quoted
Key: CALCITE-4545
URL: https://issues.apache.org/jira/browse/CALCITE-4545
Project: Calcite
> > > >
> > > > > CALCITE-1490 suggests only add to SQL server, but as Oracle,
> > Snowflake
> > > > and
> > > > > BigQuery seems all support the simplified syntax, it might be
> enough
> > to
> > > > > justify
gt; > >
> > > On Thu, Oct 29, 2020 at 11:28 AM Julian Hyde wrote:
> > >
> > > > Can we drop the word "polymorphic" from the discussion? Polymorphic
> > > > table functions are a valid ask, but can be a separate discussion.
> > > > T
Hi all,
It's great to see Calcite already supports PTF syntax and support the
out-of-box new window syntax.
SELECT *
FROM TABLE(TUMBLE(TABLE Bid, DESCRIPTOR(bidtime), INTERVAL '10' MINUTES));
However, some people from the Flink community think that the TABLE()
keyword is a little verbose for use
Hi Julian,
What do you think about the idea above that merging window start and window
end as a composite column?
cc @Julian
On Thu, 22 Oct 2020 at 12:01, Rui Wang wrote:
> This seems reasonable to merge window metadata as a column (more compact
> format).
>
> Maybe Julian can comment whether
Jark Wu created CALCITE-3476:
Summary: ParameterScope should override resolveColumn interface
Key: CALCITE-3476
URL: https://issues.apache.org/jira/browse/CALCITE-3476
Project: Calcite
Issue
Congratulations Danny!
Best,
Jark
On Tue, 14 May 2019 at 09:57, Yuzhao Chen wrote:
> Thank you everyone for your kind messages.
>
> Currently I am working in Alibaba Blink SQL Engine team in Hangzhou,
> Zhejiang, China. We are developing a production version of Apache Flink.
> Our team has done
+1 for "pull-request-available"
On Tue, 8 Jan 2019 at 05:33, Francis Chuang
wrote:
> +1 for "pull-request-available"
>
> On 8/01/2019 8:13 am, Julian Hyde wrote:
> > There seem to be two mechanisms to indicate that a pull-request is
> available for a JIRA case.
> >
> > 1. The “Patch” flag (13 i
Jark Wu created CALCITE-2150:
Summary: CurrentTimestamp is reduced in subquery
Key: CALCITE-2150
URL: https://issues.apache.org/jira/browse/CALCITE-2150
Project: Calcite
Issue Type: Bug
Jark Wu created CALCITE-1917:
Summary: Support column reference in "FOR SYSTEM_TIME AS OF"
Key: CALCITE-1917
URL: https://issues.apache.org/jira/browse/CALCITE-1917
Project: Calcite
Jark Wu created CALCITE-1912:
Summary: Support "FOR SYSTEM_TIME AS OF" in regular queries
Key: CALCITE-1912
URL: https://issues.apache.org/jira/browse/CALCITE-1912
Project: Calcite
Great! I have logged a JIRA https://issues.apache.org/jira/browse/CALCITE-1472
<https://issues.apache.org/jira/browse/CALCITE-1472>
- Jark Wu
> 在 2016年10月25日，下午11:54，Julian Hyde 写道：
>
> It seems as if it is syntactic sugar for a feature we already have. So, I’d
> have no
Jark Wu created CALCITE-1472:
Summary: Support CROSS/OUTER APPLY syntax
Key: CALCITE-1472
URL: https://issues.apache.org/jira/browse/CALCITE-1472
Project: Calcite
Issue Type: New Feature
k-table/src/main/codegen/templates/Parser.jj>
- Jark Wu
Jark Wu created CALCITE-1461:
Summary: Hard code in JaninoRelMetadataProvider makes shading for
Calcite failed
Key: CALCITE-1461
URL: https://issues.apache.org/jira/browse/CALCITE-1461
Project: Calcite
I have logged https://issues.apache.org/jira/browse/CALCITE-1309
<https://issues.apache.org/jira/browse/CALCITE-1309> for this.
- Jark Wu
> 在 2016年7月8日，上午9:26，Julian Hyde 写道：
>
> I believe that we should allow LATERAL TABLE. Can you log a JIRA case, please?
>
> As a
Jark Wu created CALCITE-1309:
Summary: Support LATERAL TABLE
Key: CALCITE-1309
URL: https://issues.apache.org/jira/browse/CALCITE-1309
Project: Calcite
Issue Type: New Feature
From myTable lateral view posexplode(myCol) as (pos,
myNewCol)”.
Is there any way to do this in calcite ?
- Jark Wu
From myTable lateral view posexplode(myCol) as (pos,
myNewCol)”.
Is there any way to do this in calcite ?
- Jark Wu
? If not , how can I
support it myself?
- Jark Wu
Jark Wu created CALCITE-1297:
Summary: RelBuilder does not translate identity projects even if
they rename fields
Key: CALCITE-1297
URL: https://issues.apache.org/jira/browse/CALCITE-1297
Project
Jark Wu created CALCITE-1295:
Summary: ReduceExpressionRule should not reduce AS operator
Key: CALCITE-1295
URL: https://issues.apache.org/jira/browse/CALCITE-1295
Project: Calcite
Issue Type
Thanks Jinfeng and Jason,
I have solved my problem, the reason is that the planner I used hasn’t been set
an executor.
Thanks for your advice again!
- Jark Wu
> 在 2016年6月15日，下午1:26，Jinfeng Ni 写道：
>
> If you put ReduceExpressionsRule in a HepPlanner, then you do not have
>
, b, c+5 as d FROM Orders WHERE b > 5
It seems that ReduceExpressionsRule is what I need, and I tried it many times
but it didn’t work.
Is the way I used wrong ? Or there is any exist rule to use, or I have to
implement one myself ?
- Jark Wu
24 matches
Mail list logo
