Conversation
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
My JIRA id is deepujain |
ctubbsii
left a comment
There was a problem hiding this comment.
+1 to the changes to the docs, and the addition of the test. However, it does not fully resolve the issue described in the JIRA issue. To fully resolve the issue, the FileSystem methods need to be fixed, because their trailing slashes do matter.
|
@ctubbsii thanks for the review. I have made additional changes. Please take another look when you have a moment. |
ctubbsii
left a comment
There was a problem hiding this comment.
I think this is an improvement, but I had a question about how API changes should be marked in my below comments.
|
💔 -1 overall
This message was automatically generated. |
|
I really hate yetus being so spammy. It makes it hard to follow the human conversation and makes trying to contribute to Hadoop, even as a reviewer or reporter, extremely painful. Its comments should be collapsed by default. |
|
@ctubbsii Thanks for approving the MR. |
f817f26 to
04e6c16
Compare
|
Rebased on trunk. Fixed bootstrap null-working-directory handling in RawLocalFileSystem and ViewFileSystem, and updated the local filesystem home-directory expectation for directory-form URIs. Ran the impacted targeted Maven tests locally and they passed. Ready for CI. |
04e6c16 to
2beb43c
Compare
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
2beb43c to
3d9e7dc
Compare
|
Rebased onto trunk and backed out the broader FileSystem URI changes that were causing the common/viewfs regressions. Kept the Path(String) vs Path(URI) docs/tests, and verified |
|
🎊 +1 overall
This message was automatically generated. |
|
@deepujain I would love for it to be merged and closed, but I am not a committer and don't have write access. |
|
CI is still green on the current head, and this branch has the narrowed scope plus prior approval. @steveloughran, when you have a moment, could you please take a look or point me to the right committer for this one? Happy to make any follow-up changes. |
steveloughran
left a comment
There was a problem hiding this comment.
move to assertj asserts to work with junit5 and backports
|
@steveloughran wrote:
What does this mean? It doesn't seem related to this PR. |
|
Applied the latest review follow-up by moving the updated |
|
Applied the latest review follow-up on July 10, 2026 by moving the updated |
d4741ce to
aa92e1e
Compare
|
Rebased this branch onto Fresh local validation on the rebased branch: Leaving this here so the refreshed CI is tied to the current trunk head. @steveloughran, when you have a moment, could you please take another look? Happy to make any follow-up changes. |
|
🎊 +1 overall
This message was automatically generated. |
|
No code changes here. The latest review follow-up is already in, the branch was rebased onto current |
|
Is @steveloughran the only active maintainer for this project that can merge a PR? This PR has been ready for months and @deepujain seems to be putting in a lot of work to keep it maintained in good faith. I don't think that's fair to them. Please merge this, or provide code reviews to suggest changes. |
|
The AssertJ follow-up from the July 9, 2026 review is already in, the branch was rebased onto current apache/trunk on July 21, 2026, and CI is green on the current head. @steveloughran, if anything is still pending from my side, I’m happy to address it. Otherwise, could you please take another look when you have a moment? |
|
No, there are others, which is good as I'm inactive |
Okay, sorry for tagging you then. You're the only one who has offered a code review. |
|
Ask on the Hadoop developer mailing lists, specifically common-dev. The trouble with tagging people in PR is not only is it completely unexpected, is that it gets completely lost in the noise of all the fully automated messages we get from anything we submit ourselves. I think I only noticed this PR precisely because I'm not actually submitting any work anymore. |
aa92e1e to
5ab8595
Compare
|
Thanks for the guidance on outreach. I posted a review request to common-dev instead of tagging individuals here. I will not use @-mention reminders on this PR going forward. For anyone following the thread: the AssertJ follow-up from the July review is on the current head (5ab8595), the branch is rebased on current apache/trunk, and Yetus is green on the latest run. Scope is Path docs/tests only (broader FileSystem URI experiments were backed out after regressions). Discussion welcome here or on the list. |
|
🎊 +1 overall
This message was automatically generated. |
|
Hi @Hexiaoqiao @slfan1989 @pan3793, HADOOP-19815 (Path URI vs String docs) has been open since March. AssertJ follow-ups from the July review are on the current head and Yetus is +1. I also posted to common-dev@. A review or a quick 'wrong approach' would unblock me. |
5ab8595 to
5e8c414
Compare
|
🎊 +1 overall
This message was automatically generated. |
5e8c414 to
73543f4
Compare
|
Rebased cleanly onto current trunk at |
|
🎊 +1 overall
This message was automatically generated. |
|
Have you reached out on the Hadoop mailing lists, as mentioned above? I think Hadoop committers aren't watching the GitHub activity from outside contributors. |
Summary
Documents how
Pathhandles trailing slashes and how that affectsURI.resolve(). The string constructor removes trailing slashes from non-root paths, while the URI constructor preserves a trailing slash after normalization.The current scope is documentation and regression coverage only. Earlier
FileSystembehavior and public API changes were removed after review and regression findings.Change
Path.java: document trailing slash normalization for string and URI constructors, and recommend path concatenation when callers should not rely on URI resolution semantics.TestPath.java: cover constructor andURI.resolve()behavior.TestLocalFileSystem.java: preserve existing local filesystem path expectations.Evidence it works
JAVA_HOME=/opt/homebrew/opt/openjdk@17/libexec/openjdk.jdk/Contents/Home PATH=/opt/homebrew/opt/openjdk@17/libexec/openjdk.jdk/Contents/Home/bin:$PATH ./mvnw -Dmaven.repo.local=/private/tmp/hadoop-m2 test -pl hadoop-common-project/hadoop-common -am -Dtest=TestChRootedFileSystem,TestChRootedFs,TestViewFileSystemWithAuthorityLocalFileSystem,TestViewFsWithAuthorityLocalFs -DskipTests=falseJIRA
Fixes HADOOP-19815