[ 
https://issues.apache.org/jira/browse/KNOX-2963?focusedWorklogId=884063&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-884063
 ]

ASF GitHub Bot logged work on KNOX-2963:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 09/Oct/23 12:09
            Start Date: 09/Oct/23 12:09
    Worklog Time Spent: 10m 
      Work Description: zeroflag opened a new pull request, #801:
URL: https://github.com/apache/knox/pull/801

   ## What changes were proposed in this pull request?
   
   If cloudera manager legacy mode is turned off then certain hdfs config 
values are moved under the CORE_SETTINGS service.
   
   When the service model generator fetches `hdfs_hadoop_ssl_enabled` it will 
find a null value (since the real config is under CORE_SETTINGS) and it will 
generate a non-ssl URL even despite SSL is enabled.
   
   
   ## How was this patch tested?
   
   Tested with HDFS in non legacy mode.
   




Issue Time Tracking
-------------------

            Worklog Id:     (was: 884063)
    Remaining Estimate: 0h
            Time Spent: 10m

> CM service discovery should work when legacy mode is turned off
> ---------------------------------------------------------------
>
>                 Key: KNOX-2963
>                 URL: https://issues.apache.org/jira/browse/KNOX-2963
>             Project: Apache Knox
>          Issue Type: Improvement
>            Reporter: Attila Magyar
>            Assignee: Attila Magyar
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> If Legacy Cloudera Manager API Clients Compatibility is turned on then 
> certain HDFS configs are moved to CORE_SETTINGS.
> When the service model generator fetches hdfs_hadoop_ssl_enabled it will find 
> a null value (since the real config is under CORE_SETTINGS) and it will 
> generate a non-ssl URL even despite SSL is enabled.
> Service discovery should fetch CORE_SETTINGS configs so that the model 
> generators can look up configs values from there too.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to