Great!

It saves us from always specifying "Pandas API on Spark" in PR titles.

Thanks!


Xinrong Meng

Software Engineer

Databricks


On Tue, May 17, 2022 at 1:08 AM Maciej <mszymkiew...@gmail.com> wrote:

> Sounds good!
>
> +1
>
> On 5/17/22 06:08, Yikun Jiang wrote:
> > It's a pretty good idea, +1.
> >
> > To be clear in Github:
> >
> > - For each PR Title: [SPARK-XXX][PYTHON][PS] The Pandas on spark pr title
> > (*still keep [PYTHON]* and [PS] new added)
> >
> > - For PR label: new added: `PANDAS API ON Spark`, still keep: `PYTHON`,
> > `CORE`
> > (*still keep `PYTHON`, `CORE`* and `PANDAS API ON SPARK` new added)
> > https://github.com/apache/spark/pull/36574
> > <https://github.com/apache/spark/pull/36574>
> >
> > Right?
> >
> > Regards,
> > Yikun
> >
> >
> > On Tue, May 17, 2022 at 11:26 AM Hyukjin Kwon <gurwls...@gmail.com
> > <mailto:gurwls...@gmail.com>> wrote:
> >
> >     Hi all,
> >
> >     What about we introduce a component in JIRA "Pandas API on Spark",
> >     and use "PS"  (pandas-on-Spark) in PR titles? We already use "ps" in
> >     many places when we: import pyspark.pandas as ps.
> >     This is similar to "Structured Streaming" in JIRA, and "SS" in PR
> title.
> >
> >     I think it'd be easier to track the changes here with that.
> >     Currently it's a bit difficult to identify it from pure PySpark
> changes.
> >
>
>
> --
> Best regards,
> Maciej Szymkiewicz
>
> Web: https://zero323.net
> PGP: A30CEF0C31A501EC
>

Reply via email to