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
I am using the dev-branch version. I already tried out some other gson versions, but that didnt help.
Thanks a alot !
Exception in thread "main" java.lang.RuntimeException: No-args constructor for class org.kairosdb.client.response.ErrorResponse does not exist. Register an InstanceCreator with Gson for this type to fix this problem.
at com.google.gson.MappedObjectConstructor.constructWithNoArgConstructor(MappedObjectConstructor.java:64)
.
.
.
at org.kairosdb.client.AbstractClient.query(AbstractClient.java:104)
The text was updated successfully, but these errors were encountered:
lespaula
changed the title
Runtime Exception on simple query
Runtime Exception, No-args constructor during Gson mapping
May 24, 2014
lespaula
changed the title
Runtime Exception, No-args constructor during Gson mapping
Runtime Exception, No-args constructor Issue during Gson mapping
May 24, 2014
lespaula
changed the title
Runtime Exception, No-args constructor Issue during Gson mapping
Runtime Exception, No-args constructor issue during Gson mapping
May 24, 2014
Hi,
I am getting a RuntimeException during queries, also for the most simple one like that:
QueryBuilder qb = QueryBuilder.getInstance();
qb.setStart(10, TimeUnit.HOURS).addMetric("kairosdb.http.ingest_time");
c.client.query(qb);
I am using the dev-branch version. I already tried out some other gson versions, but that didnt help.
Thanks a alot !
Exception in thread "main" java.lang.RuntimeException: No-args constructor for class org.kairosdb.client.response.ErrorResponse does not exist. Register an InstanceCreator with Gson for this type to fix this problem.
at com.google.gson.MappedObjectConstructor.constructWithNoArgConstructor(MappedObjectConstructor.java:64)
.
.
.
at org.kairosdb.client.AbstractClient.query(AbstractClient.java:104)
The text was updated successfully, but these errors were encountered: