If the ecl code includes a "+", e.g. to concatenate two sets, the query fails during execution. The query is sent to the HPCC server via HTTP requests, whereby the ecl code itself is part of the request body. Since "+" is a reserved character in such a request presenting a space character, the HPCC server receives a query without a "+" and instead a " ".
There are two possible points, where the encoding could fail. Either within the Java JDBC driver when creating the HTTP request or within the HPCC server when reading the request. A logged request includes the "+" encoded with a hex code of "2b". However this request failed during execution on the server.
A workaround to solve this problem is to replace each "+" with "%2b" within the ecl code in the JDBC driver.
If the ecl code includes a "+", e.g. to concatenate two sets, the query fails during execution. The query is sent to the HPCC server via HTTP requests, whereby the ecl code itself is part of the request body. Since "+" is a reserved character in such a request presenting a space character, the HPCC server receives a query without a "+" and instead a " ".
There are two possible points, where the encoding could fail. Either within the Java JDBC driver when creating the HTTP request or within the HPCC server when reading the request. A logged request includes the "+" encoded with a hex code of "2b". However this request failed during execution on the server.
A workaround to solve this problem is to replace each "+" with "%2b" within the ecl code in the JDBC driver.