[
https://issues.apache.org/jira/browse/RANGER-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yikaifei updated RANGER-4125:
-----------------------------
Description:
Currently, {{ranger-plugin-commons}} module relies on {{{}gethostname4j{}}},
{{jna and jna-platform}} to get the native hostname, which is for
{{AuthzAuditEvent}} only.
{{{}gethostname4j{}}}, {{jna and jna-platform}} is too onerous, it doesn't seem
worthwhile to maintain the three jars to get the hostname, and
{{{}gethostname4j{}}}, {{jna and jna-platform}} relies on the native lib, which
prevents users from doing shade.
was:
Currently, {{ranger-plugin-commons}} module relies on {{{}gethostname4j{}}},
{{jna }} and {{jna-platform}} to get the native hostname, which is for
{{AuthzAuditEvent}} only.
{{{}gethostname4j{}}}, {{jna }} and {{jna-platform}} is too onerous, it doesn't
seem worthwhile to maintain the three jars to get the hostname, and
{{{}gethostname4j{}}}, {{jna }} and {{jna-platform}} relies on the native lib,
which prevents users from doing shade.
> Simplifies the dependency of gethostname4j for the ranger client
> -----------------------------------------------------------------
>
> Key: RANGER-4125
> URL: https://issues.apache.org/jira/browse/RANGER-4125
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
> Reporter: yikaifei
> Priority: Minor
>
> Currently, {{ranger-plugin-commons}} module relies on {{{}gethostname4j{}}},
> {{jna and jna-platform}} to get the native hostname, which is for
> {{AuthzAuditEvent}} only.
> {{{}gethostname4j{}}}, {{jna and jna-platform}} is too onerous, it doesn't
> seem worthwhile to maintain the three jars to get the hostname, and
> {{{}gethostname4j{}}}, {{jna and jna-platform}} relies on the native lib,
> which prevents users from doing shade.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
