[CALCITE-4787] Move core to use Immutables instead of ImmutableBeans

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.28.0
• Labels: pull-request-available
• Assignee: Jacques Nadeau
• Reporter: Jacques Nadeau
• Created: 19/Sep/21 23:50
• Updated: 18/Sep/23 15:19
• Resolved: 04/Oct/21 17:02

Description

In the creation of CALCITE-3328, Immutables was discussed as an alternative to a custom implementation. This ticket is to evaluate the impact to the codebase of changing. Ideally, introduction of immutables would both add flexibility and reduce the amount of code associated with these classes.

Immutables works via annotation processor which means that it is should be relatively seamless to build systems and IDEs.

The switch would also make it easier to work with these objects types in the context of aot compilation tools like GraalVM.

 

This initial task covers key classes in the core module. Will open up follow-on tickets for other locations.

Issue Links

• blocks: CALCITE-4786 Facilitate use of graalvm native-image compilation
• causes: CALCITE-5332 Configuring PruneEmptyRules is cumbersome
• causes: CALCITE-6010 RelRule.Config requires too much ceremony for trivial cases
• incorporates: CALCITE-4839 Remove remnants of ImmutableBeans post 1.28 release
• links to: GitHub Pull Request #2531
• mentioned in: Page Loading...