Max Michels created FLINK-1624:
--
Summary: Build of old sources fails due to git-commit-id plugin
Key: FLINK-1624
URL: https://issues.apache.org/jira/browse/FLINK-1624
Project: Flink
Issue Type
Max Michels created FLINK-1621:
--
Summary: Create a generalized combine function
Key: FLINK-1621
URL: https://issues.apache.org/jira/browse/FLINK-1621
Project: Flink
Issue Type: Improvement
, and
Flink is taking care of the rest.
As far as I understood it, Hadoop has already all the utilities in place for
getting and transferring the delegation tokens.
Max Michels, another committer in our project has quite a good understanding
of the details there. It would be great if you (Max) could
understanding of Flink usage correct?
Where does the Flink-compiler come into the picture.
Appreciate all the help in advance.
On Wed, Feb 25, 2015 at 4:05 PM, Max Michels m...@apache.org wrote:
Hi Amit,
Nice to hear you're interested in Flink. The first thing you could do
is run the provided
Hi Amit,
Nice to hear you're interested in Flink. The first thing you could do
is run the provided examples. Next, you could try to implement a
simple Flink job yourself. Besides the How to contribute guide, take
a look at the material page [1], the Flink blog [2], and the Data
Artisans blog [3].
Max Michels created FLINK-1599:
--
Summary: TypeComperator
Key: FLINK-1599
URL: https://issues.apache.org/jira/browse/FLINK-1599
Project: Flink
Issue Type: Bug
Components: Distributed
This is a must-have. I would like to take a look at the automatic doc
build infrastructure next week. Basically we have to write some
buildbot rules which issue a build and upload of the docs on a daily
basis.
On Wed, Feb 18, 2015 at 4:53 PM, Robert Metzger rmetz...@apache.org wrote:
Thats
Hi Henry,
I forgot to leave a message stating that I'm fine with Stephan's
changes that would soon be merged into the master. Stephan did not
push to the master immediately, so further comments could have been
made to the pull request.
It would have been more transparent if we had posted the
If we want to have a tight integration with our existing API we have
to hide the results of the expressions behind a wrapper. This enables
us to change the internal implementation at any time and support
future Flink API changes and features.
+1 for not directly exposing the results as a row
+1 The static memory assignment of the network buffer tool caused some
problems for users in the past. Ultimately, dynamic memory management
would be desirable. Until then, let's remove the absolute value
configuration for the network buffers and introduce a parameter to
divide the heap memory
Let me clarify my suggestion: Let's put mandatory tags in the second
line of the commit message. That way, they can be filtered using git
log --grep=TAG and do not take away the first line's 80 characters.
On Wed, Jan 28, 2015 at 3:37 AM, Henry Saputra henry.sapu...@gmail.com wrote:
Just found
, but it seems
to be a problem with the object re-use mode.
– Ufuk
On 20 Jan 2015, at 20:53, Max Michels m...@data-artisans.com wrote:
Hi everyone,
I'm running into some problems implementing a Accumulator for
returning a list of a DataSet.
https://github.com/mxm/flink/tree/count
Let's make it clear that count/collection type of actions execute the
plan up till that point (including the data sinks). From a user
perspective, this seems most logic to me. The user might even rely on
the data generated by the sinks.
On Mon, Jan 19, 2015 at 11:46 AM, Fabian Hueske
+1 for having an optional flink-contrib maven dependency and an
extension repository in the long run.
On Mon, Jan 26, 2015 at 12:00 PM, Robert Metzger rmetz...@apache.org wrote:
I've added a JIRA issue to create the module:
https://issues.apache.org/jira/browse/FLINK-1452
On Mon, Jan 26,
Max Michels created FLINK-1436:
--
Summary: Command-line interface verbose option (-v)
Key: FLINK-1436
URL: https://issues.apache.org/jira/browse/FLINK-1436
Project: Flink
Issue Type: Improvement
Hi Robert,
I like your solution using Travis and Google App Engine. However, I
think there's a much simpler solution which can prevent commiters from
pushing not even compiling or test-failing code to the master in the
first place.
Commiters could simply install a git pre-push hook in their git
16 matches
Mail list logo
