+1(non-binding) I add to the difference will it make that it will also simplify package maintenance and easily release a bug fix/new feature without needing to wait for Pyspark to release.
On Mon, Apr 1, 2024 at 4:56 PM Chao Sun <sunc...@apache.org> wrote: > +1 > > On Sun, Mar 31, 2024 at 10:31 PM Hyukjin Kwon <gurwls...@apache.org> > wrote: > >> Oh I didn't send the discussion thread out as it's pretty simple, >> non-invasive and the discussion was sort of done as part of the Spark >> Connect initial discussion .. >> >> On Mon, Apr 1, 2024 at 1:59 PM Mridul Muralidharan <mri...@gmail.com> >> wrote: >> >>> >>> Can you point me to the SPIP’s discussion thread please ? >>> I was not able to find it, but I was on vacation, and so might have >>> missed this … >>> >>> >>> Regards, >>> Mridul >>> >> >>> On Sun, Mar 31, 2024 at 9:08 PM Haejoon Lee >>> <haejoon....@databricks.com.invalid> wrote: >>> >>>> +1 >>>> >>>> On Mon, Apr 1, 2024 at 10:15 AM Hyukjin Kwon <gurwls...@apache.org> >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> I'd like to start the vote for SPIP: Pure Python Package in PyPI >>>>> (Spark Connect) >>>>> >>>>> JIRA <https://issues.apache.org/jira/browse/SPARK-47540> >>>>> Prototype <https://github.com/apache/spark/pull/45053> >>>>> SPIP doc >>>>> <https://docs.google.com/document/d/1Pund40wGRuB72LX6L7cliMDVoXTPR-xx4IkPmMLaZXk/edit?usp=sharing> >>>>> >>>>> Please vote on the SPIP for the next 72 hours: >>>>> >>>>> [ ] +1: Accept the proposal as an official SPIP >>>>> [ ] +0 >>>>> [ ] -1: I don’t think this is a good idea because … >>>>> >>>>> Thanks. >>>>> >>>>
