Hi, > Required field 'timestampPrecision' was not present!
It is a new feature introduced by PR#285 [1]. The PR is merged into the master, rather than 0.8.. [1] https://github.com/apache/incubator-iotdb/pull/285 Best, ----------------------------------- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer <j.feina...@pragmaticminds.de> 于2019年8月6日周二 上午7:18写道: > Sorry, was my own mistake, I had some issues somewhere else... everything > is fine : ) > > Am 06.08.19, 15:46 schrieb "Julian Feinauer" < > j.feina...@pragmaticminds.de>: > > Hi all, > > after merging Chris PR (thank you Chris!) I just checked everything > before preparing the next RC and I observed that I get an issue with the > created binaries. > I can start the server without Problems. > But when I start the Client I get: > > 2019-08-06 15:43:32,498 [pool-1-IoTDB-JDBC-Client-thread-1] ERROR > org.apache.thrift.server.TThreadPoolServer$WorkerProcess:295 - Thrift error > occurred during processing of message. > org.apache.thrift.protocol.TProtocolException: Required field > 'timestampPrecision' was not present! Struct: > ServerProperties(version:0.8.0, > supportedTimeAggregationOperations:[max_time, min_time], > timestampPrecision:null) > at > org.apache.iotdb.service.rpc.thrift.ServerProperties.validate(ServerProperties.java:482) > at > org.apache.iotdb.service.rpc.thrift.TSIService$getProperties_result.validate(TSIService.java:11262) > at > org.apache.iotdb.service.rpc.thrift.TSIService$getProperties_result$getProperties_resultStandardScheme.write(TSIService.java:11321) > at > org.apache.iotdb.service.rpc.thrift.TSIService$getProperties_result$getProperties_resultStandardScheme.write(TSIService.java:11288) > at > org.apache.iotdb.service.rpc.thrift.TSIService$getProperties_result.write(TSIService.java:11239) > at > org.apache.thrift.ProcessFunction.process(ProcessFunction.java:53) > at > org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39) > at > org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > 2019-08-06 15:43:32,499 [pool-1-IoTDB-JDBC-Client-thread-1] INFO > org.apache.iotdb.db.service.TSServiceImpl:207 - IoTDB: receive close > operation > 2019-08-06 15:43:32,501 [pool-1-IoTDB-JDBC-Client-thread-1] INFO > org.apache.iotdb.db.service.TSServiceImpl:182 - IoTDB: receive close session > 2019-08-06 15:43:32,503 [pool-1-IoTDB-JDBC-Client-thread-1] WARN > org.apache.thrift.transport.TIOStreamTransport:112 - Error closing output > stream. > java.net.SocketException: Socket closed > at > java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:116) > at > java.net.SocketOutputStream.write(SocketOutputStream.java:153) > at > java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82) > at > java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140) > at > java.io.FilterOutputStream.close(FilterOutputStream.java:158) > at > org.apache.thrift.transport.TIOStreamTransport.close(TIOStreamTransport.java:110) > at > org.apache.thrift.transport.TSocket.close(TSocket.java:235) > at > org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:303) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > > has anybody an idea how this has happened and what to do to fix it? > > Thank you! > > Julian > > PS.: All tests do pass. > > >