Skip to content

Redundant volatiles in BaseTopNAlgorithm.BaseArrayProvider #3857

@leventov

Description

@leventov

https://github.com/druid-io/druid/blob/master/processing/src/main/java/io/druid/query/topn/BaseTopNAlgorithm.java#L176-L179

Similar to situation here: #3797 (comment)

I expect that at most one field should remain volatile. Or none (probably a little refactoring needed).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions