Hi Ricardo,
you're right. The uploaded jars are not persisted. However, if you enable
HA mode and start a job, then they will be persisted as part of the job
information. If you need to resubmit the job from the web ui, however, you
still need to reupload them after a failover.
Cheers,
Till
On W
Xingcan Cui created FLINK-10323:
---
Summary: A single backslash cannot be successfully parsed in Java
Table API
Key: FLINK-10323
URL: https://issues.apache.org/jira/browse/FLINK-10323
Project: Flink
Till Rohrmann created FLINK-10324:
-
Summary: Replace
ZooKeeperStateHandleStore#getAllSortedByNameAndLock by getAllAndLock
Key: FLINK-10324
URL: https://issues.apache.org/jira/browse/FLINK-10324
Projec
Andrey Zagrebin created FLINK-10325:
---
Summary: [State TTL] Refactor TtlListState to use only loops, no
java stream API for performance
Key: FLINK-10325
URL: https://issues.apache.org/jira/browse/FLINK-10325
Till Rohrmann created FLINK-10326:
-
Summary: Simplify ZooKeeperSubmittedJobGraphStore constructor
Key: FLINK-10326
URL: https://issues.apache.org/jira/browse/FLINK-10326
Project: Flink
Issue
Piotr Nowojski created FLINK-10327:
--
Summary: Pass processWatermark calls from (Co)ProcessOperator to
(Co)ProcessFunction
Key: FLINK-10327
URL: https://issues.apache.org/jira/browse/FLINK-10327
Proje
Till Rohrmann created FLINK-10328:
-
Summary: Stopping the ZooKeeperSubmittedJobGraphStore should
release all currently held locks
Key: FLINK-10328
URL: https://issues.apache.org/jira/browse/FLINK-10328
Till Rohrmann created FLINK-10329:
-
Summary: Fail with exception if job cannot be removed by
ZooKeeperSubmittedJobGraphStore#removeJobGraph
Key: FLINK-10329
URL: https://issues.apache.org/jira/browse/FLINK-10329
