You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Neville Dipale (Jira)" <ji...@apache.org> on 2021/01/13 10:14:00 UTC
[jira] [Updated] (ATLAS-4100) Recent datamodel changes (Jan 2021)
broke our installation
[ https://issues.apache.org/jira/browse/ATLAS-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neville Dipale updated ATLAS-4100:
----------------------------------
Summary: Recent datamodel changes (Jan 2021) broke our installation (was: Recent datamodel changes broke our installation)
> Recent datamodel changes (Jan 2021) broke our installation
> ----------------------------------------------------------
>
> Key: ATLAS-4100
> URL: https://issues.apache.org/jira/browse/ATLAS-4100
> Project: Atlas
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Neville Dipale
> Priority: Critical
>
> Hi Atlas developers
> We run an Atlas installation (with external Cassandra & ElasticSearch) where we build Atlas via a Docker script, pointing to specific git commits.
> The last update we have was from early December 2020. Yesterday I updated to the latest git tree, but after the update, the Atlas UI doesn't show entities. I can see the entity count on the sidebar, and inspecting the API shows that it retrieves information, but that information can't be shown.
> I suspect that the changes to the cloud datamodel could be the cause (or at least one of the causes). ATLAS-4082 created patches to the Azure entity definitions, but ATLAS-4083 directly modified the entity definitions. I can't definitively pinpoint the issue, but I noticed the issue with no longer being able to view data, after trying to apply the changes to ATLAS-4083 to our installation.
> The export API isn't working, so we have no viable alternative but to try extract the data manually from Cassandra, or worse, to destroy our data & start from scratch.
> Further, I unfortunately don't have any logs to attach, because in order for us to run Atlas with LDAP integration + a keystore file, the way we run Atlas (going in the container to manually start each time) doesn't output logs, even though we have configured the log4j.xml file propertly.
> I suppose I'm opening this in case other people come across this issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)