If P4InfoParser fail to parse p4info file, the parser will pass exact exception message to Apps by Cause of P4InfoParserException.
So, developer must use P4InfoParserException.getCause().getMessage() to gain exact failure cause.
This is hard to be reminded, especially when it is packed into IllegalStateException or other Exception class.
Change-Id: Ica9cd24521a9eb8700cd1cbfce573631c30cbff2
This is related to ONOS-7595. In a recent P4Runtime update, it has been
made explicit that tables can support at most 1 direct counter. Hence,
the pipeline interpreter no longer needs to provide a mapping between a
table and one of potentially many counters. If needed, such mapping can
be derived from the pipeline model (i.e. the p4info)
Change-Id: Ibdece52f35a4d187ab9dbeb90f5527b6285e9788
