beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Groh (JIRA)" <>
Subject [jira] [Created] (BEAM-847) DelelgatingAggregator uses UUID.randomUUID, which is synchronized
Date Thu, 27 Oct 2016 16:41:58 GMT
Thomas Groh created BEAM-847:

             Summary: DelelgatingAggregator uses UUID.randomUUID, which is synchronized
                 Key: BEAM-847
             Project: Beam
          Issue Type: Bug
          Components: runner-core, runner-dataflow, runner-direct, runner-flink, sdk-java-core
            Reporter: Thomas Groh
            Assignee: Thomas Groh

This normally would not be a problem, as users are expected to create Aggregators in a non-performance-sensitive
fashion. {{GroupAlsoByWindowViaWindowSet}} also creates an {{Aggregator}}, and this is a runner-provided
{{DoFn}} (and may be created some arbitrary number of times on workers); this call should
not use a shared resource.

As the IDs of an {{Aggregator}} are used only to ensure that an {{Aggregator}} has a consistent
identity across a serialization boundary, used in the {{AggregatorPipelineExtractor}}, these
can be less random so long as they remain mostly unique.

This message was sent by Atlassian JIRA

View raw message