[
https://issues.apache.org/jira/browse/OOZIE-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated OOZIE-1656:
---------------------------------
Description:
Currently, to use the {{<credentials>}} section, the user has to add the
associated Credentials class to a property in oozie-site.xml and also come up
with a name for that class.
To make things easier for the user, and to standardize the names, I think it
would be helpful to include the built-in Credentials classes by default. We
can do it similar to how we do the Services and some other properties where we
have a {{.ext}} version of the property. i.e.
{code:title=oozie-default.xml}
<property>
<name>oozie.credentials.credentialclasses</name>
<value>
hcat=org.apache.oozie.action.hadoop.HCatCredentials,
hbase=org.apache.oozie.action.hadoop.HbaseCredentials,
</value>
<description>
foo
</description>
</property>
{code}
{code:title=oozie-site.xml}
<property>
<name>oozie.credentials.ext.credentialclasses</name>
<value> </value>
<description>
bar
</description>
</property>
{code}
Oozie would then load the built-in ones by default (and with standardized
names) and users could add/override custom ones.
The documentation should also be updated ([here|
http://oozie.apache.org/docs/4.0.0/DG_UnifiedCredentialsModule.html#Built-in_Credentials_Implementations])
was:
Currently, to use the {{<credentials>}} section, the user has to add the
associated Credentials class to a property in oozie-site.xml and also come up
with a name for that class.
To make things easier for the user, and to standardize the names, I think it
would be helpful to include the built-in Credentials classes by default. We
can do it similar to how we do the Services and some other properties where we
have a {{.ext}} version of the property. i.e.
{code:title=oozie-default.xml}
<property>
<name>oozie.credentials.credentialclasses</name>
<value>
hcat=org.apache.oozie.action.hadoop.HCatCredentials,
hbase=org.apache.oozie.action.hadoop.HbaseCredentials,
</value>
<description>
foo
</description>
</property>
{code}
{code:title=oozie-site.xml}
<property>
<name>oozie.credentials.ext.credentialclasses</name>
<value> </value>
<description>
bar
</description>
</property>
{code}
Oozie would then load the built-in ones by default (and with standardized
names) and users could add/override custom ones.
The documentation should also be updated.
> Load the included Credential classes by default
> -----------------------------------------------
>
> Key: OOZIE-1656
> URL: https://issues.apache.org/jira/browse/OOZIE-1656
> Project: Oozie
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.3.2, 4.0.0
> Reporter: Robert Kanter
> Labels: newbie
>
> Currently, to use the {{<credentials>}} section, the user has to add the
> associated Credentials class to a property in oozie-site.xml and also come up
> with a name for that class.
> To make things easier for the user, and to standardize the names, I think it
> would be helpful to include the built-in Credentials classes by default. We
> can do it similar to how we do the Services and some other properties where
> we have a {{.ext}} version of the property. i.e.
> {code:title=oozie-default.xml}
> <property>
> <name>oozie.credentials.credentialclasses</name>
> <value>
> hcat=org.apache.oozie.action.hadoop.HCatCredentials,
> hbase=org.apache.oozie.action.hadoop.HbaseCredentials,
> </value>
> <description>
> foo
> </description>
> </property>
> {code}
> {code:title=oozie-site.xml}
> <property>
> <name>oozie.credentials.ext.credentialclasses</name>
> <value> </value>
> <description>
> bar
> </description>
> </property>
> {code}
> Oozie would then load the built-in ones by default (and with standardized
> names) and users could add/override custom ones.
> The documentation should also be updated ([here|
> http://oozie.apache.org/docs/4.0.0/DG_UnifiedCredentialsModule.html#Built-in_Credentials_Implementations])
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
