sunchao opened a new pull request #29959:
URL: https://github.com/apache/spark/pull/29959
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://spark.apache.org/contributing.html
2. Ensure you have added or run the appropriate tests for your PR:
https://spark.apache.org/developer-tools.html
3. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP][SPARK-XXXX] Your PR title ...'.
4. Be sure to keep the PR description updated to reflect all changes.
5. Please write your PR title to summarize what this PR proposes.
6. If possible, provide a concise example to reproduce the issue for a
faster review.
7. If you want to add a new configuration, please read the guideline first
for naming configurations in
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
-->
### What changes were proposed in this pull request?
<!--
Please clarify what changes you are proposing. The purpose of this section
is to outline the changes and how this PR fixes the issue.
If possible, please consider writing useful notes for better and faster
reviews in your PR. See the examples below.
1. If you refactor some codes with changing classes, showing the class
hierarchy will help reviewers.
2. If you fix some SQL features, you can provide some references of other
DBMSes.
3. If there is design documentation, please add the link.
4. If there is a discussion in the mailing list, please add the link.
-->
This PR is a follow-up of #29471 and does the following improvements for
`HadoopFSUtils`:
1. Removes the extra `filterFun` from the listing API and combines it with
the `filter`.
2. Removes `SerializableBlockLocation` and `SerializableFileStatus` given
that `BlockLocation` and `FileStatus` are already serializable.
3. Simplify file listing logic by relying on `FileSystem.listLocatedStatus`
and `FileSystem.listStatus` based on the `ignoreLocality` flag. In contrast,
currently we only call `listLocatedStatus` for `DistributedFileSystem` and
`ViewFileSystem` which means Spark cannot take advantage on more efficient
`listLocatedStatus` impls from sub-`FileSystem` classes.
4. Hides the `isRootLevel` flag from the top-level API.
### Why are the changes needed?
<!--
Please clarify why the changes are needed. For instance,
1. If you propose a new API, clarify the use case for a new API.
2. If you fix a bug, you can clarify why it is a bug.
-->
Main purpose is to simplify the logic within `HadoopFSUtils`.
### Does this PR introduce _any_ user-facing change?
<!--
Note that it means *any* user-facing change including all aspects such as
the documentation fix.
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.
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.
If no, write 'No'.
-->
The change 3) above could potentially change user behavior when
`spark.sql.files.ignoreMissingFiles` is set and there are race conditions
during listing.
For instance, if locality is required and some files in the listing result
were deleted right after the listing op, but before the subsequent
`getFileBlockLocations` call in the previous code, previous impl would return
partial listing result but the current impl will return an empty set, since the
default `listLocatedStatus` will call `getFileBlockLocations` which will cause
it fail as a whole.
On the other hand, there could also be case where the new impl returns a
full list rather than a partial list in the previous impl, since we don't call
`getFileBlockLocations` as a separate step now.
### How was this patch tested?
<!--
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.
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.
If tests were not added, please describe why they were not added and/or why
it was difficult to add.
-->
Existing unit tests (e.g., `FileIndexSuite`)
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
