Skip to content

CAS: store full-length keys in JSON metadata objects - #2288

Draft
k-morozov wants to merge 2 commits into
antalya-26.6from
cas/full_key_json_nodex
Draft

CAS: store full-length keys in JSON metadata objects#2288
k-morozov wants to merge 2 commits into
antalya-26.6from
cas/full_key_json_nodex

Conversation

@k-morozov

@k-morozov k-morozov commented Aug 28, 2026

Copy link
Copy Markdown

Changelog category (leave one):

  • New Feature
  • Backward Incompatible Change

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

Store full-length keys in JSON CAS metadata objects instead of abbreviated ones

Documentation entry for user-facing changes

...

CI/CD Options

Exclude tests:

  • Fast test
  • Integration Tests
  • Stateless tests
  • Stateful tests
  • Unit tests
  • Performance tests
  • Aarch64 tests
  • All with ASAN
  • All with TSAN
  • All with MSAN
  • All with UBSAN
  • All with Coverage
  • All Regression
  • Disable CI Cache

Regression jobs to run:

  • Fast suites (mostly <1h)
  • Aggregate Functions (2h)
  • Alter (1.5h)
  • Benchmark (30m)
  • CAS (content-addressed storage; Antalya only)
  • ClickHouse Keeper (1h)
  • Iceberg (2h)
  • LDAP (1h)
  • OAuth (5m)
  • Parquet (1.5h)
  • RBAC (1.5h)
  • SSL Server (1h)
  • S3 (2h)
  • S3 Export (2h)
  • Swarms (30m)
  • Tiered Storage (2h)

Signed-off-by: Konstantin Morozov <just.morozov.k@gmail.com>
@github-actions

github-actions Bot commented Aug 28, 2026

Copy link
Copy Markdown

Workflow [PR], commit [37417b6b]

Signed-off-by: Konstantin Morozov <just.morozov.k@gmail.com>
@k-morozov k-morozov changed the title CAS use full keys in json CAS: store full-length keys in JSON metadata objects Aug 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant