David Anderson created FLINK-34477:
--
Summary: support capture groups in REGEXP_REPLACE
Key: FLINK-34477
URL: https://issues.apache.org/jira/browse/FLINK-34477
Project: Flink
Issue Type
Piotr, I think the situation is more nuanced than what you've described.
One concern I have is that unaligned checkpoints are somewhat less flexible
in terms of which operational tasks can be safely performed with them --
i.e., if you look at the table in the docs [1], aligned checkpoints support
That's great news. Congratulations, Alex!
David
On Tue, Jan 2, 2024 at 9:00 AM Ryan Skraba
wrote:
> Awesome news for the community -- congratulations Alex (and Happy New
> Year everyone!)
>
> Ryan
>
> On Tue, Jan 2, 2024 at 2:55 PM Yun Tang wrote:
> >
> > Congratulation to Alex and Happy New
I'm delighted to see the progress on this. This is going to be a major
enabler for some important use cases.
The proposed simplifications (global config and ordered mode) for V1 make a
lot of sense to me. +1
David
On Wed, Dec 20, 2023 at 12:31 PM Alan Sheinberg
wrote:
> Thanks for that
The current situation (where we have both the legacy windows and the
TVF-based windows) is confusing for users, and I'd like to see us move
forward as rapidly as possible.
Since the early fire, late fire, and allowed lateness features were never
documented or exposed to users, I don't feel that
Rui,
I don't have any direct experience with this topic, but given the
motivation you shared, the proposal makes sense to me. Given that the new
default feels more complex than the current behavior, if we decide to do
this I think it will be important to include the rationale you've shared in
the
The implementation of Flink CEP was largely based on Efficient Pattern
Matching over Event Streams by Jagrati Agrawal, Yanlei Diao, Daniel
Gyllstrom, and Neil Immerman from UMass Amherst [1].
[1] https://people.cs.umass.edu/~yanlei/publications/sase-sigmod08.pdf
Cheers,
David
On Tue, Oct 31,
+1
Keeping the legacy implementation in place is confusing and encourages
adoption of something that really shouldn't be used.
Thanks for driving this,
David
On Fri, Sep 1, 2023 at 8:45 AM Jing Ge wrote:
>
> Hi Wencong,
>
> Thanks for your clarification! +1
>
> Best regards,
> Jing
>
> On Fri,
Flink switched to using log4j2 with the 1.11 release. Looking at the
ticket involved [1] should give you some idea of the effort involved
in backporting that to 1.10.
My initial impression is that you might not have to do much to get it
working, The comments in [2] appear to outline what's
s JoinOpertor to always buffer
> records when isBacklog=true, whereas isBacklog's semantics only says it is
> "optional" to buffer records, which can be an issue in the long term.
>
> Thanks,
> Dong
>
> On Tue, Jul 25, 2023 at 2:37 AM David Anderson wrot
I'm delighted to see interest in developing support for
processing-time temporal joins.
The proposed implementation seems rather complex, and I'm not
convinced this complexity is justified/necessary. I'd like to outline
a simpler alternative that I think would satisfy the key objectives.
Key
David Anderson created FLINK-32099:
--
Summary: create flink_data volume for operations playground
Key: FLINK-32099
URL: https://issues.apache.org/jira/browse/FLINK-32099
Project: Flink
Issue
Chesnay, thank you for all your hard work on this!
David
On Fri, May 12, 2023 at 4:03 PM Chesnay Schepler wrote:
>
>
> What happened?
>
> I have just merged the last commits to properly support Maven 3.3+ on
> the Flink master branch.
>
> mvnw and CI have been updated to use Maven 3.8.6.
Does anyone know what happened to the diagrams that used to be in
FLIP-24: SQL Client? The last time I looked at this FLIP -- a few
weeks ago -- there were architecture diagrams for Gateway Mode and
Embedded Mode, but now those images are missing.
David
1. The timestamp passed to testHarness.processElement should be the
timestamp that would have been extracted from the element by the
timestamp extractor in your watermark strategy.
2. Your tests should call testHarness.processWatermark and pass in the
watermark(s) you want to work with.
David Anderson created FLINK-31388:
--
Summary: restart from savepoint fails with "userVisibleTail should
not be larger than offset. This is a bug."
Key: FLINK-31388
URL: https://issues.apache.org/j
David Anderson created FLINK-31361:
--
Summary: job created by sql-client can't authenticate to kafka,
can't find org.apache.kafka.common.security.plain.PlainLoginModule
Key: FLINK-31361
URL: https
+1
I don't have anything substantive to add, but I want to express how pleased
I am to see this conversation happening.
David
On Thu, Feb 2, 2023 at 5:09 AM Martijn Visser
wrote:
> Hi all,
>
> +1 for the overall proposal. My feedback matches with what Matthias
> has already provided earlier.
David Anderson created FLINK-30563:
--
Summary: Update training exercises to use Flink 1.16
Key: FLINK-30563
URL: https://issues.apache.org/jira/browse/FLINK-30563
Project: Flink
Issue Type
I'm also in favor of extending the feature freeze to Jan 31st.
David
On Thu, Dec 29, 2022 at 9:01 AM Leonard Xu wrote:
> Thanks Qingsheng for the proposal, the pandemic has really impacted
> development schedules.
>
> Jan 31st makes sense to me.
>
>
> Best,
> Leonard
>
>
+1 (binding)
On Fri, Dec 16, 2022 at 12:22 PM Martijn Visser
wrote:
> Hi all,
>
> I'm bumping this old vote thread once more.
>
> If we want to add Java 17 support at some point, we will need to update
> our Scala 2.12 version (see
> https://issues.apache.org/jira/browse/FLINK-25000). As
David Anderson created FLINK-30442:
--
Summary: Update table walkthrough playground for 1.12
Key: FLINK-30442
URL: https://issues.apache.org/jira/browse/FLINK-30442
Project: Flink
Issue Type
David Anderson created FLINK-30440:
--
Summary: Update operations playground for 1.16
Key: FLINK-30440
URL: https://issues.apache.org/jira/browse/FLINK-30440
Project: Flink
Issue Type: Sub
David Anderson created FLINK-30441:
--
Summary: Update pyflink walkthrough playground for 1.16
Key: FLINK-30441
URL: https://issues.apache.org/jira/browse/FLINK-30441
Project: Flink
Issue
David Anderson created FLINK-30439:
--
Summary: Update playgrounds for 1.16
Key: FLINK-30439
URL: https://issues.apache.org/jira/browse/FLINK-30439
Project: Flink
Issue Type: Improvement
Martijn,
Thank you for bringing this up. From my (admittedly narrow) perspective,
I'd like to see a release sooner rather than later, as there's an
already merged bug fix I'd like to get released.
David
On Thu, Dec 15, 2022 at 1:53 PM Martijn Visser
wrote:
> Hi everyone,
>
> I would like to
>
> For the partition
> idleness problem could you elaborate more about it? I assume both
> FlinkKafkaConsumer and KafkaSource need a WatermarkStrategy to decide
> whether to mark the partition as idle.
As a matter of fact, no, that's not the case -- which is why I mentioned it.
The
>
> [H]ow one can migrate from the
> FlinkKafkaConsumer/FlinkKafkaProducer to KafkaSource/KafkaSink, while
> preserving exactly-once guarantees etc?
The responses from Fabian Paul in [1] and [2] address the question of how
to handle the migration in terms of managing the state (where the short
+1
On Wed, Oct 12, 2022 at 10:59 PM Martijn Visser
wrote:
> Hi everyone,
>
> I would like to open a vote for dropping Gelly, which was discussed a long
> time ago but never put to a vote [1].
>
> Voting will be open for at least 72 hours.
>
> Best regards,
>
> Martijn
>
+1
On Mon, Oct 17, 2022 at 3:39 PM Martijn Visser
wrote:
> Hi everyone,
>
> I'm hereby opening a vote for FLIP-265 Deprecate and remove Scala API
> support. The related discussion can be found here [1].
>
> Voting will be open for at least 72 hours.
>
> Best regards,
>
> Martijn
>
David Anderson created FLINK-28975:
--
Summary: withIdleness marks all streams from FLIP-27 sources as
idle
Key: FLINK-28975
URL: https://issues.apache.org/jira/browse/FLINK-28975
Project: Flink
I'm in favor of adopting this fix in 1.16.0.
+1
On Tue, Aug 9, 2022 at 7:13 AM tison wrote:
> +1
>
> This looks reasonable.
>
> Best,
> tison.
>
>
> Thomas Weise 于2022年8月9日周二 21:33写道：
>
> > +1 for bumping the Kafka dependency.
> >
> > Flink X.Y.0 releases require thorough testing, so
David Anderson created FLINK-28754:
--
Summary: document that Java 8 is required to build table store
Key: FLINK-28754
URL: https://issues.apache.org/jira/browse/FLINK-28754
Project: Flink
+1
Thank you Chesnay.
On Tue, Jul 19, 2022 at 3:09 PM Alexander Fedulov
wrote:
> +1
> Looking forward to using the API to simplify tests setups.
>
> Best,
> Alexander Fedulov
>
> On Tue, Jul 19, 2022 at 2:31 PM Martijn Visser
> wrote:
>
> > Thanks for creating the FLIP and opening the vote
I've found that with our current tooling it's frustrating to try to write
good end-to-end tests for real-world jobs with multiple sinks.
DataStream#executeAndCollect() is okay for simple pipelines with one sink,
but in my opinion we do need something like FLIP-251.
The proposed interface looks
are available in Jira:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351546
We would like to thank all contributors of the Apache Flink community who
made this release possible!
Regards,
David Anderson
I am pleased to announce that we have approved this release candidate.
There are 7 approving votes, 4 of which are binding:
- Chesnay Schepler (+1 binding)
- Xingbo Huang (+1 non-binding)
- Qingsheng Ren (+1 non-binding)
- Robert Metzger (+1 binding)
- Konstantin Knauf (+1 binding)
- Jingsong Li
Hi everyone,
Please review and vote on release candidate #1 for version 1.15.1, as
follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
The complete staging area is available for your review, which includes:
* JIRA release notes [1],
* the
I'm very happy with this. +1
A lot of SourceFunction implementations used in demos/POC implementations
include a call to sleep(), so adding rate limiting is a good idea, in my
opinion.
Best,
David
On Mon, Jun 20, 2022 at 10:10 AM Qingsheng Ren wrote:
> Hi Alexander,
>
> Thanks for creating
it behaves on the CI for the next few weeks, and
plan a quick Flink 1.15.2 release (most likely something like a month
later).
[1] https://issues.apache.org/jira/browse/FLINK-28060
Best,
David
On Wed, Jun 15, 2022 at 11:37 AM David Anderson
wrote:
> I'm now thinking we should delay 1.1
I'm now thinking we should delay 1.15.1 long enough to see if we can
include a fix for FLINK-28060 [1], which is a serious regression affecting
several Kafka users.
[1] https://issues.apache.org/jira/browse/FLINK-28060
On Fri, Jun 10, 2022 at 12:15 PM David Anderson
wrote:
> Since no one
Thank you for bringing this up!
+1
On Mon, Jun 13, 2022 at 1:48 PM Rui Fan <1996fan...@gmail.com> wrote:
> Strongly +1
>
> Best,
> Rui Fan
>
> On Mon, Jun 13, 2022 at 7:35 PM Martijn Visser
> wrote:
>
> > > BTW, from my knowledge, nothing would happen for HashMapStateBackend,
> > which does
eering to manage the release.
> > > > >
> > > > > Best,
> > > > > Jingsong
> > > > >
> > > > > On Wed, Jun 8, 2022 at 6:21 PM Jark Wu wrote:
> > > > >> Hi David, thank you for driving the release.
> &
be built
> > from
> > > > >>> the
> > > > >>>>>> same
> > > > >>>>>>> pieces?
> > > > >>>>>>> I'm also wondering what handles threading, is that on the
> user
> > or
> &g
I would like to start a discussion on releasing 1.15.1. Flink 1.15 was
released on the 5th of May [1] and so far 43 issues have been resolved,
including several user-facing issues with blocker and critical priorities
[2]. (The recent problem with FileSink rolling policies not working
properly in
now.
> > > >
> > > >
> > > >
> > > > Ingo Bürk 于2022年6月5日 周日05:32写道：
> > > >
> > > > > I +1 everything David said. The new Source API raised the
> complexity
> > > > > significantly. It's great
I'm in favor of this, but I think we need to make it easier to implement
data generators and test sources. As things stand in 1.15, unless you can
be satisfied with using a NumberSequenceSource followed by a map, things
get quite complicated. I looked into reworking the data generators used in
the
I've taken care of this.
David
On Sun, May 22, 2022 at 4:12 AM Shubham Bansal
wrote:
> Hi Everyone,
>
> I am not sure who to reach out for the reviews of these changesets, so I
> am putting this on the mailing list here.
>
> I have raised the review for
> FLINK-27507 -
gt;> interaction
>>> >> experiences. Admittedly, there are questions being repeatedly asked &
>>> >> answered, but TBH I don't think that compares to the benefit of a
>>> >> self-driven user community. I'd really love to see if we can bring
>>
I have mixed feelings about this.
I have been rather visible on stack overflow, and as a result I get a lot
of DMs asking for help. I enjoy helping, but want to do it on a platform
where the responses can be searched and shared.
It is currently the case that good questions on stack overflow
David Anderson created FLINK-27513:
--
Summary: Update table walkthrough playground for 1.15
Key: FLINK-27513
URL: https://issues.apache.org/jira/browse/FLINK-27513
Project: Flink
Issue Type
David Anderson created FLINK-27512:
--
Summary: Update pyflink walkthrough playground for 1.15
Key: FLINK-27512
URL: https://issues.apache.org/jira/browse/FLINK-27512
Project: Flink
Issue
David Anderson created FLINK-27511:
--
Summary: Update operations playground for 1.15
Key: FLINK-27511
URL: https://issues.apache.org/jira/browse/FLINK-27511
Project: Flink
Issue Type: Sub
David Anderson created FLINK-27510:
--
Summary: update playgrounds for Flink 1.15
Key: FLINK-27510
URL: https://issues.apache.org/jira/browse/FLINK-27510
Project: Flink
Issue Type
David Anderson created FLINK-27509:
--
Summary: Update table walkthrough playground for 1.14
Key: FLINK-27509
URL: https://issues.apache.org/jira/browse/FLINK-27509
Project: Flink
Issue Type
David Anderson created FLINK-27508:
--
Summary: Update pyflink walkthrough playground for 1.14
Key: FLINK-27508
URL: https://issues.apache.org/jira/browse/FLINK-27508
Project: Flink
Issue
David Anderson created FLINK-27507:
--
Summary: Update operations playground for 1.14
Key: FLINK-27507
URL: https://issues.apache.org/jira/browse/FLINK-27507
Project: Flink
Issue Type: Sub
David Anderson created FLINK-27506:
--
Summary: update playgrounds for Flink 1.14
Key: FLINK-27506
URL: https://issues.apache.org/jira/browse/FLINK-27506
Project: Flink
Issue Type
David Anderson created FLINK-27456:
--
Summary: mistake and confusion with CEP example in docs
Key: FLINK-27456
URL: https://issues.apache.org/jira/browse/FLINK-27456
Project: Flink
Issue
tate type not limited to `TemporalState`. By this, user can
> specify the namespace
> and the TemporalState is one of the special case that it use timestamp as
> the namespace. I think it will be more extendable.
> What do you think about this ?
>
> Best,
> Aitozi.
>
>
> the namespace. I think it will be more extendable.
> What do you think about this ?
>
> Best,
> Aitozi.
>
> David Anderson 于2022年4月11日周一 20:54写道：
>
> > Greetings, Flink developers.
> >
> > I would like to open up a discussion of a proposal [1] to add a new
an we support expose the namespace
> in
> > > the different state type not limited to `TemporalState`. By this, user
> > can
> > > specify the namespace
> > > and the TemporalState is one of the special case that it use timestamp
> as
> > > the namespa
Greetings, Flink developers.
I would like to open up a discussion of a proposal [1] to add a new kind of
state to Flink.
The goal here is to optimize a fairly common pattern, which is using
MapState>
to store lists of events associated with timestamps. This pattern is used
internally in quite
David Anderson created FLINK-27184:
--
Summary: Optimize IntervalJoinOperator by using temporal state
Key: FLINK-27184
URL: https://issues.apache.org/jira/browse/FLINK-27184
Project: Flink
David Anderson created FLINK-27183:
--
Summary: Optimize CepOperator by using temporal state
Key: FLINK-27183
URL: https://issues.apache.org/jira/browse/FLINK-27183
Project: Flink
Issue Type
David Anderson created FLINK-27182:
--
Summary: Optimize RowTimeSortOperator by using temporal state
Key: FLINK-27182
URL: https://issues.apache.org/jira/browse/FLINK-27182
Project: Flink
David Anderson created FLINK-27181:
--
Summary: Optimize TemporalRowTimeJoinOperator by using temporal
state
Key: FLINK-27181
URL: https://issues.apache.org/jira/browse/FLINK-27181
Project: Flink
David Anderson created FLINK-27180:
--
Summary: Docs for temporal state
Key: FLINK-27180
URL: https://issues.apache.org/jira/browse/FLINK-27180
Project: Flink
Issue Type: Sub-task
David Anderson created FLINK-27179:
--
Summary: Update training example to use temporal state
Key: FLINK-27179
URL: https://issues.apache.org/jira/browse/FLINK-27179
Project: Flink
Issue Type
David Anderson created FLINK-27178:
--
Summary: create examples that use temporal state
Key: FLINK-27178
URL: https://issues.apache.org/jira/browse/FLINK-27178
Project: Flink
Issue Type: Sub
David Anderson created FLINK-27177:
--
Summary: Implement Temporal State
Key: FLINK-27177
URL: https://issues.apache.org/jira/browse/FLINK-27177
Project: Flink
Issue Type: Sub-task
David Anderson created FLINK-27176:
--
Summary: FLIP-220: Temporal State
Key: FLINK-27176
URL: https://issues.apache.org/jira/browse/FLINK-27176
Project: Flink
Issue Type: Improvement
+1
For flink-training we initially tried cloning the scalastyle setup from
flink, but we decided to use spotless + scalafmt instead.
David
On Mon, Mar 7, 2022 at 1:12 PM Timo Walther wrote:
> Big +1
>
> This will improve the contribution experience. Even though we stopped
> adding more Scala
What's the current status of using the Apple Silicon (M1) platform for
Flink development? Have we reached the point where everything "just works",
or do there remain lingering annoyances (or worse)?
In the past, I've seen reports of issues involving, e.g., RocksDB, nodejs,
protobuf, and pyflink.
+1
On Mon, Jan 31, 2022 at 11:47 AM Martijn Visser
wrote:
> Hi everyone,
>
> I would like to open up a vote to remove the Twitter connector in Flink
> 1.15. This was brought up previously for a discussion [1].
>
> The vote will last for at least 72 hours, and will be accepted by
> a consensus
I agree.
The Twitter connector is used in a few (unofficial) tutorials, so if we
remove it that will make it more difficult for those tutorials to be
maintained. On the other hand, if I recall correctly, that connector uses
V1 of the Twitter API, which has been deprecated, so it's really not very
For questions like this one, please address them to either Stack Overflow
or the user mailing list, but not both at once. Those two forums are
appropriate places to get help with using Flink's APIs. And once you've
asked a question, please allow some days for folks to respond before trying
again.
+1 (non-binding)
I'm pleased to see this significant improvement coming along, as well as
the effort made in the FLIP to document what is and isn't supported (and
where ??? remain).
On Wed, Jan 26, 2022 at 10:58 AM Yu Li wrote:
> +1 (binding)
>
> Thanks for driving this Piotr! Just one more
> I have a very similar question to State Processor API. Is it the same
scenario in this case?
> Should it also be working with checkpoints but might be just untested?
I have used the State Processor API with aligned, full checkpoints. There
it has worked just fine.
David
On Thu, Jan 13, 2022
Most of the inquiries I've had about Gelly in recent memory have been from
folks looking for a streaming solution, and it's only been a handful.
+1 for dropping Gelly
David
On Mon, Jan 3, 2022 at 2:41 PM Till Rohrmann wrote:
> I haven't seen any changes or requests to/for Gelly in ages.
For what it's worth, I recently rewrote all of the tests in flink-training
to use assertj, removing a mixture of junit4 assertions and hamcrest in the
process. I chose assertj because I found it to be more expressive and made
the tests more readable.
+1 from me
David
On Fri, Nov 12, 2021 at
David Anderson created FLINK-24478:
--
Summary: gradle quickstart is out-of-date
Key: FLINK-24478
URL: https://issues.apache.org/jira/browse/FLINK-24478
Project: Flink
Issue Type: Improvement
David Anderson created FLINK-24118:
--
Summary: enable TaxiFareGenerator to produce a bounded stream
Key: FLINK-24118
URL: https://issues.apache.org/jira/browse/FLINK-24118
Project: Flink
David Anderson created FLINK-23926:
--
Summary: change TaxiRide data model to have a single timestamp
Key: FLINK-23926
URL: https://issues.apache.org/jira/browse/FLINK-23926
Project: Flink
Most of the table/bundle related classes such as
MapBundleFunction, MapBundleOperator, and CountBundleTrigger aren't marked
as either @Internal or @Public. What was the intention?
I ask because I'm starting to see some interest in using them for
implementing pre-aggregation via the DataStream
David Anderson created FLINK-23840:
--
Summary: Confusing message from
MemCheckpointStreamFactory#checkSize
Key: FLINK-23840
URL: https://issues.apache.org/jira/browse/FLINK-23840
Project: Flink
David Anderson created FLINK-23653:
--
Summary: improve training exercises and tests so they are better
examples
Key: FLINK-23653
URL: https://issues.apache.org/jira/browse/FLINK-23653
Project: Flink
I am hearing quite often from users who are struggling to manage memory
usage, and these are all users using RocksDB. While I don't know for
certain that RocksDB is the cause in every case, from my perspective,
getting the better memory stability of version 6.20 in place is critical.
Regards,
David Anderson created FLINK-23128:
--
Summary: Translate update to operations playground docs to Chinese
Key: FLINK-23128
URL: https://issues.apache.org/jira/browse/FLINK-23128
Project: Flink
David Anderson created FLINK-23100:
--
Summary: Update pyflink walkthrough playground for 1.13
Key: FLINK-23100
URL: https://issues.apache.org/jira/browse/FLINK-23100
Project: Flink
Issue
David Anderson created FLINK-23099:
--
Summary: Update table walkthrough playground for 1.13
Key: FLINK-23099
URL: https://issues.apache.org/jira/browse/FLINK-23099
Project: Flink
Issue Type
David Anderson created FLINK-23098:
--
Summary: Update operations playground for 1.13
Key: FLINK-23098
URL: https://issues.apache.org/jira/browse/FLINK-23098
Project: Flink
Issue Type: Sub
I've been trying to upgrade the pyflink-walkthrough to Flink 1.13.1, but
without any success.
Unless I give it a lot of resources the data generator times out trying to
connect to Kafka. If I give it 6 cores and 11GB (which is about all I can
offer it) it does manage to connect, but then fails
David Anderson created FLINK-23059:
--
Summary: Update playgrounds for Flink 1.13
Key: FLINK-23059
URL: https://issues.apache.org/jira/browse/FLINK-23059
Project: Flink
Issue Type
David Anderson created FLINK-22948:
--
Summary: Scala example for toDataStream does not compile
Key: FLINK-22948
URL: https://issues.apache.org/jira/browse/FLINK-22948
Project: Flink
Issue
David Anderson created FLINK-22894:
--
Summary: Window Top-N should allow n=1
Key: FLINK-22894
URL: https://issues.apache.org/jira/browse/FLINK-22894
Project: Flink
Issue Type: Bug
David Anderson created FLINK-22868:
--
Summary: Update training exercises for 1.13
Key: FLINK-22868
URL: https://issues.apache.org/jira/browse/FLINK-22868
Project: Flink
Issue Type
David Anderson created FLINK-22737:
--
Summary: Add support for CURRENT_WATERMARK to SQL
Key: FLINK-22737
URL: https://issues.apache.org/jira/browse/FLINK-22737
Project: Flink
Issue Type: Sub
David Anderson created FLINK-22543:
--
Summary: layout of exception history tab isn't very usable with
Flink SQL
Key: FLINK-22543
URL: https://issues.apache.org/jira/browse/FLINK-22543
Project: Flink
+1 (non-binding)
Checks:
- I built from source, successfully.
- I tested the new backpressure metrics and UI. I found one non-critical
bug that's been around for years, and for which a fix has already been
merged for 1.13.1 (https://issues.apache.org/jira/browse/FLINK-22489
1 - 100 of 236 matches
Mail list logo
