Take advantage of AugmentationIdentifier.create() 65/82865/2
authorRobert Varga <robert.varga@pantheon.tech>
Tue, 4 Jun 2019 17:51:43 +0000 (19:51 +0200)
committerRobert Varga <nite@hq.sk>
Wed, 3 Jul 2019 06:44:02 +0000 (06:44 +0000)
When we are reading an augmentation identifier for the first
time we can optimize the number of identifiers by consulting
the global weak cache.

JIRA: CONTROLLER-1898
Change-Id: I5cd2d87e0a7c3f01357beb1b097d4a16a6eda3e0
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
(cherry picked from commit 7c06dc0a88d544a0096ecf55e95680748f949b0f)

opendaylight/md-sal/sal-clustering-commons/src/main/java/org/opendaylight/controller/cluster/datastore/node/utils/stream/LithiumNormalizedNodeInputStreamReader.java

index ae8738e60f2d02ae82a797be6e26403f1976200b..78cb0759c7fb3ece196585e6a2058144b6ee4fd0 100755 (executable)
@@ -250,7 +250,7 @@ class LithiumNormalizedNodeInputStreamReader extends ForwardingDataInput impleme
     }
 
     AugmentationIdentifier readAugmentationIdentifier() throws IOException {
-        return new AugmentationIdentifier(readQNameSet());
+        return AugmentationIdentifier.create(readQNameSet());
     }
 
     NodeIdentifier readNodeIdentifier() throws IOException {