+1 from me as well
> On Oct 27, 2021, at 6:58 PM, Brian Hulette <bhule...@apache.org> wrote: > > > +1 > > I don't think there's much reason to keep the compute code around when > there's a more performant, easier to use alternative. I think the only unique > feature of the arrow compute code was the ability to optimize queries on > dictionary-encoded columns, but Jeff added this to Arquero almost a year ago > now [1]. > > Brian > > [1] https://github.com/uwdata/arquero/issues/86 > >> On Wed, Oct 27, 2021 at 4:46 PM Dominik Moritz <domor...@apache.org> wrote: >> Dear Arrow community, >> >> We are proposing to remove the compute code from Arrow JS. Right now, the >> compute code is encapsulated in a DataFrame class that extends Table. The >> DataFrame implements a few functions such as filtering and counting with >> expressions. However, the predicate code is not very efficient (it’s >> interpreted) and most people only use Arrow to read data but don’t need >> compute. There are also more complete alternatives for doing compute on >> Arrow data structures such as Arquero (https://github.com/uwdata/arquero). >> By removing the compute code, we can focus on the IPC reading/writing and >> primitive types. >> >> The vote will be open for at least 72 hours. >> >> [ ] +1 Remove compute from Arrow JS >> [ ] +0 >> [ ] -1 Do not remove compute because… >> >> Thank you, >> Dominik
