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

2020-12-02 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3966:


Commit 1e47cff1f12c19c765c38cf638ad6adfface5407 in atlas's branch 
refs/heads/branch-2.0 from Deep Singh
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=1e47cff ]

ATLAS-3966 Consider newer value for atlas.metadata.namespace if defined 
multiple times

Signed-off-by: Sarath Subramanian 
(cherry picked from commit 420983d5841fb6de545e101329cf7e12de68f4a0)


> 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)


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

2020-12-02 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on ATLAS-3966:


Commit 420983d5841fb6de545e101329cf7e12de68f4a0 in atlas's branch 
refs/heads/master from Deep Singh
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=420983d ]

ATLAS-3966 Consider newer value for atlas.metadata.namespace if defined 
multiple times

Signed-off-by: Sarath Subramanian 


> 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)


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

2020-10-01 Thread Deep Singh (Jira)


[ 
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)