Upgrade Guava to 28.2-jre version

[medb]

Description

Upgrades Guava version to improve compatibility with Hadoop 3.2+ and other newer dependencies.

---

This PR has:

• been self-reviewed.
• added or updated version, license, or notice information in licenses.yaml
• added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
• been tested in a test Druid cluster.

[stale]

This pull request has been marked as stale due to 60 days of inactivity. It will be closed in 4 weeks if no further activity occurs. If you think that's incorrect or this pull request should instead be reviewed, please simply write any comment. Even if closed, you can still revive the PR at any time or discuss it on the [email protected] list. Thank you for your contributions.

[medb]

@clintropolis PTAL

[stale]

This issue is no longer marked as stale.

[clintropolis]

@clintropolis PTAL

Apologies for the delay. I haven't looked into upgrading Guava in a while, but I recall that there might be compatibility issues with the currently supported Hadoop version (2.8.5) if we were to upgrade. Do you know if this is still true? Otherwise we might have to hold off until we bump the supported Hadoop version to 3+, or until it can thoroughly tested to ensure that this will not cause any issues with 2.8.x.

[medb]

Apologies for the delay. I haven't looked into upgrading Guava in a while, but I recall that there might be compatibility issues with the currently supported Hadoop version (2.8.5) if we were to upgrade. Do you know if this is still true? Otherwise we might have to hold off until we bump the supported Hadoop version to 3+, or until it can thoroughly tested to ensure that this will not cause any issues with 2.8.x.

You are right, not all changes are compatible with Hadoop 2.x versions. I will try to separate out changes that work with existing Guava version.

Do you have any plans to update to Hadoop 3?

[stale]

This pull request has been marked as stale due to 60 days of inactivity. It will be closed in 4 weeks if no further activity occurs. If you think that's incorrect or this pull request should instead be reviewed, please simply write any comment. Even if closed, you can still revive the PR at any time or discuss it on the [email protected] list. Thank you for your contributions.