[STALE] feat: metadata indexing infrastructure (Phase 1)#4
Open
[STALE] feat: metadata indexing infrastructure (Phase 1)#4
Conversation
Add issue_metadata_index table that indexes top-level scalar values from Issue.Metadata JSON blobs. This establishes the "Index as Cache" pattern (Option A from Discussion steveyegge#1588) where JSONL metadata is the canonical source of truth and SQLite provides fast querying. Changes: - Migration 044: create issue_metadata_index table with composite indexes on (key, value_text) and (key, value_int) - New metadata_index.go: updateMetadataIndex() indexes scalars including one level of nesting for namespaced keys (e.g., jira.story_points); RebuildMetadataIndex() for bd doctor - Wire indexing into all write paths: insertIssueStrict (single create), insertIssuesStrict (batch create), insertIssues (import), UpdateIssue (queries.go), and transaction UpdateIssue - 6 tests covering string/int/float/bool types, nested keys, update refresh, empty metadata, and full rebuild Closes steveyegge#1589 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Status: NOT VIABLE FOR MERGE
This branch targets SQLite code that was deleted during the Dolt migration.
It would need a complete rewrite against the Dolt backend to be viable.
Keeping as reference for the indexing approach/design.
Original Summary
internal/storage/sqlite/which no longer exists in mainRebase conflicts