Thanks @Tison for starting the discussion and sorry for joining so late.
Yes, I think this is a very good idea. we already tweak the flink-yarn
package internally to support something similar to what @Thomas mentioned:
to support registering a Jar that has already uploaded to some DFS
(needless to
Zhangcheng Hu created FLINK-14933:
-
Summary: translate "Data Streaming Fault Tolerance" page in to
Key: FLINK-14933
URL: https://issues.apache.org/jira/browse/FLINK-14933
Project: Flink
Issu
Hi Zhu Zhu,
Thanks a lot for letting us know!
We can't cut the first RC right now due to the wait of the flink-shade
release, so go ahead.
Theoretically, we will cut the first RC of 1.8.3 and vote for it once the
release of flink-shade is done,
but I will try my best to have it in 1.8.3. Hope we
The voting period has passed, and the release was unanimously approved.
+1 votes:
- Aljoscha (binding)
- Tison (non-binding)
- Dian (non-binding)
- Jongsong (non-binding)
- Ufuk (binding)
- Hequn (non-binding)
- Chesnay (binding)
On 19/11/2019 23:13, Chesnay Schepler wrote:
Hi everyone,
Please
Hi,
+1 for disabling it in the Blink planner. Once FLIP-65 is implemented
and a UDX is registered with the new
TableEnvironment.createTemporaryFunction() we will also have the
possibility to be fully compliant with the new type system because we
can advertise a new UDF stack with new behavior
Thanks for driving this, Dawid.
I’m +1 on it.
One minor suggestion: I think it’s better to override the `equals()` and
`hashCode()` methods for `KeyConstraint`.
Thanks,
Xingcan
> On Nov 23, 2019, at 2:40 AM, Jingsong Li wrote:
>
> +1 thanks dawid for driving this.
>
> Best
> Jingsong Lee
>
