Hi All,
build jar file from the beam quickstart. while run the jar on Flinkcluster
got below error.?
anybody got this error?
Could you please help how to resolve this?
root1@master:~/NAI/Tools/flink-1.3.0$ *bin/flink run -c
org.apache.beam.examples.WordCount
/home/root1/NAI/Tools/word-count-beam
Yes, the runner can hold the entire side input in the right way.But it will be
some waste, in the case of large amounts of data.
Best, Jingsong Lee
--From:Lukasz
Cwik Time:2017 Aug 25 (Fri) 23:26To:dev
Cc:JingsongLee Subject:Re:
[
I sent a PR for review with something that I think is a still better option:
https://github.com/apache/beam/pull/3753 +Ben Chambers
Example usage:
p.apply("Read", AvroIO.read(GenericClass.class)
.from(*p.newProvider*(outputFile.getAbsolutePath()
TestPipeline.newProvider() returns a Value
I agree with you Aljoscha, a data driven approach of what features work
based upon test results being summarized and which ones scale based upon
benchmarks seems like a great way to differentiate runners strengths.
On Mon, Aug 28, 2017 at 8:39 AM, Aljoscha Krettek
wrote:
> I like where this is g
Thanks. I think I agree that file-based IOs (at least widely used ones)
should, for convenience, still provide FooIO.read().from(filepattern), and
for performance until SDF has full support in all runners, implement it via
a BoundedSource.
The second case with Create.of(filepattern) illustrates wh
I like where this is going!
Regarding benchmarking, I think we could do this if we had common benchmarking
infrastructure and pipelines that regularly run on different Runners so that we
have up-to-date data.
I think we can also have a more technical section where we show stats on the
level of
Hi Eugene,
+1 to this, it is nice to add this common behavior to all the file-based
IOs. I find the design elegant, I just have one minor API comment, I
would prefer
p.apply(FooIO.read().from(filepattern))
to
p.apply(Create.of(filepattern))
IMHO, it is more readable and analogous to the ot
