[Enh]: Spark Expr missing methods

[FBruzzesi]

Methods with one asterisk (*) are row order dependent and should be deprioritized for now, until a decision for the lazy api is reached (see stable v2 discussion).
Methods with two asterisk (**) denote a namespace - namespace methods are not included, and they are all missing as of now.

High priority:

• abs
• all
• any
• arg_true
• clip
• drop_nulls
• fill_null (* if strategy is prodived)
• filter
• is_between
• is_duplicated
• is_finite
• is_in
• is_nan
• is_unique
• len
• map_batches
• median
• mode
• n_unique
• null_count
• over
• quantile
• replace_strict
• round
• sample
• skew
• sort
• unique

Deprioritized:

• arg_max (*)
• arg_min (*)
• cum_count (*)
• cum_max (*)
• cum_min (*)
• cum_prod (*)
• cum_sum (*)
• diff (*)
• ewm_mean (*)
• gather_every (*)
• head (*)
• is_first_distinct (*)
• is_last_distinct (*)
• rolling_mean (*)
• rolling_std (*)
• rolling_sum (*)
• rolling_var (*)
• shift (*)
• tail (*)

Namespaces:

• cat (**)
• dt (**)
• list (**)
• name (**)
• str (**)

[lucas-nelson-uiuc]

Hey @FBruzzesi ,

Working on implementing scalar methods like any and all - should be ready to push later today.

Planning on working on the following methods - want to first check if my thought process is "correct".

• arg_true
• drop_nulls
• filter
• gather_every
• sort
• unique

Thinking of implementing two patterns for these methods:

# if predicate-based (e.g. drop_nulls, which uses predicate function `F.isnull`)
def method(self) -> Self:
        def _method(_input: Column) -> Column:
            from pyspark.sql import functions as F  # noqa: N812

            return F.explode(F.filter(F.array(_input), <predicate_func>))

        return self._from_call(_method, "method", returns_scalar=False)


# if not predicate-based (e.g. unique, which uses array function `F.array_distinct`)
def method(self) -> Self:
        def _method(_input: Column) -> Column:
            from pyspark.sql import functions as F  # noqa: N812

            return F.explode(<array_func>(F.array(_input)))

        return self._from_call(_method, "method", returns_scalar=False)

Not sure how expensive doing this is or if it collides with future API developments. Lmk what you think

[MarcoGorelli]

thanks @lucas-nelson-uiuc for your efforts here

can we leave the row-order dependent ones out for now, make sure we've got everything done from the others first? there's some broader api decisions we need to make for those