wrong result for selecting high local perference prefix in best path selection algorithm

An example to make it simple, peer A 100.0.0.101 and peer B 100.0.0.102 connect to ODL which is 100.0.0.254. Configured A with default lp 100, and B with 200. Both of A and B announced a prefix which is 53.0.0.100/32. The RIB on ODL gotten from restconf API ''/restconf/operational/bgp-rib:bgp-rib/rib/example-bgp-rib’ showed that 53.0.0.100/32 with next hop 100.0.0.101, lp 100 instead of the right one with lp 200 from 100.0.0.102.