Re: Offset and fetch

2022-11-06 Thread Haisheng Yuan
There is a similar story behind.
https://issues.apache.org/jira/browse/CALCITE-4058

It appears difficult to achieve consensus in the community. However, I don't 
think there is any harm to do it in your own project.

On 2022/11/07 06:19:21 Sasha Syrotenko wrote:
> Hi, Calcite community!
> I have a story offset and fetch fields in the Sort operator - I want to
> extract them into
> a separate Limit rel (in my project), but I wonder -- does it make sense.
> Will I make a mistake, if I do this extraction, in your opinion? Is there
> any story behind,
> which may refrain me to do that?
> Thank you!
> 
> Sincerely, Sasha S.
> 


Offset and fetch

2022-11-06 Thread Sasha Syrotenko
Hi, Calcite community!
I have a story offset and fetch fields in the Sort operator - I want to
extract them into
a separate Limit rel (in my project), but I wonder -- does it make sense.
Will I make a mistake, if I do this extraction, in your opinion? Is there
any story behind,
which may refrain me to do that?
Thank you!

Sincerely, Sasha S.


Re: Returning the Intermediate Representation of the rewrite rules

2022-11-06 Thread Haisheng Yuan
No, there is no API to return rule output.
But there is a class RuleEventLogger, which can log the input and output of the 
rule.

On 2022/11/02 16:53:53 "G.O. Barbulescu" wrote:
> Dear Apache Calcite development team,
> 
> I am currently working on a research project in which I am considering Apache 
> Calcite for the parsing stage. I was wondering if there exists an API to 
> return the intermediate representation (relational tree) for the pre-defined 
> SQL rewrite rules?
> For instance, a relational tree for push-filter-though-join rule in format 
> (LHS relational tree => RHS relational tree).
> The motivation behind this is to have a set of rewrite rules in the same 
> format (IR) as the output of opTree.explain() to build new optimizers.
> 
> Thanks for your time.
> 
> Many thanks,
> George Barbulescu
> 
> 
> 


[jira] [Created] (CALCITE-5369) In Avatica DateTimeUtils, add support for FLOOR and CEIL to ISOYEAR

2022-11-06 Thread Julian Hyde (Jira)
Julian Hyde created CALCITE-5369:


 Summary: In Avatica DateTimeUtils, add support for FLOOR and CEIL 
to ISOYEAR
 Key: CALCITE-5369
 URL: https://issues.apache.org/jira/browse/CALCITE-5369
 Project: Calcite
  Issue Type: Bug
Reporter: Julian Hyde


In Avatica DateTimeUtils, add support for computing the FLOOR and CEIL of a 
date to ISOYEAR.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (CALCITE-5368) Automated site build should not bring changes to SQL reference

2022-11-06 Thread Julian Hyde (Jira)
Julian Hyde created CALCITE-5368:


 Summary: Automated site build should not bring changes to SQL 
reference
 Key: CALCITE-5368
 URL: https://issues.apache.org/jira/browse/CALCITE-5368
 Project: Calcite
  Issue Type: Bug
  Components: site
Reporter: Julian Hyde


The automated site build (added in CALCITE-3129) brings over changes to the 
[SQL reference|https://calcite.apache.org/docs/reference.html] in the middle of 
the release, but these refer to changes that will not be available until the 
next release.

Specifically, commit 
[f7bf867b|https://github.com/apache/calcite/commit/f7bf867ba96578e7cc40e2aac1adf47015d06913]
 on main was cherry-picked as commit 
[07421a67https://github.com/apache/calcite/commit/07421a67a021e68d7a6772f9f94b8d994000a54f]
 on the [site|https://github.com/apache/calcite/tree/site], and it contains 
changes to {{site/doc/reference.md}}. The function {{DATEDIFF}}, which was 
added to reference.md in this change, is not available in  the current release, 
1.32.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)