Re: Assembling an initial development roadmap for Arrow in R
We've made pretty amazing progress on the R library in the last 2
months (kudos to Romain and Javier)! I made a pass through that
initial document I drafted and opened JIRA issues for anything that
seemed well-scoped that isn't done yet. Others are free to double
check my work and open any issues for work you want to see happen
There's 37 issues open on
There's still a lot of work ahead of us (not the least figuring out
how to package / enable R users to install this software on all
platforms), but we are on our way!
On Thu, Sep 6, 2018 at 6:49 PM Wes McKinney <wesmckinn@xxxxxxxxx> wrote:
> I'm going to transfer the document over to Confluence soon and start
> creating JIRA issues. If anyone has further comments about the
> roadmap, please add them to the document or request edit access.
> On Tue, Aug 28, 2018 at 5:16 PM Wes McKinney <wesmckinn@xxxxxxxxx> wrote:
> > hi folks,
> > In light of Romain's progress on setting up an R Arrow library
> > (https://github.com/apache/arrow/pull/2489), I started putting
> > together a Google document to sketch out a general scaffold for R
> > interfaces to the Arrow ecosystem and some of the initial deliverables
> > that would be of high value to the community (like plugging into
> > Spark+Arrow):
> > https://docs.google.com/document/d/16QpgNH0_uYkVZsaVK1VyQcuSYS5vRl_d0XCSvEyh6o8/edit#heading=h.uvtfq03inyw5
> > It's essentially patterned after the analogous functionality we've
> > developed in Python. If anyone would like edit access let me know and
> > I'll add you
> > This should eventually be transferred to the dev wiki
> > (https://cwiki.apache.org/confluence/display/ARROW) but started this
> > as a Google doc to make collaboration a little lighter weight as we
> > get started.
> > After some comments collect, I suggest we move the roadmap to
> > Confluence and create as many JIRA issues as possible to capture the
> > granular work needed to develop each feature listed. I think it's OK
> > to create 50-100 R-related issues as a means of helping organize the
> > development roadmap.
> > Looking forward to getting this work off the ground!
> > thanks,
> > Wes