Using "in" condition type with no items results in an exception on Elastic

[peterbanda]

HTTP/1.1 400 Bad Request
{"error":{"root_cause":[{"type":"parsing_exception","reason":"[terms] query requires a field name, followed by array of terms or a document lookup specification","line":1,"col":37}],"type":"parsing_exception","reason":"[terms] query requires a field name, followed by array of terms or a document lookup specification","line":1,"col":37},"status":400}

[peterbanda]

Data-access layer on the server side should return [] if any condition has an empty in-list for any data storage type (Mongo, Elastic, Ignite).

On the client/UI side this situation should be prevented by an error message or silently by removing a "erroneous" condition.