Determining time encoding and compression in a TsFile
- Dominant language
- Java
- Stars
- 203
- Forks
- 104
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 33
Description
The time compression and encoding can be specified via config. However, this information is not included in a TsFile, and one cannot know the time compression and encoding if he only has the TsFile.
For TsFile V4, there is a property map at the end of the file, so we can and WE SHOULD record the time compression and encoding in the map.
For TsFile V3 and older, unfortunately, there seems to be no good solution, but maybe we can provide some protection mechanism: if the decoding or uncompressing of a time page fails, the reader should try another decoding/compression automatically until success or all methods have failed.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by tracing the TsFile V4 property map and the reader's time-page decoding and decompression paths; define how V4 metadata is recorded and how V3 and older files try alternatives, with tests covering successful detection and complete failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100