Matthias Pohl created FLINK-32710:
-
Summary: The LeaderElection component IDs for running is only the
JobID which might be confusing in the log output
Key: FLINK-32710
URL: https://issues.apache.org/jira/browse/FL
+1 (binding)
On Fri, Jul 14, 2023 at 11:59 AM Prabhu Joseph
wrote:
> *+1 (non-binding)*
>
> Thanks for working on this. We have seen good improvement during the cool
> down period with this feature.
> Below are details on the test results from one of our clusters:
>
> On a scale-out operation, 8
Aitozi created FLINK-32711:
--
Summary: Type mismatch when proctime function used as parameter
Key: FLINK-32711
URL: https://issues.apache.org/jira/browse/FLINK-32711
Project: Flink
Issue Type: Improv
Hi Ran Tao,
What is the current status? @Dian There were many options. Which one is the
most feasible one you prefer?
Best regards,
Jing
On Fri, Jul 7, 2023 at 2:37 PM Mason Chen wrote:
> Hi all,
>
> I also agree with what's been said above.
>
> +1, I think the Table API delegation is a good s
Hi all,
Currently, I am working on adding support for nested fields filter push
down. In our use case running Flink on Batch, we found nested fields filter
push down is key - without it, it is significantly slow. Note: Spark SQL
supports nested fields filter push down.
While debugging the code us
