You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Deep Singh (Jira)" <ji...@apache.org> on 2020/10/01 17:04:00 UTC

[jira] [Commented] (ATLAS-3966) Newer value for a property in application configuration is not loaded

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

Deep Singh commented on ATLAS-3966:
-----------------------------------

Patch Attached
PreCpmmit Build Test passed
https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/46//

Review board link
https://reviews.apache.org/r/72921/

> Newer value for a property in application configuration is not loaded 
> ----------------------------------------------------------------------
>
>                 Key: ATLAS-3966
>                 URL: https://issues.apache.org/jira/browse/ATLAS-3966
>             Project: Atlas
>          Issue Type: Bug
>          Components: atlas-intg
>            Reporter: Deep Singh
>            Assignee: Deep Singh
>            Priority: Major
>         Attachments: 0003-ATLAS-3966-Newer-value-for-atlas.metadata.namespace-.patch
>
>
> If a property is defined multiple times with different values in the application configuration file,  while loading the proper, the oldest value is read. Technically this is correct behavior. However many times, instead of updating the value of a particular property, its convenient to just append the property again with a new value in the configuration file.  
> This ask is specifically for a property called "atlas.metadata.namespace" 



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