I'm fine to have the version number, but breaking API compatibility should be discussed separately in the community. We decided to strive to avoid breaking APIs even in major versions and made a policy for that.
https://spark.apache.org/versioning-policy.html > The Spark project strives to avoid breaking APIs or silently changing behavior, even at major versions. On Mon, Sep 13, 2021 at 9:00 PM Senthil Kumar <sen...@gmail.com> wrote: > We can have a feature(new tab) in Spark UI for Data, so that we can use it > to display data related metrics and detect skewness in the data. It will be > helpful to the users to understand their data in a better/deeper way. > > On Tue, Sep 14, 2021 at 4:07 AM Sean Owen <sro...@gmail.com> wrote: > >> Sure, doesn't hurt to have a placeholder. >> >> On Mon, Sep 13, 2021, 5:32 PM Holden Karau <hol...@pigscanfly.ca> wrote: >> >>> Hi Folks, >>> >>> I'm going through the Spark 3.2 tickets just to make sure were not >>> missing anything important and I was wondering what folks thoughts are on >>> adding Spark 4 so we can target API breaking changes to the next major >>> version and avoid loosing track of the issue. >>> >>> Cheers, >>> >>> >>> Holden :) >>> >>> -- >>> Twitter: https://twitter.com/holdenkarau >>> Books (Learning Spark, High Performance Spark, etc.): >>> https://amzn.to/2MaRAG9 <https://amzn.to/2MaRAG9> >>> YouTube Live Streams: https://www.youtube.com/user/holdenkarau >>> >> > > -- > Senthil kumar >
