platinumhamburg opened a new pull request, #2399:
URL: https://github.com/apache/fluss/pull/2399
This commit introduces a new fluss-codegen module that provides runtime code
generation capabilities using Janino compiler.
Core framework:
- CodeGeneratorContext: Manages reusable code fragments and member variables
- JavaCodeBuilder: Type-safe builder for constructing Java source code with
support for modifiers, parameters, and various code constructs
- CompileUtils: Compiles generated source code using Janino with caching
- GeneratedClass: Wrapper for generated class with source and compiled class
- CodeGenException: Exception for code generation failures
Code generators:
- EqualiserCodeGenerator: Generates RecordEqualiser implementations for
comparing InternalRow instances, supporting all Fluss data types
Key features:
- Type-safe API with Modifier enum, PrimitiveType enum, and Param class
- Comprehensive support for all Fluss data types including nested types
- Field projection support for partial row comparison
- Compiled class caching for performance
- Janino dependency shaded to avoid classpath conflicts
Testing:
- Comprehensive unit tests for all components
- Generated code snapshot tests for reviewer understanding
- 297 test cases covering edge cases and error handling
License:
- Janino (BSD 3-Clause) license included in META-INF/licenses/
<!--
*Thank you very much for contributing to Fluss - we are happy that you want
to help us improve Fluss. To help the community review your contribution in the
best possible way, please go through the checklist below, which will get the
contribution into a shape in which it can be best reviewed.*
## Contribution Checklist
- Make sure that the pull request corresponds to a [GitHub
issue](https://github.com/apache/fluss/issues). Exceptions are made for typos
in JavaDoc or documentation files, which need no issue.
- Name the pull request in the format "[component] Title of the pull
request", where *[component]* should be replaced by the name of the component
being changed. Typically, this corresponds to the component label assigned to
the issue (e.g., [kv], [log], [client], [flink]). Skip *[component]* if you are
unsure about which is the best component.
- Fill out the template below to describe the changes contributed by the
pull request. That will give reviewers the context they need to do the review.
- Make sure that the change passes the automated tests, i.e., `mvn clean
verify` passes.
- Each pull request should address only one issue, not mix up code from
multiple issues.
**(The sections below can be removed for hotfixes or typos)**
-->
### Purpose
<!-- Linking this pull request to the issue -->
Linked issue: close #2398 2398
<!-- What is the purpose of the change -->
### Brief change log
<!-- Please describe the changes made in this pull request and explain how
they address the issue -->
### Tests
<!-- List UT and IT cases to verify this change -->
### API and Format
<!-- Does this change affect API or storage format -->
### Documentation
<!-- Does this change introduce a new feature -->
--
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]
