Skip to content

Dynamic data type for @Configured properties where value is provided by either InputColumn or some enumerable setting #6

@kaspersorensen

Description

@kaspersorensen

For quite a lot of analyzers we could use a smarter way to configure in situations where input can either be provided in a fixed form (typically an enum) or be dynamic based on input column values.

For instance: Any aggregation could be based on record count (fixed "1" value) or based on some count in a column. To support both options, you would typically provide two @configured properties, leading to a confusion since the user has to decide on one rule using two separate properties.

A rough/initial proposal could be like this:

enum MyOption {
  RECORD_COUNT
}

@Configured
DynamicOption<MyOptions, Number> count;

...

MyOption countOption = count.getEnumValue()
InputColumn<Number> countInputColumn = count.getInputColumn();

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions