So I was just playing with the Swift client to build a Mac app and everything worked nicely! However, similar to the Go repository, my suggestion would be to handle issues directly in Github and not in Jira because the vast majority of initial issues will be simply compatibility issues. And creating them in Jira instead of GH where I'm already, is going to be a big overhead.
What do you think? In the Go client, we follow the approach that cross-language issues go to Jira, whereas client-specific ones go directly into Github. On Tue, Mar 11, 2025 at 3:28 AM Jules Damji <jules.da...@gmail.com> wrote: > + 1 (non-binding) > > Generally speaking, it’s a good idea to separate repositories for all > Spark Connect clients under Spark. > - better organization > - better visibility > - easier for contribution > - better for growth & extension of Spark Connect ecosystem > > Cheers > Jules > — > Sent from my iPhone > Pardon the dumb thumb typos :) > > > — > Sent from my iPhone > Pardon the dumb thumb typos :) > > On Mar 10, 2025, at 4:37 PM, Dongjoon Hyun <dongj...@apache.org> wrote: > > > > Thank you everyone for your support. > > > > New Apache Spark repository is created at the proposed location with ASF > license and open for `Spark Connect Client for Swift language` > contributions. > > > > https://github.com/apache/spark-connect-swift > > > > FYI, this repository will be managed in the same way with > `spark-kubernetes-operator` repository. > > > > Thank you again. > > > > Dongjoon. > > > > --------------------------------------------------------------------- > > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > > --------------------------------------------------------------------- > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > >
