Re: [VOTE] Release Apache Spark 2.3.3 (RC1)

2019-01-31 Thread Takeshi Yamamuro
Thanks for letting me know, Jungtaek!
OK, I'll start to test branch-2.3 by myself and prepare the RC2 package
this weekend.
I'll open the next vote then.

Best,
Takeshi

On Thu, Jan 31, 2019 at 8:54 AM Jungtaek Lim  wrote:

> Please proceed without SPARK-26154 given that it is unlikely expected to
> get merged in one week. The patch needs some more work, and we still
> haven't reached consensus on the approach.
>
> Btw, could one of committer justify and modify the priority and
> correctness label on SPARK-26154? I mentioned some committers before and
> got no response.
>
> 2019년 1월 29일 (화) 오전 10:23, Takeshi Yamamuro 님이 작성:
>
>> If there is no objection in following responses, I'll wait one more week
>> while watching that PR progress.
>> Once that PR merged, I'll start to prepare the next vote.
>>
>>
>>
>> On Tue, Jan 29, 2019 at 4:57 AM Jungtaek Lim  wrote:
>>
>>> Regarding PR 23634, it is waiting for getting consensus on the approach
>>> for the fix, as well as it also needs to have some time to clean up some
>>> code and move focus to concern backward compatibility. I'm postponing these
>>> works since I haven't reached consensus on the approach.
>>>
>>> So it may take some days or even some weeks to get PR 23634 merged (if
>>> consensus will not be made in time).
>>>
>>> 2019년 1월 29일 (화) 오전 2:18, Sean Owen 님이 작성:
>>>
 More analysis at https://github.com/apache/spark/pull/23634
 It's not a regression, though it does relate to correctness, although
 somewhat niche.
 TD, Jose et al, is this a Blocker? and is the fix probably reliable
 enough to commit now?

 On Mon, Jan 28, 2019 at 10:59 AM Sandeep Katta
  wrote:
 >
 > I feel this https://issues.apache.org/jira/browse/SPARK-26154 bug
 should be fixed in this release as it is related to data correctness
 >
 > On Mon, 28 Jan 2019 at 17:55, Takeshi Yamamuro 
 wrote:
 >>
 >> Hi, all
 >>
 >> I checked the two issues below had been resolved and there is no
 blocker for branch-2.3 now, so I'll start prepare RC2 tomorrow.
 >> https://issues.apache.org/jira/browse/SPARK-26682
 >> https://issues.apache.org/jira/browse/SPARK-26709
 >>
 >> If there are some blockers and critical issues in branch-2.3, please
 let me know.
 >>
 >> Best,
 >> Takeshi
 >>
 >> On Thu, Jan 24, 2019 at 10:06 AM Takeshi Yamamuro <
 linguin@gmail.com> wrote:
 >>>
 >>> Thanks, all.
 >>>
 >>> I'll start a new vote as rc2 after the two issues above resolved.
 >>>
 >>> Best,
 >>> Takeshi
 >>>
 >>>
 >>> On Thu, Jan 24, 2019 at 7:59 AM Xiao Li 
 wrote:
 
  -1
 
  https://issues.apache.org/jira/browse/SPARK-26709 is another
 blocker ticket that returns incorrect results.
 
 
  Marcelo Vanzin  于2019年1月23日周三
 下午12:01写道:
 >
 > -1 too.
 >
 > I just upgraded https://issues.apache.org/jira/browse/SPARK-26682
 to
 > blocker. It's a small fix and we should make it in 2.3.3.
 >
 > On Thu, Jan 17, 2019 at 6:49 PM Takeshi Yamamuro <
 linguin@gmail.com> wrote:
 > >
 > > Please vote on releasing the following candidate as Apache
 Spark version 2.3.3.
 > >
 > > The vote is open until January 20 8:00PM (PST) and passes if a
 majority +1 PMC votes are cast, with
 > > a minimum of 3 +1 votes.
 > >
 > > [ ] +1 Release this package as Apache Spark 2.3.3
 > > [ ] -1 Do not release this package because ...
 > >
 > > To learn more about Apache Spark, please see
 http://spark.apache.org/
 > >
 > > The tag to be voted on is v2.3.3-rc1 (commit
 b5ea9330e3072e99841270b10dc1d2248127064b):
 > > https://github.com/apache/spark/tree/v2.3.3-rc1
 > >
 > > The release files, including signatures, digests, etc. can be
 found at:
 > > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-bin/
 > >
 > > Signatures used for Spark RCs can be found in this file:
 > > https://dist.apache.org/repos/dist/dev/spark/KEYS
 > >
 > > The staging repository for this release can be found at:
 > >
 https://repository.apache.org/content/repositories/orgapachespark-1297
 > >
 > > The documentation corresponding to this release can be found at:
 > > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-docs/
 > >
 > > The list of bug fixes going into 2.3.3 can be found at the
 following URL:
 > > https://issues.apache.org/jira/projects/SPARK/versions/12343759
 > >
 > > FAQ
 > >
 > > =
 > > How can I help test this release?
 > > =
 > >
 > > If you are a Spark user, you can help us test this 

Re: [VOTE] Release Apache Spark 2.3.3 (RC1)

2019-01-30 Thread Jungtaek Lim
Please proceed without SPARK-26154 given that it is unlikely expected to
get merged in one week. The patch needs some more work, and we still
haven't reached consensus on the approach.

Btw, could one of committer justify and modify the priority and correctness
label on SPARK-26154? I mentioned some committers before and got no
response.

2019년 1월 29일 (화) 오전 10:23, Takeshi Yamamuro 님이 작성:

> If there is no objection in following responses, I'll wait one more week
> while watching that PR progress.
> Once that PR merged, I'll start to prepare the next vote.
>
>
>
> On Tue, Jan 29, 2019 at 4:57 AM Jungtaek Lim  wrote:
>
>> Regarding PR 23634, it is waiting for getting consensus on the approach
>> for the fix, as well as it also needs to have some time to clean up some
>> code and move focus to concern backward compatibility. I'm postponing these
>> works since I haven't reached consensus on the approach.
>>
>> So it may take some days or even some weeks to get PR 23634 merged (if
>> consensus will not be made in time).
>>
>> 2019년 1월 29일 (화) 오전 2:18, Sean Owen 님이 작성:
>>
>>> More analysis at https://github.com/apache/spark/pull/23634
>>> It's not a regression, though it does relate to correctness, although
>>> somewhat niche.
>>> TD, Jose et al, is this a Blocker? and is the fix probably reliable
>>> enough to commit now?
>>>
>>> On Mon, Jan 28, 2019 at 10:59 AM Sandeep Katta
>>>  wrote:
>>> >
>>> > I feel this https://issues.apache.org/jira/browse/SPARK-26154 bug
>>> should be fixed in this release as it is related to data correctness
>>> >
>>> > On Mon, 28 Jan 2019 at 17:55, Takeshi Yamamuro 
>>> wrote:
>>> >>
>>> >> Hi, all
>>> >>
>>> >> I checked the two issues below had been resolved and there is no
>>> blocker for branch-2.3 now, so I'll start prepare RC2 tomorrow.
>>> >> https://issues.apache.org/jira/browse/SPARK-26682
>>> >> https://issues.apache.org/jira/browse/SPARK-26709
>>> >>
>>> >> If there are some blockers and critical issues in branch-2.3, please
>>> let me know.
>>> >>
>>> >> Best,
>>> >> Takeshi
>>> >>
>>> >> On Thu, Jan 24, 2019 at 10:06 AM Takeshi Yamamuro <
>>> linguin@gmail.com> wrote:
>>> >>>
>>> >>> Thanks, all.
>>> >>>
>>> >>> I'll start a new vote as rc2 after the two issues above resolved.
>>> >>>
>>> >>> Best,
>>> >>> Takeshi
>>> >>>
>>> >>>
>>> >>> On Thu, Jan 24, 2019 at 7:59 AM Xiao Li 
>>> wrote:
>>> 
>>>  -1
>>> 
>>>  https://issues.apache.org/jira/browse/SPARK-26709 is another
>>> blocker ticket that returns incorrect results.
>>> 
>>> 
>>>  Marcelo Vanzin  于2019年1月23日周三
>>> 下午12:01写道:
>>> >
>>> > -1 too.
>>> >
>>> > I just upgraded https://issues.apache.org/jira/browse/SPARK-26682
>>> to
>>> > blocker. It's a small fix and we should make it in 2.3.3.
>>> >
>>> > On Thu, Jan 17, 2019 at 6:49 PM Takeshi Yamamuro <
>>> linguin@gmail.com> wrote:
>>> > >
>>> > > Please vote on releasing the following candidate as Apache Spark
>>> version 2.3.3.
>>> > >
>>> > > The vote is open until January 20 8:00PM (PST) and passes if a
>>> majority +1 PMC votes are cast, with
>>> > > a minimum of 3 +1 votes.
>>> > >
>>> > > [ ] +1 Release this package as Apache Spark 2.3.3
>>> > > [ ] -1 Do not release this package because ...
>>> > >
>>> > > To learn more about Apache Spark, please see
>>> http://spark.apache.org/
>>> > >
>>> > > The tag to be voted on is v2.3.3-rc1 (commit
>>> b5ea9330e3072e99841270b10dc1d2248127064b):
>>> > > https://github.com/apache/spark/tree/v2.3.3-rc1
>>> > >
>>> > > The release files, including signatures, digests, etc. can be
>>> found at:
>>> > > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-bin/
>>> > >
>>> > > Signatures used for Spark RCs can be found in this file:
>>> > > https://dist.apache.org/repos/dist/dev/spark/KEYS
>>> > >
>>> > > The staging repository for this release can be found at:
>>> > >
>>> https://repository.apache.org/content/repositories/orgapachespark-1297
>>> > >
>>> > > The documentation corresponding to this release can be found at:
>>> > > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-docs/
>>> > >
>>> > > The list of bug fixes going into 2.3.3 can be found at the
>>> following URL:
>>> > > https://issues.apache.org/jira/projects/SPARK/versions/12343759
>>> > >
>>> > > FAQ
>>> > >
>>> > > =
>>> > > How can I help test this release?
>>> > > =
>>> > >
>>> > > If you are a Spark user, you can help us test this release by
>>> taking
>>> > > an existing Spark workload and running on this release
>>> candidate, then
>>> > > reporting any regressions.
>>> > >
>>> > > If you're working in PySpark you can set up a virtual env and
>>> install
>>> > > the current RC and see if anything important breaks, in the
>>> Java/Scala
>>> > > you can add the 

Re: [VOTE] Release Apache Spark 2.3.3 (RC1)

2019-01-28 Thread Takeshi Yamamuro
If there is no objection in following responses, I'll wait one more week
while watching that PR progress.
Once that PR merged, I'll start to prepare the next vote.



On Tue, Jan 29, 2019 at 4:57 AM Jungtaek Lim  wrote:

> Regarding PR 23634, it is waiting for getting consensus on the approach
> for the fix, as well as it also needs to have some time to clean up some
> code and move focus to concern backward compatibility. I'm postponing these
> works since I haven't reached consensus on the approach.
>
> So it may take some days or even some weeks to get PR 23634 merged (if
> consensus will not be made in time).
>
> 2019년 1월 29일 (화) 오전 2:18, Sean Owen 님이 작성:
>
>> More analysis at https://github.com/apache/spark/pull/23634
>> It's not a regression, though it does relate to correctness, although
>> somewhat niche.
>> TD, Jose et al, is this a Blocker? and is the fix probably reliable
>> enough to commit now?
>>
>> On Mon, Jan 28, 2019 at 10:59 AM Sandeep Katta
>>  wrote:
>> >
>> > I feel this https://issues.apache.org/jira/browse/SPARK-26154 bug
>> should be fixed in this release as it is related to data correctness
>> >
>> > On Mon, 28 Jan 2019 at 17:55, Takeshi Yamamuro 
>> wrote:
>> >>
>> >> Hi, all
>> >>
>> >> I checked the two issues below had been resolved and there is no
>> blocker for branch-2.3 now, so I'll start prepare RC2 tomorrow.
>> >> https://issues.apache.org/jira/browse/SPARK-26682
>> >> https://issues.apache.org/jira/browse/SPARK-26709
>> >>
>> >> If there are some blockers and critical issues in branch-2.3, please
>> let me know.
>> >>
>> >> Best,
>> >> Takeshi
>> >>
>> >> On Thu, Jan 24, 2019 at 10:06 AM Takeshi Yamamuro <
>> linguin@gmail.com> wrote:
>> >>>
>> >>> Thanks, all.
>> >>>
>> >>> I'll start a new vote as rc2 after the two issues above resolved.
>> >>>
>> >>> Best,
>> >>> Takeshi
>> >>>
>> >>>
>> >>> On Thu, Jan 24, 2019 at 7:59 AM Xiao Li  wrote:
>> 
>>  -1
>> 
>>  https://issues.apache.org/jira/browse/SPARK-26709 is another
>> blocker ticket that returns incorrect results.
>> 
>> 
>>  Marcelo Vanzin  于2019年1月23日周三
>> 下午12:01写道:
>> >
>> > -1 too.
>> >
>> > I just upgraded https://issues.apache.org/jira/browse/SPARK-26682
>> to
>> > blocker. It's a small fix and we should make it in 2.3.3.
>> >
>> > On Thu, Jan 17, 2019 at 6:49 PM Takeshi Yamamuro <
>> linguin@gmail.com> wrote:
>> > >
>> > > Please vote on releasing the following candidate as Apache Spark
>> version 2.3.3.
>> > >
>> > > The vote is open until January 20 8:00PM (PST) and passes if a
>> majority +1 PMC votes are cast, with
>> > > a minimum of 3 +1 votes.
>> > >
>> > > [ ] +1 Release this package as Apache Spark 2.3.3
>> > > [ ] -1 Do not release this package because ...
>> > >
>> > > To learn more about Apache Spark, please see
>> http://spark.apache.org/
>> > >
>> > > The tag to be voted on is v2.3.3-rc1 (commit
>> b5ea9330e3072e99841270b10dc1d2248127064b):
>> > > https://github.com/apache/spark/tree/v2.3.3-rc1
>> > >
>> > > The release files, including signatures, digests, etc. can be
>> found at:
>> > > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-bin/
>> > >
>> > > Signatures used for Spark RCs can be found in this file:
>> > > https://dist.apache.org/repos/dist/dev/spark/KEYS
>> > >
>> > > The staging repository for this release can be found at:
>> > >
>> https://repository.apache.org/content/repositories/orgapachespark-1297
>> > >
>> > > The documentation corresponding to this release can be found at:
>> > > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-docs/
>> > >
>> > > The list of bug fixes going into 2.3.3 can be found at the
>> following URL:
>> > > https://issues.apache.org/jira/projects/SPARK/versions/12343759
>> > >
>> > > FAQ
>> > >
>> > > =
>> > > How can I help test this release?
>> > > =
>> > >
>> > > If you are a Spark user, you can help us test this release by
>> taking
>> > > an existing Spark workload and running on this release candidate,
>> then
>> > > reporting any regressions.
>> > >
>> > > If you're working in PySpark you can set up a virtual env and
>> install
>> > > the current RC and see if anything important breaks, in the
>> Java/Scala
>> > > you can add the staging repository to your projects resolvers and
>> test
>> > > with the RC (make sure to clean up the artifact cache
>> before/after so
>> > > you don't end up building with a out of date RC going forward).
>> > >
>> > > ===
>> > > What should happen to JIRA tickets still targeting 2.3.3?
>> > > ===
>> > >
>> > > The current list of open tickets targeted at 2.3.3 can be found
>> at:
>> > > 

Re: [VOTE] Release Apache Spark 2.3.3 (RC1)

2019-01-28 Thread Jungtaek Lim
Regarding PR 23634, it is waiting for getting consensus on the approach for
the fix, as well as it also needs to have some time to clean up some code
and move focus to concern backward compatibility. I'm postponing these
works since I haven't reached consensus on the approach.

So it may take some days or even some weeks to get PR 23634 merged (if
consensus will not be made in time).

2019년 1월 29일 (화) 오전 2:18, Sean Owen 님이 작성:

> More analysis at https://github.com/apache/spark/pull/23634
> It's not a regression, though it does relate to correctness, although
> somewhat niche.
> TD, Jose et al, is this a Blocker? and is the fix probably reliable
> enough to commit now?
>
> On Mon, Jan 28, 2019 at 10:59 AM Sandeep Katta
>  wrote:
> >
> > I feel this https://issues.apache.org/jira/browse/SPARK-26154 bug
> should be fixed in this release as it is related to data correctness
> >
> > On Mon, 28 Jan 2019 at 17:55, Takeshi Yamamuro 
> wrote:
> >>
> >> Hi, all
> >>
> >> I checked the two issues below had been resolved and there is no
> blocker for branch-2.3 now, so I'll start prepare RC2 tomorrow.
> >> https://issues.apache.org/jira/browse/SPARK-26682
> >> https://issues.apache.org/jira/browse/SPARK-26709
> >>
> >> If there are some blockers and critical issues in branch-2.3, please
> let me know.
> >>
> >> Best,
> >> Takeshi
> >>
> >> On Thu, Jan 24, 2019 at 10:06 AM Takeshi Yamamuro <
> linguin@gmail.com> wrote:
> >>>
> >>> Thanks, all.
> >>>
> >>> I'll start a new vote as rc2 after the two issues above resolved.
> >>>
> >>> Best,
> >>> Takeshi
> >>>
> >>>
> >>> On Thu, Jan 24, 2019 at 7:59 AM Xiao Li  wrote:
> 
>  -1
> 
>  https://issues.apache.org/jira/browse/SPARK-26709 is another blocker
> ticket that returns incorrect results.
> 
> 
>  Marcelo Vanzin  于2019年1月23日周三 下午12:01写道:
> >
> > -1 too.
> >
> > I just upgraded https://issues.apache.org/jira/browse/SPARK-26682 to
> > blocker. It's a small fix and we should make it in 2.3.3.
> >
> > On Thu, Jan 17, 2019 at 6:49 PM Takeshi Yamamuro <
> linguin@gmail.com> wrote:
> > >
> > > Please vote on releasing the following candidate as Apache Spark
> version 2.3.3.
> > >
> > > The vote is open until January 20 8:00PM (PST) and passes if a
> majority +1 PMC votes are cast, with
> > > a minimum of 3 +1 votes.
> > >
> > > [ ] +1 Release this package as Apache Spark 2.3.3
> > > [ ] -1 Do not release this package because ...
> > >
> > > To learn more about Apache Spark, please see
> http://spark.apache.org/
> > >
> > > The tag to be voted on is v2.3.3-rc1 (commit
> b5ea9330e3072e99841270b10dc1d2248127064b):
> > > https://github.com/apache/spark/tree/v2.3.3-rc1
> > >
> > > The release files, including signatures, digests, etc. can be
> found at:
> > > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-bin/
> > >
> > > Signatures used for Spark RCs can be found in this file:
> > > https://dist.apache.org/repos/dist/dev/spark/KEYS
> > >
> > > The staging repository for this release can be found at:
> > >
> https://repository.apache.org/content/repositories/orgapachespark-1297
> > >
> > > The documentation corresponding to this release can be found at:
> > > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-docs/
> > >
> > > The list of bug fixes going into 2.3.3 can be found at the
> following URL:
> > > https://issues.apache.org/jira/projects/SPARK/versions/12343759
> > >
> > > FAQ
> > >
> > > =
> > > How can I help test this release?
> > > =
> > >
> > > If you are a Spark user, you can help us test this release by
> taking
> > > an existing Spark workload and running on this release candidate,
> then
> > > reporting any regressions.
> > >
> > > If you're working in PySpark you can set up a virtual env and
> install
> > > the current RC and see if anything important breaks, in the
> Java/Scala
> > > you can add the staging repository to your projects resolvers and
> test
> > > with the RC (make sure to clean up the artifact cache before/after
> so
> > > you don't end up building with a out of date RC going forward).
> > >
> > > ===
> > > What should happen to JIRA tickets still targeting 2.3.3?
> > > ===
> > >
> > > The current list of open tickets targeted at 2.3.3 can be found at:
> > > https://issues.apache.org/jira/projects/SPARK and search for
> "Target Version/s" = 2.3.3
> > >
> > > Committers should look at those and triage. Extremely important bug
> > > fixes, documentation, and API tweaks that impact compatibility
> should
> > > be worked on immediately. Everything else please retarget to an
> > > appropriate release.
> > >
> > > 

Re: [VOTE] Release Apache Spark 2.3.3 (RC1)

2019-01-28 Thread Sean Owen
More analysis at https://github.com/apache/spark/pull/23634
It's not a regression, though it does relate to correctness, although
somewhat niche.
TD, Jose et al, is this a Blocker? and is the fix probably reliable
enough to commit now?

On Mon, Jan 28, 2019 at 10:59 AM Sandeep Katta
 wrote:
>
> I feel this https://issues.apache.org/jira/browse/SPARK-26154 bug should be 
> fixed in this release as it is related to data correctness
>
> On Mon, 28 Jan 2019 at 17:55, Takeshi Yamamuro  wrote:
>>
>> Hi, all
>>
>> I checked the two issues below had been resolved and there is no blocker for 
>> branch-2.3 now, so I'll start prepare RC2 tomorrow.
>> https://issues.apache.org/jira/browse/SPARK-26682
>> https://issues.apache.org/jira/browse/SPARK-26709
>>
>> If there are some blockers and critical issues in branch-2.3, please let me 
>> know.
>>
>> Best,
>> Takeshi
>>
>> On Thu, Jan 24, 2019 at 10:06 AM Takeshi Yamamuro  
>> wrote:
>>>
>>> Thanks, all.
>>>
>>> I'll start a new vote as rc2 after the two issues above resolved.
>>>
>>> Best,
>>> Takeshi
>>>
>>>
>>> On Thu, Jan 24, 2019 at 7:59 AM Xiao Li  wrote:

 -1

 https://issues.apache.org/jira/browse/SPARK-26709 is another blocker 
 ticket that returns incorrect results.


 Marcelo Vanzin  于2019年1月23日周三 下午12:01写道:
>
> -1 too.
>
> I just upgraded https://issues.apache.org/jira/browse/SPARK-26682 to
> blocker. It's a small fix and we should make it in 2.3.3.
>
> On Thu, Jan 17, 2019 at 6:49 PM Takeshi Yamamuro  
> wrote:
> >
> > Please vote on releasing the following candidate as Apache Spark 
> > version 2.3.3.
> >
> > The vote is open until January 20 8:00PM (PST) and passes if a majority 
> > +1 PMC votes are cast, with
> > a minimum of 3 +1 votes.
> >
> > [ ] +1 Release this package as Apache Spark 2.3.3
> > [ ] -1 Do not release this package because ...
> >
> > To learn more about Apache Spark, please see http://spark.apache.org/
> >
> > The tag to be voted on is v2.3.3-rc1 (commit 
> > b5ea9330e3072e99841270b10dc1d2248127064b):
> > https://github.com/apache/spark/tree/v2.3.3-rc1
> >
> > The release files, including signatures, digests, etc. can be found at:
> > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-bin/
> >
> > Signatures used for Spark RCs can be found in this file:
> > https://dist.apache.org/repos/dist/dev/spark/KEYS
> >
> > The staging repository for this release can be found at:
> > https://repository.apache.org/content/repositories/orgapachespark-1297
> >
> > The documentation corresponding to this release can be found at:
> > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-docs/
> >
> > The list of bug fixes going into 2.3.3 can be found at the following 
> > URL:
> > https://issues.apache.org/jira/projects/SPARK/versions/12343759
> >
> > FAQ
> >
> > =
> > How can I help test this release?
> > =
> >
> > If you are a Spark user, you can help us test this release by taking
> > an existing Spark workload and running on this release candidate, then
> > reporting any regressions.
> >
> > If you're working in PySpark you can set up a virtual env and install
> > the current RC and see if anything important breaks, in the Java/Scala
> > you can add the staging repository to your projects resolvers and test
> > with the RC (make sure to clean up the artifact cache before/after so
> > you don't end up building with a out of date RC going forward).
> >
> > ===
> > What should happen to JIRA tickets still targeting 2.3.3?
> > ===
> >
> > The current list of open tickets targeted at 2.3.3 can be found at:
> > https://issues.apache.org/jira/projects/SPARK and search for "Target 
> > Version/s" = 2.3.3
> >
> > Committers should look at those and triage. Extremely important bug
> > fixes, documentation, and API tweaks that impact compatibility should
> > be worked on immediately. Everything else please retarget to an
> > appropriate release.
> >
> > ==
> > But my bug isn't fixed?
> > ==
> >
> > In order to make timely releases, we will typically not hold the
> > release unless the bug in question is a regression from the previous
> > release. That being said, if there is something which is a regression
> > that has not been correctly targeted please ping me or a committer to
> > help target the issue.
> >
> > --
> > ---
> > Takeshi Yamamuro
>
>
>
> --
> Marcelo
>
> -
> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
>

Re: [VOTE] Release Apache Spark 2.3.3 (RC1)

2019-01-28 Thread Sandeep Katta
I feel this https://issues.apache.org/jira/browse/SPARK-26154 bug should be
fixed in this release as it is related to data correctness

On Mon, 28 Jan 2019 at 17:55, Takeshi Yamamuro 
wrote:

> Hi, all
>
> I checked the two issues below had been resolved and there is no blocker
> for branch-2.3 now, so I'll start prepare RC2 tomorrow.
> https://issues.apache.org/jira/browse/SPARK-26682
> https://issues.apache.org/jira/browse/SPARK-26709
>
> If there are some blockers and critical issues in branch-2.3, please let
> me know.
>
> Best,
> Takeshi
>
> On Thu, Jan 24, 2019 at 10:06 AM Takeshi Yamamuro 
> wrote:
>
>> Thanks, all.
>>
>> I'll start a new vote as rc2 after the two issues above resolved.
>>
>> Best,
>> Takeshi
>>
>>
>> On Thu, Jan 24, 2019 at 7:59 AM Xiao Li  wrote:
>>
>>> -1
>>>
>>> https://issues.apache.org/jira/browse/SPARK-26709 is another blocker
>>> ticket that returns incorrect results.
>>>
>>>
>>> Marcelo Vanzin  于2019年1月23日周三 下午12:01写道:
>>>
 -1 too.

 I just upgraded https://issues.apache.org/jira/browse/SPARK-26682 to
 blocker. It's a small fix and we should make it in 2.3.3.

 On Thu, Jan 17, 2019 at 6:49 PM Takeshi Yamamuro 
 wrote:
 >
 > Please vote on releasing the following candidate as Apache Spark
 version 2.3.3.
 >
 > The vote is open until January 20 8:00PM (PST) and passes if a
 majority +1 PMC votes are cast, with
 > a minimum of 3 +1 votes.
 >
 > [ ] +1 Release this package as Apache Spark 2.3.3
 > [ ] -1 Do not release this package because ...
 >
 > To learn more about Apache Spark, please see http://spark.apache.org/
 >
 > The tag to be voted on is v2.3.3-rc1 (commit
 b5ea9330e3072e99841270b10dc1d2248127064b):
 > https://github.com/apache/spark/tree/v2.3.3-rc1
 >
 > The release files, including signatures, digests, etc. can be found
 at:
 > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-bin/
 >
 > Signatures used for Spark RCs can be found in this file:
 > https://dist.apache.org/repos/dist/dev/spark/KEYS
 >
 > The staging repository for this release can be found at:
 >
 https://repository.apache.org/content/repositories/orgapachespark-1297
 >
 > The documentation corresponding to this release can be found at:
 > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-docs/
 >
 > The list of bug fixes going into 2.3.3 can be found at the following
 URL:
 > https://issues.apache.org/jira/projects/SPARK/versions/12343759
 >
 > FAQ
 >
 > =
 > How can I help test this release?
 > =
 >
 > If you are a Spark user, you can help us test this release by taking
 > an existing Spark workload and running on this release candidate, then
 > reporting any regressions.
 >
 > If you're working in PySpark you can set up a virtual env and install
 > the current RC and see if anything important breaks, in the Java/Scala
 > you can add the staging repository to your projects resolvers and test
 > with the RC (make sure to clean up the artifact cache before/after so
 > you don't end up building with a out of date RC going forward).
 >
 > ===
 > What should happen to JIRA tickets still targeting 2.3.3?
 > ===
 >
 > The current list of open tickets targeted at 2.3.3 can be found at:
 > https://issues.apache.org/jira/projects/SPARK and search for "Target
 Version/s" = 2.3.3
 >
 > Committers should look at those and triage. Extremely important bug
 > fixes, documentation, and API tweaks that impact compatibility should
 > be worked on immediately. Everything else please retarget to an
 > appropriate release.
 >
 > ==
 > But my bug isn't fixed?
 > ==
 >
 > In order to make timely releases, we will typically not hold the
 > release unless the bug in question is a regression from the previous
 > release. That being said, if there is something which is a regression
 > that has not been correctly targeted please ping me or a committer to
 > help target the issue.
 >
 > --
 > ---
 > Takeshi Yamamuro



 --
 Marcelo

 -
 To unsubscribe e-mail: dev-unsubscr...@spark.apache.org


>>
>> --
>> ---
>> Takeshi Yamamuro
>>
>
>
> --
> ---
> Takeshi Yamamuro
>


Re: [VOTE] Release Apache Spark 2.3.3 (RC1)

2019-01-28 Thread Takeshi Yamamuro
Hi, all

I checked the two issues below had been resolved and there is no blocker
for branch-2.3 now, so I'll start prepare RC2 tomorrow.
https://issues.apache.org/jira/browse/SPARK-26682
https://issues.apache.org/jira/browse/SPARK-26709

If there are some blockers and critical issues in branch-2.3, please let me
know.

Best,
Takeshi

On Thu, Jan 24, 2019 at 10:06 AM Takeshi Yamamuro 
wrote:

> Thanks, all.
>
> I'll start a new vote as rc2 after the two issues above resolved.
>
> Best,
> Takeshi
>
>
> On Thu, Jan 24, 2019 at 7:59 AM Xiao Li  wrote:
>
>> -1
>>
>> https://issues.apache.org/jira/browse/SPARK-26709 is another blocker
>> ticket that returns incorrect results.
>>
>>
>> Marcelo Vanzin  于2019年1月23日周三 下午12:01写道:
>>
>>> -1 too.
>>>
>>> I just upgraded https://issues.apache.org/jira/browse/SPARK-26682 to
>>> blocker. It's a small fix and we should make it in 2.3.3.
>>>
>>> On Thu, Jan 17, 2019 at 6:49 PM Takeshi Yamamuro 
>>> wrote:
>>> >
>>> > Please vote on releasing the following candidate as Apache Spark
>>> version 2.3.3.
>>> >
>>> > The vote is open until January 20 8:00PM (PST) and passes if a
>>> majority +1 PMC votes are cast, with
>>> > a minimum of 3 +1 votes.
>>> >
>>> > [ ] +1 Release this package as Apache Spark 2.3.3
>>> > [ ] -1 Do not release this package because ...
>>> >
>>> > To learn more about Apache Spark, please see http://spark.apache.org/
>>> >
>>> > The tag to be voted on is v2.3.3-rc1 (commit
>>> b5ea9330e3072e99841270b10dc1d2248127064b):
>>> > https://github.com/apache/spark/tree/v2.3.3-rc1
>>> >
>>> > The release files, including signatures, digests, etc. can be found at:
>>> > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-bin/
>>> >
>>> > Signatures used for Spark RCs can be found in this file:
>>> > https://dist.apache.org/repos/dist/dev/spark/KEYS
>>> >
>>> > The staging repository for this release can be found at:
>>> > https://repository.apache.org/content/repositories/orgapachespark-1297
>>> >
>>> > The documentation corresponding to this release can be found at:
>>> > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-docs/
>>> >
>>> > The list of bug fixes going into 2.3.3 can be found at the following
>>> URL:
>>> > https://issues.apache.org/jira/projects/SPARK/versions/12343759
>>> >
>>> > FAQ
>>> >
>>> > =
>>> > How can I help test this release?
>>> > =
>>> >
>>> > If you are a Spark user, you can help us test this release by taking
>>> > an existing Spark workload and running on this release candidate, then
>>> > reporting any regressions.
>>> >
>>> > If you're working in PySpark you can set up a virtual env and install
>>> > the current RC and see if anything important breaks, in the Java/Scala
>>> > you can add the staging repository to your projects resolvers and test
>>> > with the RC (make sure to clean up the artifact cache before/after so
>>> > you don't end up building with a out of date RC going forward).
>>> >
>>> > ===
>>> > What should happen to JIRA tickets still targeting 2.3.3?
>>> > ===
>>> >
>>> > The current list of open tickets targeted at 2.3.3 can be found at:
>>> > https://issues.apache.org/jira/projects/SPARK and search for "Target
>>> Version/s" = 2.3.3
>>> >
>>> > Committers should look at those and triage. Extremely important bug
>>> > fixes, documentation, and API tweaks that impact compatibility should
>>> > be worked on immediately. Everything else please retarget to an
>>> > appropriate release.
>>> >
>>> > ==
>>> > But my bug isn't fixed?
>>> > ==
>>> >
>>> > In order to make timely releases, we will typically not hold the
>>> > release unless the bug in question is a regression from the previous
>>> > release. That being said, if there is something which is a regression
>>> > that has not been correctly targeted please ping me or a committer to
>>> > help target the issue.
>>> >
>>> > --
>>> > ---
>>> > Takeshi Yamamuro
>>>
>>>
>>>
>>> --
>>> Marcelo
>>>
>>> -
>>> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
>>>
>>>
>
> --
> ---
> Takeshi Yamamuro
>


-- 
---
Takeshi Yamamuro


Re: [VOTE] Release Apache Spark 2.3.3 (RC1)

2019-01-23 Thread Takeshi Yamamuro
Thanks, all.

I'll start a new vote as rc2 after the two issues above resolved.

Best,
Takeshi


On Thu, Jan 24, 2019 at 7:59 AM Xiao Li  wrote:

> -1
>
> https://issues.apache.org/jira/browse/SPARK-26709 is another blocker
> ticket that returns incorrect results.
>
>
> Marcelo Vanzin  于2019年1月23日周三 下午12:01写道:
>
>> -1 too.
>>
>> I just upgraded https://issues.apache.org/jira/browse/SPARK-26682 to
>> blocker. It's a small fix and we should make it in 2.3.3.
>>
>> On Thu, Jan 17, 2019 at 6:49 PM Takeshi Yamamuro 
>> wrote:
>> >
>> > Please vote on releasing the following candidate as Apache Spark
>> version 2.3.3.
>> >
>> > The vote is open until January 20 8:00PM (PST) and passes if a majority
>> +1 PMC votes are cast, with
>> > a minimum of 3 +1 votes.
>> >
>> > [ ] +1 Release this package as Apache Spark 2.3.3
>> > [ ] -1 Do not release this package because ...
>> >
>> > To learn more about Apache Spark, please see http://spark.apache.org/
>> >
>> > The tag to be voted on is v2.3.3-rc1 (commit
>> b5ea9330e3072e99841270b10dc1d2248127064b):
>> > https://github.com/apache/spark/tree/v2.3.3-rc1
>> >
>> > The release files, including signatures, digests, etc. can be found at:
>> > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-bin/
>> >
>> > Signatures used for Spark RCs can be found in this file:
>> > https://dist.apache.org/repos/dist/dev/spark/KEYS
>> >
>> > The staging repository for this release can be found at:
>> > https://repository.apache.org/content/repositories/orgapachespark-1297
>> >
>> > The documentation corresponding to this release can be found at:
>> > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-docs/
>> >
>> > The list of bug fixes going into 2.3.3 can be found at the following
>> URL:
>> > https://issues.apache.org/jira/projects/SPARK/versions/12343759
>> >
>> > FAQ
>> >
>> > =
>> > How can I help test this release?
>> > =
>> >
>> > If you are a Spark user, you can help us test this release by taking
>> > an existing Spark workload and running on this release candidate, then
>> > reporting any regressions.
>> >
>> > If you're working in PySpark you can set up a virtual env and install
>> > the current RC and see if anything important breaks, in the Java/Scala
>> > you can add the staging repository to your projects resolvers and test
>> > with the RC (make sure to clean up the artifact cache before/after so
>> > you don't end up building with a out of date RC going forward).
>> >
>> > ===
>> > What should happen to JIRA tickets still targeting 2.3.3?
>> > ===
>> >
>> > The current list of open tickets targeted at 2.3.3 can be found at:
>> > https://issues.apache.org/jira/projects/SPARK and search for "Target
>> Version/s" = 2.3.3
>> >
>> > Committers should look at those and triage. Extremely important bug
>> > fixes, documentation, and API tweaks that impact compatibility should
>> > be worked on immediately. Everything else please retarget to an
>> > appropriate release.
>> >
>> > ==
>> > But my bug isn't fixed?
>> > ==
>> >
>> > In order to make timely releases, we will typically not hold the
>> > release unless the bug in question is a regression from the previous
>> > release. That being said, if there is something which is a regression
>> > that has not been correctly targeted please ping me or a committer to
>> > help target the issue.
>> >
>> > --
>> > ---
>> > Takeshi Yamamuro
>>
>>
>>
>> --
>> Marcelo
>>
>> -
>> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
>>
>>

-- 
---
Takeshi Yamamuro


Re: [VOTE] Release Apache Spark 2.3.3 (RC1)

2019-01-23 Thread Xiao Li
-1

https://issues.apache.org/jira/browse/SPARK-26709 is another blocker ticket
that returns incorrect results.


Marcelo Vanzin  于2019年1月23日周三 下午12:01写道:

> -1 too.
>
> I just upgraded https://issues.apache.org/jira/browse/SPARK-26682 to
> blocker. It's a small fix and we should make it in 2.3.3.
>
> On Thu, Jan 17, 2019 at 6:49 PM Takeshi Yamamuro 
> wrote:
> >
> > Please vote on releasing the following candidate as Apache Spark version
> 2.3.3.
> >
> > The vote is open until January 20 8:00PM (PST) and passes if a majority
> +1 PMC votes are cast, with
> > a minimum of 3 +1 votes.
> >
> > [ ] +1 Release this package as Apache Spark 2.3.3
> > [ ] -1 Do not release this package because ...
> >
> > To learn more about Apache Spark, please see http://spark.apache.org/
> >
> > The tag to be voted on is v2.3.3-rc1 (commit
> b5ea9330e3072e99841270b10dc1d2248127064b):
> > https://github.com/apache/spark/tree/v2.3.3-rc1
> >
> > The release files, including signatures, digests, etc. can be found at:
> > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-bin/
> >
> > Signatures used for Spark RCs can be found in this file:
> > https://dist.apache.org/repos/dist/dev/spark/KEYS
> >
> > The staging repository for this release can be found at:
> > https://repository.apache.org/content/repositories/orgapachespark-1297
> >
> > The documentation corresponding to this release can be found at:
> > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-docs/
> >
> > The list of bug fixes going into 2.3.3 can be found at the following URL:
> > https://issues.apache.org/jira/projects/SPARK/versions/12343759
> >
> > FAQ
> >
> > =
> > How can I help test this release?
> > =
> >
> > If you are a Spark user, you can help us test this release by taking
> > an existing Spark workload and running on this release candidate, then
> > reporting any regressions.
> >
> > If you're working in PySpark you can set up a virtual env and install
> > the current RC and see if anything important breaks, in the Java/Scala
> > you can add the staging repository to your projects resolvers and test
> > with the RC (make sure to clean up the artifact cache before/after so
> > you don't end up building with a out of date RC going forward).
> >
> > ===
> > What should happen to JIRA tickets still targeting 2.3.3?
> > ===
> >
> > The current list of open tickets targeted at 2.3.3 can be found at:
> > https://issues.apache.org/jira/projects/SPARK and search for "Target
> Version/s" = 2.3.3
> >
> > Committers should look at those and triage. Extremely important bug
> > fixes, documentation, and API tweaks that impact compatibility should
> > be worked on immediately. Everything else please retarget to an
> > appropriate release.
> >
> > ==
> > But my bug isn't fixed?
> > ==
> >
> > In order to make timely releases, we will typically not hold the
> > release unless the bug in question is a regression from the previous
> > release. That being said, if there is something which is a regression
> > that has not been correctly targeted please ping me or a committer to
> > help target the issue.
> >
> > --
> > ---
> > Takeshi Yamamuro
>
>
>
> --
> Marcelo
>
> -
> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
>
>


Re: [VOTE] Release Apache Spark 2.3.3 (RC1)

2019-01-23 Thread Marcelo Vanzin
-1 too.

I just upgraded https://issues.apache.org/jira/browse/SPARK-26682 to
blocker. It's a small fix and we should make it in 2.3.3.

On Thu, Jan 17, 2019 at 6:49 PM Takeshi Yamamuro  wrote:
>
> Please vote on releasing the following candidate as Apache Spark version 
> 2.3.3.
>
> The vote is open until January 20 8:00PM (PST) and passes if a majority +1 
> PMC votes are cast, with
> a minimum of 3 +1 votes.
>
> [ ] +1 Release this package as Apache Spark 2.3.3
> [ ] -1 Do not release this package because ...
>
> To learn more about Apache Spark, please see http://spark.apache.org/
>
> The tag to be voted on is v2.3.3-rc1 (commit 
> b5ea9330e3072e99841270b10dc1d2248127064b):
> https://github.com/apache/spark/tree/v2.3.3-rc1
>
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-bin/
>
> Signatures used for Spark RCs can be found in this file:
> https://dist.apache.org/repos/dist/dev/spark/KEYS
>
> The staging repository for this release can be found at:
> https://repository.apache.org/content/repositories/orgapachespark-1297
>
> The documentation corresponding to this release can be found at:
> https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-docs/
>
> The list of bug fixes going into 2.3.3 can be found at the following URL:
> https://issues.apache.org/jira/projects/SPARK/versions/12343759
>
> FAQ
>
> =
> How can I help test this release?
> =
>
> If you are a Spark user, you can help us test this release by taking
> an existing Spark workload and running on this release candidate, then
> reporting any regressions.
>
> If you're working in PySpark you can set up a virtual env and install
> the current RC and see if anything important breaks, in the Java/Scala
> you can add the staging repository to your projects resolvers and test
> with the RC (make sure to clean up the artifact cache before/after so
> you don't end up building with a out of date RC going forward).
>
> ===
> What should happen to JIRA tickets still targeting 2.3.3?
> ===
>
> The current list of open tickets targeted at 2.3.3 can be found at:
> https://issues.apache.org/jira/projects/SPARK and search for "Target 
> Version/s" = 2.3.3
>
> Committers should look at those and triage. Extremely important bug
> fixes, documentation, and API tweaks that impact compatibility should
> be worked on immediately. Everything else please retarget to an
> appropriate release.
>
> ==
> But my bug isn't fixed?
> ==
>
> In order to make timely releases, we will typically not hold the
> release unless the bug in question is a regression from the previous
> release. That being said, if there is something which is a regression
> that has not been correctly targeted please ping me or a committer to
> help target the issue.
>
> --
> ---
> Takeshi Yamamuro



-- 
Marcelo

-
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org



Re: [VOTE] Release Apache Spark 2.3.3 (RC1)

2019-01-23 Thread DB Tsai
-1

Agreed with Anton that this bug will potentially corrupt the data
silently. As he is ready to submit a PR, I'll suggest to wait to
include the fix. Thanks!

Sincerely,

DB Tsai
--
Web: https://www.dbtsai.com
PGP Key ID: 0x5CED8B896A6BDFA0

On Wed, Jan 23, 2019 at 7:10 AM Anton Okolnychyi
 wrote:
>
> It is a correctness bug. I have updated the description with an example. It 
> has been there for a while, so I am not sure about the priority.
>
> ср, 23 янв. 2019 г. в 14:48, Sean Owen :
>>
>> I'm not clear if it's a correctness bug from that description, and if
>> it's not a regression, no it does not need to go into 2.3.3. If it's a
>> real bug, sure it can be merged to 2.3.x.
>>
>> On Wed, Jan 23, 2019 at 7:54 AM Anton Okolnychyi
>>  wrote:
>> >
>> > Recently, I came across this bug: 
>> > https://issues.apache.org/jira/browse/SPARK-26706.
>> >
>> > It seems appropriate to include it in 2.3.3, doesn't it?
>> >
>> > Thanks,
>> > Anton
>> >

-
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org



Re: [VOTE] Release Apache Spark 2.3.3 (RC1)

2019-01-23 Thread Anton Okolnychyi
It is a correctness bug. I have updated the description with an example. It
has been there for a while, so I am not sure about the priority.

ср, 23 янв. 2019 г. в 14:48, Sean Owen :

> I'm not clear if it's a correctness bug from that description, and if
> it's not a regression, no it does not need to go into 2.3.3. If it's a
> real bug, sure it can be merged to 2.3.x.
>
> On Wed, Jan 23, 2019 at 7:54 AM Anton Okolnychyi
>  wrote:
> >
> > Recently, I came across this bug:
> https://issues.apache.org/jira/browse/SPARK-26706.
> >
> > It seems appropriate to include it in 2.3.3, doesn't it?
> >
> > Thanks,
> > Anton
> >
>


Re: [VOTE] Release Apache Spark 2.3.3 (RC1)

2019-01-23 Thread Sean Owen
I'm not clear if it's a correctness bug from that description, and if
it's not a regression, no it does not need to go into 2.3.3. If it's a
real bug, sure it can be merged to 2.3.x.

On Wed, Jan 23, 2019 at 7:54 AM Anton Okolnychyi
 wrote:
>
> Recently, I came across this bug: 
> https://issues.apache.org/jira/browse/SPARK-26706.
>
> It seems appropriate to include it in 2.3.3, doesn't it?
>
> Thanks,
> Anton
>

-
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org



Re: [VOTE] Release Apache Spark 2.3.3 (RC1)

2019-01-23 Thread Anton Okolnychyi
Recently, I came across this bug:
https://issues.apache.org/jira/browse/SPARK-26706.

It seems appropriate to include it in 2.3.3, doesn't it?

Thanks,
Anton

ср, 23 янв. 2019 г. в 13:08, Takeshi Yamamuro :

> Thanks for the check, Felix!
>
> Yea, I'll wait for the new test report.
> But, it never took so much time to run tests in branch-2.3 before, ...
> network issue?
>
> On Wed, Jan 23, 2019 at 2:19 AM Felix Cheung 
> wrote:
>
>> I’ve tried a couple of times. The latest test run took 12 hr+
>>
>> 1 aborted suite:
>> 00:53:25.769 WARN
>> org.apache.spark.sql.hive.HiveExternalCatalogVersionsSuite: Failed to
>> download Spark 2.3.2 from
>> http://mirrors.koehn.com/apache//spark/spark-2.3.2/spark-2.3.2-bin-hadoop2.7.tgz:
>> Error writing to server
>> 00:53:25.812 WARN
>> org.apache.spark.sql.hive.HiveExternalCatalogVersionsSuite: Failed to
>> download Spark 2.3.2 from
>> http://mirror.cc.columbia.edu/pub/software/apache//spark/spark-2.3.2/spark-2.3.2-bin-hadoop2.7.tgz:
>> Error writing to server
>> 00:53:25.838 WARN
>> org.apache.spark.sql.hive.HiveExternalCatalogVersionsSuite: Failed to
>> download Spark 2.3.2 from
>> https://archive.apache.org/dist/spark/spark-2.3.2/spark-2.3.2-bin-hadoop2.7.tgz:
>> Socket closed
>>
>> org.apache.spark.sql.hive.HiveExternalCatalogVersionsSuite *** ABORTED ***
>> Exception encountered when invoking run on a nested suite - Unable to
>> download Spark 2.3.2 (HiveExternalCatalogVersionsSuite.scala:97)
>>
>> And then it stopped. I checked this morning the archive link should be
>> valid. Try to see if I can try again/resume from it.
>>
>>
>> ----------
>> *From:* Takeshi Yamamuro 
>> *Sent:* Sunday, January 20, 2019 6:45 PM
>> *To:* Sean Owen
>> *Cc:* Spark dev list
>> *Subject:* Re: [VOTE] Release Apache Spark 2.3.3 (RC1)
>>
>> Oh, sorry for that and I misunderstood the Apache release policy.
>> Yea, its ok to keep the RC1 voting.
>>
>> Best,
>> Takeshi
>>
>> On Mon, Jan 21, 2019 at 11:07 AM Sean Owen  wrote:
>>
>>> OK, if it passes tests, I'm +1 on the release.
>>> Can anyone else verify the tests pass?
>>>
>>> What is the reason for a new RC? I didn't see any other issues reported.
>>>
>>> On Sun, Jan 20, 2019 at 8:03 PM Takeshi Yamamuro 
>>> wrote:
>>> >
>>> > Hi, all
>>> >
>>> > Thanks for the checks, Sean and Felix.
>>> > I'll start the next vote as RC2 this Tuesday noon (PST).
>>> >
>>> > > Sean
>>> > I re-run JavaTfIdfSuite on my env and it passed.
>>> > I used `-Pyarn -Phadoop-2.7 -Phive -Phive-thriftserver -Pmesos
>>> -Psparkr` and
>>> > run the tests on a EC2 instance below (I launched the new instance for
>>> the tests);
>>> > 
>>> > $ cat /etc/os-release
>>> > NAME="Amazon Linux"
>>> > VERSION="2"
>>> > ID="amzn"
>>> > ID_LIKE="centos rhel fedora"
>>> > VERSION_ID="2"
>>> > PRETTY_NAME="Amazon Linux 2"
>>> > ANSI_COLOR="0;33"
>>> > CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2"
>>> > HOME_URL="https://amazonlinux.com/;
>>> > $ java -version
>>> > openjdk version "1.8.0_191"
>>> > OpenJDK Runtime Environment (build 1.8.0_191-b12)
>>> > OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode)
>>> >
>>> >
>>> >
>>> >
>>> > On Mon, Jan 21, 2019 at 9:53 AM Felix Cheung <
>>> felixcheun...@hotmail.com> wrote:
>>> >>
>>> >> +1
>>> >>
>>> >> My focus is on R (sorry couldn’t cross validate what’s Sean is seeing)
>>> >>
>>> >> tested:
>>> >> reviewed doc
>>> >> R package test
>>> >> win-builder, r-hub
>>> >> Tarball/package signature
>>> >>
>>> >>
>>> >>
>>> >> 
>>> >> From: Takeshi Yamamuro 
>>> >> Sent: Thursday, January 17, 2019 6:49 PM
>>> >> To: Spark dev list
>>> >> Subject: [VOTE] Release Apache Spark 2.3.3 (RC1)
>>> >>
>>> >> Please vote on releasing the following candidate as Apache Spark
>>> version 2.3.3.
>>> >>
>>> >> The vote is open until January 20 8:00PM (P

Re: [VOTE] Release Apache Spark 2.3.3 (RC1)

2019-01-20 Thread Takeshi Yamamuro
Oh, sorry for that and I misunderstood the Apache release policy.
Yea, its ok to keep the RC1 voting.

Best,
Takeshi

On Mon, Jan 21, 2019 at 11:07 AM Sean Owen  wrote:

> OK, if it passes tests, I'm +1 on the release.
> Can anyone else verify the tests pass?
>
> What is the reason for a new RC? I didn't see any other issues reported.
>
> On Sun, Jan 20, 2019 at 8:03 PM Takeshi Yamamuro 
> wrote:
> >
> > Hi, all
> >
> > Thanks for the checks, Sean and Felix.
> > I'll start the next vote as RC2 this Tuesday noon (PST).
> >
> > > Sean
> > I re-run JavaTfIdfSuite on my env and it passed.
> > I used `-Pyarn -Phadoop-2.7 -Phive -Phive-thriftserver -Pmesos -Psparkr`
> and
> > run the tests on a EC2 instance below (I launched the new instance for
> the tests);
> > 
> > $ cat /etc/os-release
> > NAME="Amazon Linux"
> > VERSION="2"
> > ID="amzn"
> > ID_LIKE="centos rhel fedora"
> > VERSION_ID="2"
> > PRETTY_NAME="Amazon Linux 2"
> > ANSI_COLOR="0;33"
> > CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2"
> > HOME_URL="https://amazonlinux.com/;
> > $ java -version
> > openjdk version "1.8.0_191"
> > OpenJDK Runtime Environment (build 1.8.0_191-b12)
> > OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode)
> >
> >
> >
> >
> > On Mon, Jan 21, 2019 at 9:53 AM Felix Cheung 
> wrote:
> >>
> >> +1
> >>
> >> My focus is on R (sorry couldn’t cross validate what’s Sean is seeing)
> >>
> >> tested:
> >> reviewed doc
> >> R package test
> >> win-builder, r-hub
> >> Tarball/package signature
> >>
> >>
> >>
> >> 
> >> From: Takeshi Yamamuro 
> >> Sent: Thursday, January 17, 2019 6:49 PM
> >> To: Spark dev list
> >> Subject: [VOTE] Release Apache Spark 2.3.3 (RC1)
> >>
> >> Please vote on releasing the following candidate as Apache Spark
> version 2.3.3.
> >>
> >> The vote is open until January 20 8:00PM (PST) and passes if a majority
> +1 PMC votes are cast, with
> >> a minimum of 3 +1 votes.
> >>
> >> [ ] +1 Release this package as Apache Spark 2.3.3
> >> [ ] -1 Do not release this package because ...
> >>
> >> To learn more about Apache Spark, please see http://spark.apache.org/
> >>
> >> The tag to be voted on is v2.3.3-rc1 (commit
> b5ea9330e3072e99841270b10dc1d2248127064b):
> >> https://github.com/apache/spark/tree/v2.3.3-rc1
> >>
> >> The release files, including signatures, digests, etc. can be found at:
> >> https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-bin/
> >>
> >> Signatures used for Spark RCs can be found in this file:
> >> https://dist.apache.org/repos/dist/dev/spark/KEYS
> >>
> >> The staging repository for this release can be found at:
> >> https://repository.apache.org/content/repositories/orgapachespark-1297
> >>
> >> The documentation corresponding to this release can be found at:
> >> https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-docs/
> >>
> >> The list of bug fixes going into 2.3.3 can be found at the following
> URL:
> >> https://issues.apache.org/jira/projects/SPARK/versions/12343759
> >>
> >> FAQ
> >>
> >> =
> >> How can I help test this release?
> >> =
> >>
> >> If you are a Spark user, you can help us test this release by taking
> >> an existing Spark workload and running on this release candidate, then
> >> reporting any regressions.
> >>
> >> If you're working in PySpark you can set up a virtual env and install
> >> the current RC and see if anything important breaks, in the Java/Scala
> >> you can add the staging repository to your projects resolvers and test
> >> with the RC (make sure to clean up the artifact cache before/after so
> >> you don't end up building with a out of date RC going forward).
> >>
> >> ===
> >> What should happen to JIRA tickets still targeting 2.3.3?
> >> ===
> >>
> >> The current list of open tickets targeted at 2.3.3 can be found at:
> >> https://issues.apache.org/jira/projects/SPARK and search for "Target
> Version/s" = 2.3.3
> >>
> >> Committers should look at those and triage. Extremely important bug
> >> fixes, documentation, and API tweaks that impact compatibility should
> >> be worked on immediately. Everything else please retarget to an
> >> appropriate release.
> >>
> >> ==
> >> But my bug isn't fixed?
> >> ==
> >>
> >> In order to make timely releases, we will typically not hold the
> >> release unless the bug in question is a regression from the previous
> >> release. That being said, if there is something which is a regression
> >> that has not been correctly targeted please ping me or a committer to
> >> help target the issue.
> >>
> >> --
> >> ---
> >> Takeshi Yamamuro
> >
> >
> >
> > --
> > ---
> > Takeshi Yamamuro
>


-- 
---
Takeshi Yamamuro


Re: [VOTE] Release Apache Spark 2.3.3 (RC1)

2019-01-20 Thread Sean Owen
OK, if it passes tests, I'm +1 on the release.
Can anyone else verify the tests pass?

What is the reason for a new RC? I didn't see any other issues reported.

On Sun, Jan 20, 2019 at 8:03 PM Takeshi Yamamuro  wrote:
>
> Hi, all
>
> Thanks for the checks, Sean and Felix.
> I'll start the next vote as RC2 this Tuesday noon (PST).
>
> > Sean
> I re-run JavaTfIdfSuite on my env and it passed.
> I used `-Pyarn -Phadoop-2.7 -Phive -Phive-thriftserver -Pmesos -Psparkr` and
> run the tests on a EC2 instance below (I launched the new instance for the 
> tests);
> 
> $ cat /etc/os-release
> NAME="Amazon Linux"
> VERSION="2"
> ID="amzn"
> ID_LIKE="centos rhel fedora"
> VERSION_ID="2"
> PRETTY_NAME="Amazon Linux 2"
> ANSI_COLOR="0;33"
> CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2"
> HOME_URL="https://amazonlinux.com/;
> $ java -version
> openjdk version "1.8.0_191"
> OpenJDK Runtime Environment (build 1.8.0_191-b12)
> OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode)
>
>
>
>
> On Mon, Jan 21, 2019 at 9:53 AM Felix Cheung  
> wrote:
>>
>> +1
>>
>> My focus is on R (sorry couldn’t cross validate what’s Sean is seeing)
>>
>> tested:
>> reviewed doc
>> R package test
>> win-builder, r-hub
>> Tarball/package signature
>>
>>
>>
>> 
>> From: Takeshi Yamamuro 
>> Sent: Thursday, January 17, 2019 6:49 PM
>> To: Spark dev list
>> Subject: [VOTE] Release Apache Spark 2.3.3 (RC1)
>>
>> Please vote on releasing the following candidate as Apache Spark version 
>> 2.3.3.
>>
>> The vote is open until January 20 8:00PM (PST) and passes if a majority +1 
>> PMC votes are cast, with
>> a minimum of 3 +1 votes.
>>
>> [ ] +1 Release this package as Apache Spark 2.3.3
>> [ ] -1 Do not release this package because ...
>>
>> To learn more about Apache Spark, please see http://spark.apache.org/
>>
>> The tag to be voted on is v2.3.3-rc1 (commit 
>> b5ea9330e3072e99841270b10dc1d2248127064b):
>> https://github.com/apache/spark/tree/v2.3.3-rc1
>>
>> The release files, including signatures, digests, etc. can be found at:
>> https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-bin/
>>
>> Signatures used for Spark RCs can be found in this file:
>> https://dist.apache.org/repos/dist/dev/spark/KEYS
>>
>> The staging repository for this release can be found at:
>> https://repository.apache.org/content/repositories/orgapachespark-1297
>>
>> The documentation corresponding to this release can be found at:
>> https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-docs/
>>
>> The list of bug fixes going into 2.3.3 can be found at the following URL:
>> https://issues.apache.org/jira/projects/SPARK/versions/12343759
>>
>> FAQ
>>
>> =
>> How can I help test this release?
>> =
>>
>> If you are a Spark user, you can help us test this release by taking
>> an existing Spark workload and running on this release candidate, then
>> reporting any regressions.
>>
>> If you're working in PySpark you can set up a virtual env and install
>> the current RC and see if anything important breaks, in the Java/Scala
>> you can add the staging repository to your projects resolvers and test
>> with the RC (make sure to clean up the artifact cache before/after so
>> you don't end up building with a out of date RC going forward).
>>
>> ===
>> What should happen to JIRA tickets still targeting 2.3.3?
>> ===
>>
>> The current list of open tickets targeted at 2.3.3 can be found at:
>> https://issues.apache.org/jira/projects/SPARK and search for "Target 
>> Version/s" = 2.3.3
>>
>> Committers should look at those and triage. Extremely important bug
>> fixes, documentation, and API tweaks that impact compatibility should
>> be worked on immediately. Everything else please retarget to an
>> appropriate release.
>>
>> ==
>> But my bug isn't fixed?
>> ==
>>
>> In order to make timely releases, we will typically not hold the
>> release unless the bug in question is a regression from the previous
>> release. That being said, if there is something which is a regression
>> that has not been correctly targeted please ping me or a committer to
>> help target the issue.
>>
>> --
>> ---
>> Takeshi Yamamuro
>
>
>
> --
> ---
> Takeshi Yamamuro

-
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org



Re: [VOTE] Release Apache Spark 2.3.3 (RC1)

2019-01-20 Thread Takeshi Yamamuro
Hi, all

Thanks for the checks, Sean and Felix.
I'll start the next vote as RC2 this Tuesday noon (PST).

> Sean
I re-run JavaTfIdfSuite on my env and it passed.
I used `-Pyarn -Phadoop-2.7 -Phive -Phive-thriftserver -Pmesos -Psparkr` and
run the tests on a EC2 instance below (I launched the new instance for the
tests);

$ cat /etc/os-release
NAME="Amazon Linux"
VERSION="2"
ID="amzn"
ID_LIKE="centos rhel fedora"
VERSION_ID="2"
PRETTY_NAME="Amazon Linux 2"
ANSI_COLOR="0;33"
CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2"
HOME_URL="https://amazonlinux.com/;
$ java -version
openjdk version "1.8.0_191"
OpenJDK Runtime Environment (build 1.8.0_191-b12)
OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode)




On Mon, Jan 21, 2019 at 9:53 AM Felix Cheung 
wrote:

> +1
>
> My focus is on R (sorry couldn’t cross validate what’s Sean is seeing)
>
> tested:
> reviewed doc
> R package test
> win-builder, r-hub
> Tarball/package signature
>
>
>
> --
> *From:* Takeshi Yamamuro 
> *Sent:* Thursday, January 17, 2019 6:49 PM
> *To:* Spark dev list
> *Subject:* [VOTE] Release Apache Spark 2.3.3 (RC1)
>
> Please vote on releasing the following candidate as Apache Spark version
> 2.3.3.
>
> The vote is open until January 20 8:00PM (PST) and passes if a majority +1
> PMC votes are cast, with
> a minimum of 3 +1 votes.
>
> [ ] +1 Release this package as Apache Spark 2.3.3
> [ ] -1 Do not release this package because ...
>
> To learn more about Apache Spark, please see http://spark.apache.org/
>
> The tag to be voted on is v2.3.3-rc1 (commit
> b5ea9330e3072e99841270b10dc1d2248127064b):
> https://github.com/apache/spark/tree/v2.3.3-rc1
>
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-bin/
>
> Signatures used for Spark RCs can be found in this file:
> https://dist.apache.org/repos/dist/dev/spark/KEYS
>
> The staging repository for this release can be found at:
> https://repository.apache.org/content/repositories/orgapachespark-1297
>
> The documentation corresponding to this release can be found at:
> https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-docs/
>
> The list of bug fixes going into 2.3.3 can be found at the following URL:
> https://issues.apache.org/jira/projects/SPARK/versions/12343759
>
> FAQ
>
> =
> How can I help test this release?
> =
>
> If you are a Spark user, you can help us test this release by taking
> an existing Spark workload and running on this release candidate, then
> reporting any regressions.
>
> If you're working in PySpark you can set up a virtual env and install
> the current RC and see if anything important breaks, in the Java/Scala
> you can add the staging repository to your projects resolvers and test
> with the RC (make sure to clean up the artifact cache before/after so
> you don't end up building with a out of date RC going forward).
>
> ===
> What should happen to JIRA tickets still targeting 2.3.3?
> ===
>
> The current list of open tickets targeted at 2.3.3 can be found at:
> https://issues.apache.org/jira/projects/SPARK and search for "Target
> Version/s" = 2.3.3
>
> Committers should look at those and triage. Extremely important bug
> fixes, documentation, and API tweaks that impact compatibility should
> be worked on immediately. Everything else please retarget to an
> appropriate release.
>
> ==
> But my bug isn't fixed?
> ==
>
> In order to make timely releases, we will typically not hold the
> release unless the bug in question is a regression from the previous
> release. That being said, if there is something which is a regression
> that has not been correctly targeted please ping me or a committer to
> help target the issue.
>
> --
> ---
> Takeshi Yamamuro
>


-- 
---
Takeshi Yamamuro


Re: [VOTE] Release Apache Spark 2.3.3 (RC1)

2019-01-20 Thread Felix Cheung
+1

My focus is on R (sorry couldn’t cross validate what’s Sean is seeing)

tested:
reviewed doc
R package test
win-builder, r-hub
Tarball/package signature




From: Takeshi Yamamuro 
Sent: Thursday, January 17, 2019 6:49 PM
To: Spark dev list
Subject: [VOTE] Release Apache Spark 2.3.3 (RC1)

Please vote on releasing the following candidate as Apache Spark version 2.3.3.

The vote is open until January 20 8:00PM (PST) and passes if a majority +1 PMC 
votes are cast, with
a minimum of 3 +1 votes.

[ ] +1 Release this package as Apache Spark 2.3.3
[ ] -1 Do not release this package because ...

To learn more about Apache Spark, please see http://spark.apache.org/

The tag to be voted on is v2.3.3-rc1 (commit 
b5ea9330e3072e99841270b10dc1d2248127064b):
https://github.com/apache/spark/tree/v2.3.3-rc1

The release files, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-bin/

Signatures used for Spark RCs can be found in this file:
https://dist.apache.org/repos/dist/dev/spark/KEYS

The staging repository for this release can be found at:
https://repository.apache.org/content/repositories/orgapachespark-1297

The documentation corresponding to this release can be found at:
https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-docs/

The list of bug fixes going into 2.3.3 can be found at the following URL:
https://issues.apache.org/jira/projects/SPARK/versions/12343759

FAQ

=
How can I help test this release?
=

If you are a Spark user, you can help us test this release by taking
an existing Spark workload and running on this release candidate, then
reporting any regressions.

If you're working in PySpark you can set up a virtual env and install
the current RC and see if anything important breaks, in the Java/Scala
you can add the staging repository to your projects resolvers and test
with the RC (make sure to clean up the artifact cache before/after so
you don't end up building with a out of date RC going forward).

===
What should happen to JIRA tickets still targeting 2.3.3?
===

The current list of open tickets targeted at 2.3.3 can be found at:
https://issues.apache.org/jira/projects/SPARK and search for "Target Version/s" 
= 2.3.3

Committers should look at those and triage. Extremely important bug
fixes, documentation, and API tweaks that impact compatibility should
be worked on immediately. Everything else please retarget to an
appropriate release.

==
But my bug isn't fixed?
==

In order to make timely releases, we will typically not hold the
release unless the bug in question is a regression from the previous
release. That being said, if there is something which is a regression
that has not been correctly targeted please ping me or a committer to
help target the issue.

--
---
Takeshi Yamamuro


Re: [VOTE] Release Apache Spark 2.3.3 (RC1)

2019-01-20 Thread Sean Owen
I'm getting different errors when I run on a different machine; not
quite the same. Things like:

[ERROR] Errors:
[ERROR]   JavaTfIdfSuite.tfIdf:44 » Spark Job aborted due to stage
failure: Task 0 in st...
[ERROR]   JavaTfIdfSuite.tfIdfMinimumDocumentFrequency:64 » Spark Job
aborted due to sta...

It seems like it must be env-related, but on two different environments.

What type of OS are you running on and what -P flags?

If anyone else is successfully building and running tests, I'll assume
it's env and test issues. The rest looks OK.

On Fri, Jan 18, 2019 at 6:53 PM Takeshi Yamamuro  wrote:
>
> Hi, sean,
>
> I run these tests again though, these tests passed on my AWS env.
> But, I notice these streaming tests are a little flaky though...
>
>
> On Sat, Jan 19, 2019 at 1:51 AM Sean Owen  wrote:
>>
>> The release itself looks OK. I'm getting, as before, a lot of errors
>> on the machine I'm building on. Is anyone else seeing this? if not I'm
>> going to scrap the env and try something new. Errors like:
>>
>>
>> - event ordering *** FAILED ***
>>   The code passed to failAfter did not complete within 10 seconds.
>> (StreamingQueryListenerSuite.scala:434)
>>
>> - left outer early state exclusion on right *** FAILED ***
>>   Assert on query failed: Check total state rows = List(4), updated
>> state rows = List(4): Array(1) did not equal List(4) incorrect updates
>> rows
>>
>> - left outer join with non-key condition violated *** FAILED ***
>>   == Results ==
>>   !== Correct Answer - 3 ==   == Spark Answer - 0 ==
>>struct<>   struct<>
>>   ![1,10,2,null]
>>   ![2,10,4,null]
>>   ![3,10,6,null]
>>
>> - HDFSMetadataLog: metadata directory collision *** FAILED ***
>>   The await method on Waiter timed out. (HDFSMetadataLogSuite.scala:201)
>>
>> and then streaming suites that never finish
>>
>> On Thu, Jan 17, 2019 at 8:49 PM Takeshi Yamamuro  
>> wrote:
>> >
>> > Please vote on releasing the following candidate as Apache Spark version 
>> > 2.3.3.
>> >
>> > The vote is open until January 20 8:00PM (PST) and passes if a majority +1 
>> > PMC votes are cast, with
>> > a minimum of 3 +1 votes.
>> >
>> > [ ] +1 Release this package as Apache Spark 2.3.3
>> > [ ] -1 Do not release this package because ...
>> >
>> > To learn more about Apache Spark, please see http://spark.apache.org/
>> >
>> > The tag to be voted on is v2.3.3-rc1 (commit 
>> > b5ea9330e3072e99841270b10dc1d2248127064b):
>> > https://github.com/apache/spark/tree/v2.3.3-rc1
>> >
>> > The release files, including signatures, digests, etc. can be found at:
>> > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-bin/
>> >
>> > Signatures used for Spark RCs can be found in this file:
>> > https://dist.apache.org/repos/dist/dev/spark/KEYS
>> >
>> > The staging repository for this release can be found at:
>> > https://repository.apache.org/content/repositories/orgapachespark-1297
>> >
>> > The documentation corresponding to this release can be found at:
>> > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-docs/
>> >
>> > The list of bug fixes going into 2.3.3 can be found at the following URL:
>> > https://issues.apache.org/jira/projects/SPARK/versions/12343759
>> >
>> > FAQ
>> >
>> > =
>> > How can I help test this release?
>> > =
>> >
>> > If you are a Spark user, you can help us test this release by taking
>> > an existing Spark workload and running on this release candidate, then
>> > reporting any regressions.
>> >
>> > If you're working in PySpark you can set up a virtual env and install
>> > the current RC and see if anything important breaks, in the Java/Scala
>> > you can add the staging repository to your projects resolvers and test
>> > with the RC (make sure to clean up the artifact cache before/after so
>> > you don't end up building with a out of date RC going forward).
>> >
>> > ===
>> > What should happen to JIRA tickets still targeting 2.3.3?
>> > ===
>> >
>> > The current list of open tickets targeted at 2.3.3 can be found at:
>> > https://issues.apache.org/jira/projects/SPARK and search for "Target 
>> > Version/s" = 2.3.3
>> >
>> > Committers should look at those and triage. Extremely important bug
>> > fixes, documentation, and API tweaks that impact compatibility should
>> > be worked on immediately. Everything else please retarget to an
>> > appropriate release.
>> >
>> > ==
>> > But my bug isn't fixed?
>> > ==
>> >
>> > In order to make timely releases, we will typically not hold the
>> > release unless the bug in question is a regression from the previous
>> > release. That being said, if there is something which is a regression
>> > that has not been correctly targeted please ping me or a committer to
>> > help target the issue.
>> >
>> > --
>> > ---
>> > Takeshi Yamamuro
>
>
>
> --
> ---
> Takeshi Yamamuro


Re: [VOTE] Release Apache Spark 2.3.3 (RC1)

2019-01-18 Thread Takeshi Yamamuro
Hi, sean,

I run these tests again though, these tests passed on my AWS env.
But, I notice these streaming tests are a little flaky though...


On Sat, Jan 19, 2019 at 1:51 AM Sean Owen  wrote:

> The release itself looks OK. I'm getting, as before, a lot of errors
> on the machine I'm building on. Is anyone else seeing this? if not I'm
> going to scrap the env and try something new. Errors like:
>
>
> - event ordering *** FAILED ***
>   The code passed to failAfter did not complete within 10 seconds.
> (StreamingQueryListenerSuite.scala:434)
>
> - left outer early state exclusion on right *** FAILED ***
>   Assert on query failed: Check total state rows = List(4), updated
> state rows = List(4): Array(1) did not equal List(4) incorrect updates
> rows
>
> - left outer join with non-key condition violated *** FAILED ***
>   == Results ==
>   !== Correct Answer - 3 ==   == Spark Answer - 0 ==
>struct<>   struct<>
>   ![1,10,2,null]
>   ![2,10,4,null]
>   ![3,10,6,null]
>
> - HDFSMetadataLog: metadata directory collision *** FAILED ***
>   The await method on Waiter timed out. (HDFSMetadataLogSuite.scala:201)
>
> and then streaming suites that never finish
>
> On Thu, Jan 17, 2019 at 8:49 PM Takeshi Yamamuro 
> wrote:
> >
> > Please vote on releasing the following candidate as Apache Spark version
> 2.3.3.
> >
> > The vote is open until January 20 8:00PM (PST) and passes if a majority
> +1 PMC votes are cast, with
> > a minimum of 3 +1 votes.
> >
> > [ ] +1 Release this package as Apache Spark 2.3.3
> > [ ] -1 Do not release this package because ...
> >
> > To learn more about Apache Spark, please see http://spark.apache.org/
> >
> > The tag to be voted on is v2.3.3-rc1 (commit
> b5ea9330e3072e99841270b10dc1d2248127064b):
> > https://github.com/apache/spark/tree/v2.3.3-rc1
> >
> > The release files, including signatures, digests, etc. can be found at:
> > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-bin/
> >
> > Signatures used for Spark RCs can be found in this file:
> > https://dist.apache.org/repos/dist/dev/spark/KEYS
> >
> > The staging repository for this release can be found at:
> > https://repository.apache.org/content/repositories/orgapachespark-1297
> >
> > The documentation corresponding to this release can be found at:
> > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-docs/
> >
> > The list of bug fixes going into 2.3.3 can be found at the following URL:
> > https://issues.apache.org/jira/projects/SPARK/versions/12343759
> >
> > FAQ
> >
> > =
> > How can I help test this release?
> > =
> >
> > If you are a Spark user, you can help us test this release by taking
> > an existing Spark workload and running on this release candidate, then
> > reporting any regressions.
> >
> > If you're working in PySpark you can set up a virtual env and install
> > the current RC and see if anything important breaks, in the Java/Scala
> > you can add the staging repository to your projects resolvers and test
> > with the RC (make sure to clean up the artifact cache before/after so
> > you don't end up building with a out of date RC going forward).
> >
> > ===
> > What should happen to JIRA tickets still targeting 2.3.3?
> > ===
> >
> > The current list of open tickets targeted at 2.3.3 can be found at:
> > https://issues.apache.org/jira/projects/SPARK and search for "Target
> Version/s" = 2.3.3
> >
> > Committers should look at those and triage. Extremely important bug
> > fixes, documentation, and API tweaks that impact compatibility should
> > be worked on immediately. Everything else please retarget to an
> > appropriate release.
> >
> > ==
> > But my bug isn't fixed?
> > ==
> >
> > In order to make timely releases, we will typically not hold the
> > release unless the bug in question is a regression from the previous
> > release. That being said, if there is something which is a regression
> > that has not been correctly targeted please ping me or a committer to
> > help target the issue.
> >
> > --
> > ---
> > Takeshi Yamamuro
>


-- 
---
Takeshi Yamamuro


Re: [VOTE] Release Apache Spark 2.3.3 (RC1)

2019-01-18 Thread Sean Owen
The release itself looks OK. I'm getting, as before, a lot of errors
on the machine I'm building on. Is anyone else seeing this? if not I'm
going to scrap the env and try something new. Errors like:


- event ordering *** FAILED ***
  The code passed to failAfter did not complete within 10 seconds.
(StreamingQueryListenerSuite.scala:434)

- left outer early state exclusion on right *** FAILED ***
  Assert on query failed: Check total state rows = List(4), updated
state rows = List(4): Array(1) did not equal List(4) incorrect updates
rows

- left outer join with non-key condition violated *** FAILED ***
  == Results ==
  !== Correct Answer - 3 ==   == Spark Answer - 0 ==
   struct<>   struct<>
  ![1,10,2,null]
  ![2,10,4,null]
  ![3,10,6,null]

- HDFSMetadataLog: metadata directory collision *** FAILED ***
  The await method on Waiter timed out. (HDFSMetadataLogSuite.scala:201)

and then streaming suites that never finish

On Thu, Jan 17, 2019 at 8:49 PM Takeshi Yamamuro  wrote:
>
> Please vote on releasing the following candidate as Apache Spark version 
> 2.3.3.
>
> The vote is open until January 20 8:00PM (PST) and passes if a majority +1 
> PMC votes are cast, with
> a minimum of 3 +1 votes.
>
> [ ] +1 Release this package as Apache Spark 2.3.3
> [ ] -1 Do not release this package because ...
>
> To learn more about Apache Spark, please see http://spark.apache.org/
>
> The tag to be voted on is v2.3.3-rc1 (commit 
> b5ea9330e3072e99841270b10dc1d2248127064b):
> https://github.com/apache/spark/tree/v2.3.3-rc1
>
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-bin/
>
> Signatures used for Spark RCs can be found in this file:
> https://dist.apache.org/repos/dist/dev/spark/KEYS
>
> The staging repository for this release can be found at:
> https://repository.apache.org/content/repositories/orgapachespark-1297
>
> The documentation corresponding to this release can be found at:
> https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc1-docs/
>
> The list of bug fixes going into 2.3.3 can be found at the following URL:
> https://issues.apache.org/jira/projects/SPARK/versions/12343759
>
> FAQ
>
> =
> How can I help test this release?
> =
>
> If you are a Spark user, you can help us test this release by taking
> an existing Spark workload and running on this release candidate, then
> reporting any regressions.
>
> If you're working in PySpark you can set up a virtual env and install
> the current RC and see if anything important breaks, in the Java/Scala
> you can add the staging repository to your projects resolvers and test
> with the RC (make sure to clean up the artifact cache before/after so
> you don't end up building with a out of date RC going forward).
>
> ===
> What should happen to JIRA tickets still targeting 2.3.3?
> ===
>
> The current list of open tickets targeted at 2.3.3 can be found at:
> https://issues.apache.org/jira/projects/SPARK and search for "Target 
> Version/s" = 2.3.3
>
> Committers should look at those and triage. Extremely important bug
> fixes, documentation, and API tweaks that impact compatibility should
> be worked on immediately. Everything else please retarget to an
> appropriate release.
>
> ==
> But my bug isn't fixed?
> ==
>
> In order to make timely releases, we will typically not hold the
> release unless the bug in question is a regression from the previous
> release. That being said, if there is something which is a regression
> that has not been correctly targeted please ping me or a committer to
> help target the issue.
>
> --
> ---
> Takeshi Yamamuro

-
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org