Hi,
I came to a limitation that I would like to propose a resolution to.
TL;DR; currently, users plan UDFs calls via a call of the form
let e = scalar_functions(“my_udf”, vec![col(“a”)],DataType::Float64)]);
df.select(vec![e])
The proposal is to use instead:
let f = df.registry();
let e = f.u
Cool -- thanks Jorge and Andy. I'll start working on an actual proposed PR
to merge. I really like Jorge's idea of trying to port the Aggregate
operator to use a LogicalPlan Node style and see how easy that would be.
Andrew
On Sat, Aug 22, 2020 at 12:01 PM Andy Grove wrote:
> I've added some co
Arrow Build Report for Job nightly-2020-08-23-0
All tasks:
https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-08-23-0
Failed Tasks:
- conda-osx-clang-py36:
URL:
https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-08-23-0-azure-conda-osx-clang-py36
- cond
2. [done] upload source
3. [done] upload binaries
4. [done] update website
5. [done] upload ruby gems
6. [wontdo] upload js packages
8. [done] upload C# packages
9. [done] upload rust crates
10. [in-progress] update conda recipes
11. [done] upload wheels to pypi
12. [ ] update homebrew packa