-
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-17205. Move personality file from Yetus to Hadoop repository #2226
Conversation
(!) A patch to the testing environment has been detected. |
💔 -1 overall
This message was automatically generated. |
@aajisaka : this adds personality file to the trunk. Once agreed on this I'll also add to other branches. |
In addition, I think we can revert apache/yetus#46 in Hadoop repository. |
Thanks @aajisaka . Addressed your comments and re-triggering CI. |
(!) A patch to the testing environment has been detected. |
💔 -1 overall
This message was automatically generated. |
(!) A patch to the testing environment has been detected. |
💔 -1 overall
This message was automatically generated. |
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, thank you @sunchao
…2226) Signed-off-by: Akira Ajisaka <[email protected]> (cherry picked from commit fefacf2)
…2226) Signed-off-by: Akira Ajisaka <[email protected]> (cherry picked from commit fefacf2)
…2226) Signed-off-by: Akira Ajisaka <[email protected]> (cherry picked from commit fefacf2)
…2226) Signed-off-by: Akira Ajisaka <[email protected]> (cherry picked from commit fefacf2)
…2226) Signed-off-by: Akira Ajisaka <[email protected]> (cherry picked from commit fefacf2)
Currently for CI build and testing we maintain personality scripts in both Apache Yetus and Apache Hadoop. This poses problem when one needs to change both places, for example HADOOP-17125.
This proposes to move the personality file into the Hadoop repo itself, so that we can manage them in a single place. The downside for this is we may need to duplicate the scripts in every branch.