I would be definitely Interested and planning to start to contribute on those radars. Can someone guide me where to start?
On Fri, Mar 17, 2023 at 3:13 PM Jacek Laskowski <ja...@japila.pl> wrote: > Hey Maxim, > > Very great kudos for the idea! > > Pozdrawiam, > Jacek Laskowski > ---- > "The Internals Of" Online Books <https://books.japila.pl/> > Follow me on https://twitter.com/jaceklaskowski > > <https://twitter.com/jaceklaskowski> > > > On Fri, Mar 17, 2023 at 2:18 PM Maxim Gekk > <maxim.g...@databricks.com.invalid> wrote: > >> Hello Devs, >> >> If you want to contribute to Apache Spark but don't know where to start >> from, I would like to propose new starter tasks for you. All the tasks >> below in the umbrella JIRA >> https://issues.apache.org/jira/browse/SPARK-37935 aim to improve Spark >> error messages: >> - SPARK-42838: Assign a name to the error class _LEGACY_ERROR_TEMP_2000 >> - SPARK-42839: Assign a name to the error class _LEGACY_ERROR_TEMP_2003 >> - SPARK-42840: Assign a name to the error class _LEGACY_ERROR_TEMP_2004 >> - SPARK-42841: Assign a name to the error class _LEGACY_ERROR_TEMP_2005 >> - SPARK-42842: Assign a name to the error class _LEGACY_ERROR_TEMP_2006 >> - SPARK-42843: Assign a name to the error class _LEGACY_ERROR_TEMP_2007 >> - SPARK-42844: Assign a name to the error class _LEGACY_ERROR_TEMP_2008 >> - SPARK-42845: Assign a name to the error class _LEGACY_ERROR_TEMP_2010 >> - SPARK-42846: Assign a name to the error class _LEGACY_ERROR_TEMP_2011 >> - SPARK-42847: Assign a name to the error class _LEGACY_ERROR_TEMP_2013 >> >> Improving Spark errors makes you more familiar with Spark code base, and >> you will impact on user experience with Spark SQL directly. >> >> If you have any questions, please, leave comments in the JIRAs, and feel >> free to ping me (and other contributors) in your PRs. >> >> Maxim Gekk >> >> Software Engineer >> >> Databricks, Inc. >> >
