Skip to content

feat: Support aggregation client in preprocessing steps#618

Open
ThanKarab wants to merge 1 commit into
masterfrom
feature/MIP-1273_add_agg_client_in_preprocessing_steps
Open

feat: Support aggregation client in preprocessing steps#618
ThanKarab wants to merge 1 commit into
masterfrom
feature/MIP-1273_add_agg_client_in_preprocessing_steps

Conversation

@ThanKarab

Copy link
Copy Markdown
Member

No description provided.

@ThanKarab ThanKarab marked this pull request as ready for review July 6, 2026 21:23

@KFilippopolitis KFilippopolitis left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need configurable aggregation client parameter names? Since aggregation client injection is a framework-level API, enforcing a single reserved parameter (agg_client) would simplify the runtime and avoid reflection-based injection. The same applies to preprocessing steps. Unless backward compatibility requires custom names, I would remove agg_client_name and always inject agg_client.
WDYT?

data=data,
metadata=metadata,
agg_client=agg_client,
agg_client_name=_get_udf_aggregation_client_name(udf_registry_key),

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we need this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants