kkzi commented on issue #910:
URL: https://github.com/apache/tsfile/issues/910#issuecomment-5330521373
Follow-up: the production integration that hit this bug uses exactly the
same public Tablet API as the reproducer above.
In the production TsFile archive module (`TsFileArchive.cpp`), data is
written through the standard `Tablet` path:
```cpp
storage::Tablet curTablet(device, tabletSchemas, tabletRowsLimit);
// tablet rows default 2048
curTablet.set_timestamps(colTsBuf.data(), rows);
curTablet.set_column_values(colSchemaOfRow[c], colValBuf.data(), nullptr,
...);
const int writeRet = alignedGroup ? w0->write_tablet_aligned(curTablet)
: w0->write_tablet(curTablet);
// DOUBLE + TS_2DIFF + UNCOMPRESSED
```
- Defaults: value encoding `TS_2DIFF`, compression `UNCOMPRESSED` (both
configurable), `TabletMaxRows` default 2048.
- Non-aligned groups use `write_tablet`; aligned groups use
`register_aligned_timeseries` + `write_tablet_aligned`.
- With 2048-row tablets, a DOUBLE page routinely carries 16 TS_2DIFF
segments (128 values each); the Java `FloatDecoder` mis-parse happens on the
second segment, so any page with more than 128 points fails `selfCheck`.
A real C105 flight-data file written by this module reproduces the exact
failure (`self-check cannot proceed ... because : 0` → `file has crashed`), and
the standalone 200-value `repro_ts2diff` file reproduces it identically. The
reported issue is not specific to any custom/internal API usage.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]