https://issues.apache.org/jira/browse/ARROW-7085

@pitrou @wesm PTAL

@fexolm The Parser, ColumnBuilder.. APIs are currently internal, and slightly messy. We'll have to think about cleaning them up before making them public.

@pitrou the other option is to define a class inherited from ExtentionType with an additional method for creating column builder for that type.

This solution wouldn't require changing stable API.
I can make a sample implementation if it sounds better for you.

No, this would have the same problem since ColumnBuilder takes a BlockParser.

@pitrou We would not mind if this ExtensionType based approach is implemented in internal namespace as well, so it will not appear as a stable API right away.
[updated] I mean ExtensionType is already defined. What we need is additional flexibility in of its usage which will not touch public API but will allow to define our custom converter even if it is internal or uses internal inputs at the moment,

Closing this PR since it has grown stale. I think it would be worth defining a public API for this, but we're going to have to take time to propose clean, well-documented interfaces rather than poking through internal APIs into the public API without any changes