Zakelly Lan created FLINK-36589:
---
Summary: Decouple the initialization of sync and async keyed
statebackend
Key: FLINK-36589
URL: https://issues.apache.org/jira/browse/FLINK-36589
Project: Flink
Hi devs,
I'm happy to announce that FLIP-349: Move RocksDB statebackend classes to
o.a.f.state.rocksdb package[1] has been accepted with 4 approving votes,
all of which are binding [2]:
- Gabor Somogyi
- Yuan Mei
- Rui Fan
- Zakelly Lan
And there is no disapproving one.
Thanks t
>
> > G
> >
> >
> > On Mon, Oct 7, 2024 at 6:20 PM Zakelly Lan
> wrote:
> >
> > > Hi everyone,
> > >
> > > I'd like to start a vote on FLIP-349: Move RocksDB statebackend classes
> > to
> > > o.a.f.state.rocksdb
+1 (binding)
Best,
Rui
On Tue, Oct 8, 2024 at 12:28 AM Gabor Somogyi
wrote:
> +1 (binding)
>
> G
>
>
> On Mon, Oct 7, 2024 at 6:20 PM Zakelly Lan wrote:
>
> > Hi everyone,
> >
> > I'd like to start a vote on FLIP-349: Move RocksDB statebackend cla
+1
Best
Yuan
On Tue, Oct 8, 2024 at 12:28 AM Gabor Somogyi
wrote:
> +1 (binding)
>
> G
>
>
> On Mon, Oct 7, 2024 at 6:20 PM Zakelly Lan wrote:
>
> > Hi everyone,
> >
> > I'd like to start a vote on FLIP-349: Move RocksDB statebackend classes
&
+1 (binding)
G
On Mon, Oct 7, 2024 at 6:20 PM Zakelly Lan wrote:
> Hi everyone,
>
> I'd like to start a vote on FLIP-349: Move RocksDB statebackend classes to
> o.a.f.state.rocksdb package [1]. The discussion can be found here [2].
>
> The vote will be open for at leas
Hi everyone,
I'd like to start a vote on FLIP-349: Move RocksDB statebackend classes to
o.a.f.state.rocksdb package [1]. The discussion can be found here [2].
The vote will be open for at least 72 hours unless there are any objections
or insufficient votes.
[1] https://cwiki.apach
> >> >
> >> > Best
> >> > Yun Tang
> >> >
> >> > From: Yu Li
> >> > Sent: Wednesday, July 26, 2023 14:10
> >> > To: dev@flink.apache.org
> >> > Subject: Re: [DISCUSS][2.0
ang 于2023年7月26日周三 14:19写道：
>>
>> > +1 (binding)
>> >
>> > Best
>> > Yun Tang
>> >
>> > From: Yu Li
>> > Sent: Wednesday, July 26, 2023 14:10
>> > To: dev@flink.apache.org
>> > Subject: Re: [DISCUSS][2.0] FLIP-349: Move
Zakelly Lan created FLINK-36376:
---
Summary: More friendly error or warn message for misconfigured
statebackend with async state processing
Key: FLINK-36376
URL: https://issues.apache.org/jira/browse/FLINK-36376
Zakelly Lan created FLINK-36374:
---
Summary: Bundle forst statebackend in flink-dist and provide
shortcut to enable
Key: FLINK-36374
URL: https://issues.apache.org/jira/browse/FLINK-36374
Project: Flink
Xuannan Su created FLINK-36304:
--
Summary: Remove deprecated Statebackend config options
Key: FLINK-36304
URL: https://issues.apache.org/jira/browse/FLINK-36304
Project: Flink
Issue Type: Sub
Junrui Li created FLINK-36251:
-
Summary: Remove StateBackend-related configuration getters/setters
that return/set complex Java objects
Key: FLINK-36251
URL: https://issues.apache.org/jira/browse/FLINK-36251
Hangxiang Yu created FLINK-35044:
Summary: Introduce statebackend-forst module
Key: FLINK-35044
URL: https://issues.apache.org/jira/browse/FLINK-35044
Project: Flink
Issue Type: Sub-task
Hi devs,
I'm happy to announce that FLIP-420: Add API annotations for
RocksDB StateBackend user-facing classes [1] has been accepted with 7
approving votes (4 binding) [2]:
- Yun Tang (binding)
- Jeyhun Karimov (non-binding)
- Hangxiang Yu (binding)
- Yanfei Lei (binding)
- Zakelly Lan
, Mar 7, 2024 at 9:34 AM Yun Tang wrote:
> >> > >
> >> > > > > +1 for this FLIP.
> >> > > > Sorry for not being clear in my previous reply, it's a binding
> vote.
> >> > > >
> >> > > > Best
>
Hi Jing,
Thanks for your feedback!
> I am fine with @Internal and once we
> use @Internal, we should add it to all classes within a module to keep the
> consistency.
I think the scope to keep consistency within a module is all interfaces,
not all classes.
For example, in changelog-sta
2024 at 9:34 AM Yun Tang wrote:
>> > >
>> > > > > +1 for this FLIP.
>> > > > Sorry for not being clear in my previous reply, it's a binding vote.
>> > > >
>> > > > Best
>> > > > Yun Tang
>
Mar 11, 2024 at 9:03 AM Jinzhong Li
wrote:
> Hi Jing.
>
> Thanks for your suggestion.
>
> >> I was wondering if SingleStateIterator and RocksDBRestoreOperation are
> exposed to users even if they are interfaces.
>
> I agree that very very few users implement the
Hi Jing.
Thanks for your suggestion.
>> I was wondering if SingleStateIterator and RocksDBRestoreOperation are
exposed to users even if they are interfaces.
I agree that very very few users implement these two interfaces, except for
some advanced users who implement their own StateB
> > > Best
> > > > Yun Tang
> > > >
> > > > From: Jeyhun Karimov
> > > > Sent: Thursday, March 7, 2024 4:40
> > > > To: dev@flink.apache.org
> > > > Subject: Re: [VOTE] FL
implementation
classes. The flink-statebackend-rocksdb module has many more classes than
the FLIP described. Only adding @Internal annotation to these two
interfaces could be considered as an implicit hint that users can replace
the default behaviour with their own implementation.
Another suggestion is
hursday, March 7, 2024 4:40
> > > To: dev@flink.apache.org
> > > Subject: Re: [VOTE] FLIP-420: Add API annotations for RocksDB
> StateBackend
> > > user-facing classes
> > >
> > > Hi Jinzhong,
> > >
> > > Thanks for the FLIP.
> &
ing vote.
> >
> > Best
> > Yun Tang
> >
> > From: Jeyhun Karimov
> > Sent: Thursday, March 7, 2024 4:40
> > To: dev@flink.apache.org
> > Subject: Re: [VOTE] FLIP-420: Add API annotations for RocksDB StateBackend
> > user-facing classes
> >
>
4:40
> To: dev@flink.apache.org
> Subject: Re: [VOTE] FLIP-420: Add API annotations for RocksDB StateBackend
> user-facing classes
>
> Hi Jinzhong,
>
> Thanks for the FLIP.
>
> +1 (non-binding)
>
> Regards,
> Jeyhun
>
> On Wed, Mar 6, 2024 at 5:09 PM
> +1 for this FLIP.
Sorry for not being clear in my previous reply, it's a binding vote.
Best
Yun Tang
From: Jeyhun Karimov
Sent: Thursday, March 7, 2024 4:40
To: dev@flink.apache.org
Subject: Re: [VOTE] FLIP-420: Add API annotations for RocksDB Stat
ev@flink.apache.org
> Subject: [VOTE] FLIP-420: Add API annotations for RocksDB StateBackend
> user-facing classes
>
> Hi All,
>
> I'd like to start a vote on the FLIP-420: Add API annotations for RocksDB
> StateBackend user-facing classes[1].
> The discussion thread i
+1 for this FLIP.
Best
Yun Tang
From: Jinzhong Li
Sent: Wednesday, March 6, 2024 20:29
To: dev@flink.apache.org
Subject: [VOTE] FLIP-420: Add API annotations for RocksDB StateBackend
user-facing classes
Hi All,
I'd like to start a vote on the FLIP-420
Hi All,
I'd like to start a vote on the FLIP-420: Add API annotations for RocksDB
StateBackend user-facing classes[1].
The discussion thread is here [2].
The vote will be open for at least 72 hours unless there is an objection or
not enough votes.
[1]https://cwiki.apache.org/conflue
/docs/ops/state/large_state_tuning/#tuning-rocksdb-memory
> >
> >
> > Best
> > Yun Tang
> >
> > From: Yanfei Lei
> > Sent: Thursday, February 22, 2024 15:39
> > To: dev@flink.apache.org
> > Subject: Re: [DISCUSS]
rocksdb-memory
>
>
> Best
> Yun Tang
>
> From: Yanfei Lei
> Sent: Thursday, February 22, 2024 15:39
> To: dev@flink.apache.org
> Subject: Re: [DISCUSS]FLIP-420: Add API annotations for RocksDB StateBackend
> user-facing classes
&
://nightlies.apache.org/flink/flink-docs-master/docs/ops/state/large_state_tuning/#tuning-rocksdb-memory
Best
Yun Tang
From: Yanfei Lei
Sent: Thursday, February 22, 2024 15:39
To: dev@flink.apache.org
Subject: Re: [DISCUSS]FLIP-420: Add API annotations for RocksDB StateBackend
user
t; > > *RocksDBStateDownloader
> > > *with @Internal, as they seem to be ordinary classes without interacting
> > > with other modules.
> > > Also, I have reservations about annotating *SingleStateIterator*, but I'd
> > > like to hear others' opinions an
e to hear others' opinions and won't insist on this.
> >
> > Best,
> > Zakelly
> >
> > On Wed, Jan 24, 2024 at 10:26 PM Jinzhong Li
> > wrote:
> >
> > > Hi devs,
> > >
> > > I’m opening this thread to discuss about FLIP-420:
t; >
> > I’m opening this thread to discuss about FLIP-420: Add API annotations
> for
> > RocksDB StateBackend user-facing classes[1].
> >
> > As described in FLINK-18255[2] , several user-facing classes in
> > flink-statebackend-rocksdb module don'
about annotating *SingleStateIterator*, but I'd
like to hear others' opinions and won't insist on this.
Best,
Zakelly
On Wed, Jan 24, 2024 at 10:26 PM Jinzhong Li
wrote:
> Hi devs,
>
> I’m opening this thread to discuss about FLIP-420: Add API annotations for
> RocksDB
Hi devs,
I’m opening this thread to discuss about FLIP-420: Add API annotations for
RocksDB StateBackend user-facing classes[1].
As described in FLINK-18255[2] , several user-facing classes in
flink-statebackend-rocksdb module don't have any API annotations, not even
@PublicEvolving. This
+1,
Best,
Ron
Yun Tang 于2023年7月26日周三 14:19写道：
> +1 (binding)
>
> Best
> Yun Tang
>
> From: Yu Li
> Sent: Wednesday, July 26, 2023 14:10
> To: dev@flink.apache.org
> Subject: Re: [DISCUSS][2.0] FLIP-349: Move Rock
+1 (binding)
Best
Yun Tang
From: Yu Li
Sent: Wednesday, July 26, 2023 14:10
To: dev@flink.apache.org
Subject: Re: [DISCUSS][2.0] FLIP-349: Move RocksDB statebackend classes to
o.a.f.state.rocksdb package
+1
Best Regards,
Yu
On Wed, 26 Jul 2023 at 10:47
+1
> > >
> > >
> > >
> > > > On 24. Jul 2023, at 12:25, Chesnay Schepler
> wrote:
> > > >
> > > > To properly reflect the state of the rocksdb statebackend I propose
> to
> > > move all classes in the state-backend-rocksdb
t;
> Best regards,
> Jing
>
> On Tue, Jul 25, 2023 at 4:29 PM Stefan Richter
> wrote:
>
> >
> > +1
> >
> >
> >
> > > On 24. Jul 2023, at 12:25, Chesnay Schepler wrote:
> > >
> > > To properly reflect the state of the rocksdb stat
make sense.
Best regards,
Jing
On Tue, Jul 25, 2023 at 4:29 PM Stefan Richter
wrote:
>
> +1
>
>
>
> > On 24. Jul 2023, at 12:25, Chesnay Schepler wrote:
> >
> > To properly reflect the state of the rocksdb statebackend I propose to
> move all classes in th
+1
> On 24. Jul 2023, at 12:25, Chesnay Schepler wrote:
>
> To properly reflect the state of the rocksdb statebackend I propose to move
> all classes in the state-backend-rocksdb module under the classes to
> o.a.f.state.rocksdb package.
>
>
> https://ww
+1
Best,
Xintong
On Mon, Jul 24, 2023 at 6:25 PM Chesnay Schepler wrote:
> To properly reflect the state of the rocksdb statebackend I propose to
> move all classes in the state-backend-rocksdb module under the classes
> to o.a.f.state.rocksdb package.
>
>
>
> htt
To properly reflect the state of the rocksdb statebackend I propose to
move all classes in the state-backend-rocksdb module under the classes
to o.a.f.state.rocksdb package.
https://cwiki.apache.org/confluence/display/FLINK/FLIP-349%3A+Move+RocksDB+statebackend+classes+to+o.a.f.state.rocksdb
Yuan Mei created FLINK-32651:
Summary: Benchmark Support for Changelog Statebackend
Key: FLINK-32651
URL: https://issues.apache.org/jira/browse/FLINK-32651
Project: Flink
Issue Type: Improvement
Sergey Nuyanzin created FLINK-30316:
---
Summary: [JUnit5 Migration] Migrate flink-statebackend-common
Key: FLINK-30316
URL: https://issues.apache.org/jira/browse/FLINK-30316
Project: Flink
Hangxiang Yu created FLINK-29776:
Summary: [JUnit5 Migration] Module: flink-statebackend-changelog
Key: FLINK-29776
URL: https://issues.apache.org/jira/browse/FLINK-29776
Project: Flink
Hangxiang Yu created FLINK-29775:
Summary: [JUnit5 Migration] Module: flink-statebackend-rocksdb
Key: FLINK-29775
URL: https://issues.apache.org/jira/browse/FLINK-29775
Project: Flink
Issue
Hangxiang Yu created FLINK-28581:
Summary: Test Changelog StateBackend V2 Manually
Key: FLINK-28581
URL: https://issues.apache.org/jira/browse/FLINK-28581
Project: Flink
Issue Type: Bug
Feifan Wang created FLINK-28178:
---
Summary: Show the delegated StateBackend and whether changelog is
enabled in the UI
Key: FLINK-28178
URL: https://issues.apache.org/jira/browse/FLINK-28178
Project
Chesnay Schepler created FLINK-27470:
Summary: [JUnit5 Migration] Module:
flink-statebackend-heap-spillable
Key: FLINK-27470
URL: https://issues.apache.org/jira/browse/FLINK-27470
Project: Flink
Damian Święcki created FLINK-26876:
--
Summary: flink-statebackend-rocksdb EmbeddedRocksDBStateBackend
crashing on mac m1
Key: FLINK-26876
URL: https://issues.apache.org/jira/browse/FLINK-26876
Roman Khachatryan created FLINK-25750:
-
Summary: Performance regression on 20.01.2021 in globalWindow and
stateBackend benchmarks
Key: FLINK-25750
URL: https://issues.apache.org/jira/browse/FLINK-25750
Piotr Nowojski created FLINK-25744:
--
Summary: Support native savepoints (w/o modifying the statebackend
specific snapshot strategies)
Key: FLINK-25744
URL: https://issues.apache.org/jira/browse/FLINK-25744
Dawid Wysakowicz created FLINK-23534:
Summary: Banned dependencies in flink-statebackend-changelog
Key: FLINK-23534
URL: https://issues.apache.org/jira/browse/FLINK-23534
Project: Flink
Xintong Song created FLINK-23104:
Summary: flink-statebackend-changelog does not build with scala
2.12
Key: FLINK-23104
URL: https://issues.apache.org/jira/browse/FLINK-23104
Project: Flink
levels
- Define explicitly the meaning of "enable flag" = true/false/unset
- Hide ChangelogStateBackend from users
According to the discussion in this thread, we will go with
Option 3: Enable Changelog Statebackend through a Boolean Flag + W/O
ChangelogStateBackend Exposed
this discussion.
> >
> > I prefer option-3 as this is the easiest to understand for users.
> >
> >
> > Best
> > Yun Tang
> > ____
> > From: Roman Khachatryan
> > Sent: Monday, May 31, 2021 16:53
> > To: dev
&
sał(a):
> Hi Yuan, thanks for launching this discussion.
>
> I prefer option-3 as this is the easiest to understand for users.
>
>
> Best
> Yun Tang
>
> From: Roman Khachatryan
> Sent: Monday, May 31, 2021 16:53
> To: dev
> Sub
Hi Yuan, thanks for launching this discussion.
I prefer option-3 as this is the easiest to understand for users.
Best
Yun Tang
From: Roman Khachatryan
Sent: Monday, May 31, 2021 16:53
To: dev
Subject: Re: [DISCUSS][Statebackend][Runtime] Changelog Statebackend
og
> Statebakcend.
>
> As part of FLIP-158[1], Changelog state backend wraps on top of existing
> state backend (HashMapStateBackend, EmbeddedRocksDBStateBackend and may
> expect more) and delegates state changes to the underlying state backends.
> This thread is to discuss the pr
state backends.
This thread is to discuss the problem of how Changelog StateBackend should
be enabled and configured.
Proposed options to enable/config state changelog is listed below:
Option 1: Enable Changelog Statebackend through a Boolean Flag
Option 2: Enable Changelog Statebackend through
Yuan Mei created FLINK-22678:
Summary: Fix Loading Changelog Statebackend with configs set in
job-level and cluster-level separately
Key: FLINK-22678
URL: https://issues.apache.org/jira/browse/FLINK-22678
Seth Wiesman created FLINK-22563:
Summary: Add migration guide for new StateBackend interfaces
Key: FLINK-22563
URL: https://issues.apache.org/jira/browse/FLINK-22563
Project: Flink
Issue
Yun Gao created FLINK-22301:
---
Summary: Statebackend and CheckpointStorage type is not shown in
the Web UI
Key: FLINK-22301
URL: https://issues.apache.org/jira/browse/FLINK-22301
Project: Flink
Yun Tang created FLINK-22146:
Summary: Migrate StateBackend related Chinese docs to latest state
backend
Key: FLINK-22146
URL: https://issues.apache.org/jira/browse/FLINK-22146
Project: Flink
xiaogang zhou created FLINK-22059:
-
Summary: add a new option is rocksdb statebackend to enable job
threads setting
Key: FLINK-22059
URL: https://issues.apache.org/jira/browse/FLINK-22059
Project
Robert Metzger created FLINK-21929:
--
Summary: flink-statebackend-rocksdb crashes with Error occurred in
starting fork
Key: FLINK-21929
URL: https://issues.apache.org/jira/browse/FLINK-21929
Project
Guowei Ma created FLINK-21900:
-
Summary: flink-statebackend-rocksdb test core dump
Key: FLINK-21900
URL: https://issues.apache.org/jira/browse/FLINK-21900
Project: Flink
Issue Type: Bug
Guowei Ma created FLINK-21897:
-
Summary: CalcITCase.testPrimitiveMapType[StateBackend=HEAP] fail
because of "Not enough resources available for scheduling"
Key: FLINK-21897
URL: https://issues.apache.org/j
Jiayi Liao created FLINK-21413:
--
Summary: TtlMapState and TtlListState cannot be clean completely
with Filesystem StateBackend
Key: FLINK-21413
URL: https://issues.apache.org/jira/browse/FLINK-21413
Chesnay Schepler created FLINK-20022:
Summary: Move statebackend tradeoffs to from production readiness
checklist to statebackend page
Key: FLINK-20022
URL: https://issues.apache.org/jira/browse/FLINK-20022
Seth Wiesman created FLINK-18978:
Summary: Support full table scan of key and namespace from
statebackend
Key: FLINK-18978
URL: https://issues.apache.org/jira/browse/FLINK-18978
Project: Flink
Farnight created FLINK-18712:
Summary: Flink RocksDB statebackend memory leak issue
Key: FLINK-18712
URL: https://issues.apache.org/jira/browse/FLINK-18712
Project: Flink
Issue Type: Bug
Xinyuan Liu created FLINK-18165:
---
Summary: When savingpoint is restored, select the checkpoint
directory and stateBackend
Key: FLINK-18165
URL: https://issues.apache.org/jira/browse/FLINK-18165
Project
Dian Fu created FLINK-17923:
---
Summary: It will throw MemoryAllocationException if rocksdb
statebackend and Python UDF are used in the same slot
Key: FLINK-17923
URL: https://issues.apache.org/jira/browse/FLINK-17923
Peidian Li created FLINK-17302:
--
Summary: Add multiget() interface for state of rocksdb
statebackend
Key: FLINK-17302
URL: https://issues.apache.org/jira/browse/FLINK-17302
Project: Flink
Yu Li created FLINK-11833:
-
Summary: Cleanup unnecessary createKeyedStateBackend methods in
StateBackend
Key: FLINK-11833
URL: https://issues.apache.org/jira/browse/FLINK-11833
Project: Flink
Issue
Yun Tang created FLINK-11107:
Summary: [state] Avoid memory stateBackend to create arbitrary
folders under HA path when no checkpoint path configured
Key: FLINK-11107
URL: https://issues.apache.org/jira/browse/FLINK
Gyula Fora created FLINK-10387:
--
Summary: StateBackend create methods should return interface not
abstract KeyedStateBackend classes
Key: FLINK-10387
URL: https://issues.apache.org/jira/browse/FLINK-10387
aitozi created FLINK-10254:
--
Summary: Fix check in stateBackend
Key: FLINK-10254
URL: https://issues.apache.org/jira/browse/FLINK-10254
Project: Flink
Issue Type: Improvement
Components
Bowen Li created FLINK-8189:
---
Summary: move flink-statebackend-rocksdb out of flink-contrib
Key: FLINK-8189
URL: https://issues.apache.org/jira/browse/FLINK-8189
Project: Flink
Issue Type: Sub
Piotr Nowojski created FLINK-7683:
-
Summary: Add method to iterate over all of the existing keys in a
statebackend
Key: FLINK-7683
URL: https://issues.apache.org/jira/browse/FLINK-7683
Project: Flink
Aljoscha Krettek created FLINK-7041:
---
Summary: Deserialize StateBackend from JobCheckpointingSettings
with user classloader
Key: FLINK-7041
URL: https://issues.apache.org/jira/browse/FLINK-7041
Stephan Ewen created FLINK-5823:
---
Summary: Store Checkpoint Root Metadata in StateBackend (not in HA
custom store)
Key: FLINK-5823
URL: https://issues.apache.org/jira/browse/FLINK-5823
Project: Flink
Stephan Ewen created FLINK-5821:
---
Summary: Create StateBackend root interface
Key: FLINK-5821
URL: https://issues.apache.org/jira/browse/FLINK-5821
Project: Flink
Issue Type: Sub-task
Robert Metzger created FLINK-5468:
-
Summary: Restoring from a semi async rocksdb statebackend (1.1) to
1.2 fails with ClassNotFoundException
Key: FLINK-5468
URL: https://issues.apache.org/jira/browse/FLINK-5468
Aljoscha Krettek created FLINK-5240:
---
Summary: Properly Close StateBackend in StreamTask when
closing/canceling
Key: FLINK-5240
URL: https://issues.apache.org/jira/browse/FLINK-5240
Project: Flink
MaGuowei created FLINK-5222:
---
Summary: Rename StateBackend interface to StateBinder
Key: FLINK-5222
URL: https://issues.apache.org/jira/browse/FLINK-5222
Project: Flink
Issue Type: Improvement
Zhijiang Wang created FLINK-5138:
Summary: The StateBackend provides the method to estimate memory
usage based on hint of state size in ResourceSpec
Key: FLINK-5138
URL: https://issues.apache.org/jira/browse
Gyula Fora created FLINK-4441:
-
Summary: RocksDB statebackend makes all operators appear stateful
Key: FLINK-4441
URL: https://issues.apache.org/jira/browse/FLINK-4441
Project: Flink
Issue Type
s for a while for state size scaling reasons
> but have switched to RocksDB later and therefore this statebackend has been
> removed from Flink to cut some maintenance costs.
>
> You can find the initial PR here that contains the description:
> https://github.com/apache/flink/pull/130
Hi,
I have done something similar in the past for storing state in sharded
MySql databases. We used this for a while for state size scaling reasons
but have switched to RocksDB later and therefore this statebackend has been
removed from Flink to cut some maintenance costs.
You can find the
system does not know
> > about any relation between them. We have to introduce such a relation,
> > basically putting the checkpoints into a graph structure that shows the
> > lineage of the checkpoints. Then, when we are cleaning up old checkpoints
> > we check the
t; lineage of the checkpoints. Then, when we are cleaning up old checkpoints
> we check the ranges of (logical) timestamps of the checkpoints that we can
> remove and instruct the StateBackend to remove the relevant ranges.
>
> This leads to another interesting thing. We might need to hav
hen we are cleaning up old checkpoints
we check the ranges of (logical) timestamps of the checkpoints that we can
remove and instruct the StateBackend to remove the relevant ranges.
This leads to another interesting thing. We might need to have a
StateBackend component running in the JobManager t
Hi Aljoscha,
Cool! I created a JIRA for this.
https://issues.apache.org/jira/browse/FLINK-4266
Some comments inline.
Chen
On Mon, Jul 25, 2016 at 2:41 AM, Aljoscha Krettek
wrote:
> Hi,
> I thought there was a Jira for that but I looked and couldn't find it. If
> you'd like you can create one a
Chen Qin created FLINK-4266:
---
Summary: Cassandra Statebackend
Key: FLINK-4266
URL: https://issues.apache.org/jira/browse/FLINK-4266
Project: Flink
Issue Type: New Feature
Components
Hi,
I thought there was a Jira for that but I looked and couldn't find it. If
you'd like you can create one and we can discuss the design. Do you have
any ideas yet?
The tricky things I see in this are:
- Knowing which data is the current data. This will require some kind of
timestamps or increas
1 - 100 of 121 matches
Mail list logo
