When should I prepare for upgrading ZK to 3.5 or newer?
We're operating a Hadoop cluster w/ ZK 3.4.6 for running only Flink jobs.
Just hope that the rolling update is not that painful - any advice on this?
Best,
Dongwon
On Tue, Dec 7, 2021 at 3:22 AM Chesnay Schepler wrote:
> Current users of
Since this is only relevant for 1.15, if you intend to migrate to 1.15
close to the release, then somewhere around February.
The only resource I could find for migrating Zookeeper is this FAQ:
https://cwiki.apache.org/confluence/display/ZOOKEEPER/Upgrade+FAQ
On 07/12/2021 04:02, Dongwon Kim w
Fabian Paul created FLINK-25206:
---
Summary: Add config option to disable configurations in the user
program
Key: FLINK-25206
URL: https://issues.apache.org/jira/browse/FLINK-25206
Project: Flink
Hi Wenlong,
> First, we add a newStateLayout because of some improvement in state, in
> order to keep compatibility we may still keep the old state for the first
> version. We need to update the version, so that we can generate a new
> version plan for the new job and keep the exec node compatib
Hi all,
Thanks Till for starting this discussion. It is great to see these
facts written down since they definitely caused friction in the past
because of different interpretations. Overall I agree with everything
being said in this FLIP. I was just wondering whether we can put the
label explainin
Stephan Pirson created FLINK-25207:
--
Summary: sample pyflink from documentation doesn't work in jupyter
notebooks
Key: FLINK-25207
URL: https://issues.apache.org/jira/browse/FLINK-25207
Project: Flin
ZhuoYu Chen created FLINK-25208:
---
Summary: AsyncSink\Source lock of documentation or Blog
Key: FLINK-25208
URL: https://issues.apache.org/jira/browse/FLINK-25208
Project: Flink
Issue Type: Impr
Chesnay Schepler created FLINK-25209:
Summary: SQLClientSchemaRegistryITCase#testReading is broken
Key: FLINK-25209
URL: https://issues.apache.org/jira/browse/FLINK-25209
Project: Flink
I
Chesnay Schepler created FLINK-25210:
Summary: PulsarSource(Un)OrderedE2ECase is brokern
Key: FLINK-25210
URL: https://issues.apache.org/jira/browse/FLINK-25210
Project: Flink
Issue Type:
Adam Roberts created FLINK-25211:
Summary: Elasticsearch connector version compatibility
Key: FLINK-25211
URL: https://issues.apache.org/jira/browse/FLINK-25211
Project: Flink
Issue Type: Imp
jocean.shi created FLINK-25212:
--
Summary: Support "yarn-ships" directory in client classpath
Key: FLINK-25212
URL: https://issues.apache.org/jira/browse/FLINK-25212
Project: Flink
Issue Type: Im
ZhuoYu Chen created FLINK-25213:
---
Summary: Add @Public annotations to flink-table-common
Key: FLINK-25213
URL: https://issues.apache.org/jira/browse/FLINK-25213
Project: Flink
Issue Type: Sub-t
+1 (binding)
On Tue, Dec 7, 2021 at 3:32 AM Zhu Zhu wrote:
> +1 (binding)
>
> Thanks,
> Zhu
>
> Yang Wang 于2021年12月7日周二 上午9:52写道：
>
> > +1 (non-binding)
> >
> > Best,
> > Yang
> >
> > Xintong Song 于2021年12月7日周二 上午9:38写道：
> >
> > > +1 (binding)
> > >
> > > Thank you~
> > >
> > > Xintong Song
>
Thanks for pushing this Chesnay!
+1 (binding)
On Mon, Dec 6, 2021 at 9:44 PM Martijn Visser wrote:
> +1 (non-binding)
>
> Op ma 6 dec. 2021 om 19:58 schreef Ingo Bürk
>
> > Before more people let me know, let me update my vote to
> >
> > +1 (binding)
> >
> >
> > (In all seriousness, thanks for
Till Rohrmann created FLINK-25214:
-
Summary:
FlinkKafkaProducerITCase.testMigrateFromAtLeastOnceToExactlyOnce fails on AZP
with incorrect result
Key: FLINK-25214
URL: https://issues.apache.org/jira/browse/FLINK-2
Sergey Nuyanzin created FLINK-25215:
---
Summary: ISODOW for timestamps with timezones fails with Invalid
start unit
Key: FLINK-25215
URL: https://issues.apache.org/jira/browse/FLINK-25215
Project: Fli
Dian Fu created FLINK-25216:
---
Summary: test_sliding_group_window_over_proctime failed with
"IndexError: list index out of range"
Key: FLINK-25216
URL: https://issues.apache.org/jira/browse/FLINK-25216
Proje
Hi Timo,
1) I haven't fully thought where to put it but I guess that flink-core
might be a good place for the FlinkVersion. We should then also unify any
other enums if possible.
2) I think it makes sense to also review our deprecation process. I think
it makes a lot of sense to add since when so
Hi Fabian,
Thanks for your input. Adding the definition of the different labels to our
documentation is definitely part of this FLIP.
I agree that deprecation is related to API stability. For the sake of
keeping this FLIP narrowly scoped I left it out, though. For the time being
I suggest that we
Timo Walther created FLINK-25217:
Summary: FLIP-190: Support Version Upgrades for Table API & SQL
Programs
Key: FLINK-25217
URL: https://issues.apache.org/jira/browse/FLINK-25217
Project: Flink
Hi, Timo, +1 for multi metadata.
The compatible change I mean in the last email is the slight state change
example you gave, so we have got consensus on this actually, IMO.
Another question based on the example you gave:
In the example "JSON node gets an additional property in 1.16", if we don'
Hi Martijn,
We just created a cherry-pick pull-request for
https://issues.apache.org/jira/browse/FLINK-20370
We could finish it as soon as possible.
Best,
Jingsong
On Fri, Dec 3, 2021 at 10:25 PM Fabian Paul wrote:
>
> I just opened a PR for
> https://issues.apache.org/jira/browse/FLINK-25126 I
ZhuoYu Chen created FLINK-25218:
---
Summary: Performance issues with lookup join accessing external
dimension tables
Key: FLINK-25218
URL: https://issues.apache.org/jira/browse/FLINK-25218
Project: Flink
23 matches
Mail list logo
