Hey <@U071FMQUR7W>, any thoughts if we expose a `f...
# daft-dev
j
Hey @Cory Grinstead, any thoughts if we expose a
from daft import functions as F
API similar to Spark? It would read more like this:
F.ends_with(col("x"), "foo")
I’m thinking it would be nice almost entirely because it’s a much more consistent API between SQL and Python: • Nice wins for auto-generating our SQL function documentation • We can standardize naming across the Py/SQL APIs I do worry about potentially confusing folks because there will be more than 1 way of calling many of these functions (
.str.endswith(…)
). Perhaps we could start with a private module that we can use exclusively for generating our SQL docs for now (since Sphinx relies on being able to read these Python classes/objects for generating docstrings) Curious to get your thoughts
👀 1
c
hmm that's an interesting idea.
I do worry about potentially confusing folks because there will be more than 1 way of calling many of these function
Yeah I definitely worry about this too. We don't want to end up in a pandas scenario where there's 20+ ways of doing everything.
j
Yeah….
Ok maybe for now we can try doing it as a private module then. I probably will need it to get Sphinx to generate docs for us anyways