[
https://issues.apache.org/jira/browse/HIVE-8583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185335#comment-14185335
]
Alan Gates commented on HIVE-8583:
----------------------------------
I'm not opposed to changing the order of the modifiers, I just didn't
understand why it mattered. So no need for a new patch.
We do need the tests to run on this patch though. I don't think the build
failure has anything with your patch. So just canceling the patch,
re-attaching the file, and re-submitting the patch should force the tests to
run.
> HIVE-8341 Cleanup & Test for hive.script.operator.env.blacklist
> ---------------------------------------------------------------
>
> Key: HIVE-8583
> URL: https://issues.apache.org/jira/browse/HIVE-8583
> Project: Hive
> Issue Type: Improvement
> Reporter: Lars Francke
> Assignee: Lars Francke
> Priority: Minor
> Attachments: HIVE-8583.1.patch
>
>
> [~alangates] added the following in HIVE-8341:
> {code}
> String bl =
> hconf.get(HiveConf.ConfVars.HIVESCRIPT_ENV_BLACKLIST.toString());
> if (bl != null && bl.length() > 0) {
> String[] bls = bl.split(",");
> for (String b : bls) {
> b.replaceAll(".", "_");
> blackListedConfEntries.add(b);
> }
> }
> {code}
> The {{replaceAll}} call is confusing as its result is not used at all.
> This patch contains the following:
> * Minor style modification (missorted modifiers)
> * Adds reading of default value for HIVESCRIPT_ENV_BLACKLIST
> * Removes replaceAll
> * Lets blackListed take a Configuration job as parameter which allowed me to
> add a test for this
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
