feat(parquet): add ParquetPushDecoder::swap_strategy for adaptive scans

.github/workflows/dev_pr.yml

@@ -44,7 +44,7 @@ jobs:
           github.event_name == 'pull_request_target' &&
             (github.event.action == 'opened' ||
              github.event.action == 'synchronize')
-        uses: actions/labeler@v6.0.1
+        uses: actions/labeler@v6.1.0
         with:
           repo-token: ${{ secrets.GITHUB_TOKEN }}
           configuration-path: .github/workflows/dev_pr/labeler.yml

CONTRIBUTING.md

@@ -256,3 +256,21 @@ If sometimes you want to commit without checking, just run `git commit` with `--
 ```bash
 git commit --no-verify -m "... commit message ..."
 ```
+
+## AI Generated Submissions
+
+This project follows the guidance for AI generated submissions used by the
+[Arrow Project](https://arrow.apache.org/docs/dev/developers/overview.html#ai-generated-code).
+As such, it is expected that you will:
+
+- Only submit a PR if you are able to debug and own the changes yourself - review all generated
+  code to understand every detail
+- Match the style and conventions used in the rest of the codebase, including PR titles and descriptions
+- Be upfront about AI usage and summarise what was AI-generated
+- If there are parts you don’t fully understand, leave comments on your own PR explaining what steps you took to verify correctness
+- Watch for AI’s tendency to generate overly verbose comments, unnecessary test cases, and incorrect fixes
+- Break down large PRs into smaller ones to make review easier
+
+It is also important for submitters to be aware of potential copyright issues. See the ASF's
+[guidance](https://www.apache.org/legal/generative-tooling.html) on AI-generated code for further
+information on licensing considerations.