samperson1997 commented on a change in pull request #761: [IOTDB-443] Fix ReadOnlyMemChunk round float and double data incorrectly URL: https://github.com/apache/incubator-iotdb/pull/761#discussion_r374061557
########## File path: server/src/main/java/org/apache/iotdb/db/engine/storagegroup/StorageGroupProcessor.java ########## @@ -86,23 +86,14 @@ /** * For sequence data, a StorageGroupProcessor has some TsFileProcessors, in which there is only one - * TsFileProcessor in the working status. <br/> - * <p> - * There are two situations to set the working TsFileProcessor to closing status:<br/> - * <p> - * (1) when inserting data into the TsFileProcessor, and the TsFileProcessor shouldFlush() (or - * shouldClose())<br/> - * <p> - * (2) someone calls waitForAllCurrentTsFileProcessorsClosed(). (up to now, only flush command from - * cli will call this method)<br/> - * <p> - * UnSequence data has the similar process as above. - * <p> - * When a sequence TsFileProcessor is submitted to be flushed, the updateLatestFlushTimeCallback() - * method will be called as a callback.<br/> - * <p> - * When a TsFileProcessor is closed, the closeUnsealedTsFileProcessor() method will be called as a - * callback. + * TsFileProcessor in the working status. <br/> <p> There are two situations to set the working + * TsFileProcessor to closing status:<br/> <p> (1) when inserting data into the TsFileProcessor, and + * the TsFileProcessor shouldFlush() (or shouldClose())<br/> <p> (2) someone calls + * waitForAllCurrentTsFileProcessorsClosed(). (up to now, only flush command from cli will call this + * method)<br/> <p> UnSequence data has the similar process as above. <p> When a sequence + * TsFileProcessor is submitted to be flushed, the updateLatestFlushTimeCallback() method will be + * called as a callback.<br/> <p> When a TsFileProcessor is closed, the + * closeUnsealedTsFileProcessor() method will be called as a callback. Review comment: Sorry my fault... I have reversed all formats like this. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
