[IOTDB-4156] import csv has error time after timestamp_precision set ns#7032
Merged
HTHou merged 5 commits intoapache:masterfrom Aug 18, 2022
Merged
[IOTDB-4156] import csv has error time after timestamp_precision set ns#7032HTHou merged 5 commits intoapache:masterfrom
HTHou merged 5 commits intoapache:masterfrom
Conversation
HTHou
reviewed
Aug 17, 2022
wangchao316
reviewed
Aug 17, 2022
| <artifactId>iotdb-server</artifactId> | ||
| <version>${project.version}</version> | ||
| <type>test-jar</type> | ||
| <scope>test</scope> |
Member
There was a problem hiding this comment.
The client cannot directly import iotdb-server and jar. need deal...
Contributor
Author
There was a problem hiding this comment.
Using shade plugin shaded DatetimeUtils.class into iotdb-client.jar
Contributor
|
Some tests failed, PTAL |
HTHou
reviewed
Aug 18, 2022
HTHou
approved these changes
Aug 18, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a option "tp" to specify timestamp precision (ms/ns/us)