Java api: remove support for lookup cache in TermsLooukpBuilder
TermsQueryParser doesn't support the cache field anymore, so if it gets set through java api, the subsequent parsing of that query will throw error Relates to #12870
This commit is contained in:
parent
470f5370b9
commit
2e0b548b06
|
@ -34,7 +34,6 @@ public class TermsLookupQueryBuilder extends QueryBuilder {
|
|||
private String lookupId;
|
||||
private String lookupRouting;
|
||||
private String lookupPath;
|
||||
private Boolean lookupCache;
|
||||
|
||||
private String queryName;
|
||||
|
||||
|
@ -87,11 +86,6 @@ public class TermsLookupQueryBuilder extends QueryBuilder {
|
|||
return this;
|
||||
}
|
||||
|
||||
public TermsLookupQueryBuilder lookupCache(boolean lookupCache) {
|
||||
this.lookupCache = lookupCache;
|
||||
return this;
|
||||
}
|
||||
|
||||
@Override
|
||||
public void doXContent(XContentBuilder builder, Params params) throws IOException {
|
||||
builder.startObject(TermsQueryParser.NAME);
|
||||
|
@ -105,9 +99,6 @@ public class TermsLookupQueryBuilder extends QueryBuilder {
|
|||
if (lookupRouting != null) {
|
||||
builder.field("routing", lookupRouting);
|
||||
}
|
||||
if (lookupCache != null) {
|
||||
builder.field("cache", lookupCache);
|
||||
}
|
||||
builder.field("path", lookupPath);
|
||||
builder.endObject();
|
||||
|
||||
|
|
Loading…
Reference in New Issue