chore: Introduce exprHandlers map in QueryPlanSerde

[andygrove]

Which issue does this PR close?

N/A

Rationale for this change

We recently started to make QueryPlanSerde more maintainable by moving expression serde logic into individual classes or objects per expression using a new CometExpressionSerde trait. This was meant as a step towards having a registry of supported expressions to reduce some of the boilerplate code and to enable automatic generation of documentation for supported expressions.

What changes are included in this PR?

Remove custom matching of some expressions and use a registry approach.

How are these changes tested?

[andygrove]

This was fixed in #1889

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 59.05%. Comparing base (f09f8af) to head (593e2c8).
Report is 281 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #1903      +/-   ##
============================================
+ Coverage     56.12%   59.05%   +2.93%     
- Complexity      976     1140     +164     
============================================
  Files           119      130      +11     
  Lines         11743    12826    +1083     
  Branches       2251     2388     +137     
============================================
+ Hits           6591     7575     +984     
- Misses         4012     4033      +21     
- Partials       1140     1218      +78     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[andygrove]

@Kontinuation you may be interested in this since it is a step towards making Comet more extensible

[comphead]

Thats neat

[comphead]

Prob we can call exprMappers or sparkToCometExprMapper ?

[andygrove]

I renamed to exprSerdeMap since the map holds CometExpressionSerde instances. I am open to other suggestions though,

[comphead]

lgtm thanks @andygrove

[parthchandra]

I assume this is not the end of it and we would be enhancing this as we go?
Some initial thoughts on that -
Add one or more annotations that can include additional information about the expressions/functions. A documentation annotation would be most useful for instance.
Auto register a new implementation

[andygrove]

I assume this is not the end of it and we would be enhancing this as we go?

Yes, this is just a first step.

Some initial thoughts on that - Add one or more annotations that can include additional information about the expressions/functions. A documentation annotation would be most useful for instance.

Yes, this will help with generating documentation from the source code rather than manually updating our docs for supported expressions.

[mbutrovich]

Nice change @andygrove!