Stephan Ewen created FLINK-2520:
---
Summary: StreamFaultToleranceTestBase does not allow for multiple
tests
Key: FLINK-2520
URL: https://issues.apache.org/jira/browse/FLINK-2520
Project: Flink
Hi!
Nice idea.
It would be good to have this implemented as a kind of service that
components can acquire.
A component that needs time can do something like Clock clock =
ClockService.aquire(), which increments a reference count in the central
clock service and starts the thread if it has not
Nezih Yigitbasi created FLINK-2517:
--
Summary: Wrong KafkaSink arguments in streaming guide
Key: FLINK-2517
URL: https://issues.apache.org/jira/browse/FLINK-2517
Project: Flink
Issue Type:
+1 for proposal (2)
On Fri, Aug 14, 2015 at 10:28 AM, Fabian Hueske fhue...@gmail.com wrote:
Hi Liang Chen,
thanks for starting this discussion.
I have no strong preference for one of your proposals. Both are fine with
me.
What would proposal 2 mean if we add examples for other API
Thank you Fengbin Fang for doing this microbenchmark!
The numbers clearly show that your approach is a lot faster.
I'm curious if this does also affect the performance of a complete data
flow.
Looking forward to your results,
Fabian
2015-08-13 8:35 GMT+02:00 Fangfengbin fangfeng...@huawei.com:
In case of merging we would have to add a `scala` tag to some of the
examples because some of the examples exist in both packages. The drawback
of merging both examples modules is that we'll have another mixed
Java/Scala project. This might be bothering for the eclipse folks, but we
already have
Hello,
I would like to submit an abstract to Flink Forward, but the webpage
of the conference (flink-forward.org) seems to be down. It prints
Error establishing a database connection for me. It worked
yesterday.
Best regards,
Gabor
Stephan Ewen created FLINK-2524:
---
Summary: Add getTaskNameWithSubtasks() to RuntimeContext
Key: FLINK-2524
URL: https://issues.apache.org/jira/browse/FLINK-2524
Project: Flink
Issue Type:
A big part of the cost of currentTimeMillis() is that it does a lot of work
to make sure that the time is really time.
If you only need a monotonic timer, nanoTime() might be what you want
instead of currentTimeMillis(). nanoTime() is particularly handy when you
want to avoid issues to do with
In many cases, we actually need a proper timestamp (for example for
timestamps in streaming records).
I just ran a small micro-benchmark (Java 8, Linux kernel 3.11, 64bit VM)
Making 5,000,000 function calls
System.currentTimeMillis() took: 13240msecs
System.nanoTime() took: 13355msecs
At least
fangfengbin created FLINK-2525:
--
Summary: Add configuration support in Storm-compatibility
Key: FLINK-2525
URL: https://issues.apache.org/jira/browse/FLINK-2525
Project: Flink
Issue Type: New
Sounds good to me +1
On Fri, Aug 14, 2015 at 11:06 AM, Stephan Ewen se...@apache.org wrote:
Concerning mixed projects: Should be okay even for Eclipse users, because
no Scala code is referenced from Java code (that is the tricky part).
Even for someone without a Scala IDE plugin, they would
Till Rohrmann created FLINK-2521:
Summary: Add automatic test name logging for tests
Key: FLINK-2521
URL: https://issues.apache.org/jira/browse/FLINK-2521
Project: Flink
Issue Type:
Till Rohrmann created FLINK-2518:
Summary: Avoid predetermination of ports for network services
Key: FLINK-2518
URL: https://issues.apache.org/jira/browse/FLINK-2518
Project: Flink
Issue
Stephan Ewen created FLINK-2519:
---
Summary: BarrierBuffers get stuck infinitely when some inputs end
early
Key: FLINK-2519
URL: https://issues.apache.org/jira/browse/FLINK-2519
Project: Flink
Nikolaas Steenbergen created FLINK-2522:
---
Summary: Integrate Streaming Api into Flink-scala-shell
Key: FLINK-2522
URL: https://issues.apache.org/jira/browse/FLINK-2522
Project: Flink
16 matches
Mail list logo
