GH-51697: [Dev] Apply integration name filters to Flight scenarios - #51698
Draft
shatrughnaupadhyay wants to merge 1 commit into
Draft
shatrughnaupadhyay wants to merge 1 commit into
shatrughnaupadhyay wants to merge 1 commit into
Conversation
|
|
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
2 participants
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.
archery integration --run-flight -k flight_sqlfilters JSON fixtures but still runs unrelated Flight scenarios. Apply the same substring filter to the Flight scenario catalog and clarify the CLI help.Fixes #51697. Related to the conformance work around #41840; this patch only addresses scenario selection.
Validation: 11 focused tests passed, including eight new cases covering empty/default selectors, SQL-family and exact-scenario matches, unmatched selectors, catalog preservation, and serial/parallel dispatch. Flake8, autopep8 and whitespace checks passed. The dispatch tests use test doubles; they do not establish cross-language conformance. Native C++/Java integration remains unverified locally.
Draft: human author review is pending. The author must review, understand and own the changes before marking this ready.