Submitting a PR and marking it as a "Draft" would be fine and so would writing up a design doc and soliciting feedback on this mailing list. It really depends on what you think would help you the most at this point. If you submit a draft PR, reply to this email thread with a link to increase its visibility.
Is the original issue [1] sufficiently descriptive of the work you're looking to do? If so, comment "take" on it which will assign the issue to you, letting others know you're working on it. If it's not, you might open a new issue and we can close the old one. [1] https://github.com/apache/arrow/issues/27001 On Fri, Nov 3, 2023 at 3:47 PM Logan Riggs <logan.ri...@dremio.com.invalid> wrote: > > Hi, > > I'm working on adding List support to Gandiva and its turning into a fairly > complicated feature. I have code that works for a few list types (ie > list<int32> etc) but I'm not at the stage yet for a formal PR (needs more > tests and some tests are broken, code needs to be cleaned up some). Is > there a general process for getting early feedback on a proposed change? > For example a work in progress PR or design doc review maybe? > > For reference, my change is an expansion/continuation of this abandoned PR: > https://github.com/apache/arrow/pull/9060 > > Thanks > Logan
