[jira] [Commented] (KNOX-2265) Cloudera Manager discovery - check configs by their related names

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on KNOX-2265:
-------------------------------------------------------

Commit c48ff3ec7247de10b9fa4418456ec606f81fa427 in knox's branch refs/heads/master from Sandor Molnar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=c48ff3e ]

KNOX-2265 - Checking CM configs by their related names and read hive.server2.use.SSL from the service configuration (#280)



> Cloudera Manager discovery - check configs by their related names
> -----------------------------------------------------------------
>
>                 Key: KNOX-2265
>                 URL: https://issues.apache.org/jira/browse/KNOX-2265
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: cm-discovery
>    Affects Versions: 1.4.0
>            Reporter: Sandor Molnar
>            Assignee: Sandor Molnar
>            Priority: Major
>             Fix For: 1.4.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Cloudera Manager provided configurations (service and role configs) have two unique identifiers:
>  * name
>  * related name
> As of now, during service discovery, Knox only checks for the first one. However, it's perfectly fine if a particular service model identifies a configuration with the corresponding related name.
> For instance, at the time of this Jira being filed, Hive Server 2 tries to identify the schema using {{hive.server2.use.SSL}} from 
> {code:java}
> class ApiConfig {
>         name: hiveserver2_enable_ssl
>         value: true
>         required: false
>         _default: false
>         displayName: Enable TLS/SSL for HiveServer2
>         description: Encrypt communication between clients and HiveServer2 using Transport Layer Security (TLS) (formerly known as Secure Socket Layer (SSL)).
>         relatedName: hive.server2.use.SSL
>         sensitive: false
>         validationState: OK
>         validationMessage: null
>         validationWarningsSuppressed: null
>     } {code}
> As this sample shows, this particular configuration's name is {{hiveserver2_enable_ssl}} so that the discovery process will always default to {{http}} as the scheme.
>  
> Cc.: [~pzampino@apache.org]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)