Not a show stopper, however, I was looking at the structured streaming programming guide and under arbitrary stateful operations (https://people.apache.org/~pwendell/spark-releases/spark-2.2.0-rc5-docs/structured-streaming-programming-guide.html#arbitrary-stateful-operations) the suggestion is to take a look at the examples (Scala/Java). These link to an non existing file (called StructuredSessionization or JavaStructuredSessionization, I couldn’t find either of these files in the repository).
If the example file exists, I think it would be nice to add it, otherwise I would suggest simply removing the examples link from the programming guide (there are examples inside the group state API https://people.apache.org/~pwendell/spark-releases/spark-2.2.0-rc5-docs/api/scala/index.html#org.apache.spark.sql.streaming.GroupState).
From: Michael Armbrust [via Apache Spark Developers List] [mailto:ml+[hidden email]]
Please vote on releasing the following candidate as Apache Spark version 2.2.0. The vote is open until Friday, June 23rd, 2017 at 18:00 PST and passes if a majority of at least 3 +1 PMC votes are cast.
[ ] +1 Release this package as Apache Spark 2.2.0
[ ] -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 v2.2.0-rc5 (62e442e73a2fa663892d2edaff5f7d72d7f402ed)
List of JIRA tickets resolved can be found with this filter.
The release files, including signatures, digests, etc. can be found at:
Release artifacts are signed with the following key:
The staging repository for this release can be found at:
The documentation corresponding to this release can be found at:
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.
What should happen to JIRA tickets still targeting 2.2.0?
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.3.0 or 2.2.1.
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.
If you reply to this email, your message will be added to the discussion below:
You need to "v2.2.0" to "v2.2.0-rc5" in GitHub links because there is no v2.2.0 right now.
On Mon, Jun 26, 2017 at 12:57 AM, assaf.mendelson <[hidden email]> wrote:
|Free forum by Nabble||Edit this page|