HLRC: Fix user parser

It was strange and hacky and the parser checker didn't like it.
elastic · Oct 26, 2018 · cb20f9e · cb20f9e
1 parent 6cdf3f7
commit cb20f9e
Showing 1 changed file with 4 additions and 2 deletions.
diff --git a/client/rest-high-level/src/main/java/org/elasticsearch/client/security/PutUserResponse.java b/client/rest-high-level/src/main/java/org/elasticsearch/client/security/PutUserResponse.java
@@ -61,8 +61,10 @@ public int hashCode() {
         true, args -> new PutUserResponse((boolean) args[0]));
 
     static {
-        PARSER.declareBoolean(constructorArg(), new ParseField("created"));
-        PARSER.declareObject((a,b) -> {}, (parser, context) -> null, new ParseField("user")); // ignore the user field!
+        ConstructingObjectParser<Boolean, Void> roleMappingParser = new ConstructingObjectParser<>(
+                "put_user_response.user", true, args -> (Boolean) args[0]);
+        roleMappingParser.declareBoolean(constructorArg(), new ParseField("created"));
+        PARSER.declareObject(constructorArg(), roleMappingParser::parse, new ParseField("user"));
     }
 
     public static PutUserResponse fromXContent(XContentParser parser) throws IOException {