Closed bestbeforetoday closed 1 month ago
If you agree with this approach, I would be happy to take on this change.
I brought this up in the substrait sync yesterday and the response was generally positive.
In terms of your proposal, I think splitting out the CLI component into isthmus-cli
and leaving the core package as isthmus
makes the most sense, as this will minimize the amount of works our downstreams will need to do to migrate.
Resolved by PR #249 and published in v0.31.0.
The isthmus component currently contains both library code that is useful to other components, and a CLI command implementation. This means that code that depends on the isthmus component as a library is forced to pull in CLI-specific dependencies, which includes a concrete logging provider (as described in issue #243).
I propose splitting the current content of the isthmus component into two: a library and CLI component. The library component could remain as isthmus since projects likely already depend on that component, or could be renamed to something like substrait-calcite. The CLI portion could be named isthmus-cli, or could remain as isthmus if the library component used a different name.