(Sounds good, thanks! We'll follow-up there.)
On Tue, Feb 27, 2018 at 10:49 AM, David Morávek
wrote:
> Hi Davor,
>
> sorry for the delay, we were blocked by our legal department. I've send
> both SGA and CCLA to priv...@apache.beam.org, please let me know if you
> need
Hi Davor,
sorry for the delay, we were blocked by our legal department. I've send
both SGA and CCLA to priv...@apache.beam.org, please let me know if you
need anything else.
Regards,
David
On Mon, Feb 19, 2018 at 6:13 AM, Jean-Baptiste Onofré
wrote:
> Hi Davor,
>
> We still
Hi Davor,
We still have some discussion/paperwork on Euphoria side (SGA, ...).
So, it's on track but it takes a little more time than expected.
Regards
JB
On 02/19/2018 05:40 AM, Davor Bonaci wrote:
> I may have missed things, but any update on the progress of this donation?
>
> On Tue, Jan
I may have missed things, but any update on the progress of this donation?
On Tue, Jan 2, 2018 at 10:52 PM, Jean-Baptiste Onofré
wrote:
> Great !
>
> Thanks !
> Regards
> JB
>
> On 01/03/2018 07:29 AM, David Morávek wrote:
>
>> Hello JB,
>>
>> Perfect! I'm already on the Beam
Great !
Thanks !
Regards
JB
On 01/03/2018 07:29 AM, David Morávek wrote:
Hello JB,
Perfect! I'm already on the Beam Slack workspace, I'll contact you once I get to
the office.
Thanks!
D.
On Wed, Jan 3, 2018 at 6:19 AM, Jean-Baptiste Onofré >
Hello JB,
Perfect! I'm already on the Beam Slack workspace, I'll contact you once I
get to the office.
Thanks!
D.
On Wed, Jan 3, 2018 at 6:19 AM, Jean-Baptiste Onofré
wrote:
> Hi David,
>
> absolutely !! Let's move forward on the preparation steps.
>
> Are you on Slack
Hi David,
absolutely !! Let's move forward on the preparation steps.
Are you on Slack and/or hangout to plan this ?
Thanks,
Regards
JB
On 01/02/2018 05:35 PM, David Morávek wrote:
Hello JB,
can we help in any way to move things forward?
Thanks,
D.
On Mon, Dec 18, 2017 at 4:28 PM,
+1 here. I already liked Euphoria, and I like the merger even more :-)
Kenn
On Tue, Jan 2, 2018 at 8:45 AM, Tyler Akidau wrote:
> +1, I'm supportive of seeing this move forward. What remaining concrete
> concerns are there?
>
> -Tyler
>
>
> On Tue, Jan 2, 2018 at 8:35 AM
+1, I'm supportive of seeing this move forward. What remaining concrete
concerns are there?
-Tyler
On Tue, Jan 2, 2018 at 8:35 AM David Morávek
wrote:
> Hello JB,
>
> can we help in any way to move things forward?
>
> Thanks,
> D.
>
> On Mon, Dec 18, 2017 at 4:28 PM,
Hello JB,
can we help in any way to move things forward?
Thanks,
D.
On Mon, Dec 18, 2017 at 4:28 PM, Jean-Baptiste Onofré
wrote:
> Thanks Jan,
>
> It makes sense.
>
> Let me take a look on the code to understand the "interaction".
>
> Regards
> JB
>
>
> On 12/18/2017 04:26
Thanks Jan,
It makes sense.
Let me take a look on the code to understand the "interaction".
Regards
JB
On 12/18/2017 04:26 PM, Jan Lukavský wrote:
Hi JB,
basically you are not wrong. The project started about three or four years ago
with a goal to unify batch and streaming processing into
Hi JB,
basically you are not wrong. The project started about three or four
years ago with a goal to unify batch and streaming processing into
single portable, executor independent API. Because of that, it is
currently "close" to Beam in this sense. But we don't see much added
value keeping
Hi Jan,
Thanks for your answers.
However, they confused me ;)
Regarding what you replied, Euphoria seems like a programming model/SDK "close"
to Beam more than a DSL on top of an existing Beam SDK.
Am I wrong ?
Regards
JB
On 12/18/2017 03:44 PM, Jan Lukavský wrote:
Hi Ismael,
basically
Hi Ismael,
basically we adopted the Beam's design regarding partitioning
(https://github.com/seznam/euphoria/issues/160) and implemented the
sorting manually (https://github.com/seznam/euphoria/issues/158). I'm
not aware of the time model differences (Euphoria supports ingestion and
event
Hi,
It is great to see that you guys have achieved a maturity point to
propose this. Congratulations for your work and the idea to contribute
it into Beam.
I remember from a previous discussion with Jan about the model
mismatch between Euphoria and Beam, because of some design decisions
of both
Depending of the donation, you would need ICLA for each contributor, and CCLA in
addition of SGA.
We can sync with Davor and I for the legal stuff.
However, I would wait a little bit just to have feedback from the whole team and
start a formal vote.
I would be happy to start the formal vote.
Hello,
Thanks for the awesome feedback!
Romain:
We already use Java Stream API in all operators where it makes sense (eg.:
ReduceByKey). Still not sure if it was a good choice, but i can be easily
converted to iterator anyway.
Side outputs support is coming soon, we already made an initial
Hi guys
A DSL would be very welcomed, in particular if fluent.
Open question: did you study to implement Stream API (surely extending it
to have a BeamStream and a few more features like sides etc)? Would be very
natural and integrable easily anywhere and avoid a new API discovery.
Hazelcast
Hi David,
As JB noted, merging of these two projects is a great idea. If fact, some
of us have had those discussions in the past.
Legally, nothing particular is strictly necessary as the code seem to
already be Apache 2.0 licensed. We don't, however, want to be perceived as
making hostile forks,
Hi David,
Generally speaking, having different fluent DSL on top of the Beam SDK is great.
I would like to take a look on your wordcount examples to give you a complete
feedback. I like the idea and a fluent Java DSL is valuable.
Let's wait feedback from others. If we have a consensus, then
Hello,
First of all, thanks for the amazing work the Apache Beam community is
doing!
In 2014, we've started development of the runtime independent Java 8 API,
that helps us to create unified big-data processing flows. It has been used
as a core building block of Seznam.cz web crawler data
21 matches
Mail list logo