Robert Metzger created FLINK-3410:
-
Summary: setting setNumberOfExecutionRetries to 0 still leads to
RESTARTs.
Key: FLINK-3410
URL: https://issues.apache.org/jira/browse/FLINK-3410
Project: Flink
Matthias J. Sax created FLINK-3409:
--
Summary: Integrate STOP with Savepoints
Key: FLINK-3409
URL: https://issues.apache.org/jira/browse/FLINK-3409
Project: Flink
Issue Type: Improvement
Hi,
I've now created a "preview RC" for the upcoming 1.0.0 release.
There are still some blocking issues and important pull requests to be
merged but nevertheless I would like to start testing Flink for the release.
In past major releases, we needed to create many release candidates, often
for fi
Matthias J. Sax created FLINK-3408:
--
Summary: Make STOP signal reliable
Key: FLINK-3408
URL: https://issues.apache.org/jira/browse/FLINK-3408
Project: Flink
Issue Type: Improvement
Matthias J. Sax created FLINK-3407:
--
Summary: Extend TwitterSource with interface StoppableFunction
Key: FLINK-3407
URL: https://issues.apache.org/jira/browse/FLINK-3407
Project: Flink
Issue
Matthias J. Sax created FLINK-3406:
--
Summary: Extend RabbitMQ source with interface StoppableFunction
Key: FLINK-3406
URL: https://issues.apache.org/jira/browse/FLINK-3406
Project: Flink
Iss
Matthias J. Sax created FLINK-3405:
--
Summary: Extend NiFiSource with interface StoppableFunction
Key: FLINK-3405
URL: https://issues.apache.org/jira/browse/FLINK-3405
Project: Flink
Issue Ty
Matthias J. Sax created FLINK-3404:
--
Summary: Extend Kafka consumers with interface StoppableFunction
Key: FLINK-3404
URL: https://issues.apache.org/jira/browse/FLINK-3404
Project: Flink
Iss
Aljoscha Krettek created FLINK-3403:
---
Summary: Create Section "Working with Time" in Streaming Guide
Key: FLINK-3403
URL: https://issues.apache.org/jira/browse/FLINK-3403
Project: Flink
Iss
Aljoscha Krettek created FLINK-3402:
---
Summary: Refactor Common Parts of Stream/Batch Documentation
Key: FLINK-3402
URL: https://issues.apache.org/jira/browse/FLINK-3402
Project: Flink
Issue
I agree with Martin that the original topic of this thread was about how to
keep FlinkML active so that new changes will be promptly merged. The things
we want to implement is then up to the active contributors of FlinkML.
Personally, I would prefer to keep FlinkML as part of Flink's main
reposito
Stephan Ewen created FLINK-3401:
---
Summary: AscendingTimestampExtractor should not fail on order
violation
Key: FLINK-3401
URL: https://issues.apache.org/jira/browse/FLINK-3401
Project: Flink
I
Hi everybody,
I started to sketch the syntax of the streaming Table API.
-->
https://docs.google.com/document/d/19kSOAOINKCSWLBCKRq2WvNtmuaA9o3AyCh2ePqr3V5E/edit?usp=sharing
The draft is of course inspired by the current Table API but also from
Calcite's StreamingSQL draft [1].
In the the versi
Hi,
sorry about not answering but I wanted to wait since I already voiced my
opinion on the PR.
I think it is better to assume an already running redis because it is easier to
work around clashes in running redis instances (ports, data directory, and
such). Then, however, care needs to be taken
Anyone?
Otherwise, I will suggest to move forward with the PR using the
assumption that Redis must be started manually.
-Matthias
On 02/11/2016 08:28 PM, Matthias J. Sax wrote:
> Hi,
>
> In Flink it is possible to have different backends for operator state. I
> am wondering what the best approa
Aljoscha Krettek created FLINK-3400:
---
Summary: RocksDB Backend does not work when not in Flink lib folder
Key: FLINK-3400
URL: https://issues.apache.org/jira/browse/FLINK-3400
Project: Flink
16 matches
Mail list logo
