+1 On Tue, Oct 3, 2017 at 11:00 PM, Kazuaki Ishizaki <ishiz...@jp.ibm.com> wrote:
> +1 (non-binding) > > I tested it on Ubuntu 16.04 and OpenJDK8 on ppc64le. All of the tests for > core/sql-core/sql-catalyst/mllib/mllib-local have passed. > > $ java -version > openjdk version "1.8.0_131" > OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-2ubuntu1. > 16.04.3-b11) > OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode) > > % build/mvn -DskipTests -Phive -Phive-thriftserver -Pyarn -Phadoop-2.7 -T > 24 clean package install > % build/mvn -Phive -Phive-thriftserver -Pyarn -Phadoop-2.7 test -pl core > -pl 'sql/core' -pl 'sql/catalyst' -pl mllib -pl mllib-local > ... > Run completed in 12 minutes, 19 seconds. > Total number of tests run: 1035 > Suites: completed 166, aborted 0 > Tests: succeeded 1035, failed 0, canceled 0, ignored 5, pending 0 > All tests passed. > [INFO] ------------------------------------------------------------ > ------------ > [INFO] Reactor Summary: > [INFO] > [INFO] Spark Project Core ................................. SUCCESS > [17:13 min] > [INFO] Spark Project ML Local Library ..................... SUCCESS [ > 5.759 s] > [INFO] Spark Project Catalyst ............................. SUCCESS [09:48 > min] > [INFO] Spark Project SQL .................................. SUCCESS > [12:01 min] > [INFO] Spark Project ML Library ........................... SUCCESS [15:16 > min] > [INFO] ------------------------------------------------------------ > ------------ > [INFO] BUILD SUCCESS > [INFO] ------------------------------------------------------------ > ------------ > [INFO] Total time: 54:28 min > [INFO] Finished at: 2017-10-03T23:53:33+09:00 > [INFO] Final Memory: 112M/322M > [INFO] ------------------------------------------------------------ > ------------ > [WARNING] The requested profile "hive" could not be activated because it > does not exist. > > Kazuaki Ishizaki > > > > > From: Dongjoon Hyun <dongjoon.h...@gmail.com> > To: Spark dev list <dev@spark.apache.org> > Date: 2017/10/03 23:23 > Subject: Re: [VOTE] Spark 2.1.2 (RC4) > ------------------------------ > > > > +1 (non-binding) > > Dongjoon. > > On Tue, Oct 3, 2017 at 5:13 AM, Herman van Hövell tot Westerflier < > *hvanhov...@databricks.com* <hvanhov...@databricks.com>> wrote: > +1 > > On Tue, Oct 3, 2017 at 1:32 PM, Sean Owen <*so...@cloudera.com* > <so...@cloudera.com>> wrote: > +1 same as last RC. Tests pass, sigs and hashes are OK. > > On Tue, Oct 3, 2017 at 7:24 AM Holden Karau <*hol...@pigscanfly.ca* > <hol...@pigscanfly.ca>> wrote: > Please vote on releasing the following candidate as Apache Spark > version 2.1.2. The vote is open until Saturday October 7th at 9:00 PST and > passes if a majority of at least 3 +1 PMC votes are cast. > > [ ] +1 Release this package as Apache Spark 2.1.2 > [ ] -1 Do not release this package because ... > > > To learn more about Apache Spark, please see *https://spark.apache.org/* > <https://urldefense.proofpoint.com/v2/url?u=https-3A__spark.apache.org_&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=b70dG_9wpCdZSkBJahHYQ4IwKMdp2hQM29f-ZCGj9Pg&m=cF_k_lDBFIRW7HXbcjAQSyY9hc2aq_au5TZdMKxvSQ8&s=oO_pnYI_zEguPHn9cIWmJabSdYmutt2Gd9UO7riE1h0&e=> > > The tag to be voted on is *v2.1.2-rc4* > <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_spark_tree_v2.1.2-2Drc4&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=b70dG_9wpCdZSkBJahHYQ4IwKMdp2hQM29f-ZCGj9Pg&m=cF_k_lDBFIRW7HXbcjAQSyY9hc2aq_au5TZdMKxvSQ8&s=CM1lVDnnKDkUYUnsSXYcCng3VmusP6LGYZFHsm_a_Uc&e=> > (2abaea9e40fce81cd4626498e0f5c28a70917499) > > List of JIRA tickets resolved in this release can be found *with this > filter.* > <https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_issues_-3Fjql-3Dproject-2520-253D-2520SPARK-2520AND-2520fixVersion-2520-253D-25202.1.2&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=b70dG_9wpCdZSkBJahHYQ4IwKMdp2hQM29f-ZCGj9Pg&m=cF_k_lDBFIRW7HXbcjAQSyY9hc2aq_au5TZdMKxvSQ8&s=HIL-A2GxedK0z2b3ojaTst1-DdnH6r3BdoE7-4-fOfY&e=> > > The release files, including signatures, digests, etc. can be found at: > *https://home.apache.org/~holden/spark-2.1.2-rc4-bin/* > <https://urldefense.proofpoint.com/v2/url?u=https-3A__home.apache.org_-7Eholden_spark-2D2.1.2-2Drc4-2Dbin_&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=b70dG_9wpCdZSkBJahHYQ4IwKMdp2hQM29f-ZCGj9Pg&m=cF_k_lDBFIRW7HXbcjAQSyY9hc2aq_au5TZdMKxvSQ8&s=zen74-f0FyM_GzLU-2TIYj_Sz0l-xuxmSMbmYZtNEf8&e=> > > Release artifacts are signed with a key from: > *https://people.apache.org/~holden/holdens_keys.asc* > <https://urldefense.proofpoint.com/v2/url?u=https-3A__people.apache.org_-7Eholden_holdens-5Fkeys.asc&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=b70dG_9wpCdZSkBJahHYQ4IwKMdp2hQM29f-ZCGj9Pg&m=cF_k_lDBFIRW7HXbcjAQSyY9hc2aq_au5TZdMKxvSQ8&s=IJtPSqPzOPPR8YC8MFk4h5A3JEj-oX9-jPQr5-mTDwk&e=> > > The staging repository for this release can be found at: > *https://repository.apache.org/content/repositories/orgapachespark-1252* > <https://urldefense.proofpoint.com/v2/url?u=https-3A__repository.apache.org_content_repositories_orgapachespark-2D1252&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=b70dG_9wpCdZSkBJahHYQ4IwKMdp2hQM29f-ZCGj9Pg&m=cF_k_lDBFIRW7HXbcjAQSyY9hc2aq_au5TZdMKxvSQ8&s=VE211HRYaInhszp_zyf9dU3aXEIcEqO1IsNbeeYn79A&e=> > > The documentation corresponding to this release can be found at: > *https://people.apache.org/~holden/spark-2.1.2-rc4-docs/* > <https://urldefense.proofpoint.com/v2/url?u=https-3A__people.apache.org_-7Eholden_spark-2D2.1.2-2Drc4-2Ddocs_&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=b70dG_9wpCdZSkBJahHYQ4IwKMdp2hQM29f-ZCGj9Pg&m=cF_k_lDBFIRW7HXbcjAQSyY9hc2aq_au5TZdMKxvSQ8&s=Y5IXtXZ5XML6p89aHUkYB-UIdFLgxHRx-ObFUhvnlWo&e=> > > > *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.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 2.1.3. > > *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 2.1.1. That being said if > there is something which is a regression form 2.1.1 that has not been > correctly targeted please ping a committer to help target the issue (you > can see the *open issues listed as impacting Spark 2.1.1 & 2.1.2* > <https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_SPARK-2D21985-3Fjql-3Dproject-2520-253D-2520SPARK-2520AND-2520status-2520-253D-2520OPEN-2520AND-2520-28affectedVersion-2520-253D-25202.1.2-2520OR-2520affectedVersion-2520-253D-25202.1.1-29&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=b70dG_9wpCdZSkBJahHYQ4IwKMdp2hQM29f-ZCGj9Pg&m=cF_k_lDBFIRW7HXbcjAQSyY9hc2aq_au5TZdMKxvSQ8&s=ily1j3njGjxPUe369q6irX_yECLa1jRgTseS-gmqDRA&e=> > ) > > *What are the unresolved* *issues targeted for 2.1.2* > <https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_SPARK-2D21985-3Fjql-3Dproject-2520-253D-2520SPARK-2520AND-2520status-2520in-2520-28Open-252C-2520-2522In-2520Progress-2522-252C-2520Reopened-29-2520AND-2520-2522Target-2520Version-252Fs-2522-2520-253D-25202.1.2&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=b70dG_9wpCdZSkBJahHYQ4IwKMdp2hQM29f-ZCGj9Pg&m=cF_k_lDBFIRW7HXbcjAQSyY9hc2aq_au5TZdMKxvSQ8&s=jina3dyKmrG3I6g1QBh2vbyafUdATaS6CwUTD0_AqlU&e=> > ? > > At this time there are no open unresolved issues. > > *Is there anything different about this release?* > > This is the first release in awhile not built on the AMPLAB Jenkins. This > is good because it means future releases can more easily be built and > signed securely (and I've been updating the documentation in > *https://github.com/apache/spark-website/pull/66* > <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_spark-2Dwebsite_pull_66&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=b70dG_9wpCdZSkBJahHYQ4IwKMdp2hQM29f-ZCGj9Pg&m=cF_k_lDBFIRW7HXbcjAQSyY9hc2aq_au5TZdMKxvSQ8&s=7bXZCc6_vzMMe_xhzkbfp7iBGafk5C3tF4dKghY3QiI&e=> > as > I progress), however the chances of a mistake are higher with any change > like this. If there something you normally take for granted as correct when > checking a release, please double check this time :) > > *Should I be committing code to branch-2.1?* > > Thanks for asking! Please treat this stage in the RC process as "code > freeze" so bug fixes only. If you're uncertain if something should be back > ported please reach out. If you do commit to branch-2.1 please tag your > JIRA issue fix version for 2.1.3 and if we cut another RC I'll move > the 2.1.3 fixed into 2.1.2 as appropriate. > > *What happened to RC3?* > > Some R+zinc interactions kept it from getting out the door. > -- > Twitter: *https://twitter.com/holdenkarau* > <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_holdenkarau&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=b70dG_9wpCdZSkBJahHYQ4IwKMdp2hQM29f-ZCGj9Pg&m=cF_k_lDBFIRW7HXbcjAQSyY9hc2aq_au5TZdMKxvSQ8&s=P9h5SBpzXhoiU3Q-z7f9KQTxMrqiXdBvmAnJDdXfqDM&e=> > > > >
