Ivan Mushketyk created FLINK-5349:
-
Summary: Fix code sample for Twitter connector
Key: FLINK-5349
URL: https://issues.apache.org/jira/browse/FLINK-5349
Project: Flink
Issue Type: Bug
Jark Wu created FLINK-5348:
--
Summary: Support custom field names for RowTypeInfo
Key: FLINK-5348
URL: https://issues.apache.org/jira/browse/FLINK-5348
Project: Flink
Issue Type: Improvement
Ted Yu created FLINK-5347:
-
Summary: Unclosed stream in
OperatorBackendSerializationProxy#write()
Key: FLINK-5347
URL: https://issues.apache.org/jira/browse/FLINK-5347
Project: Flink
Issue Type: Bug
Stephan Ewen created FLINK-5346:
---
Summary: Remove all ad-hoc config loading via GlobalConfiguration
Key: FLINK-5346
URL: https://issues.apache.org/jira/browse/FLINK-5346
Project: Flink
Issue Ty
Hey,
I'm trying out 1.2 because I need the new Kafka 0.10 connector.
I compiled my job using the SNAPSHOT releases of flink 1.2 and the job
works fine in local mode.
The problem is that deploying the job to our EMR/YARN cluster fails with
a
-
java.lang.VerifyError: Cannot inherit from f
Robert Metzger created FLINK-5345:
-
Summary: IOManager failed to properly clean up temp file directory
Key: FLINK-5345
URL: https://issues.apache.org/jira/browse/FLINK-5345
Project: Flink
Iss
Hey Gabor,
These are some meaningful concerns!
Joining data outside one's scope is somewhat similar to a “goto” statement when
you write imperative code. It certainly allows you to have more complex data
flow but then...programs become arbitrary (nested structures have no meaning).
On top of t
I experienced a quite similar issue with RocksDB on my cluster, also after
some retries (with the Flink 1.1.4 RC3)
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x7f1611829f4e, pid=3545, tid=139732543575808
#
# JRE version: Java(TM) SE Runtime En
Hi Paris and Fouad,
I finally had some time to delve into this. Thanks for the nice proposal!
+1 for also having a CoLoopFunction. That might be useful even if the
input and feedback have the same type, as it might happen that I want
to treat the elements coming on the feedback in a different way
David Anderson created FLINK-5344:
-
Summary: docs don't build in dockerized jekyll
Key: FLINK-5344
URL: https://issues.apache.org/jira/browse/FLINK-5344
Project: Flink
Issue Type: Bug
It's going to be a fun discussion. The most obvious questions have been
brought up already: Release cycles and API stability towards usage by code
in other repositories.
Looking forward :-)
On Thu, Dec 15, 2016 at 11:48 AM, Till Rohrmann
wrote:
> I'm in favour of splitting the project up into m
I'm in favour of splitting the project up into multiple repositories. This
will decrease building and testing time locally as well as on Travis. The
downside, however, will be that if not built together, conflicting changes
between different modules might go unnoticed until the release or the next
Fabian Hueske created FLINK-5343:
Summary: Add option to CsvTableSink to overwrite files
Key: FLINK-5343
URL: https://issues.apache.org/jira/browse/FLINK-5343
Project: Flink
Issue Type: Impro
13 matches
Mail list logo