Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[To rel/0.12][IOTDB-1578] Set unsequnce when loading TsFile with the same establish time #3983

Merged
merged 3 commits into from Sep 21, 2021

Conversation

yschengzi
Copy link
Contributor

change rule for loading tsfile with the same establish time

e.g.
we want to load a tsfile in sequence list,
the previous tsfile has file name "a-b-c-d", the subsequence tsfile has file name "e-f-g-h".
and a(establish time of this file) is equal to e.

before:
we throw a exception with message "can not load TsFile because of can not find suitable location",
and stop loading process

now:
we load this file in unsequence folder.

and this update also solve the problem of "IoTDBLoadExternalTsfileIT.loadUnsequenceTsfileTest", it will be located in unsequence folder

@HTHou HTHou changed the title [To rel/0.12] Set unsequnce when loading TsFile with the same establish time [IOTDB-1578][To rel/0.12] Set unsequnce when loading TsFile with the same establish time Sep 16, 2021
@HTHou
Copy link
Contributor

HTHou commented Sep 17, 2021

You can revert the commit 9ba55d9 and c3a8735 by git revert...

@HTHou HTHou added the 0.12.3 label Sep 18, 2021
@yschengzi
Copy link
Contributor Author

yschengzi commented Sep 18, 2021

You can revert the commit 9ba55d9 and c3a8735 by git revert...

okk, i wil do it now

@wangchao316 wangchao316 changed the title [IOTDB-1578][To rel/0.12] Set unsequnce when loading TsFile with the same establish time [To rel/0.12][IOTDB-1578] Set unsequnce when loading TsFile with the same establish time Sep 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants