Hi everyone,
Thanks for the feedback!
It sounds like their is positive consensus around the logo. As a next step,
I am working on getting the original design files and will make them
available to the project. ETA is probably next week at this point.
Cheers!
James
On Fri, Feb 19, 2016 at 1:14 A
Nice idea, Amit. We'll definitely need validation suite that applies at the
model level to catch things like aggregating an unbounded collection
without windowing/triggers or not using a deterministic coder for key
grouping. Adding optional hints/suggestions there too could be interesting.
Or alter
I agree with Frances, optimizations are mostly runner-specific, and Beam
will probably provide a library of common (well optimized) graph
transformations and composite transforms.
We could however provide some sort of pipeline "reviewer" by implementing a
PipelineVisitor that reviews the graph of t
The colorful logo looks really nice. The condensed logo is OK in my
opinion. I wonder if we could use a small variant of the colorful logo
instead?
On Thu, Feb 18, 2016 at 9:47 PM, Ufuk Celebi wrote:
> Amazing job!
>
> On Thu, Feb 18, 2016 at 9:39 PM, Stephan Ewen wrote:
>> I like it, too :-)
>>
