Junrui Li created FLINK-35669:
-
Summary: Release Testing: Verify FLIP-383: Support Job Recovery
from JobMaster Failures for Batch Jobs
Key: FLINK-35669
URL: https://issues.apache.org/jira/browse/FLINK-35669
+1 (binding)
On Fri, Jun 21, 2024 at 6:52 PM Jeyhun Karimov wrote:
>
> Hi Sergio,
>
> +1 (non-binding)
>
> Regards,
> Jeyhun
>
> On Fri, Jun 21, 2024 at 4:59 PM Jim Hughes
> wrote:
>
> > Hi Sergio,
> >
> > +1 (non-binding)
> >
> > Thanks,
> >
> > Jim
> >
> > On Fri, Jun 21, 2024 at 10:50 AM
>I think so. But this is orthogonal to this issue [1] (deciding whether to
>provide the proposed feature or not), no?
thanks for your response
yep, I looked into the issue however still not clear what problem is
solved with this approach
from my point of view the query there is good to highlight
Hi Sergey,
Thanks for your comments.
Could you please elaborate more on use cases of this feature?
IMHO, the main use-cases can be
- simplifying some SQL queries (e.g., with queries including many/long
column names)
- having consistency when refactoring (e.g., columns are renamed)
- handling
Hi Sergio,
+1 (non-binding)
Regards,
Jeyhun
On Fri, Jun 21, 2024 at 4:59 PM Jim Hughes
wrote:
> Hi Sergio,
>
> +1 (non-binding)
>
> Thanks,
>
> Jim
>
> On Fri, Jun 21, 2024 at 10:50 AM Timo Walther wrote:
>
> > +1 (binding)
> >
> > Thanks,
> > Timo
> >
> >
> > On 21.06.24 16:18, Sergio Pena
Hi Sergio,
+1 (non-binding)
Thanks,
Jim
On Fri, Jun 21, 2024 at 10:50 AM Timo Walther wrote:
> +1 (binding)
>
> Thanks,
> Timo
>
>
> On 21.06.24 16:18, Sergio Pena wrote:
> > Hi everyone,
> >
> > Thanks for all the feedback about FLIP-463: Schema Definition in CREATE
> > TABLE AS Statement
+1 (binding)
Thanks,
Timo
On 21.06.24 16:18, Sergio Pena wrote:
Hi everyone,
Thanks for all the feedback about FLIP-463: Schema Definition in CREATE
TABLE AS Statement [1]. The discussion thread is here [2].
I'd like to start a vote for it. The vote will be open for at least 72
hours unless
Hi everyone,
Thanks for all the feedback about FLIP-463: Schema Definition in CREATE
TABLE AS Statement [1]. The discussion thread is here [2].
I'd like to start a vote for it. The vote will be open for at least 72
hours unless there is an objection or insufficient votes. The FLIP will be
Lv Luo Gang created FLINK-35668:
---
Summary: Throw exception "java.lang.OutOfMemoryError" when import
data of a MySQL table to StarRocks
Key: FLINK-35668
URL: https://issues.apache.org/jira/browse/FLINK-35668
Zakelly Lan created FLINK-35667:
---
Summary: Implement Reducing Async State API for ForStStateBackend
Key: FLINK-35667
URL: https://issues.apache.org/jira/browse/FLINK-35667
Project: Flink
Issue
Zakelly Lan created FLINK-35666:
---
Summary: Implement Aggregating Async State API for
ForStStateBackend
Key: FLINK-35666
URL: https://issues.apache.org/jira/browse/FLINK-35666
Project: Flink
Hi Muhammet,
Thanks for your comment.
Personally, I find this feature confusing, it feels always natural to use
> column names.
- I also have the similar experience w.r.t. using column ordinals.
But it seems counterintuitive to enable flag for this feature. Enabling
it, should not disable
Rui Fan created FLINK-35665:
---
Summary: Release Testing: FLIP-441: Show the JobType and remove
Execution Mode on Flink WebUI
Key: FLINK-35665
URL: https://issues.apache.org/jira/browse/FLINK-35665
13 matches
Mail list logo