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
By the way, nightly build is not impacted, nor all PRs. I keep you posted.
Regards
JB
On 01/02/2018 07:38 PM, Kenneth Knowles wrote:
Figure anything out? If it keeps happening, maybe we could gather knowledge
about it on a JIRA.
Kenn
On Sun, Dec 31, 2017 at 11:18 PM, Jean-Baptiste Onofré
Hi Charles,
Maybe you can setup data sets and use the TestPipeline to validate (with
PAssert) that it works as expected in your pipeline.
The data sets can be store somewhere (database or filesystem) and loaded in
tests (basically as we do in the Beam ITs).
Thought ?
Regards
JB
On
Hi Kenn,
I will create the Jira and the corresponding PR today.
Regards
JB
On 01/02/2018 07:38 PM, Kenneth Knowles wrote:
Figure anything out? If it keeps happening, maybe we could gather knowledge
about it on a JIRA.
Kenn
On Sun, Dec 31, 2017 at 11:18 PM, Jean-Baptiste Onofré
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,
Hello Beam list!
We are looking at adopting some more advanced use cases with Beam code at
its core including automated testing and data dependency tracking.
Specifically I'm interested in things like making sure data changes don't
break pipelines, or things that depend on pipeline output,
+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 all around. 2017 was excellent, and we're in a great position for 2018
to be even better. Looking forward to it. :-)
On Tue, Jan 2, 2018 at 10:34 AM Kenneth Knowles wrote:
> Happy new year! Very excited for 2018's possibilities. And nice work, JB.
>
> Kenn
>
> On Tue, Jan 2,
Figure anything out? If it keeps happening, maybe we could gather knowledge
about it on a JIRA.
Kenn
On Sun, Dec 31, 2017 at 11:18 PM, Jean-Baptiste Onofré
wrote:
> Hi,
>
> The Spark runner itests fails on Jenkins for some pull requests.
>
> I'm trying to reproduce locally
Happy new year! Very excited for 2018's possibilities. And nice work, JB.
Kenn
On Tue, Jan 2, 2018 at 6:42 AM, Ismaël Mejía wrote:
> Happy new year everyone !
>
> Agree 100% with Davor. 2017 was a good year for the project and it is
> worth to thank everyone who helped to
+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
Happy new year everyone !
Agree 100% with Davor. 2017 was a good year for the project and it is
worth to thank everyone who helped to make the project better.
Now is the time to work to have a great project in 2018 too !
Best wishes to all (and kudos to JB too for the top 5) !
Ismaël
On Mon,
14 matches
Mail list logo