Skip to content

Fix InMemoryDataTableStore.getRows returning only first matching bucket#7276

Closed
jkschneider wants to merge 1 commit intomainfrom
fix/data-table-store-getrows-aggregation
Closed

Fix InMemoryDataTableStore.getRows returning only first matching bucket#7276
jkschneider wants to merge 1 commit intomainfrom
fix/data-table-store-getrows-aggregation

Conversation

@jkschneider
Copy link
Copy Markdown
Member

Summary

  • InMemoryDataTableStore.getRows returned early on the first (name, group) match instead of iterating all buckets and concatenating rows. When multiple ungrouped tables with different instance names contributed rows, only the first bucket's rows were returned.
  • Adds a test (getRowsAggregatesAcrossUngroupedBuckets) that inserts rows into two ungrouped tables with different instance names and asserts getRows returns rows from both. This test fails against the old code and passes with the fix.

Test plan

  • New test getRowsAggregatesAcrossUngroupedBuckets verified to fail before fix and pass after
  • Existing DataTableStoreTest tests continue to pass

getRows returned early on the first (name, group) match instead of
concatenating rows from all matching buckets. This caused ungrouped
tables with different instance names to lose rows.
@github-project-automation github-project-automation bot moved this to In Progress in OpenRewrite Apr 3, 2026
@jkschneider jkschneider marked this pull request as draft April 3, 2026 20:02
@jkschneider jkschneider closed this Apr 4, 2026
@github-project-automation github-project-automation bot moved this from In Progress to Done in OpenRewrite Apr 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant