merging in patch - #63
Conversation
… of invalidated blocks
* Build Hadoop for arm64 * Rely on buildpack for docker usage * Use Java 11 * try without maven cache * Compute env vars inside build.sh * use buildpack maven support * back to master dependencies Co-authored-by: Charles Connell <cconnell@hubspot.com>
Co-authored-by: Charles Connell <cconnell@hubspot.com>
Co-authored-by: Charles Connell <cconnell@hubspot.com>
Co-authored-by: Charles Connell <cconnell@hubspot.com>
Co-authored-by: Charles Connell <cconnell@hubspot.com>
Co-authored-by: Charles Connell <cconnell@hubspot.com>
Co-authored-by: Charles Connell <cconnell@hubspot.com>
Co-authored-by: Charles Connell <cconnell@hubspot.com>
Co-authored-by: Charles Connell <cconnell@hubspot.com>
…fallback (#26) Co-authored-by: Charles Connell <cconnell@hubspot.com>
Hadoop release process involves creating a new branch for every release, so we can't easily follow the expected process of having a branch per major release. Instead we need to have a branch per release as well, and cherry-pick our changes over to each new release. Update our build script and rpm spec to account.
Co-authored-by: Charles Connell <cconnell@hubspot.com>
* Update .blazar.yaml * Update .blazar.yaml * Update .blazar.yaml * Update .blazar.yaml
- Update build versioning to be based around patch versions - Use single-module builds to ease dependency graph issues - Force HBase1 building to work around activeByDefault behavior
…ble with node.js 12 to avoid compilation error. (apache#5827). Contributed by Masatake Iwasaki Reviewed-by: Shilun Fan <slfan1989@apache.org> Signed-off-by: Ayush Saxena <ayushsaxena@apache.org> (cherry picked from commit a822a3c)
* Persist build env variables withour build rc file * Add clarifying comment * Cleanup HADOOP_VERSION environment variable * Copy changes to all blazar yaml files * Revert "Copy changes to all blazar yaml files" This reverts commit 5f4457e. --------- Co-authored-by: Samuel McCann <smccann@hubspot.com>
…ddTransferRateMetric(). (apache#6290). Contributed by Xing Lin. Reviewed-by: Ravindra Dingankar <rdingankar@linkedin.com> Reviewed-by: Simbarashe Dzinamarira <sdzinamarira@linkedin.com> Reviewed-by: Tao Li <tomscut@apache.org> Signed-off-by: He Xiaoqiao <hexiaoqiao@apache.org>
- Change build order to avoid deploy plugin defect - Remove build exclusion - Restore original location for argument, remove weird skip config - Move the deployAtEnd to a different spot
- Leave config in same place - Disable deployAtEnd - Increase build timeout for Hadoop
* Use new rpm buildpack * Update .blazar.yaml --------- Co-authored-by: Scott Williams <srwilliams@hubspot.com>
Co-authored-by: Charles Connell <cconnell@hubspot.com>
…twork-distance FileSystem metrics (#51)
…its in a single thread (apache#5706) (#52) Contributed by Moditha Hewasinghage Co-authored-by: Moditha Hewasinghage <33624668+modithah@users.noreply.github.com>
…15865 (apache#6223) (#53) Co-authored-by: Hiroaki Segawa <goto@stonedot.com>
This will help us use a performant job submitter in SKIR
* log the timestamp difference instead of throwing exception. * keep trailing slash for s3 filesystems use. * revert to original * add check if the cluster is a S3 cluster * null check * more universal check
…pache#5256) (#58) Contributed by Sebastian Klemke Co-authored-by: Sebastian Klemke <3669903+packet23@users.noreply.github.com>
…lease renewal interval (#59)
* Diagnose build issue * Different config * use bp branch * Remove BP branch --------- Co-authored-by: Jared Stehler <jstehler@hubspot.com>
* use offstack buildpack for module * apply patch (#66) Co-authored-by: Tanya Stickles <tstickles@hubspot.com> --------- Co-authored-by: Tanya Stickles <tanyastickles@gmail.com> Co-authored-by: Tanya Stickles <tstickles@hubspot.com>
rmdmattingly
left a comment
There was a problem hiding this comment.
This backport of apache#7886 is missing two of the three call-site migrations in UserGroupInformation.java. The upstream PR replaces all three uses of the deprecated Subject APIs, but this PR only migrates getCurrentUser() and leaves the two doAs() overloads untouched.
Both still call Subject.doAs() directly, which is deprecated-for-removal alongside Subject.getSubject() and will throw UnsupportedOperationException on Java 25:
UserGroupInformation.java ~L1540 — doAs(PrivilegedAction<T>):
- return Subject.doAs(subject, action);
+ return SubjectUtil.doAs(subject, action);UserGroupInformation.java ~L1556 — doAs(PrivilegedExceptionAction<T>):
- return Subject.doAs(subject, action);
+ return SubjectUtil.doAs(subject, action);These are heavily used code paths — UGI.doAs() is the standard way to execute code as a given user. Without these changes the Java 25 goal is only partially addressed.
0057a70 to
c1f38bb
Compare
Issue
We want to pull in this PR from apache/hadoop to unblock Java 25.