Márton Balassi created FLINK-1669:
-
Summary: Streaming tests for recovery with distributed process
failure
Key: FLINK-1669
URL: https://issues.apache.org/jira/browse/FLINK-1669
Project: Flink
Stephan Ewen created FLINK-1668:
---
Summary: Add a config option to specify delays between restarts
Key: FLINK-1668
URL: https://issues.apache.org/jira/browse/FLINK-1668
Project: Flink
Issue Type
Thanks for bringing up the discussions, Stephan.
Ufuk and Till had brought up some ideas to solve the example of issues
you mentioned in the original thread.
So In the nutshell, we need to have more strick style and rules
checking for the code to help contributors to submit code change and
maintai
Stephan Ewen created FLINK-1667:
---
Summary: Add tests for recovery with distributed process failure
Key: FLINK-1667
URL: https://issues.apache.org/jira/browse/FLINK-1667
Project: Flink
Issue Typ
Fabian Hueske created FLINK-1666:
Summary: Clean-up Field Expression Code
Key: FLINK-1666
URL: https://issues.apache.org/jira/browse/FLINK-1666
Project: Flink
Issue Type: Bug
Compon
Fabian Hueske created FLINK-1665:
Summary: Add optional annotations for POJOs to specify the order
of fields
Key: FLINK-1665
URL: https://issues.apache.org/jira/browse/FLINK-1665
Project: Flink
Fabian Hueske created FLINK-1664:
Summary: Fix sorting on POJO fields
Key: FLINK-1664
URL: https://issues.apache.org/jira/browse/FLINK-1664
Project: Flink
Issue Type: Bug
Components
Fabian Hueske created FLINK-1663:
Summary: Add a FIFO job scheduler to the JobManager
Key: FLINK-1663
URL: https://issues.apache.org/jira/browse/FLINK-1663
Project: Flink
Issue Type: New Feat
Péter Szabó created FLINK-1662:
--
Summary: NullFieldException is thrown when testing
IterativeDataStream with tuples, windowing and maxBy
Key: FLINK-1662
URL: https://issues.apache.org/jira/browse/FLINK-1662
Thanks Gyula, that helps a lot :D
Nice solution. Thank you Max!
I also support the reduced header size!
Cheers,
Gabor
On Mon, Mar 9, 2015 at 3:36 PM Márton Balassi
wrote:
> +1 for the proposed solution from Max
> +1 for decreasing the size: but let's have preview, I also think that the
> curre
+1 for Scala as a default. Looks much less verbose.
On Mon, Mar 9, 2015 at 3:34 PM, Márton Balassi wrote:
> Then if no objections in 24 hours I'd open a JIRA issue for this.
>
> On Mon, Mar 9, 2015 at 3:23 PM, Till Rohrmann wrote:
>
>> +1 for Scala :-)
>>
>> On Sat, Mar 7, 2015 at 1:56 PM, Márto
+1 for Scala
2015-03-09 15:34 GMT+01:00 Márton Balassi :
> Then if no objections in 24 hours I'd open a JIRA issue for this.
>
> On Mon, Mar 9, 2015 at 3:23 PM, Till Rohrmann
> wrote:
>
> > +1 for Scala :-)
> >
> > On Sat, Mar 7, 2015 at 1:56 PM, Márton Balassi >
> > wrote:
> >
> > > I'm strong
Hey,
Seems like a weird interaction between output splitting and windowing.
Could you please open a JIRA ticket for it?
Thanks,
Marton
On Mon, Mar 9, 2015 at 10:22 AM, Szabó Péter
wrote:
> I'm running the following code and getting the RuntimeException "Emit
> failed due to: org.apache.flink
+1 for the proposed solution from Max
+1 for decreasing the size: but let's have preview, I also think that the
current one is a bit too large
On Mon, Mar 9, 2015 at 2:16 PM, Maximilian Michels wrote:
> We can fix this for the headings by adding the following CSS rule:
>
> h1, h2, h3, h4 {
>
Then if no objections in 24 hours I'd open a JIRA issue for this.
On Mon, Mar 9, 2015 at 3:23 PM, Till Rohrmann wrote:
> +1 for Scala :-)
>
> On Sat, Mar 7, 2015 at 1:56 PM, Márton Balassi
> wrote:
>
> > I'm strongly for consistency and personally would prefer Scala as a
> default
> > - thus ma
+1 for Scala :-)
On Sat, Mar 7, 2015 at 1:56 PM, Márton Balassi
wrote:
> I'm strongly for consistency and personally would prefer Scala as a default
> - thus making the shorter page the default.
>
> On Sat, Mar 7, 2015 at 1:47 PM, Stephan Ewen wrote:
>
> > I think either way is fine as long as
We can fix this for the headings by adding the following CSS rule:
h1, h2, h3, h4 {
padding-top: 100px;
margin-top: -100px;
}
In the course of changing this, we could also reduce the size of the
navigation header in the docs. It is occupies too much space and
doesn't have a lot of functio
I think the navigation looks nice this way.
It's rather a small CSS/HTML problem that the header shades the title when
clicking on an anchor link.
(It's that the content starts at top, but there is the header covering it.)
I'm not much into web stuff, but I would gladly fix it.
Can someone help
That is right, Timo, as far as I would understand it.
On Mon, Mar 9, 2015 at 12:04 PM, Timo Walther wrote:
> Thanks for the clarification. If I have understood it correctly, forwarded
> fields are only interesting for key fields, right? So I will implement that
> key information is passed to the
Thanks for the clarification. If I have understood it correctly,
forwarded fields are only interesting for key fields, right? So I will
implement that key information is passed to the analyzer for consideration.
So if GroupReduce1 is grouped by f1, the result will be
@ForwardedFields("1") in t
Andra Lungu created FLINK-1661:
--
Summary: No Documentation for the isWeaklyConnected() Method
Key: FLINK-1661
URL: https://issues.apache.org/jira/browse/FLINK-1661
Project: Flink
Issue Type: Wis
Ufuk Celebi created FLINK-1660:
--
Summary: MultiTriggerPolicyTest timeout during test
Key: FLINK-1660
URL: https://issues.apache.org/jira/browse/FLINK-1660
Project: Flink
Issue Type: Bug
I also agree that we have too many different ways of doing things. A set of
common rules/ways would definitely be beneficial for the project.
Concerning the command line parsing: I thought that Alexander Alexandrov
wanted to unify the command line parsing by replacing both tools with a
better one.
I'm running the following code and getting the RuntimeException "Emit
failed due to: org.apache.flink.types.NullFieldException: Field 0 is null,
but expected to hold a value."
https://dl.dropboxusercontent.com/u/64242132/TestExample.java
Does somebody know what causes it?
Another issue is that if
Hey Stephan,
On 08 Mar 2015, at 23:17, Stephan Ewen wrote:
> Hi everyone!
>
> I would like to start an open discussion about some issue with the
> heterogeneity of the Flink code base.
Thanks for bringing this up. I agree with your position. The related discussion
about using Guava vs. Valida
I agree. A unified rule-set for code style & formatting would make new
contributions easier. There should be also a configuration guide for
different IDEs.
Peter
2015-03-08 23:17 GMT+01:00 Stephan Ewen :
> Hi everyone!
>
> I would like to start an open discussion about some issue with the
> hete
26 matches
Mail list logo
