Skip to content
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

[GOBBLIN-2196] Upgrade hadoop-azure-datalake dependency #4099

Merged

Conversation

abhishekmjain
Copy link
Contributor

@abhishekmjain abhishekmjain commented Feb 19, 2025

Dear Gobblin maintainers,

Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!

JIRA

Description

  • Here are some details about my PR, including screenshots (if applicable):

hadoop-azure-datalake brings in a bad dependency of hadoop-project https://repo1.maven.org/maven2/org/apache/hadoop/hadoop-project/3.0.0-alpha2/hadoop-project-3.0.0-alpha2.pom

As part of this PR we upgrade hadoop-azure-datalake to 3.2.3 where the issue no longer exists
https://repo1.maven.org/maven2/org/apache/hadoop/hadoop-project/3.2.3/hadoop-project-3.2.3.pom

Tests

  • My PR adds the following unit tests OR does not need testing for this extremely good reason:

Tested in local project

Commits

  • My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
    1. Subject is separated from body by a blank line
    2. Subject is limited to 50 characters
    3. Subject does not end with a period
    4. Subject uses the imperative mood ("add", not "adding")
    5. Body wraps at 72 characters
    6. Body explains "what" and "why", not "how"

@abhishekmjain abhishekmjain merged commit 8dde23a into apache:master Feb 20, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants