Re: [PROPOSAL] Prepare Beam 2.6.0 release

[Reuven Lax]

No problem :) I'm not entirely sure why the PR fixed his issue, but it
couldn't cause any harm so I went ahead and merged it.

On Sun, Jul 29, 2018 at 11:56 AM Jean-Baptiste Onofré 
wrote:

> Yes, it's this one and I planned to do the review tonight.
>
> Just saw that you did the review and merge it. Thanks.
>
> Regards
> JB
>
> On 29/07/2018 19:40, Reuven Lax wrote:
> > Jozef, you reference a pull request in the bug, are you referring to
> > this one?
> >
> > https://github.com/apache/beam/pull/6075/files
> >
> > On Sun, Jul 29, 2018 at 12:13 AM Jozef Vilcek  > > wrote:
> >
> > Hello, is there a change this bug make it into the release?
> >
> > https://issues.apache.org/jira/browse/BEAM-5028
> >
> > On Sat, Jul 28, 2018 at 1:38 AM Pablo Estrada  > > wrote:
> >
> > Hello all,
> > I will start daily updates of progress on the 2.6.0 release.
> > As of today, the main release blockers are issues in Dataflow
> > that are preventing us from cutting the Dataflow workers.
> >
> >   * One issue in Java SDK related to FnAPI. Specifically PR 5709
> > requires Dataflow worker changes[1].
> >   * One issue in the Python SDK related to context management.
> > PR 5356 also requires Dataflow worker changes [2].
> >
> > Please reach out to me if you have any questions.
> > Best
> > -P.
> >
> > [1] https://github.com/apache/beam/pull/5709
> > [2] https://github.com/apache/beam/pull/5356
> >
> >
> > On Thu, Jul 26, 2018 at 2:16 PM Pablo Estrada
> > mailto:pabl...@google.com>> wrote:
> >
> > Hello everyone,
> > I wanted to do an update on the state of the release, as
> > there haven't been news on this for a while.
> > We have found a few issues that broke postcommits a few
> > weeks back, but we hadn't noticed. Some people are tacking
> > these to try to stabilize the release branch[1].
> >
> > In the meantime, the release has been blocked, but Boyuan
> > Zhang has taken advantage of this to code up a few scripts
> > to try and automate release steps. (Thanks Boyuan!). We will
> > try these as soon as the release is unblocked.
> >
> > Best
> > -P.
> >
> > [1] https://github.com/apache/beam/pull/6072
> >
> > On Wed, Jul 18, 2018 at 11:03 AM Pablo Estrada
> > mailto:pabl...@google.com>> wrote:
> >
> > Hello all!
> > I've cut the release branch (release-2.6.0), with some
> > help from Ahmet and Boyuan. From now on, please
> > cherry-pick 2.6.0 blockers into the branch.
> > Now we start stabilizing it.
> >
> > Thanks!
> >
> > -P.
> >
> > On Tue, Jul 17, 2018 at 9:34 PM Jean-Baptiste Onofré
> > mailto:j...@nanthrax.net>> wrote:
> >
> > Hi Pablo,
> >
> > I'm investigating this issue, but it's a little long
> > process.
> >
> > So, I propose you start with the release process,
> > cutting the branch,
> > and then, I will create a cherry-pick PR for this
> one.
> >
> > Regards
> > JB
> >
> > On 17/07/2018 20:19, Pablo Estrada wrote:
> > > Checking once more:
> > > What does the communitythink we should do
> > >
> > about
> https://issues.apache.org/jira/browse/BEAM-4750 ?
> > Should I bump it
> > > to 2.7.0?
> > > Best
> > > -P.
> > >
> > > On Fri, Jul 13, 2018 at 5:15 PM Ahmet Altay
> > mailto:al...@google.com>
> > >  > >> wrote:
> > >
> > >
> >  Update:
> https://issues.apache.org/jira/browse/BEAM-4784 is
> > not a
> > > release blocker, details in the JIRA issue.
> > >
> > > On Fri, Jul 13, 2018 at 11:12 AM, Thomas Weise
> > mailto:t...@apache.org>
> > >  > >> wrote:
> > >
> > > Can one of our Python experts please take
> > a look
> > >
> >  at https://issues.apache.org/jira/browse/BEAM-4784
> > and advise if
> > > this 

Re: Issues with Beam SQL on Spark

[Kai Jiang]

Hi Andrew,

I tried on replacing "jdbc:calcite" to "jdbc:beam" in calcite and
re-shadow. After that, Beam Sql can run on Spark now.
However, I didn't find an approach to modify code during shading Calcite
library. I think second method you mentioned is feasible.
I'll forward this thread to dev@calcite and to see if we can connect
between calcite modules without using the DriverManager.

Best,
Kai
ᐧ

On Tue, Jul 24, 2018 at 1:04 PM Kai Jiang  wrote:

> Thank you Andrew! I will take a look at if it is feasible to rewrite
> "jdbc:calcite:" in Beam's repackaged calcite.
>
> Best,
> Kai
>
> On 2018/07/24 19:08:17, Andrew Pilloud  wrote:
> > I don't really think this is something that involves changes to
> > DriverManager. Beam is causing the problem by relocating calcite's path
> but
> > not also modifying the global state it creates.
> >
> > Andrew
> >
> > On Tue, Jul 24, 2018 at 12:03 PM Kai Jiang  wrote:
> >
> > > Thanks Andrew! It's really helpful. I'll take a try on shade calcite
> with
> > > rewriting the "jdbc:calcite".
> > > I also have a look at the doc of DriverManager. Do you think include
> all
> > > repackaged jdbc driver property setting like below will be helpful?
> > >  jdbc.drivers=org.apache.beam.repackaged.beam.
> > >
> > > Best,
> > > Kai
> > >
> > > On 2018/07/24 16:56:50, Andrew Pilloud  wrote:
> > > > Looks like calcite isn't easily repackageable. This issue can be
> fixed
> > > > either in our shading (by also rewriting the "jdbc:calcite:" string
> when
> > > we
> > > > shade calcite) or in calcite (by not using the driver manager to
> connect
> > > > between calcite modules).
> > > >
> > > > Andrew
> > > >
> > > > On Mon, Jul 23, 2018 at 11:18 PM Kai Jiang 
> wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > I met an issue when I ran Beam SQL on Spark. I want to check and
> see if
> > > > > anyone has same issue with me. I believe let beam sql running on
> spark
> > > is
> > > > > important. If you encountered same problem, it will be really
> helpful
> > > if
> > > > > you could give some inputs.
> > > > >
> > > > > Context:
> > > > > I setup TPC framework to run sql on spark. Code
> > > > > <
> > >
> https://github.com/vectorijk/beam/blob/tpch/sdks/java/extensions/tpc/src/main/java/org/apache/beam/sdk/extensions/tpc/BeamTpc.java
> > > >
> > > > > is simple which just ingests csv data and apply Sql on that. Gradle
> > > > > <
> > >
> https://github.com/vectorijk/beam/blob/tpch/sdks/java/extensions/tpc/build.gradle
> >
> > > setting
> > > > > includes `runner-spark` and necessary libraries.  Exception Stack
> trace
> > > > > <
> https://gist.github.com/vectorijk/849cbcd5bce558e5e7c97916ca4c793a>
> > > shows
> > > > > some details. However, same code can running on Flink and Dataflow
> > > > > successfully.
> > > > >
> > > > > Investigations:
> > > > > BEAM-3386  also
> > > > > describes the similar issue I have. It took me some time on
> > > investigating
> > > > > it. I guess there should be a version conflict between Calcite
> library
> > > in
> > > > > Spark and Beam SQL repackaged Calcite. The version of Calcite
> library
> > > Spark
> > > > > ( * - 2.3.1) used is very old (1.2.0-incubating).
> > > > >
> > > > > After packaging fat jar and submitting it to Spark, Spark
> registered
> > > both
> > > > > old version's calcite jdbc driver and Beam's repackaged jdbc
> driver in
> > > > >
> > > > > registeredDrivers(DriverManager.java#L294 <
> > >
> https://github.com/JetBrains/jdk8u_jdk/blob/master/src/share/classes/java/sql/DriverManager.java#L294
> >).
> > > Jdbc's DriverManager always connects to old version calcite's jdbc in
> spark
> > > instead of beam's repackaged calcite.
> > > > >
> > > > >
> > > > > Looking into Line DriverManager.java#L556 <
> > >
> https://github.com/JetBrains/jdk8u_jdk/blob/master/src/share/classes/java/sql/DriverManager.java#L556
> >
> > > and insert a breakpoint, aClass =
> > > Class.forName(driver.getClass().getName(), true, classLoader);
> > > > >
> > > > > driver.getClass().getName() -> "org.apache.calcite.jdbc.Driver"
> > > > > classLoader only has class 'org.apache.beam.**' and
> > > > > 'org.apache.beam.repackaged.beam_***'. (There is no path of class
> > > > > 'org.apache.calcite.*')
> > > > >
> > > > > Oddly, aClass is assigned with Class
> "org.apache.calcite.jdbc.Driver".
> > > I
> > > > > think it should raise an exception and be skipped. Actually, It did
> > > not.  So
> > > > > this spark's calcite jdbc driver has been connected. All logic
> > > afterwards
> > > > > goes to spark's calcite classpath. I believe that's pivot point.
> > > > >
> > > > > Potentially solutions:
> > > > > *1.* Figure out why DriverManager.java#L556
> > > > > <
> > >
> https://github.com/JetBrains/jdk8u_jdk/blob/master/src/share/classes/java/sql/DriverManager.java#L556
> >
> > > does
> > > > > not throw exception.
> > > > >
> > > > > I guess it is the best option.
> > > > >
> > > > > 2. Upgrade Spark' calcite.
> > 

Re: Beam Docs Contributor

[Kai Jiang]

Welcome Rose!
ᐧ

On Sun, Jul 29, 2018 at 8:53 PM Rui Wang  wrote:

> Welcome!
>
> -Rui
>
> On Sun, Jul 29, 2018 at 7:07 PM Griselda Cuevas  wrote:
>
>> Welcome Rose, very glad to have you in the community :)
>>
>>
>>
>> On Fri, 27 Jul 2018 at 16:29, Ahmet Altay  wrote:
>>
>>> Welcome Rose! Looking forward to your contributions.
>>>
>>> On Fri, Jul 27, 2018 at 4:08 PM, Rose Nguyen 
>>> wrote:
>>>
 Hi all:

 I'm Rose! I've worked on Cloud Dataflow documentation and now I'm
 starting a project to refresh the Beam docs and improve the onboarding
 experience. We're planning on splitting up the programming guide into
 multiple pages, making the docs more accessible for new users. I've got
 lots of ideas for doc improvements, some of which are motivated by the UX
 research, and am excited to share them with you all and work on them.

 I look forward to interacting with everybody in the community. I
 welcome comments, thoughts, feedback, etc.
 --


 Rose Thi Nguyen

   Technical Writer

 (281) 683-6900

>>>
>>>

Re: Beam Docs Contributor

[Rui Wang]

Welcome!

-Rui

On Sun, Jul 29, 2018 at 7:07 PM Griselda Cuevas  wrote:

> Welcome Rose, very glad to have you in the community :)
>
>
>
> On Fri, 27 Jul 2018 at 16:29, Ahmet Altay  wrote:
>
>> Welcome Rose! Looking forward to your contributions.
>>
>> On Fri, Jul 27, 2018 at 4:08 PM, Rose Nguyen  wrote:
>>
>>> Hi all:
>>>
>>> I'm Rose! I've worked on Cloud Dataflow documentation and now I'm
>>> starting a project to refresh the Beam docs and improve the onboarding
>>> experience. We're planning on splitting up the programming guide into
>>> multiple pages, making the docs more accessible for new users. I've got
>>> lots of ideas for doc improvements, some of which are motivated by the UX
>>> research, and am excited to share them with you all and work on them.
>>>
>>> I look forward to interacting with everybody in the community. I welcome
>>> comments, thoughts, feedback, etc.
>>> --
>>>
>>>
>>> Rose Thi Nguyen
>>>
>>>   Technical Writer
>>>
>>> (281) 683-6900
>>>
>>
>>

Re: Beam Docs Contributor

[Griselda Cuevas]

Welcome Rose, very glad to have you in the community :)



On Fri, 27 Jul 2018 at 16:29, Ahmet Altay  wrote:

> Welcome Rose! Looking forward to your contributions.
>
> On Fri, Jul 27, 2018 at 4:08 PM, Rose Nguyen  wrote:
>
>> Hi all:
>>
>> I'm Rose! I've worked on Cloud Dataflow documentation and now I'm
>> starting a project to refresh the Beam docs and improve the onboarding
>> experience. We're planning on splitting up the programming guide into
>> multiple pages, making the docs more accessible for new users. I've got
>> lots of ideas for doc improvements, some of which are motivated by the UX
>> research, and am excited to share them with you all and work on them.
>>
>> I look forward to interacting with everybody in the community. I welcome
>> comments, thoughts, feedback, etc.
>> --
>>
>>
>> Rose Thi Nguyen
>>
>>   Technical Writer
>>
>> (281) 683-6900
>>
>
>

Re: [PROPOSAL] Prepare Beam 2.6.0 release

[Jean-Baptiste Onofré]

Yes, it's this one and I planned to do the review tonight.

Just saw that you did the review and merge it. Thanks.

Regards
JB

On 29/07/2018 19:40, Reuven Lax wrote:
> Jozef, you reference a pull request in the bug, are you referring to
> this one?
> 
> https://github.com/apache/beam/pull/6075/files
> 
> On Sun, Jul 29, 2018 at 12:13 AM Jozef Vilcek  > wrote:
> 
> Hello, is there a change this bug make it into the release?
> 
> https://issues.apache.org/jira/browse/BEAM-5028
> 
> On Sat, Jul 28, 2018 at 1:38 AM Pablo Estrada  > wrote:
> 
> Hello all,
> I will start daily updates of progress on the 2.6.0 release.
> As of today, the main release blockers are issues in Dataflow
> that are preventing us from cutting the Dataflow workers.
> 
>   * One issue in Java SDK related to FnAPI. Specifically PR 5709
> requires Dataflow worker changes[1].
>   * One issue in the Python SDK related to context management.
> PR 5356 also requires Dataflow worker changes [2].
> 
> Please reach out to me if you have any questions.
> Best
> -P.
> 
> [1] https://github.com/apache/beam/pull/5709
> [2] https://github.com/apache/beam/pull/5356
> 
> 
> On Thu, Jul 26, 2018 at 2:16 PM Pablo Estrada
> mailto:pabl...@google.com>> wrote:
> 
> Hello everyone,
> I wanted to do an update on the state of the release, as
> there haven't been news on this for a while.
> We have found a few issues that broke postcommits a few
> weeks back, but we hadn't noticed. Some people are tacking
> these to try to stabilize the release branch[1].
> 
> In the meantime, the release has been blocked, but Boyuan
> Zhang has taken advantage of this to code up a few scripts
> to try and automate release steps. (Thanks Boyuan!). We will
> try these as soon as the release is unblocked.
> 
> Best
> -P.
> 
> [1] https://github.com/apache/beam/pull/6072 
> 
> On Wed, Jul 18, 2018 at 11:03 AM Pablo Estrada
> mailto:pabl...@google.com>> wrote:
> 
> Hello all!
> I've cut the release branch (release-2.6.0), with some
> help from Ahmet and Boyuan. From now on, please
> cherry-pick 2.6.0 blockers into the branch.
> Now we start stabilizing it.
> 
> Thanks!
> 
> -P.
> 
> On Tue, Jul 17, 2018 at 9:34 PM Jean-Baptiste Onofré
> mailto:j...@nanthrax.net>> wrote:
> 
> Hi Pablo,
> 
> I'm investigating this issue, but it's a little long
> process.
> 
> So, I propose you start with the release process, 
> cutting the branch,
> and then, I will create a cherry-pick PR for this one.
> 
> Regards
> JB
> 
> On 17/07/2018 20:19, Pablo Estrada wrote:
> > Checking once more:
> > What does the communitythink we should do
> >
> about https://issues.apache.org/jira/browse/BEAM-4750 ?
> Should I bump it
> > to 2.7.0?
> > Best
> > -P.
> >
> > On Fri, Jul 13, 2018 at 5:15 PM Ahmet Altay
> mailto:al...@google.com>
> >  >> wrote:
> >
> >   
>  Update:  https://issues.apache.org/jira/browse/BEAM-4784 
> is
> not a
> >     release blocker, details in the JIRA issue.
> >
> >     On Fri, Jul 13, 2018 at 11:12 AM, Thomas Weise
> mailto:t...@apache.org>
> >      >> wrote:
> >
> >         Can one of our Python experts please take
> a look
> >       
>  at https://issues.apache.org/jira/browse/BEAM-4784
> and advise if
> >         this should be addressed for the release?
> >
> >         Thanks,
> >         Thomas
> >
> >
> >         On Fri, Jul 13, 2018 at 11:02 AM Ahmet
> Altay mailto:al...@google.com>
> >          

Re: [PROPOSAL] Prepare Beam 2.6.0 release

[Reuven Lax]

Jozef, you reference a pull request in the bug, are you referring to this
one?

https://github.com/apache/beam/pull/6075/files

On Sun, Jul 29, 2018 at 12:13 AM Jozef Vilcek  wrote:

> Hello, is there a change this bug make it into the release?
>
> https://issues.apache.org/jira/browse/BEAM-5028
>
> On Sat, Jul 28, 2018 at 1:38 AM Pablo Estrada  wrote:
>
>> Hello all,
>> I will start daily updates of progress on the 2.6.0 release.
>> As of today, the main release blockers are issues in Dataflow that are
>> preventing us from cutting the Dataflow workers.
>>
>>- One issue in Java SDK related to FnAPI. Specifically PR 5709
>>requires Dataflow worker changes[1].
>>- One issue in the Python SDK related to context management. PR 5356
>>also requires Dataflow worker changes [2].
>>
>> Please reach out to me if you have any questions.
>> Best
>> -P.
>>
>> [1] https://github.com/apache/beam/pull/5709
>> [2] https://github.com/apache/beam/pull/5356
>>
>>
>> On Thu, Jul 26, 2018 at 2:16 PM Pablo Estrada  wrote:
>>
>>> Hello everyone,
>>> I wanted to do an update on the state of the release, as there haven't
>>> been news on this for a while.
>>> We have found a few issues that broke postcommits a few weeks back, but
>>> we hadn't noticed. Some people are tacking these to try to stabilize the
>>> release branch[1].
>>>
>>> In the meantime, the release has been blocked, but Boyuan Zhang has
>>> taken advantage of this to code up a few scripts to try and automate
>>> release steps. (Thanks Boyuan!). We will try these as soon as the release
>>> is unblocked.
>>>
>>> Best
>>> -P.
>>>
>>> [1] https://github.com/apache/beam/pull/6072
>>>
>>> On Wed, Jul 18, 2018 at 11:03 AM Pablo Estrada 
>>> wrote:
>>>
 Hello all!
 I've cut the release branch (release-2.6.0), with some help from Ahmet
 and Boyuan. From now on, please cherry-pick 2.6.0 blockers into the branch.
 Now we start stabilizing it.

 Thanks!

 -P.

 On Tue, Jul 17, 2018 at 9:34 PM Jean-Baptiste Onofré 
 wrote:

> Hi Pablo,
>
> I'm investigating this issue, but it's a little long process.
>
> So, I propose you start with the release process,  cutting the branch,
> and then, I will create a cherry-pick PR for this one.
>
> Regards
> JB
>
> On 17/07/2018 20:19, Pablo Estrada wrote:
> > Checking once more:
> > What does the communitythink we should do
> > about https://issues.apache.org/jira/browse/BEAM-4750 ? Should I
> bump it
> > to 2.7.0?
> > Best
> > -P.
> >
> > On Fri, Jul 13, 2018 at 5:15 PM Ahmet Altay  > > wrote:
> >
> > Update:  https://issues.apache.org/jira/browse/BEAM-4784 is not
> a
> > release blocker, details in the JIRA issue.
> >
> > On Fri, Jul 13, 2018 at 11:12 AM, Thomas Weise  > > wrote:
> >
> > Can one of our Python experts please take a look
> > at https://issues.apache.org/jira/browse/BEAM-4784 and
> advise if
> > this should be addressed for the release?
> >
> > Thanks,
> > Thomas
> >
> >
> > On Fri, Jul 13, 2018 at 11:02 AM Ahmet Altay <
> al...@google.com
> > > wrote:
> >
> >
> >
> > On Fri, Jul 13, 2018 at 10:48 AM, Pablo Estrada
> > mailto:pabl...@google.com>> wrote:
> >
> > Hi all,
> > I've triaged most issues marked for 2.6.0 release.
> I've
> > localized two that need a decision / attention:
> >
> > - https://issues.apache.org/jira/browse/BEAM-4417 -
> > Bigquery IO Numeric Datatype Support. Cham is not
> > available to fix this at the moment, but this is a
> > critical issue. Is anyone able to tackle this /
> should
> > we bump this to next release?
> >
> >
> > I bumped this to the next release. I think Cham will be
> the
> > best person to address it when he is back. And with the
> > regular release cadence, it would not be delayed by much.
> >
> >
> >
> > - https://issues.apache.org/jira/browse/BEAM-4750 -
> > Performance degradation due to some safeguards in
> > beam-sdks-java-core. JB, are you looking to fix this?
> > Should we bump? I had the impression that it was an
> easy
> > fix, but I'm not sure.
> >
> > If you're aware of any other issue that needs to be
> > included as a release blocker, please report it to
> me.
> > Best
> > -P.
> >
> > On Thu, Jul 12, 

Re: [PROPOSAL] Prepare Beam 2.6.0 release

[Jean-Baptiste Onofré]

Hi,

let me take the review as Eugene is off. We will do our best to include
in the release.

Regards
JB

On 29/07/2018 09:12, Jozef Vilcek wrote:
> Hello, is there a change this bug make it into the release?
> 
> https://issues.apache.org/jira/browse/BEAM-5028
> 
> On Sat, Jul 28, 2018 at 1:38 AM Pablo Estrada  > wrote:
> 
> Hello all,
> I will start daily updates of progress on the 2.6.0 release.
> As of today, the main release blockers are issues in Dataflow that
> are preventing us from cutting the Dataflow workers.
> 
>   * One issue in Java SDK related to FnAPI. Specifically PR 5709
> requires Dataflow worker changes[1].
>   * One issue in the Python SDK related to context management. PR
> 5356 also requires Dataflow worker changes [2].
> 
> Please reach out to me if you have any questions.
> Best
> -P.
> 
> [1] https://github.com/apache/beam/pull/5709
> [2] https://github.com/apache/beam/pull/5356
> 
> 
> On Thu, Jul 26, 2018 at 2:16 PM Pablo Estrada  > wrote:
> 
> Hello everyone,
> I wanted to do an update on the state of the release, as there
> haven't been news on this for a while.
> We have found a few issues that broke postcommits a few weeks
> back, but we hadn't noticed. Some people are tacking these to
> try to stabilize the release branch[1].
> 
> In the meantime, the release has been blocked, but Boyuan Zhang
> has taken advantage of this to code up a few scripts to try and
> automate release steps. (Thanks Boyuan!). We will try these as
> soon as the release is unblocked.
> 
> Best
> -P.
> 
> [1] https://github.com/apache/beam/pull/6072 
> 
> On Wed, Jul 18, 2018 at 11:03 AM Pablo Estrada
> mailto:pabl...@google.com>> wrote:
> 
> Hello all!
> I've cut the release branch (release-2.6.0), with some help
> from Ahmet and Boyuan. From now on, please cherry-pick 2.6.0
> blockers into the branch.
> Now we start stabilizing it.
> 
> Thanks!
> 
> -P.
> 
> On Tue, Jul 17, 2018 at 9:34 PM Jean-Baptiste Onofré
> mailto:j...@nanthrax.net>> wrote:
> 
> Hi Pablo,
> 
> I'm investigating this issue, but it's a little long
> process.
> 
> So, I propose you start with the release process, 
> cutting the branch,
> and then, I will create a cherry-pick PR for this one.
> 
> Regards
> JB
> 
> On 17/07/2018 20:19, Pablo Estrada wrote:
> > Checking once more:
> > What does the communitythink we should do
> >
> about https://issues.apache.org/jira/browse/BEAM-4750 ?
> Should I bump it
> > to 2.7.0?
> > Best
> > -P.
> >
> > On Fri, Jul 13, 2018 at 5:15 PM Ahmet Altay
> mailto:al...@google.com>
> > >>
> wrote:
> >
> >   
>  Update:  https://issues.apache.org/jira/browse/BEAM-4784 is
> not a
> >     release blocker, details in the JIRA issue.
> >
> >     On Fri, Jul 13, 2018 at 11:12 AM, Thomas Weise
> mailto:t...@apache.org>
> >     >>
> wrote:
> >
> >         Can one of our Python experts please take a look
> >       
>  at https://issues.apache.org/jira/browse/BEAM-4784 and
> advise if
> >         this should be addressed for the release?
> >
> >         Thanks,
> >         Thomas
> >
> >
> >         On Fri, Jul 13, 2018 at 11:02 AM Ahmet Altay
> mailto:al...@google.com>
> >          >> wrote:
> >
> >
> >
> >             On Fri, Jul 13, 2018 at 10:48 AM, Pablo
> Estrada
> >                >> wrote:
> >
> >                 Hi all,
> >                 I've triaged most issues marked for
> 2.6.0 release. I've
> >                 localized two that need a decision /
> attention:
> 

Re: [PROPOSAL] Prepare Beam 2.6.0 release

[Jozef Vilcek]

Hello, is there a change this bug make it into the release?

https://issues.apache.org/jira/browse/BEAM-5028

On Sat, Jul 28, 2018 at 1:38 AM Pablo Estrada  wrote:

> Hello all,
> I will start daily updates of progress on the 2.6.0 release.
> As of today, the main release blockers are issues in Dataflow that are
> preventing us from cutting the Dataflow workers.
>
>- One issue in Java SDK related to FnAPI. Specifically PR 5709
>requires Dataflow worker changes[1].
>- One issue in the Python SDK related to context management. PR 5356
>also requires Dataflow worker changes [2].
>
> Please reach out to me if you have any questions.
> Best
> -P.
>
> [1] https://github.com/apache/beam/pull/5709
> [2] https://github.com/apache/beam/pull/5356
>
>
> On Thu, Jul 26, 2018 at 2:16 PM Pablo Estrada  wrote:
>
>> Hello everyone,
>> I wanted to do an update on the state of the release, as there haven't
>> been news on this for a while.
>> We have found a few issues that broke postcommits a few weeks back, but
>> we hadn't noticed. Some people are tacking these to try to stabilize the
>> release branch[1].
>>
>> In the meantime, the release has been blocked, but Boyuan Zhang has taken
>> advantage of this to code up a few scripts to try and automate release
>> steps. (Thanks Boyuan!). We will try these as soon as the release is
>> unblocked.
>>
>> Best
>> -P.
>>
>> [1] https://github.com/apache/beam/pull/6072
>>
>> On Wed, Jul 18, 2018 at 11:03 AM Pablo Estrada 
>> wrote:
>>
>>> Hello all!
>>> I've cut the release branch (release-2.6.0), with some help from Ahmet
>>> and Boyuan. From now on, please cherry-pick 2.6.0 blockers into the branch.
>>> Now we start stabilizing it.
>>>
>>> Thanks!
>>>
>>> -P.
>>>
>>> On Tue, Jul 17, 2018 at 9:34 PM Jean-Baptiste Onofré 
>>> wrote:
>>>
 Hi Pablo,

 I'm investigating this issue, but it's a little long process.

 So, I propose you start with the release process,  cutting the branch,
 and then, I will create a cherry-pick PR for this one.

 Regards
 JB

 On 17/07/2018 20:19, Pablo Estrada wrote:
 > Checking once more:
 > What does the communitythink we should do
 > about https://issues.apache.org/jira/browse/BEAM-4750 ? Should I
 bump it
 > to 2.7.0?
 > Best
 > -P.
 >
 > On Fri, Jul 13, 2018 at 5:15 PM Ahmet Altay >>> > > wrote:
 >
 > Update:  https://issues.apache.org/jira/browse/BEAM-4784 is not a
 > release blocker, details in the JIRA issue.
 >
 > On Fri, Jul 13, 2018 at 11:12 AM, Thomas Weise >>> > > wrote:
 >
 > Can one of our Python experts please take a look
 > at https://issues.apache.org/jira/browse/BEAM-4784 and
 advise if
 > this should be addressed for the release?
 >
 > Thanks,
 > Thomas
 >
 >
 > On Fri, Jul 13, 2018 at 11:02 AM Ahmet Altay <
 al...@google.com
 > > wrote:
 >
 >
 >
 > On Fri, Jul 13, 2018 at 10:48 AM, Pablo Estrada
 > mailto:pabl...@google.com>> wrote:
 >
 > Hi all,
 > I've triaged most issues marked for 2.6.0 release.
 I've
 > localized two that need a decision / attention:
 >
 > - https://issues.apache.org/jira/browse/BEAM-4417 -
 > Bigquery IO Numeric Datatype Support. Cham is not
 > available to fix this at the moment, but this is a
 > critical issue. Is anyone able to tackle this / should
 > we bump this to next release?
 >
 >
 > I bumped this to the next release. I think Cham will be
 the
 > best person to address it when he is back. And with the
 > regular release cadence, it would not be delayed by much.
 >
 >
 >
 > - https://issues.apache.org/jira/browse/BEAM-4750 -
 > Performance degradation due to some safeguards in
 > beam-sdks-java-core. JB, are you looking to fix this?
 > Should we bump? I had the impression that it was an
 easy
 > fix, but I'm not sure.
 >
 > If you're aware of any other issue that needs to be
 > included as a release blocker, please report it to me.
 > Best
 > -P.
 >
 > On Thu, Jul 12, 2018 at 2:15 AM Etienne Chauchot
 > mailto:echauc...@apache.org>>
 wrote:
 >
 > +1,
 >
 > Thanks for volunteering Pablo, thanks also to have
 > caught tickets that I forgot to close :)
 >
 > Etienne
 >