Yes I think when we initially discussed adding the JS dataframe ops we
argued that it could be a separate library within the Apache Arrow
monorepo, since some users will just want the ability to read/write
arrow data, and we shouldn't force them to pull in a dataframe API they
won't be using.
Right now there's not much to the dataframe parts of arrow js, so I
think the cost is pretty minimal, but as it grows it will be a good idea
to separate it out. Feel free to make a JIRA for this, maybe it can be a
goal for the next JS release.
On 03/07/2018 10:00 AM, Naveen Michaud-Agrawal wrote:
Any thoughts on splitting out the dataframe like parts into a separate
library, keeping arrowjs to just handle loading data out of the arrow