hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zoltan Haindrich (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-17759) Raise class security around HiveConf.ConfVars.default fields to prevent misuses
Date Tue, 10 Oct 2017 12:53:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-17759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198615#comment-16198615
] 

Zoltan Haindrich commented on HIVE-17759:
-----------------------------------------

I would like to recommend to evaluate the following options:

* rethink the whole HiveConf...to use some annotation level thing like:
{code}
@HiveConfVariable{ name="hive.main.asd",
description = "long story",
altNames = {"hadoop.sql.main.sql","hadoop.hive.sql" }
}
Integer asd = 5; // this is the default value
// the type is the field type...can go wrong..
{code}
altought these fields are not entirely used just to collect the informations; I think it would
feel natural...

* introduce some templating if possible....(should HiveConf be tied to an enum?
* or....add some getters which check the current "type" of the conf variable


> Raise class security around HiveConf.ConfVars.default fields to prevent misuses
> -------------------------------------------------------------------------------
>
>                 Key: HIVE-17759
>                 URL: https://issues.apache.org/jira/browse/HIVE-17759
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Zoltan Haindrich
>
> issues like HIVE-17758 can be prevented if these fields wouldn't be directly accessible



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message