+1 (non-binding) - thanks Dongjoon for the work! On Wed, May 26, 2021 at 8:35 PM Dongjoon Hyun <dongjoon.h...@gmail.com> wrote:
> +1 > > Bests, > Dongjoon > > On Wed, May 26, 2021 at 7:55 PM Kent Yao <yaooq...@gmail.com> wrote: > >> +1, non-binding >> >> *Kent Yao * >> @ Data Science Center, Hangzhou Research Institute, NetEase Corp. >> *a spark enthusiast* >> *kyuubi <https://github.com/yaooqinn/kyuubi>is a >> unified multi-tenant JDBC interface for large-scale data processing and >> analytics, built on top of Apache Spark <http://spark.apache.org/>.* >> *spark-authorizer <https://github.com/yaooqinn/spark-authorizer>A Spark >> SQL extension which provides SQL Standard Authorization for **Apache >> Spark <http://spark.apache.org/>.* >> *spark-postgres <https://github.com/yaooqinn/spark-postgres> A library >> for reading data from and transferring data to Postgres / Greenplum with >> Spark SQL and DataFrames, 10~100x faster.* >> *itatchi <https://github.com/yaooqinn/spark-func-extras>A** library t**hat >> brings useful functions from various modern database management systems to >> **Apache >> Spark <http://spark.apache.org/>.* >> >> >> >> On 05/27/2021 10:44，Yuming Wang<wgy...@gmail.com> <wgy...@gmail.com> >> wrote： >> >> +1 (non-binding) >> >> On Wed, May 26, 2021 at 11:27 PM Maxim Gekk <maxim.g...@databricks.com> >> wrote: >> >>> +1 (non-binding) >>> >>> On Mon, May 24, 2021 at 9:14 AM Dongjoon Hyun <dongjoon.h...@gmail.com> >>> wrote: >>> >>>> Please vote on releasing the following candidate as Apache Spark >>>> version 3.1.2. >>>> >>>> The vote is open until May 27th 1AM (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.2 >>>> [ ] -1 Do not release this package because ... >>>> >>>> To learn more about Apache Spark, please see https://spark.apache.org/ >>>> >>>> The tag to be voted on is v3.1.2-rc1 (commit >>>> de351e30a90dd988b133b3d00fa6218bfcaba8b8): >>>> https://github.com/apache/spark/tree/v3.1.2-rc1 >>>> >>>> The release files, including signatures, digests, etc. can be found at: >>>> https://dist.apache.org/repos/dist/dev/spark/v3.1.2-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-1384/ >>>> >>>> The documentation corresponding to this release can be found at: >>>> https://dist.apache.org/repos/dist/dev/spark/v3.1.2-rc1-docs/ >>>> >>>> The list of bug fixes going into 3.1.2 can be found at the following >>>> URL: >>>> https://issues.apache.org/jira/projects/SPARK/versions/12349602 >>>> >>>> This release is using the release script of the tag v3.1.2-rc1. >>>> >>>> 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 3.1.2? >>>> =========================================== >>>> >>>> The current list of open tickets targeted at 3.1.2 can be found at: >>>> https://issues.apache.org/jira/projects/SPARK and search for "Target >>>> Version/s" = 3.1.2 >>>> >>>> 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. >>>> >>>
