Details
-
Bug
-
Status: Resolved
-
Resolution: Done
-
Helium
-
None
-
None
-
Operating System: All
Platform: PC
-
1630
Description
Ever since the commit below, my log screen is filled with these log messages:
https://gist.github.com/55a222333e4805cfc7d8
2014-08-27 08:05:15.929 EDT [DOM-OPER-DCL-989] WARN o.o.y.b.d.c.i.BindingNormalizedNodeCodecRegistry - Path %s does not have a binding equivalent, should have been caught earlier
While I believe the intent is to detect an invalid case, there should be a better way to handle it.
—
commit 47ad12ec82c78d42bb6b0e57991280cb4ee56f4b
Author: Robert Varga <rovarga@cisco.com>
Date: Tue Aug 26 21:55:22 2014 +0200
BUG-650: clarify BindingNormalizedNodeSerializer API contract
Non-representable YangInstanceIdentifiers are properly reported via a
null return instead of raising an undocumented IllegalArgumentException.
Also does some implementation house-cleaning geared towards performance,
as ArrayList gives better locality.
Change-Id: Iea4717c19587fd2cc1e403aae4c5967811240e9a
Signed-off-by: Robert Varga <rovarga@cisco.com>
====
47ad12ec (Robert Varga 2014-08-26 21:55:22 +0200 132) LOG.warn("Path %s does not have a binding equivalent, should have been caught earl\
ier", path);
Attachments
Issue Links
- blocks
-
CONTROLLER-265 Milestone: Performance/Scale testing of MDSAL: Database: 20k writes/sec
- Resolved