tbar4 commented on PR #1100:
URL:
https://github.com/apache/datafusion-ballista/pull/1100#issuecomment-2458128122
> @tbar4 lets take one step at the time, we can take optional feature at the
later time.
>
> I had a quick look at API an i wonder if rather than having objects per
type of execution, and then build method call, we make builder pattern similar
to spark, something like:
>
> ```rust
> from Ballista import Builder
> ctx : SessionContext = Ballista.builder.config("ballista.job.name","Super
Cool Ballista Python Job").standalone()
> ```
>
> and
>
> ```rust
> ctx : SessionContext = Ballista.builder.config("ballista.job.name","Super
Cool Ballista Python Job").remote("df://localhost:50050")
> ```
>
> we can even add (optional, but possible)
>
> ```rust
> ctx : SessionContext = Ballista.builder.local()
> ```
>
> which would provide a local datafusion execution.
>
> I find this approach a bit better than `Standalone().build()`, wdyt?
I think I can get this knocked out pretty easily. I like this pattern better
and will allow for more customization in the future.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org
For additional commands, e-mail: github-h...@datafusion.apache.org
