https://community.cloudera.com/t5/Support-Questions/Atlas-Lineage-Issue/m-p/306653#M222944 <P>Hi,</P><P>I have installed Atlas 2.0.0 using tarball on a Cloudera 6.1 Cluster, I am using Hbase and Solr as backend store, While importing both Hive and Kafka Lineage I see issue in the UI, For Hive only i can see Lineage for external tables, not for Managed table and also column level lineage is not visible, Just want to find where the issue is I tried with embedded solr and Kafka&nbsp; still the same issue persists, For Kafka Lineage too I am facing same issue.</P><P>Following is the error I could see in the application.log, struggling with this issue for quite sometime any inputs is highly appreciated, I have one Kafka broker and my&nbsp;<SPAN>offsets.topic.replication.factor=1 and Cluster is an unsecured cluster and I could see message flowing in both the Kafka topics without any issue using console consumer and producer.</SPAN></P><P>&nbsp;</P><LI-CODE lang="markup">ERROR - [pool-2-thread-6 - bd16ff99-871b-4248-a41b-2a022a6fabee:] ~ graph rollback due to exception AtlasBaseException:Instance hive_table with unique attribute {qualifiedName=vdr_db.customer_vw8@primary} does not exist (GraphTransactionInterceptor:166)</LI-CODE><P>&nbsp;</P><P><SPAN>The above error appears for hive_table and hive_process and for Kafka topic too.</SPAN></P><P><SPAN>Thanks,</SPAN></P><P>Vishnu Ravi</P> Tue, 01 Dec 2020 13:05:58 GMT vishnuravi 2020-12-01T13:05:58Z