+1
What we can already do is to refer the blog posts on the website (it's
what I did on the skeleton, in the news section).
Regards
JB
On 02/12/2016 06:49 PM, James Malone wrote:
Hello everyone,
Now that we have a skeleton website up (horray!) I wanted to raise the idea
of a "Beam Blog." I
Hi Max,
it sounds good to me !
Thanks,
Regards
JB
On 02/12/2016 08:06 PM, Maximilian Michels wrote:
Hi Beamers,
Now that things are getting started and we discuss the technical
vision of Beam, we would like to contribute the Flink runner and start
by sharing some details about the status and
I have the signed SGAs from data Artisans and Cloudera. They were both
awesomely quick (thank you!) I am waiting on the signed Google agreement
and then we should be set. :)
On Fri, Feb 12, 2016 at 5:04 PM, Henry Saputra
wrote:
> I am +1 to add Flink runner early as preview.
>
> Just small remi
I am +1 to add Flink runner early as preview.
Just small reminder to get DataArtisans software grant for the
runner contribution ;)
- Henry
On Friday, February 12, 2016, Maximilian Michels wrote:
> Hi Beamers,
>
> Now that things are getting started and we discuss the technical
> vision of Bea
To follow up on this original message, there's now an item to track this in
the Beam JIRA:
https://issues.apache.org/jira/browse/BEAM-9
Best,
James
On Tue, Feb 9, 2016 at 11:07 AM, Yang, Connie wrote:
> Hi Beamers,
>
> We’re considering adding an Apache Storm Runner to Apache Beam.
>
> *
Thanks for all the feedback! Please keep it coming as needed.
We've gone ahead and created components matching this structure:
https://issues.apache.org/jira/browse/BEAM/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel
We'll work on transition existing state from Google-inter
[I'll be switching to mshields...@apache.org soon.]
Hi Maximilian, I'd be all for including flink-dataflow as flink-beam as
soon as possible.
The current github version of the runner depends on some 'internal' classes
of dataflow 1.0 which have either moved, changed or disappeared in our
(still i
As we set up the JIRA, I've created a placeholder issue to track interest
in a Storm runner:
https://issues.apache.org/jira/browse/BEAM-9
On Wed, Feb 10, 2016 at 9:36 PM, Jean-Baptiste Onofré
wrote:
> Hi Taylor,
>
> In a first time, I would say in Beam (as we do for the other runners).
>
> Later
+1 and +1 to getting a snazzy logo :-)
On Fri, Feb 12, 2016 at 10:14 AM, James Malone <
jamesmal...@google.com.invalid> wrote:
> Yes, absolutely. Especially once we have a logo. :) Right now it's probably
> slightly gloomy-looking.
>
> On Fri, Feb 12, 2016 at 10:12 AM, Maximilian Michels
> wrote
Hi Beamers,
Now that things are getting started and we discuss the technical
vision of Beam, we would like to contribute the Flink runner and start
by sharing some details about the status and the roadmap.
The Flink Runner integrates deeply and naturally with the Dataflow SDK
(the Beam precursor)
Yes, absolutely. Especially once we have a logo. :) Right now it's probably
slightly gloomy-looking.
On Fri, Feb 12, 2016 at 10:12 AM, Maximilian Michels wrote:
> +1 Looks nice.
>
> I'm sure we'll iterate over the design :)
>
> On Fri, Feb 12, 2016 at 6:58 PM, Tyler Akidau wrote:
> > +1
> >
> >
+1 Looks nice.
I'm sure we'll iterate over the design :)
On Fri, Feb 12, 2016 at 6:58 PM, Tyler Akidau wrote:
> +1
>
> -Tyler
>
> On Fri, Feb 12, 2016 at 9:57 AM Amit Sela wrote:
>
>> +1
>>
>> I think we could also publish user's use-case examples and stories. "How we
>> are using Beam" or some
+1
> On 12 Feb 2016, at 18:58, Tyler Akidau wrote:
>
> +1
>
> -Tyler
>
> On Fri, Feb 12, 2016 at 9:57 AM Amit Sela wrote:
>
>> +1
>>
>> I think we could also publish user's use-case examples and stories. "How we
>> are using Beam" or something like that.
>>
>> On Fri, Feb 12, 2016, 19:49 J
+1
-Tyler
On Fri, Feb 12, 2016 at 9:57 AM Amit Sela wrote:
> +1
>
> I think we could also publish user's use-case examples and stories. "How we
> are using Beam" or something like that.
>
> On Fri, Feb 12, 2016, 19:49 James Malone
> wrote:
>
> > Hello everyone,
> >
> > Now that we have a skele
+1
I think we could also publish user's use-case examples and stories. "How we
are using Beam" or something like that.
On Fri, Feb 12, 2016, 19:49 James Malone
wrote:
> Hello everyone,
>
> Now that we have a skeleton website up (horray!) I wanted to raise the idea
> of a "Beam Blog." I am think
Hello everyone,
Now that we have a skeleton website up (horray!) I wanted to raise the idea
of a "Beam Blog." I am thinking this blog is where we can show news, cool
new Beam-things, examples for Apache Beam, and so on. This blog would live
under the project website (http://beam.incubator.apache.o
On Thu, Feb 11, 2016 at 8:53 AM, Maximilian Michels wrote:
> As for the /develop branch, I would suggest to
> make it mandatory to have it in a usable state at all times.
>
+1
If breakage is accidentally committed (as will happen) then a CTR rollback
is a encouraged.
Kenn
17 matches
Mail list logo
