[jira] [Updated] (ATLAS-3989) Behavior change in Atlas API to get Atlas Server object during metadata replication
[
https://issues.apache.org/jira/browse/ATLAS-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Mestry updated ATLAS-3989:
---
Attachment: ATLAS-3989-Updated-Export-Import-Audits-Writer-to-us.patch
> Behavior change in Atlas API to get Atlas Server object during metadata
> replication
> ---
>
> Key: ATLAS-3989
> URL: https://issues.apache.org/jira/browse/ATLAS-3989
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments:
> ATLAS-3989-Updated-Export-Import-Audits-Writer-to-us.patch
>
>
> There is a change being noticed in the Atlas server API used during atlas
> metadata replication in hive.
> Earlier the API: '/api/atlas/admin/server/cl1' where 'cl1' is the cluster
> name, used to work.
> Now, it doesn't work any more. This Api is used during replication to get
> the changeMarker info.
> Now the API works with some thing called server name which is 'default' by
> default.
> Also, now the prerequisite is to at least have one export or import API call
> in order to get this 'default' initialized.
> The change-marker is obtained prior to invoking export and hence the all
> policy is bound to fail unless we mandate calling Export or Import API
> outside hive replication once to get this object initialized, even if hive
> uses 'default' in the call.
>
> *Root cause*
> We switched from using
> {code:java}
> atlas.cluster.name{code}
> to
> {code:java}
> atlas.metadata.namespace{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3989) Behavior change in Atlas API to get Atlas Server object during metadata replication
[
https://issues.apache.org/jira/browse/ATLAS-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Mestry updated ATLAS-3989:
---
Attachment: (was:
ATLAS-3989-Updated-Export-Import-Audits-Writer-to-us.patch)
> Behavior change in Atlas API to get Atlas Server object during metadata
> replication
> ---
>
> Key: ATLAS-3989
> URL: https://issues.apache.org/jira/browse/ATLAS-3989
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
>
> There is a change being noticed in the Atlas server API used during atlas
> metadata replication in hive.
> Earlier the API: '/api/atlas/admin/server/cl1' where 'cl1' is the cluster
> name, used to work.
> Now, it doesn't work any more. This Api is used during replication to get
> the changeMarker info.
> Now the API works with some thing called server name which is 'default' by
> default.
> Also, now the prerequisite is to at least have one export or import API call
> in order to get this 'default' initialized.
> The change-marker is obtained prior to invoking export and hence the all
> policy is bound to fail unless we mandate calling Export or Import API
> outside hive replication once to get this object initialized, even if hive
> uses 'default' in the call.
>
> *Root cause*
> We switched from using
> {code:java}
> atlas.cluster.name{code}
> to
> {code:java}
> atlas.metadata.namespace{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3989) Behavior change in Atlas API to get Atlas Server object during metadata replication
[
https://issues.apache.org/jira/browse/ATLAS-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Mestry updated ATLAS-3989:
---
Description:
There is a change being noticed in the Atlas server API used during atlas
metadata replication in hive.
Earlier the API: '/api/atlas/admin/server/cl1' where 'cl1' is the cluster
name, used to work.
Now, it doesn't work any more. This Api is used during replication to get the
changeMarker info.
Now the API works with some thing called server name which is 'default' by
default.
Also, now the prerequisite is to at least have one export or import API call
in order to get this 'default' initialized.
The change-marker is obtained prior to invoking export and hence the all
policy is bound to fail unless we mandate calling Export or Import API outside
hive replication once to get this object initialized, even if hive uses
'default' in the call.
*Root cause*
We switched from using
{code:java}
atlas.cluster.name{code}
to
{code:java}
atlas.metadata.namespace{code}
was:
There is a change being noticed in the Atlas server API used during atlas
metadata replication in hive.
Earlier the API: '/api/atlas/admin/server/cl1' where 'cl1' is the cluster name,
used to work.
Now, it doesn't work any more. This Api is used during replication to get the
changeMarker info.
Now the API works with some thing called server name which is 'default' by
default.
Also, now the prerequisite is to at least have one export or import API call in
order to get this 'default' initialized.
The change-marker is obtained prior to invoking export and hence the all policy
is bound to fail unless we mandate calling Export or Import API outside hive
replication once to get this object initialized, even if hive uses 'default' in
the call.
> Behavior change in Atlas API to get Atlas Server object during metadata
> replication
> ---
>
> Key: ATLAS-3989
> URL: https://issues.apache.org/jira/browse/ATLAS-3989
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments:
> ATLAS-3989-Updated-Export-Import-Audits-Writer-to-us.patch
>
>
> There is a change being noticed in the Atlas server API used during atlas
> metadata replication in hive.
> Earlier the API: '/api/atlas/admin/server/cl1' where 'cl1' is the cluster
> name, used to work.
> Now, it doesn't work any more. This Api is used during replication to get
> the changeMarker info.
> Now the API works with some thing called server name which is 'default' by
> default.
> Also, now the prerequisite is to at least have one export or import API call
> in order to get this 'default' initialized.
> The change-marker is obtained prior to invoking export and hence the all
> policy is bound to fail unless we mandate calling Export or Import API
> outside hive replication once to get this object initialized, even if hive
> uses 'default' in the call.
>
> *Root cause*
> We switched from using
> {code:java}
> atlas.cluster.name{code}
> to
> {code:java}
> atlas.metadata.namespace{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3989) Behavior change in Atlas API to get Atlas Server object during metadata replication
[ https://issues.apache.org/jira/browse/ATLAS-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3989: --- Attachment: ATLAS-3989-Updated-Export-Import-Audits-Writer-to-us.patch > Behavior change in Atlas API to get Atlas Server object during metadata > replication > --- > > Key: ATLAS-3989 > URL: https://issues.apache.org/jira/browse/ATLAS-3989 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Attachments: > ATLAS-3989-Updated-Export-Import-Audits-Writer-to-us.patch > > > There is a change being noticed in the Atlas server API used during atlas > metadata replication in hive. > Earlier the API: '/api/atlas/admin/server/cl1' where 'cl1' is the cluster > name, used to work. > Now, it doesn't work any more. This Api is used during replication to get the > changeMarker info. > Now the API works with some thing called server name which is 'default' by > default. > Also, now the prerequisite is to at least have one export or import API call > in order to get this 'default' initialized. > The change-marker is obtained prior to invoking export and hence the all > policy is bound to fail unless we mandate calling Export or Import API > outside hive replication once to get this object initialized, even if hive > uses 'default' in the call. -- This message was sent by Atlassian Jira (v8.3.4#803005)
