aboutsummaryrefslogtreecommitdiffstats
path: root/feature-distributed-locking/src/main/feature/install/enable
diff options
context:
space:
mode:
authorJim Hahn <jrh3@att.com>2020-10-29 18:15:51 -0400
committerJim Hahn <jrh3@att.com>2020-11-02 18:17:49 -0500
commitdc6c4a21d46909dad59f4bd16cb6d4fc29fcce77 (patch)
treeef6bd7f152e189913c802d07aea43c83f3dc97e2 /feature-distributed-locking/src/main/feature/install/enable
parentd418aff3a9fd547941e40978c648d6209d332e37 (diff)
Make feature-pooling-dmaap work without filtering
As DMaaP server-side filtering has been deprecated, modified feature-pooling-dmaap to work without it. The new design assumes that each pdp gets its own unique consumer group, thus all pdps receive all events. Each pdp then uses the bucket assignments to determine whether or not to process the event. Note: this means that events no longer have to be forwarded to the correct host, thus the "Forward" class has been deleted. Other than that, the code already did post-filtering of events so most of it still works even without server-side filtering. As a result, most of the effort was in simply removing code that no longer applies. Per review comments: Modified code to use the event hash code instead of the request ID has code when routing events. This eliminated the need for the extractor classes and related properties. Replaced amsterdam and beijing properties with usecases properties. Issue-ID: POLICY-2881 Change-Id: I87e4f98c14f419593879c278d7da053c80575553 Signed-off-by: Jim Hahn <jrh3@att.com>
Diffstat (limited to 'feature-distributed-locking/src/main/feature/install/enable')
0 files changed, 0 insertions, 0 deletions