Hello,
does this JIRA have a change to be part of 2.7.0 release?
https://issues.apache.org/jira/browse/BEAM-5180
It is rather simple ask, but was not decided yet if attached PR is a
correct way of fixing it.
Thanks,
Jozef
Certainly tracking and managing these are important -- though, is Jira the
best tool for these things?
I do see it useful to put in Jira tickets in for my director to have
conversations on specific topics with people, for consensus building, etc
etc. So, I have seen it work even for non-coding ta
Option #3 "external" would fit the Kubernetes use case we discussed a while
ago also. Container(s) can be part of the same pod and need to find the
runner.
There is another option: "embedded". When the SDK is Java and the runner
Flink (or all the other OSS runners), then harness can (optionally) r
+1 Thanks for volunteering and keeping us in schedule!
On Thu, 23 Aug 2018 at 11:58, Udi Meiri wrote:
> +1
>
> On Mon, Aug 20, 2018 at 3:33 PM Boyuan Zhang wrote:
>
>> +1
>> Thanks for volunteering, Charles!
>>
>> On Mon, Aug 20, 2018 at 3:22 PM Rafael Fernandez
>> wrote:
>>
>>> +1, thanks
Very well, I'll kick this off!
On Thu, 23 Aug 2018 at 16:24, Davor Bonaci wrote:
> I'd like to get input from the PMC on how this should be pursued (people
>>> at the foundation who need to be involved, permissions needed, etc.), could
>>> you advice?
>>>
>>
> Please proceed as you see fit. Noth
>
> I'd like to get input from the PMC on how this should be pursued (people
>> at the foundation who need to be involved, permissions needed, etc.), could
>> you advice?
>>
>
Please proceed as you see fit. Nothing is needed, no restrictions.
NB: the moment vote passes (and/or the mascot is contri
This sounds great to me. Let's get us some wonderful Beam mascot : D
On Thu, Aug 23, 2018 at 2:14 PM Griselda Cuevas wrote:
> Hi Folks,
>
> I'm interested in launching a community contest to design a mascot for
> Apache Beam. I'd like to get input from the PMC on how this should be
> pursued (pe
It would be good to gather data on who the users will be and what they
expect out of it. Beam users appear to be tech savvy early adopters, and
Enterprise users of that class frequently maintain their own patch stacks
of backported fixes and features off of releases. I've been in that world
before
I like the idea of recognizing non-code contributions. These other efforts
have been very helpful.
On Thu, Aug 23, 2018 at 3:07 PM Griselda Cuevas wrote:
> Hi Beam Community,
>
> I'd like to start tracking non-code contributions for Beam, specially
> around these six categories:
> 1) Project Man
Hi Beam Community,
I'd like to start tracking non-code contributions for Beam, specially
around these six categories:
1) Project Management
2) Community Management
3) Advocacy
4) Events & Meetups
5) Documentation
6) Training
The proposal would be to create six boards in Jira, one per proposed
cat
There seems to be a misconfiguration of gradle that is causing a high rate
of failure for the last several weeks in building beam-examples-java and
beam-runners-apex. It appears to be some sort of race condition in building
dependencies. Given that no one has made progress on fixing the root cause,
Hi Folks,
I'm interested in launching a community contest to design a mascot for
Apache Beam. I'd like to get input from the PMC on how this should be
pursued (people at the foundation who need to be involved, permissions
needed, etc.), could you advice?
Here's a point-by-point description of the
+1
On Mon, Aug 20, 2018 at 3:33 PM Boyuan Zhang wrote:
> +1
> Thanks for volunteering, Charles!
>
> On Mon, Aug 20, 2018 at 3:22 PM Rafael Fernandez
> wrote:
>
>> +1, thanks for volunteering, Charles!
>>
>> On Mon, Aug 20, 2018 at 12:09 PM Charles Chen wrote:
>>
>>> Thank you Andrew for pointi
A process-based SDK harness does not IMO imply that the host is fully
provisioned by the SDK/user and invoking the user command line in the
context of the staged files is a critical aspect for it to work. So I
consider staged artifact support needed. Also, I would like to suggest that
we move to a
Tim, thanks for digging into this! There are some complexities fixing the
bug (i.e. Beam currently allows the temp directory to be different than the
target directory), but let's continue discussion on that JIRA.
Reuven
On Thu, Aug 23, 2018 at 6:05 AM Tim Robertson
wrote:
> Thanks for linking t
On Thu, Aug 23, 2018 at 3:47 PM Maximilian Michels wrote:
>
> > Going down this path may start to get fairly involved, with an almost
> > endless list of features that could be requested. Instead, I would
> > suggest we keep process-based execution very simple, and specify bash
> > script (tha
On Thu, Aug 23, 2018 at 6:47 AM Maximilian Michels wrote:
> > Going down this path may start to get fairly involved, with an almost
> > endless list of features that could be requested. Instead, I would
> > suggest we keep process-based execution very simple, and specify bash
> > script (that
> Going down this path may start to get fairly involved, with an almost
> endless list of features that could be requested. Instead, I would
> suggest we keep process-based execution very simple, and specify bash
> script (that sets up the environment and whatever else one may want to
> do) as the
I would see support for staging libraries as optional / nice to have since
that can also be done as part of host provisioning (i.e. in the Python case
a virtual environment was already setup and just needs to be activated).
Depending on how the command that launches the harness is configured,
addi
Thanks for linking this discussion with BEAM-5036 (and transitively to
BEAM-4861 which also comes in to play) Jozek.
What Reuven speculated and Jozek had previously observed is indeed the
major cause. Today I've been testing the effect of a "move" using rename()
instead of a copy() and delete().
Just to recap:
From this and the other thread ("Bootstraping Beam's Job Server") we
got sufficient evidence that process-based execution is a desired feature.
Process-based execution as an alternative to dockerized execution
https://issues.apache.org/jira/browse/BEAM-5187
Which parts are exec
On Thu, Aug 23, 2018 at 1:54 PM Maximilian Michels wrote:
>
> Big +1. Process-based execution should be simple to reason about for
> users.
+1. In fact, this is exactly what the Python local job server does,
with running Docker simply being a particular command line that's
passed down here.
http
One thing to consider that we've talked about in the past. It might make sense
to extend the environment proto and have the SDK be explicit about which kinds
of environment it support
+1 Encoding environment information there is a good idea.
Seems it will create a default docker url even if t
Big +1. Process-based execution should be simple to reason about for
users. The implementation should not be too involved. The user has to
ensure the environment is suitable for process-based execution.
There are some minor features that we should support:
- Activating a virtual environment fo
Just for reference, there is a JIRA open for
FileBasedSink.moveToOutputFiles() and filesystem move behavior
https://issues.apache.org/jira/browse/BEAM-5036
On Wed, Aug 22, 2018 at 9:15 PM Tim Robertson
wrote:
> Reuven, I think you might be on to something
>
> The Beam HadoopFileSystem copy()
Thanks Ismael!
On Thu, Aug 23, 2018 at 11:17 AM, Ismaël Mejía wrote:
> Hi!
>
> You can self assign JIRAs now, I also assigned the one you are working on.
> Good luck with your work !
>
> Ismaël
>
> On Thu, Aug 23, 2018 at 10:05 AM Pascal Gula wrote:
>
>> Dear PMC members,
>> I am currently work
Hi!
You can self assign JIRAs now, I also assigned the one you are working on.
Good luck with your work !
Ismaël
On Thu, Aug 23, 2018 at 10:05 AM Pascal Gula wrote:
> Dear PMC members,
> I am currently working on a Python version of mongoDB IO connector and
> already opened a Jira ticket for t
Hi,I agree that LTS releases are a good thing for users especially because of
the argument given by Ahmet (enterprise
users). Just 2 comments:- It will require a good amount of backports- The LTS
frequency needs to be flexible IMHO but we
must make sure the period between two LTS is acceptable.
E
Dear PMC members,
I am currently working on a Python version of mongoDB IO connector and
already opened a Jira ticket for that purpose (
https://issues.apache.org/jira/browse/BEAM-5148).
Therefore, for management purpose, Chamikara J. asked me to request the
Beam Contributor Role so that he can ass
29 matches
Mail list logo
