|
| 1 | +<!-- |
| 2 | +Thanks for sending a pull request! Here are some tips for you: |
| 3 | + 1. If this is your first time, please read our contributor guidelines: https://spark.apache.org/contributing.html |
| 4 | + 2. Ensure you have added or run the appropriate tests for your PR: https://spark.apache.org/developer-tools.html |
| 5 | + 3. If the PR is unfinished, add '[WIP]' in your PR title, e.g., '[WIP][SPARK-XXXX] Your PR title ...'. |
| 6 | + 4. Be sure to keep the PR description updated to reflect all changes. |
| 7 | + 5. Please write your PR title to summarize what this PR proposes. |
| 8 | + 6. If possible, provide a concise example to reproduce the issue for a faster review. |
| 9 | +--> |
| 10 | + |
| 11 | +### What changes were proposed in this pull request? |
| 12 | +<!-- |
| 13 | +Please clarify what changes you are proposing. The purpose of this section is to outline the changes and how this PR fixes the issue. |
| 14 | +If possible, please consider writing useful notes for better and faster reviews in your PR. See the examples below. |
| 15 | + 1. If you refactor some codes with changing classes, showing the class hierarchy will help reviewers. |
| 16 | + 2. If you fix some SQL features, you can provide some references of other DBMSes. |
| 17 | + 3. If there is design documentation, please add the link. |
| 18 | + 4. If there is a discussion in the mailing list, please add the link. |
| 19 | +--> |
| 20 | + |
| 21 | + |
| 22 | +### Why are the changes needed? |
| 23 | +<!-- |
| 24 | +Please clarify why the changes are needed. For instance, |
| 25 | + 1. If you propose a new API, clarify the use case for a new API. |
| 26 | + 2. If you fix a bug, you can clarify why it is a bug. |
| 27 | +--> |
| 28 | + |
| 29 | + |
| 30 | +### Does this PR introduce _any_ user-facing change? |
| 31 | +<!-- |
| 32 | +Note that it means *any* user-facing change including all aspects such as new features, bug fixes, or other behavior changes. Documentation-only updates are not considered user-facing changes. |
| 33 | + |
| 34 | +If yes, please clarify the previous behavior and the change this PR proposes - provide the console output, description and/or an example to show the behavior difference if possible. |
| 35 | +If possible, please also clarify if this is a user-facing change compared to the released Spark versions or within the unreleased branches such as master. |
| 36 | +If no, write 'No'. |
| 37 | +--> |
| 38 | + |
| 39 | + |
| 40 | +### How was this patch tested? |
| 41 | +<!-- |
| 42 | +If tests were added, say they were added here. Please make sure to add some test cases that check the changes thoroughly including negative and positive cases if possible. |
| 43 | +If it was tested in a way different from regular unit tests, please clarify how you tested step by step, ideally copy and paste-able, so that other reviewers can test and check, and descendants can verify in the future. |
| 44 | +If tests were not added, please describe why they were not added and/or why it was difficult to add. |
| 45 | +--> |
| 46 | + |
| 47 | + |
| 48 | +### Was this patch authored or co-authored using generative AI tooling? |
| 49 | +<!-- |
| 50 | +If generative AI tooling has been used in the process of authoring this patch, please include the |
| 51 | +phrase: 'Generated-by: ' followed by the name of the tool and its version. |
| 52 | +If no, write 'No'. |
| 53 | +Please refer to the [ASF Generative Tooling Guidance](https://www.apache.org/legal/generative-tooling.html) for details. |
| 54 | +--> |
0 commit comments