Wei-Che Wei created FLINK-6211:
--
Summary: Validation error in Kinesis Consumer when using
AT_TIMESTAMP as start position
Key: FLINK-6211
URL: https://issues.apache.org/jira/browse/FLINK-6211
Project: Fli
Ted Yu created FLINK-6210:
-
Summary: RocksDB instance should be closed in
ListViaMergeSpeedMiniBenchmark
Key: FLINK-6210
URL: https://issues.apache.org/jira/browse/FLINK-6210
Project: Flink
Issue Ty
Hi,
How can I pass yarn application tag while running flink on yarn?
Example command: ./bin/flink run -d -m yarn-cluster -yn 4 -yjm 1024 -ytm
4096 examples/batch/WordCount.jar
Thanks,
Praveen
-1 (non-binding)
We recently found out that all jobs submitted via UI will have a
parallelism of 1, potentially due to FLINK-5808.
Filed FLINK-6209 to track it.
~Haohui
On Mon, Mar 27, 2017 at 2:59 AM Chesnay Schepler wrote:
> If possible I would like to include FLINK-6183 & FLINK-6184 as wel
Haohui Mai created FLINK-6209:
-
Summary: StreamPlanEnvironment always has a parallelism of 1
Key: FLINK-6209
URL: https://issues.apache.org/jira/browse/FLINK-6209
Project: Flink
Issue Type: Bug
Dawid Wysakowicz created FLINK-6208:
---
Summary: Implement skip till next match strategy
Key: FLINK-6208
URL: https://issues.apache.org/jira/browse/FLINK-6208
Project: Flink
Issue Type: New F
Stefan Richter created FLINK-6207:
-
Summary: Duplicate type serializers for async snapshots of
CopyOnWriteStateTable
Key: FLINK-6207
URL: https://issues.apache.org/jira/browse/FLINK-6207
Project: Flin
Dan Bress created FLINK-6206:
Summary: As an Engineer, I want task state transition log to be
warn/error for FAILURE scenarios
Key: FLINK-6206
URL: https://issues.apache.org/jira/browse/FLINK-6206
Project
I think your selection of modules is okay.
Moving out storm and the scala shell would be nice as well. But storm is
not really maintained, so maybe we should consider moving it out of the
Flink repo entirely.
And the scala shell is not a library, but it also doesn't really belong
into the main rep
Kostas Kloudas created FLINK-6205:
-
Summary: Put late elements in side output.
Key: FLINK-6205
URL: https://issues.apache.org/jira/browse/FLINK-6205
Project: Flink
Issue Type: Bug
C
This make sense. Only one problem, bahir-flink is not very active. Maybe need
more committee to pay some time on it, and have some new plan.
We also plan to support carbondata[1] in bahir-flink.
By the way, to keep the code base thin, can rewrite flink with Scala step by
step until Flink 2.0 :))
sunjincheng created FLINK-6204:
--
Summary: Improve Event-Time OVER ROWS BETWEEN UNBOUNDED PRECEDING
aggregation to SQL
Key: FLINK-6204
URL: https://issues.apache.org/jira/browse/FLINK-6204
Project: Flink
We are currently looking into how we can keep the size of the code base
under control (because it is growing super large).
Part is moving libraries into a dedicated subrepository (there is a
separate mailing list thread on that) and some connectors to Bahir.
Connectors can move between Flink and B
苏拓 created FLINK-6203:
-
Summary: DataSet Transformations
Key: FLINK-6203
URL: https://issues.apache.org/jira/browse/FLINK-6203
Project: Flink
Issue Type: Bug
Components: DataSet API
Affects
Hi,
Another thought I had last night, maybe we could have another state for
recovering jobs in the future.
Deploying -> Recovering -> Running
This recovering state might only be applicable for state backends that have
to be restored before processing can start, lazy state backends (like
external d
No, we do not want to move all connectors to Apache Bahir or replace the
connectors by Bahir.
The Flink community aims to maintain the most important connectors within
Flink.
Maintaining all connectors would be a huge effort. So, we decided to move
some of the less frequently used connectors to Ba
16 matches
Mail list logo
