GitHub user zanmato1984 added a comment to the discussion: Future plans for Acero
I think this is a thoughtful and reasonable proposal. Thanks for putting it all together! It’s also delightful to see people actively using Acero “the raw way,” and I really appreciate the contributions you and your colleagues have already made. While Acero isn’t intended to be a cutting-edge query engine competing with systems like DuckDB or Velox, what we value most is enablement: giving users the ability to compose, orchestrate, and integrate Arrow-based data processing in customizable ways. From that perspective, I see your proposals as strengthening this core purpose, and none of them seem in conflict with it. I’d be glad to help continue the discussion or review individual follow-up issues/PRs. I’ve noticed some of the ongoing work already (the pipe node family idea in particular is really cool!). That said, I do need to prioritize my engagement based on factors like criticality, author enthusiasm, PR size, and my familiarity with the relative code path. So please don’t hesitate to ping me directly if there’s something you’d like me to prioritize. Overall, I really appreciate you bringing these ideas forward. It’s great to see thoughtful proposals like this shaping Acero’s future. GitHub link: https://github.com/apache/arrow/discussions/47331#discussioncomment-14142992 ---- This is an automatically sent email for user@arrow.apache.org. To unsubscribe, please send an email to: user-unsubscr...@arrow.apache.org
