Files
tasks/common/persistence/sql/sqlplugin/postgresql
0b938cd605 [CHASM] Avoid a double-encode by passing Metadata and Data as separate fields (#7507)
## What changed?
- CHASM nodes are now internally represented as split distinctly between
Metadata and Data parts.
- Additional columns were added to SQL plugins, bumping the SQL schema
- No change was made to the Cassandra columns; instead, ExecutionManager
ensures that when running on Cassandra, the entire node continues to be
represented in a single blob, to avoid lowering Cass performance
post-change.

## Why?
Before, a ChasmNode contained both its metadata fields, and the user
data blob. Decoding a ChasmNode would cause an additional (often large,
relative to the metadata) allocation to store the inner data blob, as
well as additional memcpys while encoding/decoding. With this change,
the data field can be passed along as-is, opaquely, while the metadata
field can be decoded without additional penalty from a large data blob.

## How did you test it?
- Updated tests

---------

Co-authored-by: Yichao Yang <[email protected]>
2025-03-24 17:06:10 +00:00
..
2024-08-23 14:48:10 -06:00
2024-08-23 14:48:10 -06:00
2024-08-23 14:48:10 -06:00
2024-08-23 14:48:10 -06:00