This is actually in 2.3, jira is just missing the version. https://github.com/apache/spark/pull/20765
On Wed, May 16, 2018 at 2:14 PM, kant kodali <kanth...@gmail.com> wrote: > I am not sure how SPARK-23406 is a new feature. since streaming joins are > already part of SPARK 2.3.0. The self joins didn't work because of a bug and > it is fixed but I can understand if it touches some other code paths. > > On Wed, May 16, 2018 at 3:22 AM, Marco Gaido <marcogaid...@gmail.com> wrote: >> >> I'd be against having a new feature in a minor maintenance release. I >> think such a release should contain only bugfixes. >> >> 2018-05-16 12:11 GMT+02:00 kant kodali <kanth...@gmail.com>: >>> >>> Can this https://issues.apache.org/jira/browse/SPARK-23406 be part of >>> 2.3.1? >>> >>> On Tue, May 15, 2018 at 2:07 PM, Marcelo Vanzin <van...@cloudera.com> >>> wrote: >>>> >>>> Bummer. People should still feel welcome to test the existing RC so we >>>> can rule out other issues. >>>> >>>> On Tue, May 15, 2018 at 2:04 PM, Xiao Li <gatorsm...@gmail.com> wrote: >>>> > -1 >>>> > >>>> > We have a correctness bug fix that was merged after 2.3 RC1. It would >>>> > be >>>> > nice to have that in Spark 2.3.1 release. >>>> > >>>> > https://issues.apache.org/jira/browse/SPARK-24259 >>>> > >>>> > Xiao >>>> > >>>> > >>>> > 2018-05-15 14:00 GMT-07:00 Marcelo Vanzin <van...@cloudera.com>: >>>> >> >>>> >> Please vote on releasing the following candidate as Apache Spark >>>> >> version >>>> >> 2.3.1. >>>> >> >>>> >> The vote is open until Friday, May 18, at 21:00 UTC and passes if >>>> >> a majority of at least 3 +1 PMC votes are cast. >>>> >> >>>> >> [ ] +1 Release this package as Apache Spark 2.3.1 >>>> >> [ ] -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.1-rc1 (commit cc93bc95): >>>> >> https://github.com/apache/spark/tree/v2.3.0-rc1 >>>> >> >>>> >> The release files, including signatures, digests, etc. can be found >>>> >> at: >>>> >> https://dist.apache.org/repos/dist/dev/spark/v2.3.1-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-1269/ >>>> >> >>>> >> The documentation corresponding to this release can be found at: >>>> >> https://dist.apache.org/repos/dist/dev/spark/v2.3.1-rc1-docs/ >>>> >> >>>> >> The list of bug fixes going into 2.3.1 can be found at the following >>>> >> URL: >>>> >> https://issues.apache.org/jira/projects/SPARK/versions/12342432 >>>> >> >>>> >> 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.1? >>>> >> =========================================== >>>> >> >>>> >> The current list of open tickets targeted at 2.3.1 can be found at: >>>> >> https://s.apache.org/Q3Uo >>>> >> >>>> >> 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. >>>> >> >>>> >> >>>> >> -- >>>> >> Marcelo >>>> >> >>>> >> --------------------------------------------------------------------- >>>> >> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org >>>> >> >>>> > >>>> >>>> >>>> >>>> -- >>>> Marcelo >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org >>>> >>> >> > -- Marcelo --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
