-
Notifications
You must be signed in to change notification settings - Fork 8.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HADOOP-16965. Refactor abfs stream configuration. (#1956) #4171
base: branch-2.10
Are you sure you want to change the base?
HADOOP-16965. Refactor abfs stream configuration. (#1956) #4171
Conversation
Contributed by Mukund Thakur. (cherry picked from commit 8031c66)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 in general; small code formatting clean up, otherwise looks good
...tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azurebfs/AzureBlobFileSystemStore.java
Outdated
Show resolved
Hide resolved
Hey! Could you please update more details on why this is getting backported to branch-2.10. Thanks |
Hi @mukund-thakur , this is my first pull request in apache hadoop and thank you for the review. I am trying to backport fix for https://issues.apache.org/jira/browse/HADOOP-17215 (#2246). In order to cleanly cherry pick cherry pick this commit from branch-3.3 to branch-2.10 , I need to cherry pick several other commits before I pick this one. The commit being picked in this PR is one of those several commits. |
@arjun4084346 i don't see us merging this into asf branch-2.10.x; branch 2 is feature complete and only gets security fixes. trying to backport that far is a losing battle. private LI/MSFT fork, fine, but not the apache one |
also, process police point, i see you checked the "Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?" until you explicitly state the endpoint you ran the integration tests against, this PR doesn't actually exist |
Hi @steveloughran - 2.10 is still listed as an active release line (https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+Active+Release+Lines). Has there been a community vote on just limiting it to security fixes? What's the process for declaring the branch to have security fixes only? |
Removed that 'check' on 'object storage'. It was not applicable to this PR. |
@virajith ok, it's almost completely dead. but it still has to compile against java7, uses lots of old dependencies, including the older mockito and logging apis. backporting is a major piece of work |
it absolutely is applicable to this. please declare which azure storage endpoint you ran the entire maven integration suites of the hadoop-azure module against. no tests, no review. |
Hi @steveloughran , understood what you meant. I ran the integration tests according to the link you provided. There were 0 failures. 3 Errors were, I believe, expected. |
@virajith can you please review/merge |
I agree @steveloughran. However, at LinkedIn, we continue to run 2.10 and are looking to continue maintaining branch-2.10 given we have to backport these to our internal 2.10 branch anyway. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you specific the region where the storage account you used to run the tests is located? Also, I see that 253 tests were skipped. Can you call out why these were skipped?
...tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azurebfs/AzureBlobFileSystemStore.java
Outdated
Show resolved
Hide resolved
@steveloughran / @mukund-thakur - given the above reason on why this is needs to be backported to branch-2.10, let me know if you are ok getting this into 2.10. |
Storage account's Primary location: East US, Secondary location: West US |
💔 -1 overall
This message was automatically generated. |
I ran the integration tests on branch-2.10 and that also has skipped tests. Test results are same for both the branch-2.10 and my PR in terms of tests run, failures, errors, skipped tests.
It's the same and behavior doesn't change |
Thanks for checking the skipped tests and confirming @arjun4084346! @mukund-thakur / @steveloughran unless you have any objections, I'd like to commit this. |
Yetus still failing with unit tests. Please fix those https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4171/3/artifact/out/patch-unit-hadoop-tools_hadoop-azure.txt |
Hi @mukund-thakur , those unit tests fails in branch-2.10 . This PR does not introduce any new failing tests. e.g. take this PR #4151. It is merged into branch-2.10 and it also has some failing unit tests. |
do you have a branch in your personal repo where you have cherrypicked all the changes you need and show that things are good test wise at the end of the chain? we don't need to do the patch by patch test and review if we are confident the final sequence is good |
Okay if that's the case. I am okay with the change and no longer have any concerns with the current PR. |
going with mukund then, Now, as I asked before: do you have a branch in your own github which has the chain of call Cherry pics I needed? So we can see that the full chain is good? As then you can submit a PR with that chain and we can review/verify the final output. The individual commits would still need merging one by one, but reviewing is a lot easier. After all, we shouldn't be suggesting any changes here that are not in trunk. |
Yes, these were the next PRs I plan to send https://github.com/arjun4084346/hadoop/pulls |
can you submit a single PR with that chain and we can review/verify the final output. The individual commits would still need merging one by one, but reviewing is a lot easier. especially as some of that pr list you just pointed to are failing. if we can be confident that the final change is good, we don't need to worry about test failures along the way |
sure, please find #4261 a single PR for 7 commits. @steveloughran @mukund-thakur @virajith @abhishekdas99 |
Contributed by Mukund Thakur.
(cherry picked from commit 8031c66)
Description of PR
It is an almost clean cherry pick of commit 8031c66
How was this patch tested?
Ran
mvn test -pl hadoop-tools/hadoop-azure
No new unit tests fail.
Ran all integration abfs tests using mvn -T 1C -Dparallel-tests=abfs clean verify with my storage account arjundev.dfs.core.windows.net
No tests failed. There are 3 errors; these were negative test cases where error was expected.
Same three errors are found in the current branch-2.10 code as well.
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?