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
Manager (master) to the TaskManagers. This
> way, users only have to be authenticated with Kerberos at the JobManager, 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.
>
Hi Matthias,
Did you really pull from the latest master? I just tried to compile
flink-streaming-examples using "mvn clean compile test-compile" and it
worked.
Best regards,
Max
On Wed, Feb 25, 2015 at 4:13 PM, Matthias J. Sax
wrote:
> Hi,
>
> I tried to build flink-streaming-examples, but got
Max Michels created FLINK-1610:
--
Summary: Java docs do not build
Key: FLINK-1610
URL: https://issues.apache.org/jira/browse/FLINK-1610
Project: Flink
Issue Type: Bug
Components: Build
and overloads
> the task to the worker nodes. Is my 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 wrote:
>
>> Hi Amit,
>>
>>
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]
();
env.execute();
}
}
On Tue, Feb 24, 2015 at 5:43 PM, Max Michels wrote:
> Hi Johannes,
>
> Thanks for your question. You can try to implement the Value interface
> for your Vector PoJo. It has to have an empty constructor and
> implement the write and read m
Hi Johannes,
Thanks for your question. You can try to implement the Value interface
for your Vector PoJo. It has to have an empty constructor and
implement the write and read methods of the interface for
serialization.
Based on your description, I've implemented an example to demonstrate
the use
Totally agree with you Henry. Duplicate class names just add
confusion. However, the actual problem is the lack of documentation
for a lot of classes. It would be great if we could have a
documentation sprint in the near future to at least add a doc string
for every class. This might be some work b
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 wrote:
> Thats indeed a great idea and
+1
On Tue, Feb 17, 2015 at 2:40 PM, Aljoscha Krettek wrote:
> +1
>
> On Tue, Feb 17, 2015 at 1:34 PM, Till Rohrmann wrote:
>> +1
>>
>> On Tue, Feb 17, 2015 at 1:34 PM, Kostas Tzoumas wrote:
>>
>>> +1
>>>
>>> On Tue, Feb 17, 2015 at 12:14 PM, Márton Balassi
>>> wrote:
>>>
>>> > When it comes to
Great contribution! Thanks to everyone who made it possible.
On Wed, Feb 11, 2015 at 12:21 PM, Gyula Fóra wrote:
> Great!
> Thank you guys :)
>
> On Wed, Feb 11, 2015 at 12:17 PM, Vasiliki Kalavri <
> vasilikikala...@gmail.com> wrote:
>
>> Hello everyone,
>>
>> I'm very happy ^^
>> Thank you for
Max Michels created FLINK-1486:
--
Summary: Add a string to the print method to identify output
Key: FLINK-1486
URL: https://issues.apache.org/jira/browse/FLINK-1486
Project: Flink
Issue Type
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 rele
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 DataS
+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 amon
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 wrote:
> Just found out about this, thanks S
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 wrote:
> Thi
gely enough, object re-use is disabled
>> in the config. I don't have time to look further into it now, but it seems
>> to be a problem with the object re-use mode.
>> >
>> > – Ufuk
>> >
>> > On 20 Jan 2015, at 20:53, Max Michels wrote:
>> >
>
>> 2015-01-07 18:15 GMT+01:00 Gyula Fóra :
>>
>>> +1
>>> This was much needed :)
>>> 2015.01.07. 18:10 ezt írta ("Max Michels" ):
>>>
>>> > Nice.
>>> >
>>> >
>>> > On Wed, Jan 7, 2015 at
+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 wrote:
> I've added a JIRA issue to create the module:
> https://issues.apache.org/jira/browse/FLINK-1452
>
>
> On Mon, Jan 26, 2015 at 11:39 AM,
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
Max Michels created FLINK-1427:
--
Summary: Configuration through environment variables
Key: FLINK-1427
URL: https://issues.apache.org/jira/browse/FLINK-1427
Project: Flink
Issue Type
make some changes
$ git push origin
Please commit or stash your pending changes.
Hope this comes in handy for you.
Best regards,
Max
On Wed, Jan 21, 2015 at 1:46 PM, Max Michels wrote:
> @Robert The pre-push hook only resides in your local repository. It
> cannot be pushed. Thus, we canno
@Robert The pre-push hook only resides in your local repository. It
cannot be pushed. Thus, we cannot enforce this check but it certainly
helps to prevent mistakes. As Ufuk mentioned, you can then even skip
the check with the --no-verify option if you're really sure.
On Wed, Jan 21, 2015 at 11:45
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
r
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/collect
Basically, it works fine in this test case:
ExecutionEnvironment env = ExecutionEnvironment.getExecutionEnvironment();
Integer[] in
Hi Kostas,
Thanks for putting this into the wiki. I added the JIRA link for the
off-heap memory. Now the wiki displays:
> Error rendering macro 'jira' :
> com.atlassian.confluence.macro.MacroExecutionException:
> java.lang.RuntimeException: Not Found
If persistent, we should report this.
Is t
Max Michels created FLINK-1406:
--
Summary: Windows compatibility
Key: FLINK-1406
URL: https://issues.apache.org/jira/browse/FLINK-1406
Project: Flink
Issue Type: Improvement
Reporter
Max Michels created FLINK-1379:
--
Summary: add RSS feed for the blog
Key: FLINK-1379
URL: https://issues.apache.org/jira/browse/FLINK-1379
Project: Flink
Issue Type: Improvement
Hi Kostas,
Great post.
I think it would be good to have an additional mailing list for news.
For open source projects, it's pretty common to have an announce
mailing list. In addition to the monthly newsletter we could also
announce releases.
Best regards,
Max
On Fri, Jan 9, 2015 at 12:22 PM, K
33 matches
Mail list logo
