any tasks that are important after `value_count`? ...
# daft-dev
a
any tasks that are important after
value_count
? waiting on PR comments for it before I do any more work w/ VC
.
j
Couple of user-facing asks that we’ll need folks to pick up on: • From MrKloudy: https://github.com/Eventual-Inc/Daft/issues/created_by/MisterKloudy ◦ Also the follow-on from your issue:
That would be great! The next thing I wanted to do was to retrieve the value with the highest count for each row. At first I was thinking of implementing a UDF to retrieve the list of structs, implement a custom sorting order, then return the first value. Any idea on how this could be optimized?
which we can talk about a good solution for here ◦ Hive style read (https://github.com/Eventual-Inc/Daft/issues/2957) stands out to me as a really high impact one beyond just MrKloudy
s
@Desmond Cheong when do you think you would have the PR up for the CSV reader so we can start having andrew pick some of it up?
🥳 1
d
Trying to push it now, but ran into a merge conflict. Will clean it up when I get back
https://github.com/Eventual-Inc/Daft/pull/2772/files#diff-d6caf213396c3244b82ff22222c19fa950980e5f633a639aa78e7b2d2d8bf18d current version, mostly clean. Main outstanding tasks include: • Sampling record stats • Proper schema inference instead of relying on convert options • Consider per-process buffers?