LakeShen created CALCITE-5970:
-
Summary: Add the RelRule to rewrite the Sample as Filter
Key: CALCITE-5970
URL: https://issues.apache.org/jira/browse/CALCITE-5970
Project: Calcite
Issue Type:
LakeShen created CALCITE-5971:
-
Summary: Add the RelRule to rewrite the Sample as Filter
Key: CALCITE-5971
URL: https://issues.apache.org/jira/browse/CALCITE-5971
Project: Calcite
Issue Type:
I also encountered this problem once, even force-push didn't work.
I recreated PR to bypass this problem. It also happened on windows.
https://issues.apache.org/jira/projects/CALCITE/issues/CALCITE-5878
Best Regards,
Ran Tao
Tanner Clary 于2023年9月1日周五 00:15写道：
> Hi Calcite Developers,
>
> I
Seems my PR is passing now. Thanks all for the help.
-Tanner
On Thu, Aug 31, 2023 at 2:59 PM Francis Chuang
wrote:
> I deleted the caches for the PR in GitHub Actions and retriggered the
> job. It looks like its running now.
>
> Francis
>
> On 1/09/2023 7:41 am, Julian Hyde wrote:
> >
I deleted the caches for the PR in GitHub Actions and retriggered the
job. It looks like its running now.
Francis
On 1/09/2023 7:41 am, Julian Hyde wrote:
Actually, no need to force-push, just restart the job.
On Aug 31, 2023, at 2:41 PM, Julian Hyde wrote:
I searched for the error
I just retriggered the job to see if it passes. Alessandro retriggered
it a few hours ago and it was still failing. Perhaps we need to clear
the cache in GitHub Actions.
Francis
On 1/09/2023 7:41 am, Julian Hyde wrote:
Actually, no need to force-push, just restart the job.
On Aug 31,
Actually, no need to force-push, just restart the job.
> On Aug 31, 2023, at 2:41 PM, Julian Hyde wrote:
>
> I searched for the error message and it’s maybe a corrupted Gradle cache.
> That sounds plausible, because the message doesn’t look specific to Windows
> or your change. Just one
I searched for the error message and it’s maybe a corrupted Gradle cache. That
sounds plausible, because the message doesn’t look specific to Windows or your
change. Just one container gone bad. I’d force-push and see whether I get a
healthier container next run.
Julian
[1]
Hi Calcite Developers,
I have a PR [1] that is failing the CI checks for Windows [2]. I am not
familiar with these errors and am wondering if anyone has any suggestions
on how I could fix them. Thanks so much.
Best,
Tanner Clary
[1] https://github.com/apache/calcite/pull/3391
[2]
Thanks for your advice,Julian,I will consider it.
When I have a idea, I will register a JIRA for tracking.
Best,
LakeShen
Julian Hyde 于2023年8月31日周四 03:05写道：
> How about creating a RelOptRules#EXTENDED_RULES (or using some existing
> collection) and provide a means within a Quidem test to turn
Hi Ran Tao,
Thank you for opening this PR, I tried to leave a couple of suggestions.
Best,
Tanner Clary
On Thu, Aug 31, 2023 at 4:30 AM Ran Tao wrote:
> Hi, devs.
>
> can anyone help to review this? thanks.
>
>
> Best Regards,
> Ran Tao
>
>
> Ran Tao 于2023年8月28日周一 13:07写道：
>
> > Hi devs,
>
Hi, devs.
can anyone help to review this? thanks.
Best Regards,
Ran Tao
Ran Tao 于2023年8月28日周一 13:07写道：
> Hi devs,
>
> I opened a ticket CALCITE-5948[1] to solved the questions below.
>
> If we call elements cast in array or map functions such as `array(1,
> cast(2 as tinyint))` or `map[1,
Thanks, i fill the issue.
https://issues.apache.org/jira/browse/CALCITE-5969
First off, can you create a jira case? This is clearly a bug.
I think AggregateCall.rexList is new and will need to be explicitly
handled in serialization and deserialization. Testing shouldn’t be
difficult if you
Evgeny Stanilovsky created CALCITE-5969:
---
Summary: LITERAL_AGG erroneously assembled after deserialization
Key: CALCITE-5969
URL: https://issues.apache.org/jira/browse/CALCITE-5969
Project:
14 matches
Mail list logo
