You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are stack traces:
java.lang.NullPointerException: Cannot invoke "java.util.Map.get(Object)" because "this.currentRecord" is null
at com.clickhouse.client.api.data_formats.internal.AbstractBinaryFormatReader.readValue(AbstractBinaryFormatReader.java:104) ~[client-v2-0.6.4.jar:client-v2 0.6.4 (revision: fc8d92e)]
at com.clickhouse.client.api.data_formats.internal.AbstractBinaryFormatReader.getString(AbstractBinaryFormatReader.java:169) ~[client-v2-0.6.4.jar:client-v2 0.6.4 (revision: fc8d92e)]
at com.clickhouse.client.api.data_formats.internal.BinaryReaderBackedRecord.getString(BinaryReaderBackedRecord.java:32) ~[client-v2-0.6.4.jar:client-v2 0.6.4 (revision: fc8d92e)]
The text was updated successfully, but these errors were encountered:
This issue occurs on all query() method, including:
public CompletableFuture query(String sqlQuery, Map<String, Object> queryParams, QuerySettings settings)
This is still happening in 0.6.5
As a workaround for those who found this issue before it's fixed, check the number of records prior to iterate:
Describe your feedback
It should not go inside the for loop because the query return empty dataset. See my example below
Code example
There are stack traces:
java.lang.NullPointerException: Cannot invoke "java.util.Map.get(Object)" because "this.currentRecord" is null
at com.clickhouse.client.api.data_formats.internal.AbstractBinaryFormatReader.readValue(AbstractBinaryFormatReader.java:104) ~[client-v2-0.6.4.jar:client-v2 0.6.4 (revision: fc8d92e)]
at com.clickhouse.client.api.data_formats.internal.AbstractBinaryFormatReader.getString(AbstractBinaryFormatReader.java:169) ~[client-v2-0.6.4.jar:client-v2 0.6.4 (revision: fc8d92e)]
at com.clickhouse.client.api.data_formats.internal.BinaryReaderBackedRecord.getString(BinaryReaderBackedRecord.java:32) ~[client-v2-0.6.4.jar:client-v2 0.6.4 (revision: fc8d92e)]
The text was updated successfully, but these errors were encountered: