Fix Materialize CI: retry readSchema to handle eventual consistency - #1332
Fix Materialize CI: retry readSchema to handle eventual consistency#1332mrigger merged 3 commits into
Conversation
Sorry, something went wrong.
Materialize's information_schema is eventually consistent — tables and columns may not be visible immediately after creation. This caused IndexOutOfBoundsException when generators called getRandomTable() on an empty or incomplete schema. Retry readSchema() until the snapshot has no tables with empty columns, the table count has not regressed, and — after the initial read — the table list is not suspiciously empty. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
| // Materialize's information_schema is eventually consistent: tables and columns | ||
| // may not be visible immediately after creation. Retry until the snapshot is | ||
| // consistent. |
There was a problem hiding this comment.
That's not correct. The information_schema is strongly consistent. I'm not sure what's going wrong though!
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks, I've fixed the comment. I think it's quite likely that this is an issue within Materialize. I could not reproduce it locally, though. Perhaps we can operate under the assumption that it is a bug for now and use the workaround proposed in this PR, or what do you think?
Sorry, something went wrong.
There was a problem hiding this comment.
Merging this for now, as it will make the CI test green and would allows us to catch any other issues.
Sorry, something went wrong.
Remove incorrect claim about eventual consistency in readSchema comment. Add MaterializeBugs class with bugSchemaReadIncomplete flag to guard the retry logic, following the MySQLBugs pattern. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Materialize's information_schema is eventually consistent — tables and columns may not be visible immediately after creation. This caused IndexOutOfBoundsException when generators called getRandomTable() on an empty or incomplete schema. Retry readSchema() until the snapshot has no tables with empty columns and the table count has not regressed.