chore(relational_layer): add value_meta in relational write interfaces

[wcy-fdu]

What's changed and what's your intention?

As title, relational layer provides hash and non-hash write interfaces.

Checklist

• I have written necessary docs and comments
• I have added necessary unit tests and integration tests

Refer to a related PR or issue link (optional)

[codecov]

Codecov Report

Merging #2194 (424246d) into main (9bce175) will decrease coverage by 0.02%.
The diff coverage is 44.82%.

@@            Coverage Diff             @@
##             main    #2194      +/-   ##
==========================================
- Coverage   70.92%   70.90%   -0.03%     
==========================================
  Files         650      650              
  Lines       82587    82642      +55     
==========================================
+ Hits        58578    58600      +22     
- Misses      24009    24042      +33     

Flag	Coverage Δ
rust	70.90% <44.82%> (-0.03%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
src/stream/src/executor_v2/mview/materialize.rs	91.33% <ø> (ø)
src/storage/src/table/cell_based_table.rs	79.53% <41.25%> (-10.01%)	⬇️
src/storage/src/table/state_table.rs	90.40% <85.71%> (-0.09%)	⬇️
.../src/executor/managed_state/aggregation/extreme.rs	90.02% <0.00%> (-0.27%)	⬇️
src/source/src/manager.rs	45.74% <0.00%> (ø)
src/meta/src/cluster/mod.rs	59.39% <0.00%> (ø)
src/batch/src/executor2/insert.rs	80.82% <0.00%> (ø)
src/source/src/connector_source.rs	0.00% <0.00%> (ø)
src/common/src/types/ordered_float.rs	24.30% <0.00%> (+0.19%)	⬆️
src/batch/src/executor2/delete.rs	79.50% <0.00%> (+0.47%)	⬆️
... and 3 more

📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

[xx01cyx]

LGTM. But I think an alternative is to have an inner method with a flag param indicating whether value meta needs computing, like:

fn batch_write_rows_inner(..., stateful_flag: bool) -> StorageResult<()> {
    ...
    if stateful_flag {
        // compute value meta
    }
}

and call this inner method in batch_write_rows and batch_write_rows_inner to make the code clearer.

[xx01cyx]

But since it is a storage write API, maybe we should put efficiency first and reduce unnecessary function call and if branch...

[wcy-fdu]

But since it is a storage write API, maybe we should put efficiency first and reduce unnecessary function call and if branch...

I prefer reduce unnecessary if judgment, which may pass a stateful_flag while write to storage.

[skyzh]

Two small issues:

• value meta isn't always pk. Should have another option to specify column ids (or column indices) of value meta.
• batch_write_rows_with_value_meta seems to have a lot of code in common with batch_write_rows. Maybe we can do some dedups.

[skyzh]

If you are interested, you may also refactor MaterializeExecutor to use distribution key for value meta.

#1971