FluxBuilder currently lacks support for per-component configuration because it evaluates the config block only at the global topology scope. While it successfully applies parameters like parallelism, memory, CPU, number of tasks, and groupings to ComponentDeclarer instances, forcing users to enable all other configurations topology-wide violates storm best practices for component isolation. To align Flux with storm's native capabilities, BoltDef and SpoutDef should be refactored to include a per-component config map that FluxBuilder can apply directly via declarer.addConfigurations(...).
FluxBuildercurrently lacks support for per-component configuration because it evaluates the config block only at the global topology scope. While it successfully applies parameters like parallelism, memory, CPU, number of tasks, and groupings to ComponentDeclarer instances, forcing users to enable all other configurations topology-wide violates storm best practices for component isolation. To align Flux with storm's native capabilities,BoltDefandSpoutDefshould be refactored to include a per-component config map thatFluxBuildercan apply directly viadeclarer.addConfigurations(...).