16 lines
1.3 KiB
Markdown
16 lines
1.3 KiB
Markdown
|
# Change: Handle integer overflows and persist unprocessable data
|
||
|
|
|
||
|
|
## Why
|
||
|
|
Hardware devices occasionally report `service_mask` or other bitmasks and counters (like `power_state`) where their unsigned values exceed PostgreSQL's signed boundaries (e.g. `uint64`, `uint32`, `uint16`). This triggers out of range database insertion errors which causes batch failure and falls back to individual row insertions. Previously, rows that failed due to data range constraints directly crashed out or were only logged to Redis, meaning fully invalid data or boundary constraint violations were fundamentally lost from DB history.
|
||
|
|
|
||
|
|
## What Changes
|
||
|
|
- Safely map completely oversized integers to signed `int64`, `int32`, `int16` 2's complement equivalents natively in Javascript (e.g. `(v << 16) >> 16` for `int2`).
|
||
|
|
- Refine the loop mechanism in `databaseManager.js` to avoid throwing errors exclusively built from data-level constraint mismatches when doing individual row fallback.
|
||
|
|
- Extend `_emitRejectedRecord` to persist any unprocessable, validation-failing, or insert-failing raw records directly into a dedicated error database table: `heartbeat_events_errors`.
|
||
|
|
|
||
|
|
## Impact
|
||
|
|
- Affected specs: `processor`
|
||
|
|
- Affected code:
|
||
|
|
- `src/processor/heartbeatProcessor.js`
|
||
|
|
- `src/db/databaseManager.js`
|