+1 On Tue, Jan 19, 2021 at 4:38 PM Yang,Jie(INF) <yangji...@baidu.com> wrote:
> +1 > > > > *发件人**: *Gengliang Wang <ltn...@gmail.com> > *日期**: *2021年1月19日 星期二 下午3:04 > *收件人**: *Jungtaek Lim <kabhwan.opensou...@gmail.com> > *抄送**: *Yuming Wang <wgy...@gmail.com>, Hyukjin Kwon <gurwls...@gmail.com>, > dev <dev@spark.apache.org> > *主题**: *Re: [VOTE] Release Spark 3.1.1 (RC1) > > > > +1 (non-binding) > > > > > > On Tue, Jan 19, 2021 at 2:05 PM Jungtaek Lim <kabhwan.opensou...@gmail.com> > wrote: > > +1 (non-binding) > > > > * verified signature and sha for all files (there's a glitch which I'll > describe in below) > > * built source (DISCLAIMER: didn't run tests) and made custom > distribution, and built a docker image based on the distribution > > - used profiles: kubernetes, hadoop-3.2, hadoop-cloud > > * ran some SS PySpark queries (Rate to Kafka, Kafka to Kafka) with Spark > on k8s (used MinIO - s3 compatible - as checkpoint location) > > - for Kafka reader, tested both approaches: newer (offset via admin > client) and older (offset via consumer) > > * ran simple batch query with magic committer against MinIO storage & > dynamic volume provisioning (with NFS) > > * verified DataStreamReader.table & DataStreamWriter.toTable works in > PySpark (which also verifies on Scala API as well) > > * ran test stateful SS queries and checked the new additions of SS UI > (state store & watermark information) > > > > A glitch from verifying sha; the file format of sha512 is different > between source targz and others. My tool succeeded with others and failed > with source targz, though I confirmed sha itself is the same. Not a blocker > but would be ideal if we can make it be consistent. > > > > Thanks for driving the release process! > > > > On Tue, Jan 19, 2021 at 2:25 PM Yuming Wang <wgy...@gmail.com> wrote: > > +1. > > > > On Tue, Jan 19, 2021 at 7:54 AM Hyukjin Kwon <gurwls...@gmail.com> wrote: > > I forgot to say :). I'll start with my +1. > > > > On Mon, 18 Jan 2021, 21:06 Hyukjin Kwon, <gurwls...@gmail.com> wrote: > > Please vote on releasing the following candidate as Apache Spark version > 3.1.1. > > > > The vote is open until January 22nd 4PM 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 3.1.0 > > [ ] -1 Do not release this package because ... > > > > To learn more about Apache Spark, please see http://spark.apache.org/ > <https://mailshield.baidu.com/check?q=eJcUboQ1HRRomPZKEwRzpl69wA8DbI%2fNIiRNsQ%3d%3d> > > > > The tag to be voted on is v3.1.1-rc1 (commit > 53fe365edb948d0e05a5ccb62f349cd9fcb4bb5d): > > https://github.com/apache/spark/tree/v3.1.1-rc1 > <https://mailshield.baidu.com/check?q=zbqz3MYVbEd1sSCjZ7dX%2fJD3avlvWUFYXV4XHiBGkriN7VNdz23Md8oHpZhgZNHwTl%2b6pw%3d%3d> > > > > The release files, including signatures, digests, etc. can be found at: > > https://dist.apache.org/repos/dist/dev/spark/v3.1.1-rc1-bin/ > <https://mailshield.baidu.com/check?q=aBUdO5bKlQP35zEYFIwQs7sgFgN%2bTaWXQBUm6jT9tZTdMsKBOoSjep4yC04DBd060%2bkzEn8GSVRVmKCdNzWkNA%3d%3d> > > > > Signatures used for Spark RCs can be found in this file: > > https://dist.apache.org/repos/dist/dev/spark/KEYS > <https://mailshield.baidu.com/check?q=E6fHbSXEWw02TTJBpc3bfA9mi7ea0YiWcNHkm%2fDJxwlaWinGnMdaoO1PahHhgj00vKwcbElpuHA%3d> > > > > The staging repository for this release can be found at: > > https://repository.apache.org/content/repositories/orgapachespark-1364 > <https://mailshield.baidu.com/check?q=VRy9actRQw148oVco9CQh18idb79jbu25AC5BncG93syW0z8%2fFyrn5GAVgSG4PWYkKnxeNs0GJ3sGOlFC5uqGY74FJQLjdigMqU%2fPg%3d%3d> > > > > The documentation corresponding to this release can be found at: > > https://dist.apache.org/repos/dist/dev/spark/v3.1.1-rc1-docs/ > <https://mailshield.baidu.com/check?q=BuqQ5RY8M9vELgwt8zAa05tgP3VLDkM5wCGFLETwfH46h6yW0kFTMFljBWN0FCBxW9L25rwk2mugmwQie48oBugdDnc%3d> > > > > The list of bug fixes going into 3.1.1 can be found at the following URL: > > https://s.apache.org/41kf2 > <https://mailshield.baidu.com/check?q=Gtq8o%2b5UFC60hSOfJ6de%2bsVEWcpGcb7IwyVvW%2fuTK%2b8%3d> > > > > This release is using the release script of the tag v3.1.1-rc1. > > > > FAQ > > > > =================== > What happened to 3.1.0? > > =================== > > There was a technical issue during Apache Spark 3.1.0 preparation, and it > was discussed and decided to skip 3.1.0. > Please see > https://spark.apache.org/news/next-official-release-spark-3.1.1.html > <https://mailshield.baidu.com/check?q=QADCNwn2yfjg8NxQF0Z8XlCKD1pWeI%2flwL0aMyvhC5KneSAMGvjx1iPMGubKOn50YiVHcBkWh1%2br%2frGpo5dzzA8QFvRqTagn> > for more details. > > ========================= > > 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 via "pip install > https://dist.apache.org/repos/dist/dev/spark/v3.1.1-rc1-bin/pyspark-3.1.1.tar.gz > <https://mailshield.baidu.com/check?q=joMLIhLN%2fq%2bgh99cyr7a5mYBSslorlP3n7SbsxeOrBa4d8OqZg7koIbumZ4L5seSeHBV040KquPwDlv9VGEgq28%2fLQt7ywvG1IJqBcDHgXhI2laB> > " > 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 an out of date RC going forward). > > > > =========================================== > > What should happen to JIRA tickets still targeting 3.1.1? > > =========================================== > > > > The current list of open tickets targeted at 3.1.1 can be found at: > > https://issues.apache.org/jira/projects/SPARK > <https://mailshield.baidu.com/check?q=4UUpJqq41y71Gnuj0qTUYo6hTjqzT7oytN6x%2fvgC5XUtQUC8MfJ77tj7K70O%2f1QMmNoa1A%3d%3d> > and > search for "Target Version/s" = 3.1.1 > > > > 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. > > > >
