I read some technical docs and have a few more questions.
- Scio is more of a thin Scala wrapper/DSL on top of Java SDK to offer FP
style API similar to Spark/Scalding and a few other features often found in
other Scala libraries, e.g. REPL, macro type providers, Futures. How do
those fit in the b
Nevermind, I just found another post recently answered along these lines.
On Thu, Mar 31, 2016 at 3:01 PM, Prashant Kommireddi <
prkommire...@apache.org> wrote:
> I've recently started reading up a bit on this project and was looking
> through the "How to Contribute" page
> http://beam.incubator.
I've recently started reading up a bit on this project and was looking
through the "How to Contribute" page
http://beam.incubator.apache.org/contribution-guide/
Are there any getting started docs I could refer to start playing with
beam? And may be a few trivial JIRAs I could look into? Would love
On Mon, Mar 28, 2016 at 4:29 PM Robert Bradshaw
wrote:
> On Fri, Mar 25, 2016 at 4:28 PM, Ben Chambers
> wrote:
> > My only concern is that in the example, you first need to declare all the
> > inputs, then the pipeline to be tested, then all the outputs. This can
> lead
> > to tests that are ha
I believe you can guarantee the number of shards (with a more complex set
of transforms). You just need to figure out which shards are empty, and
force the write operation. We can have two implementations of write, one
which doesn't write when zero elements (the default), and one which does go
thro
