Re: Making a bugfix Arrow JS release

2018-03-07 Thread Wes McKinney
Seems like a good idea -- we could make a lerna monorepo under the js/
directory as it stands now

On Wed, Mar 7, 2018 at 11:13 AM, Brian Hulette  wrote:
> Naveen,
>
> 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.
>
> Brian
>
>
> On 03/07/2018 10:00 AM, Naveen Michaud-Agrawal wrote:
>>
>> Hi Brian,
>>
>> Any thoughts on splitting out the dataframe like parts into a separate
>> library, keeping arrowjs to just handle loading data out of the arrow
>> buffer?
>>
>> Regards,
>> Naveen Michaud-Agrawal
>>
>


Re: Making a bugfix Arrow JS release

2018-03-07 Thread Naveen Michaud-Agrawal
Hi Brian,

Any thoughts on splitting out the dataframe like parts into a separate
library, keeping arrowjs to just handle loading data out of the arrow
buffer?

Regards,
Naveen Michaud-Agrawal


Making a bugfix Arrow JS release

2018-03-05 Thread Wes McKinney
Brian mentioned on GitHub that it might be good to make a 0.3.1 JS
release due to bugs fixed since 0.3.0. Is there any other work that
needs to be merged before doing this?

Thanks
Wes