Maximilian Michels comments

Results 43 comments of


                                            Maximilian Michels

[FLINK-28853][connector-base] Add FLIP-217 support for watermark alignment of source splits

Fair point, users may modify the job to disable alignment. It doesn't make sense to override the watermark alignment settings from the config. But the same argument applies to the...

[FLINK-28853][connector-base] Add FLIP-217 support for watermark alignment of source splits

@flinkbot run azure

[FLINK-28853][connector-base] Add FLIP-217 support for watermark alignment of source splits

Tests are passing now.

[FLINK-28853][connector-base] Add FLIP-217 support for watermark alignment of source splits

Thank you everyone!

[FLINK-34906] Only scale when all tasks are running

Thanks Rui! The changes make sense to me. To Gyulas point, I think we should try to deduplicate the logic such that both Kubernetes autoscaler and standalone use the same...

[FLINK-33960][Scheduler] Fix the bug that Adaptive Scheduler doesn't respect the lowerBound when one flink job has more than 1 tasks

Thanks for looking into this @1996fanrui! I'll take a look.

Running on Mesosphere DC/OS with persistent storage

Looks like this is not a CrateDB problem but a DC/OS configuration issue. The supplied path is not writable. Could you supply the full stack-trace for the `AccessDeniedException`?

[FLINK-31215] [autoscaler] Backpropagate processing rate limits from non-scalable bottlenecks to upstream operators

Thanks for the PR @aplyusnin! I'll take a look.

[FLINK-31215] [autoscaler] Backpropagate processing rate limits from non-scalable bottlenecks to upstream operators

> The `actual_target_data_rate_join` still can be greater than `target_data_rate_upstream_1` or `target_data_rate_upstream_2`. It means that the upstreams' target_data_rate remains unchanged. > > Also, the `actual_target_data_rate_join` can be less than the target_data_rate...

Flink: Migrate Flink `TableSchema` to `Schema`/`ResolvedSchema`

What are the obstacles for completely getting rid of TableSchema?