HONEYCOMB-211: workaround for issues introduced by VPP-376

Fix HC build issues introduced by
https://gerrit.fd.io/r/#/c/2623/

Change-Id: I2e55b4c25c2f9ec505282addd4137b2dccf56f93
Signed-off-by: Marek Gradzki <mgradzki@cisco.com>

1 files changed, 4 insertions, 2 deletions

diff --git a/lisp/lisp2vpp/src/main/java/io/fd/honeycomb/lisp/translate/read/dump/executor/LocatorDumpExecutor.java b/lisp/lisp2vpp/src/main/java/io/fd/honeycomb/lisp/translate/read/dump/executor/LocatorDumpExecutor.java
index 16e6deaab..8949f44f2 100644
--- a/lisp/lisp2vpp/src/main/java/io/fd/honeycomb/lisp/translate/read/dump/executor/LocatorDumpExecutor.java
+++ b/lisp/lisp2vpp/src/main/java/io/fd/honeycomb/lisp/translate/read/dump/executor/LocatorDumpExecutor.java
@@ -48,8 +48,10 @@ public class LocatorDumpExecutor extends AbstractDumpExecutor
         checkNotNull(params, "Params for dump request not present");
 
         LispLocatorDump request = new LispLocatorDump();
-        request.locatorSetIndex = params.getLocatorSetIndex();
-        request.filter = params.getFilter();
+        request.lsIndex = params.getLocatorSetIndex();
+        // TODO: HONEYCOMB-211: fix support for locator set filtering
+        // request.lsName
+        // request.filter = params.getFilter();
 
         try {
             return TranslateUtils.getReply(vppApi.lispLocatorDump(request).toCompletableFuture());