Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

high level roadmap for Arrow / Datafusion #1515

Closed
alamb opened this issue Jan 2, 2022 · 17 comments · Fixed by #1616
Closed

high level roadmap for Arrow / Datafusion #1515

alamb opened this issue Jan 2, 2022 · 17 comments · Fixed by #1616
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@alamb
Copy link
Contributor

alamb commented Jan 2, 2022

@matthewmturner and I we think it would be valuable to try making a high level roadmap for Arrow / Datafusion. Specifically, and how this differs from the existing roadmap, we are looking for a rough idea of what people plan on working on with a best efforts guess when they hope to finish. Of course nothing is binding, the goal is to make visible peoples plans so that the developers as a whole can better organize / plan efforts and users have a rough idea of feature roadmap.

There is a roadmap (https://github.com/apache/arrow-datafusion/blob/master/docs/source/specification/roadmap.md) but im interested in seeing how that translates to a more tangible plan. im cognizant of not wanting to have something that is too much of a burden to maintain, but some public strategy / structure / plan could be helpful.

Assuming we get enough feedback, we can merge everything in a unified plan.

started a doc here: https://docs.google.com/document/d/1t64vZwZnXm9MyFj2qz3xcAkSxK3Wu12giS3KrS4nDE0/edit

@alamb alamb added the enhancement New feature or request label Jan 2, 2022
@alamb
Copy link
Contributor Author

alamb commented Jan 2, 2022

Previous attempt at the same type of exercise from a year ago:

https://docs.google.com/document/d/1qspsOM_dknOxJKdGvKbC1aoVoO0M3i6x1CIo58mmN2Y

@alamb alamb added the documentation Improvements or additions to documentation label Jan 2, 2022
@xudong963
Copy link
Member

Make sense to me.
BTW, I don't have edit permission in https://docs.google.com/document/d/1t64vZwZnXm9MyFj2qz3xcAkSxK3Wu12giS3KrS4nDE0/edit

@matthewmturner
Copy link
Contributor

matthewmturner commented Jan 2, 2022

Make sense to me.

BTW, I don't have edit permission in https://docs.google.com/document/d/1t64vZwZnXm9MyFj2qz3xcAkSxK3Wu12giS3KrS4nDE0/edit

@xudong963 can you try now?

@xudong963
Copy link
Member

Make sense to me.
BTW, I don't have edit permission in https://docs.google.com/document/d/1t64vZwZnXm9MyFj2qz3xcAkSxK3Wu12giS3KrS4nDE0/edit

@xudong963 can you try now?

all right

@alamb
Copy link
Contributor Author

alamb commented Jan 3, 2022

I plan to add my content tomorrow, FWIW -- thank you for organizing this @matthewmturner

@liukun4515
Copy link
Contributor

I plan to add my content tomorrow, FWIW -- thank you for organizing this @matthewmturner

I give some suggestions on your plan. @alamb

@xudong963
Copy link
Member

I want a detailed evaluation of my time and what I want to do, which is expected to be completed this week. BTW, I'm at Oncall this week, so there's not a lot of time to get involved with Datafusion.

@matthewmturner
Copy link
Contributor

@Dandandan @pjmore do you think the work on tokomak optimizer could be added to roadmap?

@liukun4515
Copy link
Contributor

@Dandandan @pjmore do you think the work on tokomak optimizer could be added to roadmap?

is there a related issue or pull request?

@houqp
Copy link
Member

houqp commented Jan 11, 2022

@liukun4515 see #440

@liukun4515
Copy link
Contributor

@liukun4515 see #440

thanks

@matthewmturner
Copy link
Contributor

@hntd187 @xudong963 let me know if you think worth adding streaming to the roadmap (https://docs.google.com/document/d/1t64vZwZnXm9MyFj2qz3xcAkSxK3Wu12giS3KrS4nDE0/edit).

If so, and you both think its reasonable, I could add to Q1 something like "Begin prototyping a stream provider"

@hntd187
Copy link
Contributor

hntd187 commented Jan 11, 2022

@matthewmturner I'm fine with it, I know design discussions can take time through this venue so if a prototype is working and we can at least have a general idea of the direction/design we want then I’d consider that a very successful Q1.

@pjmore
Copy link
Contributor

pjmore commented Jan 12, 2022

@matthewmturner I've added a little blurb to the roadmap about the optimizer. I'm not entirely sure if the optimizer as it exists is useful so I made it clear that it is in an experimental context.

@matthewmturner
Copy link
Contributor

@yahoNanJing no pressure, but ive seen you on multiple ballista related topics and was wondering if you perhaps had any ballista related goals that you would like to add to our 2022 Q1 roadmap. doc is here in case you wanted to see what was already there https://docs.google.com/document/d/1t64vZwZnXm9MyFj2qz3xcAkSxK3Wu12giS3KrS4nDE0/edit.

@matthewmturner
Copy link
Contributor

As an update on this, I'm currently away but I plan on submitting PR to include roadmap in README later this week.

@matthewmturner
Copy link
Contributor

Working on PR for this now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants