andygrove opened a new pull request, #3667:
URL: https://github.com/apache/datafusion-comet/pull/3667
## Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases. You can
link an issue to this PR using the GitHub syntax. For example `Closes #123`
indicates that this PR will close issue #123.
-->
N/A
## Rationale for this change
<!--
Why are you proposing this change? If this is already explained clearly in
the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand your
changes and offer better suggestions for fixes.
-->
I would like to split the `core` create (~35k LOC) into separate crates by
functional areas, particularly for `parquet` and `shuffle`. IMO, this will make
it easier to make sure we have comprehensive test coverage and good code
coverage in each crate. This PR is the first step towards this.
## What changes are included in this PR?
<!--
There is no need to duplicate the description in the issue here but it is
sometimes worth providing a summary of the individual changes in this PR.
-->
Extract JNI bridge code (errors, jvm_bridge, SparkError, QueryContext) from
core and spark-expr into a new datafusion-comet-jvm-bridge crate.
Moved to jvm-bridge:
- errors.rs (CometError, ExecutionError, ExpressionError, JNI helpers)
- jvm_bridge/ (JNI macros, JVMClasses, cached method IDs)
- SparkError, SparkErrorWithContext, SparkResult
- QueryContext, QueryContextMap, create_query_context_map
spark-expr re-exports SparkError/QueryContext types for backward
compatibility.
## How are these changes tested?
<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code
If tests are not included in your PR, please explain why (for example, are
they covered by existing tests)?
-->
Existing tests
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
