Skip to content

MB-61890 - Introducing config for zap layer#2066

Merged
abhinavdangeti merged 4 commits into
masterfrom
zapConfig
Feb 19, 2026
Merged

MB-61890 - Introducing config for zap layer#2066
abhinavdangeti merged 4 commits into
masterfrom
zapConfig

Conversation

@Thejas-bhat
Copy link
Copy Markdown
Member

@Thejas-bhat Thejas-bhat commented Aug 29, 2024

  • Currently there isn't a concept of config at the zap layer and whatever storage level configurations present (at various points of index lifetime) are global variables. This forces all indexes' segments to use same values irrespective of how heavy indexes are.
  • The PR introduces segmentConfig that can be used to pass index specific config values for the zap level. This would help in the future to perform any index specific tuning at the zap level.
  • This involves extending the existing interface's Merge, Open and New APIs.
  • The segmentConfig is something that's constructed by parsing the scorch.config and persisted in the index_meta.json file.

@Thejas-bhat Thejas-bhat marked this pull request as ready for review August 29, 2024 14:50
@metonymic-smokey metonymic-smokey changed the title Introducing config for zap layer MB-61890 - Introducing config for zap layer Sep 5, 2024
@abhinavdangeti abhinavdangeti added this to the v2.5.0 milestone Sep 5, 2024
@abhinavdangeti abhinavdangeti removed the request for review from moshaad7 October 17, 2024 17:49
@abhinavdangeti abhinavdangeti modified the milestones: v2.5.0, v2.5.1 Feb 25, 2025
@abhinavdangeti abhinavdangeti modified the milestones: v2.5.1, v2.5.2 Apr 16, 2025
@abhinavdangeti abhinavdangeti modified the milestones: v2.5.2, v2.5.3 May 22, 2025
@abhinavdangeti abhinavdangeti modified the milestones: v2.5.3, v2.6.0 Jul 21, 2025
@abhinavdangeti abhinavdangeti removed this from the v2.6.0 milestone Nov 13, 2025
@Thejas-bhat Thejas-bhat requested review from capemox and maneuvertomars and removed request for metonymic-smokey January 15, 2026 22:47
@abhinavdangeti abhinavdangeti added this to the v2.6.0 milestone Jan 26, 2026
Copy link
Copy Markdown
Member

@abhinavdangeti abhinavdangeti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems this commit makes it clear that you'll need to introduce new APIs (blevesearch/zapx#256) to all versions of zapx.

Comment thread index/scorch/merge.go Outdated
CascadingRadium
CascadingRadium previously approved these changes Feb 4, 2026
Copy link
Copy Markdown
Member

@abhinavdangeti abhinavdangeti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine, but let's wait to get all the zapx version commits in before we take this.

@coveralls
Copy link
Copy Markdown

Coverage Status

coverage: 52.68% (+0.03%) from 52.648%
when pulling b087625 on zapConfig
into 15049fc on master.

Comment thread index/scorch/segment_plugin.go
@abhinavdangeti abhinavdangeti merged commit d0785de into master Feb 19, 2026
10 checks passed
@github-project-automation github-project-automation Bot moved this from In Progress to Done in Fast Merge Feb 19, 2026
@abhinavdangeti abhinavdangeti deleted the zapConfig branch February 19, 2026 17:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

No open projects
Status: Done

Development

Successfully merging this pull request may close these issues.

5 participants