rangareddy commented on issue #17266: URL: https://github.com/apache/hudi/issues/17266#issuecomment-5365808674
This issue was reviewed as part of the JIRA-migrated backlog triage (HUDI-8733). **Findings: this is a test-campaign deliverable rather than a code change, and there is no harness in the repo for it.** The workload described - two streaming ingestion writers producing conflicts, plus async table services, plus all metadata-table indexes, with simultaneous queries across Spark, Flink and Hudi Streamer - cannot be confirmed or refuted from the repository, and no such soak harness exists on `master`. What would make this closable is an owner, an environment, and the results recorded on the ticket: the exact workload definition, how long it ran, which non-blocking concurrency control configuration was used, and what failed. Without that, "done" is undefined. Related: #17279 (HUDI-8736) covers simplifying the archival / savepoint / restore / cleaning interplays, which is much of what this campaign would stress. Sequencing the soak run after that work would make its failures more meaningful. Keeping this open. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
