[jira] [Commented] (ATLAS-4831) Issue is with AD Group Sync in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-4831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17826774#comment-17826774 ] Jagadesh Kiran N commented on ATLAS-4831: - Also there are error msgs in the Atlas log something like groups are not assigned to users. This seems to be AD configurations missing in Atlas but problem is Atlas documentation have limited info. > Issue is with AD Group Sync in Atlas > > > Key: ATLAS-4831 > URL: https://issues.apache.org/jira/browse/ATLAS-4831 > Project: Atlas > Issue Type: Bug > Reporter: Jagadesh Kiran N >Priority: Blocker > > Atlas + Ranger + Active Directory / LDAP Integration: > Issue is with AD Group Sync in Atlas. > When a user is added to the AD group. Permissions are set to AD groups. > In this case ideally, Atlas should allow the User (Because user is added to > the AD Group) to interact with Atlas perform Read & Write operations. > But the User is not able to perform the Read & Write operations and getting > Unauthorized User Exception with 401 error code. > > I searched this ticket https://issues.apache.org/jira/browse/ATLAS-4357 > > Any alternate or work around approach for this if not direct solution -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4831) Issue is with AD Group Sync in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-4831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadesh Kiran N updated ATLAS-4831: Description: Atlas + Ranger + Active Directory / LDAP Integration: Issue is with AD Group Sync in Atlas. When a user is added to the AD group. Permissions are set to AD groups. In this case ideally, Atlas should allow the User (Because user is added to the AD Group) to interact with Atlas perform Read & Write operations. But the User is not able to perform the Read & Write operations and getting Unauthorized User Exception with 401 error code. I searched this ticket https://issues.apache.org/jira/browse/ATLAS-4357 Any alternate or work around approach for this if not direct solution was: Atlas + Ranger + Active Directory / LDAP Integration: Issue is with AD Group Sync in Atlas. When a user is added to the AD group. Permissions are set to AD groups. In this case ideally, Atlas should allow the User (Because user is added to the AD Group) to interact with Atlas perform Read & Write operations. But the User is not able to perform the Read & Write operations and getting Unauthorized User Exception with 401 error code. > Issue is with AD Group Sync in Atlas > > > Key: ATLAS-4831 > URL: https://issues.apache.org/jira/browse/ATLAS-4831 > Project: Atlas > Issue Type: Bug >Reporter: Jagadesh Kiran N >Priority: Blocker > > Atlas + Ranger + Active Directory / LDAP Integration: > Issue is with AD Group Sync in Atlas. > When a user is added to the AD group. Permissions are set to AD groups. > In this case ideally, Atlas should allow the User (Because user is added to > the AD Group) to interact with Atlas perform Read & Write operations. > But the User is not able to perform the Read & Write operations and getting > Unauthorized User Exception with 401 error code. > > I searched this ticket https://issues.apache.org/jira/browse/ATLAS-4357 > > Any alternate or work around approach for this if not direct solution -- This message was sent by Atlassian Jira (v8.20.10#820010)
Issue is with AD Group Sync in Atlas. --> 401 error code
HI, Atlas + Ranger + Active Directory / LDAP Integration: Issue is with AD Group Sync in Atlas. When a user is added to the AD group. Permissions are set to AD groups. In this case ideally, Atlas should allow the User (Because user is added to the AD Group) to interact with Atlas perform Read & Write operations. But the User is not able to perform the Read & Write operations and getting Unauthorized User Exception with 401 error code. Pls suggest how to go about the same : https://issues.apache.org/jira/browse/ATLAS-4831 Regards, Kiran
[jira] [Created] (ATLAS-4831) Issue is with AD Group Sync in Atlas
Jagadesh Kiran N created ATLAS-4831: --- Summary: Issue is with AD Group Sync in Atlas Key: ATLAS-4831 URL: https://issues.apache.org/jira/browse/ATLAS-4831 Project: Atlas Issue Type: Bug Reporter: Jagadesh Kiran N Atlas + Ranger + Active Directory / LDAP Integration: Issue is with AD Group Sync in Atlas. When a user is added to the AD group. Permissions are set to AD groups. In this case ideally, Atlas should allow the User (Because user is added to the AD Group) to interact with Atlas perform Read & Write operations. But the User is not able to perform the Read & Write operations and getting Unauthorized User Exception with 401 error code. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4808) Automatic data classification Support by Atlas
[ https://issues.apache.org/jira/browse/ATLAS-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadesh Kiran N updated ATLAS-4808: Description: a. We are maintaining a Datalake , Data we store in folders in HDFS and from there hive takes the data and stores in tables. In one of the Hive table we have bunch of columns. one of the column contains PII Data. Can Atlas automatically scan data inside and if it finds any PII information ( like name, email , phone number etc ) , It needs to mark data classification( classify columns in attribute ) for that object as PII and then propagate if any other child objects created from that by asynchronously scan data automatically. The Scan process classify a column as PII or relevant info. was: a. We are maintaining a Datalake , Data we store in folders in HDFS and from there hive takes the data and stores in tables. In one of the Hive table we have bunch of columns. one of the column contains PII Data. Can Atlas automatically scan data inside and if it finds any PII information ( like name, email , phone number etc ) , It needs to mark data classification( classify columns in attribute ) for that object as PII and then propagate if any other child objects created from that by asynchronously scan data automatically. The Scan process classify a column as PII or relevant info. b. Also do atlas support include / exclude option for tables , topics etc ? > Automatic data classification Support by Atlas > -- > > Key: ATLAS-4808 > URL: https://issues.apache.org/jira/browse/ATLAS-4808 > Project: Atlas > Issue Type: Wish > Reporter: Jagadesh Kiran N >Priority: Minor > > a. We are maintaining a Datalake , Data we store in folders in HDFS and > from there hive takes the data and stores in tables. > In one of the Hive table we have bunch of columns. one of the column contains > PII Data. Can Atlas automatically scan data inside and if it finds any PII > information ( like name, email , phone number etc ) , > It needs to mark data classification( classify columns in attribute ) for > that object as PII and then propagate if any other child objects created > from that by asynchronously scan data automatically. > The Scan process classify a column as PII or relevant info. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4808) Automatic data classification Support by Atlas
[ https://issues.apache.org/jira/browse/ATLAS-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadesh Kiran N updated ATLAS-4808: Description: a. We are maintaining a Datalake , Data we store in folders in HDFS and from there hive takes the data and stores in tables. In one of the Hive table we have bunch of columns. one of the column contains PII Data. Can Atlas automatically scan data inside and if it finds any PII information ( like name, email , phone number etc ) , It needs to mark data classification( classify columns in attribute ) for that object as PII and then propagate if any other child objects created from that by asynchronously scan data automatically. The Scan process classify a column as PII or relevant info. b. Also do atlas support include / exclude option for tables , topics etc ? was: a. We are maintaining a Datalake , Data we store in folders in HDFS and from there hive takes the data and stores in tables. In one of the Hive table we have bunch of columns. one of the column contains PII Data. Can Atlas product will automatically scan data inside and if it finds any PII information ( like name, email , phone number etc ) , It needs to mark data classification( classify columns in attribute ) for that object as PII and then propagate if any other child objects created from that by asynchronously scan data automatically. The Scan process classify a column as PII or relevant info. b. Also do atlas support include / exclude option for tables , topics etc ? > Automatic data classification Support by Atlas > -- > > Key: ATLAS-4808 > URL: https://issues.apache.org/jira/browse/ATLAS-4808 > Project: Atlas > Issue Type: Wish > Reporter: Jagadesh Kiran N >Priority: Minor > > a. We are maintaining a Datalake , Data we store in folders in HDFS and > from there hive takes the data and stores in tables. > In one of the Hive table we have bunch of columns. one of the column contains > PII Data. Can Atlas automatically scan data inside and if it finds any PII > information ( like name, email , phone number etc ) , > It needs to mark data classification( classify columns in attribute ) for > that object as PII and then propagate if any other child objects created > from that by asynchronously scan data automatically. > The Scan process classify a column as PII or relevant info. > b. Also do atlas support include / exclude option for tables , topics etc ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4808) Automatic data classification Support by Atlas
[ https://issues.apache.org/jira/browse/ATLAS-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadesh Kiran N updated ATLAS-4808: Description: a. We are maintaining a Datalake , Data we store in folders in HDFS and from there hive takes the data and stores in tables. In one of the Hive table we have bunch of columns. one of the column contains PII Data. Can Atlas product will automatically scan data inside and if it finds any PII information ( like name, email , phone number etc ) , It needs to mark data classification( classify columns in attribute ) for that object as PII and then propagate if any other child objects created from that by asynchronously scan data automatically. The Scan process classify a column as PII or relevant info. b. Also do atlas support include / exclude option for tables , topics etc ? was: a. We are maintaining a Datalake , Data we store in folders in HDFS and from there hive takes the data and stores in tables. In one of the Hive table we have bunch of columns. one of them is child_id which contains PII Data. Can Atlas product will automatically scan data inside and if it finds any PII information ( like name, email , phone number etc ) , It needs to mark data classification( classify columns in attribute ) for that object as PII and then propagate if any other child objects created from that by asynchronously scan data automatically. The Scan process classify a column as PII or relevant info. b. Also do atlas support include / exclude option for tables , topics etc ? > Automatic data classification Support by Atlas > -- > > Key: ATLAS-4808 > URL: https://issues.apache.org/jira/browse/ATLAS-4808 > Project: Atlas > Issue Type: Wish > Reporter: Jagadesh Kiran N >Priority: Minor > > a. We are maintaining a Datalake , Data we store in folders in HDFS and > from there hive takes the data and stores in tables. > In one of the Hive table we have bunch of columns. one of the column contains > PII Data. Can Atlas product will automatically scan data inside and if it > finds any PII information ( like name, email , phone number etc ) , > It needs to mark data classification( classify columns in attribute ) for > that object as PII and then propagate if any other child objects created > from that by asynchronously scan data automatically. > The Scan process classify a column as PII or relevant info. > b. Also do atlas support include / exclude option for tables , topics etc ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4808) Automatic data classification Support by Atlas
Jagadesh Kiran N created ATLAS-4808: --- Summary: Automatic data classification Support by Atlas Key: ATLAS-4808 URL: https://issues.apache.org/jira/browse/ATLAS-4808 Project: Atlas Issue Type: Wish Reporter: Jagadesh Kiran N a. We are maintaining a Datalake , Data we store in folders in HDFS and from there hive takes the data and stores in tables. In one of the Hive table we have bunch of columns. one of them is child_id which contains PII Data. Can Atlas product will automatically scan data inside and if it finds any PII information ( like name, email , phone number etc ) , It needs to mark data classification( classify columns in attribute ) for that object as PII and then propagate if any other child objects created from that by asynchronously scan data automatically. The Scan process classify a column as PII or relevant info. b. Also do atlas support include / exclude option for tables , topics etc ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4773) Can Apache Atlas Display get the delays in the lineage
[ https://issues.apache.org/jira/browse/ATLAS-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17744609#comment-17744609 ] Jagadesh Kiran N commented on ATLAS-4773: - [~umeshpadashetty] We are having a business case where we read data from Apache Kafka and write it to Apache Hadoop (HDFS) using Apache Spark Structured Streaming. Where the applications write its last processed Kafka messages minimum timestamp into Atlas Entity (Spark Process). We have the Lineage in Atlas from Kafka (Dataset) to HDFS (Dataset) with Spark (Process). _+*The requirement is:*+_ As we are storing the timestamps in Atlas Entity, is there any way that Atlas UI shows any delays based on the Atlas Entity's Timestamps??? > Can Apache Atlas Display get the delays in the lineage > --- > > Key: ATLAS-4773 > URL: https://issues.apache.org/jira/browse/ATLAS-4773 > Project: Atlas > Issue Type: New Feature > Reporter: Jagadesh Kiran N >Priority: Major > > Atlas shows lineage , can we have a feature which display getting the delays > in the lineage. > Ex :Having a heat map to showcase the difference between lineage -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4773) Can Apache Atlas Display get the delays in the lineage
[ https://issues.apache.org/jira/browse/ATLAS-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadesh Kiran N updated ATLAS-4773: Description: Atlas shows lineage , can we have a feature which display getting the delays in the lineage. Ex :Having a heat map to showcase the difference between lineage was:Atlas shows lineage , can we have a feature which display getting the delays in the lineage. > Can Apache Atlas Display get the delays in the lineage > --- > > Key: ATLAS-4773 > URL: https://issues.apache.org/jira/browse/ATLAS-4773 > Project: Atlas > Issue Type: New Feature > Reporter: Jagadesh Kiran N >Priority: Major > > Atlas shows lineage , can we have a feature which display getting the delays > in the lineage. > Ex :Having a heat map to showcase the difference between lineage -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4773) Can Apache Atlas Display get the delays in the lineage
[ https://issues.apache.org/jira/browse/ATLAS-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadesh Kiran N updated ATLAS-4773: Summary: Can Apache Atlas Display get the delays in the lineage (was: Can Apache Atlas Display getting the delays in the lineage ) > Can Apache Atlas Display get the delays in the lineage > --- > > Key: ATLAS-4773 > URL: https://issues.apache.org/jira/browse/ATLAS-4773 > Project: Atlas > Issue Type: New Feature > Reporter: Jagadesh Kiran N >Priority: Major > > Atlas shows lineage , can we have a feature which display getting the delays > in the lineage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4773) Can Apache Atlas Display getting the delays in the lineage
Jagadesh Kiran N created ATLAS-4773: --- Summary: Can Apache Atlas Display getting the delays in the lineage Key: ATLAS-4773 URL: https://issues.apache.org/jira/browse/ATLAS-4773 Project: Atlas Issue Type: New Feature Reporter: Jagadesh Kiran N Atlas shows lineage , can we have a feature which display getting the delays in the lineage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4742) Everytime changeover happens ,Atlas is taking almost an hour to switch over from PASSIVE to ACTIVE in HA mode.
[ https://issues.apache.org/jira/browse/ATLAS-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadesh Kiran N updated ATLAS-4742: Description: We have tried setting up Apache atlas(2.2.0) in High availability mode in Kubernetes with separate pods for two instance. When we simulate a failure on active instance, the failover from passive instance from active instance is taking over an hour to complete the transition. This happens when we have created around 300 entities whereas when we simulated the same failover on fresh install of Atlas, it completed the transition in 15 minutes. This is the log before the failover for the passive instance: The logs after the failover is in the attached file. This is the failover during a fresh install. It is doing the similar process but taking more time when there are more entities created in Atlas. Warning : [main:] ~ Query requires iterating over all vertices [(__patch.id = JAVA_PATCH__006)]. For better performance, use indexes (StandardJanusGraphTx$3:1357) Observation : Everytime switchover happens its recreating repetitively every-time internal typedef's because of which switchover time is more than 1 hr Please suggest how to go about the same , was: We have tried setting up Apache atlas(2.2.0) in High availability mode in Kubernetes with separate pods for two instance. When we simulate a failure on active instance, the failover from passive instance from active instance is taking over an hour to complete the transition. This happens when we have created around 300 entities whereas when we simulated the same failover on fresh install of Atlas, it completed the transition in 15 minutes. This is the log before the failover for the passive instance: The logs after the failover is in the attached file. This is the failover during a fresh install. It is doing the similar process but taking more time when there are more entities created in Atlas. Observation : Everytime switchover happens its recreating repetitively every-time internal typedef's because of which switchover time is more than 1 hr Please suggest how to go about the same , > Everytime changeover happens ,Atlas is taking almost an hour to switch over > from PASSIVE to ACTIVE in HA mode. > -- > > Key: ATLAS-4742 > URL: https://issues.apache.org/jira/browse/ATLAS-4742 > Project: Atlas > Issue Type: Bug >Reporter: Jagadesh Kiran N >Priority: Major > Attachments: application.log, image001.png > > > We have tried setting up Apache atlas(2.2.0) in High availability mode in > Kubernetes with separate pods for two instance. > > When we simulate a failure on active instance, the failover from passive > instance from active instance is taking over an hour to complete the > transition. This happens when we have created around 300 entities whereas > when we simulated the same failover on fresh install of Atlas, it completed > the transition in 15 minutes. > > This is the log before the failover for the passive instance: > The logs after the failover is in the attached file. This is the failover > during a fresh install. It is doing the similar process but taking more time > when there are more entities created in Atlas. > Warning : [main:] ~ Query requires iterating over all vertices [(__patch.id = > JAVA_PATCH__006)]. For better performance, use indexes > (StandardJanusGraphTx$3:1357) > > Observation : Everytime switchover happens its recreating repetitively > every-time internal typedef's because of which switchover time is more than 1 > hr > Please suggest how to go about the same , -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4742) Everytime changeover happens ,Atlas is taking almost an hour to switch over from PASSIVE to ACTIVE in HA mode.
Jagadesh Kiran N created ATLAS-4742: --- Summary: Everytime changeover happens ,Atlas is taking almost an hour to switch over from PASSIVE to ACTIVE in HA mode. Key: ATLAS-4742 URL: https://issues.apache.org/jira/browse/ATLAS-4742 Project: Atlas Issue Type: Bug Reporter: Jagadesh Kiran N Attachments: application.log, image001.png We have tried setting up Apache atlas(2.2.0) in High availability mode in Kubernetes with separate pods for two instance. When we simulate a failure on active instance, the failover from passive instance from active instance is taking over an hour to complete the transition. This happens when we have created around 300 entities whereas when we simulated the same failover on fresh install of Atlas, it completed the transition in 15 minutes. This is the log before the failover for the passive instance: The logs after the failover is in the attached file. This is the failover during a fresh install. It is doing the similar process but taking more time when there are more entities created in Atlas. Observation : Everytime switchover happens its recreating repetitively every-time internal typedef's because of which switchover time is more than 1 hr Please suggest how to go about the same , -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ATLAS-4716) Backward compatibility : Atlas with Hbase version 1.4.x is failing to create table
[ https://issues.apache.org/jira/browse/ATLAS-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadesh Kiran N resolved ATLAS-4716. - Resolution: Workaround The backward compatibility of Atlas Hbase is not supported now , so we planning to install HBase 2.x > Backward compatibility : Atlas with Hbase version 1.4.x is failing to create > table > --- > > Key: ATLAS-4716 > URL: https://issues.apache.org/jira/browse/ATLAS-4716 > Project: Atlas > Issue Type: Bug > Reporter: Jagadesh Kiran N >Priority: Blocker > Attachments: MicrosoftTeams-image.png, > application-20221128-hbase-1.4.9.log, application-20221128-hbase-2.4.9.log, > atlas-application.properties, atlas-env.sh, hbase-site.xml > > > We are trying to deploy Atlas using docker containers, the below is the tech > stack used for the deployment > 1. Apache Atlas v2.2.0 (Downloaded from > https://downloads.apache.org/atlas/2.2.0/apache-atlas-2.2.0-sources.tar.gz), > compiled and created a docker image out of it. > 2. Solr v8.11.1 > 3. HBase (v1.4.9) > 4. Apache Kafka & Zookeeper (v2.6.1) > NOTE: Atlas Webservice was able to setup & start successfully without any > issues when HBase v2.4.9 version is used. The application.log > (application-20221128-hbase-2.4.9.log) is attached in drive link > > I checked it is just the difference of HBase version and all others remain > (atlas-application.properties, hbase-site.xml, etc.,) > > When we tried to deploy Atlas, we were facing the following issue. The > following is the stack trace of the error: > > 2022-11-28 06:20:12,162 DEBUG - [main:] ~ Substituted default CF name > "system_properties" with short form "s" to reduce HBase KeyValue size > (HBaseStoreManager:684) > 2022-11-28 06:20:12,527 WARN - [main:] ~ Unexpected exception during > getDeployment() (HBaseStoreManager:399) > java.lang.RuntimeException: > org.janusgraph.diskstorage.TemporaryBackendException: Temporary failure in > storage backend > at > org.janusgraph.diskstorage.hbase2.HBaseStoreManager.getDeployment(HBaseStoreManager.java:358) > at > org.janusgraph.diskstorage.hbase2.HBaseStoreManager.getFeatures(HBaseStoreManager.java:397) > at > org.janusgraph.graphdb.configuration.builder.GraphDatabaseConfigurationBuilder.build(GraphDatabaseConfigurationBuilder.java:51) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:161) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:132) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:112) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.initJanusGraph(AtlasJanusGraphDatabase.java:182) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:169) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraph(AtlasJanusGraphDatabase.java:278) > at > org.apache.atlas.repository.graph.AtlasGraphProvider.getGraphInstance(AtlasGraphProvider.java:52) > at > org.apache.atlas.repository.graph.AtlasGraphProvider.get(AtlasGraphProvider.java:98) > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918.CGLIB$get$1() > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918$$FastClassBySpringCGLIB$$71b13aef.invoke() > at > org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) > at > org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:358) > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918.get() > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:162) > at > org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:588) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1176) > at > org.sprin
[jira] [Comment Edited] (ATLAS-4716) Backward compatibility : Atlas with Hbase version 1.4.x is failing to create table
[ https://issues.apache.org/jira/browse/ATLAS-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641813#comment-17641813 ] Jagadesh Kiran N edited comment on ATLAS-4716 at 12/1/22 10:28 AM: --- please close the same was (Author: jagadesh.kiran): Closing the same > Backward compatibility : Atlas with Hbase version 1.4.x is failing to create > table > --- > > Key: ATLAS-4716 > URL: https://issues.apache.org/jira/browse/ATLAS-4716 > Project: Atlas > Issue Type: Bug > Reporter: Jagadesh Kiran N >Priority: Blocker > Attachments: MicrosoftTeams-image.png, > application-20221128-hbase-1.4.9.log, application-20221128-hbase-2.4.9.log, > atlas-application.properties, atlas-env.sh, hbase-site.xml > > > We are trying to deploy Atlas using docker containers, the below is the tech > stack used for the deployment > 1. Apache Atlas v2.2.0 (Downloaded from > https://downloads.apache.org/atlas/2.2.0/apache-atlas-2.2.0-sources.tar.gz), > compiled and created a docker image out of it. > 2. Solr v8.11.1 > 3. HBase (v1.4.9) > 4. Apache Kafka & Zookeeper (v2.6.1) > NOTE: Atlas Webservice was able to setup & start successfully without any > issues when HBase v2.4.9 version is used. The application.log > (application-20221128-hbase-2.4.9.log) is attached in drive link > > I checked it is just the difference of HBase version and all others remain > (atlas-application.properties, hbase-site.xml, etc.,) > > When we tried to deploy Atlas, we were facing the following issue. The > following is the stack trace of the error: > > 2022-11-28 06:20:12,162 DEBUG - [main:] ~ Substituted default CF name > "system_properties" with short form "s" to reduce HBase KeyValue size > (HBaseStoreManager:684) > 2022-11-28 06:20:12,527 WARN - [main:] ~ Unexpected exception during > getDeployment() (HBaseStoreManager:399) > java.lang.RuntimeException: > org.janusgraph.diskstorage.TemporaryBackendException: Temporary failure in > storage backend > at > org.janusgraph.diskstorage.hbase2.HBaseStoreManager.getDeployment(HBaseStoreManager.java:358) > at > org.janusgraph.diskstorage.hbase2.HBaseStoreManager.getFeatures(HBaseStoreManager.java:397) > at > org.janusgraph.graphdb.configuration.builder.GraphDatabaseConfigurationBuilder.build(GraphDatabaseConfigurationBuilder.java:51) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:161) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:132) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:112) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.initJanusGraph(AtlasJanusGraphDatabase.java:182) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:169) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraph(AtlasJanusGraphDatabase.java:278) > at > org.apache.atlas.repository.graph.AtlasGraphProvider.getGraphInstance(AtlasGraphProvider.java:52) > at > org.apache.atlas.repository.graph.AtlasGraphProvider.get(AtlasGraphProvider.java:98) > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918.CGLIB$get$1() > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918$$FastClassBySpringCGLIB$$71b13aef.invoke() > at > org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) > at > org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:358) > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918.get() > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:162) > at > org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:588) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1176) > at > org.s
[jira] [Updated] (ATLAS-4716) Backward compatibility : Atlas with Hbase version 1.4.x is failing to create table
[ https://issues.apache.org/jira/browse/ATLAS-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadesh Kiran N updated ATLAS-4716: Attachment: MicrosoftTeams-image.png > Backward compatibility : Atlas with Hbase version 1.4.x is failing to create > table > --- > > Key: ATLAS-4716 > URL: https://issues.apache.org/jira/browse/ATLAS-4716 > Project: Atlas > Issue Type: Bug > Reporter: Jagadesh Kiran N >Priority: Blocker > Attachments: MicrosoftTeams-image.png, > application-20221128-hbase-1.4.9.log, application-20221128-hbase-2.4.9.log, > atlas-application.properties, atlas-env.sh, hbase-site.xml > > > We are trying to deploy Atlas using docker containers, the below is the tech > stack used for the deployment > 1. Apache Atlas v2.2.0 (Downloaded from > https://downloads.apache.org/atlas/2.2.0/apache-atlas-2.2.0-sources.tar.gz), > compiled and created a docker image out of it. > 2. Solr v8.11.1 > 3. HBase (v1.4.9) > 4. Apache Kafka & Zookeeper (v2.6.1) > NOTE: Atlas Webservice was able to setup & start successfully without any > issues when HBase v2.4.9 version is used. The application.log > (application-20221128-hbase-2.4.9.log) is attached in drive link > > I checked it is just the difference of HBase version and all others remain > (atlas-application.properties, hbase-site.xml, etc.,) > > When we tried to deploy Atlas, we were facing the following issue. The > following is the stack trace of the error: > > 2022-11-28 06:20:12,162 DEBUG - [main:] ~ Substituted default CF name > "system_properties" with short form "s" to reduce HBase KeyValue size > (HBaseStoreManager:684) > 2022-11-28 06:20:12,527 WARN - [main:] ~ Unexpected exception during > getDeployment() (HBaseStoreManager:399) > java.lang.RuntimeException: > org.janusgraph.diskstorage.TemporaryBackendException: Temporary failure in > storage backend > at > org.janusgraph.diskstorage.hbase2.HBaseStoreManager.getDeployment(HBaseStoreManager.java:358) > at > org.janusgraph.diskstorage.hbase2.HBaseStoreManager.getFeatures(HBaseStoreManager.java:397) > at > org.janusgraph.graphdb.configuration.builder.GraphDatabaseConfigurationBuilder.build(GraphDatabaseConfigurationBuilder.java:51) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:161) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:132) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:112) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.initJanusGraph(AtlasJanusGraphDatabase.java:182) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:169) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraph(AtlasJanusGraphDatabase.java:278) > at > org.apache.atlas.repository.graph.AtlasGraphProvider.getGraphInstance(AtlasGraphProvider.java:52) > at > org.apache.atlas.repository.graph.AtlasGraphProvider.get(AtlasGraphProvider.java:98) > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918.CGLIB$get$1() > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918$$FastClassBySpringCGLIB$$71b13aef.invoke() > at > org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) > at > org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:358) > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918.get() > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:162) > at > org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:588) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1176) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1071) > at
[jira] [Commented] (ATLAS-4716) Backward compatibility : Atlas with Hbase version 1.4.x is failing to create table
[ https://issues.apache.org/jira/browse/ATLAS-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641812#comment-17641812 ] Jagadesh Kiran N commented on ATLAS-4716: - [~mad...@apache.org] , thank you for mail response , we will upgarde to Hbase 2.x > Backward compatibility : Atlas with Hbase version 1.4.x is failing to create > table > --- > > Key: ATLAS-4716 > URL: https://issues.apache.org/jira/browse/ATLAS-4716 > Project: Atlas > Issue Type: Bug > Reporter: Jagadesh Kiran N >Priority: Blocker > Attachments: MicrosoftTeams-image.png, > application-20221128-hbase-1.4.9.log, application-20221128-hbase-2.4.9.log, > atlas-application.properties, atlas-env.sh, hbase-site.xml > > > We are trying to deploy Atlas using docker containers, the below is the tech > stack used for the deployment > 1. Apache Atlas v2.2.0 (Downloaded from > https://downloads.apache.org/atlas/2.2.0/apache-atlas-2.2.0-sources.tar.gz), > compiled and created a docker image out of it. > 2. Solr v8.11.1 > 3. HBase (v1.4.9) > 4. Apache Kafka & Zookeeper (v2.6.1) > NOTE: Atlas Webservice was able to setup & start successfully without any > issues when HBase v2.4.9 version is used. The application.log > (application-20221128-hbase-2.4.9.log) is attached in drive link > > I checked it is just the difference of HBase version and all others remain > (atlas-application.properties, hbase-site.xml, etc.,) > > When we tried to deploy Atlas, we were facing the following issue. The > following is the stack trace of the error: > > 2022-11-28 06:20:12,162 DEBUG - [main:] ~ Substituted default CF name > "system_properties" with short form "s" to reduce HBase KeyValue size > (HBaseStoreManager:684) > 2022-11-28 06:20:12,527 WARN - [main:] ~ Unexpected exception during > getDeployment() (HBaseStoreManager:399) > java.lang.RuntimeException: > org.janusgraph.diskstorage.TemporaryBackendException: Temporary failure in > storage backend > at > org.janusgraph.diskstorage.hbase2.HBaseStoreManager.getDeployment(HBaseStoreManager.java:358) > at > org.janusgraph.diskstorage.hbase2.HBaseStoreManager.getFeatures(HBaseStoreManager.java:397) > at > org.janusgraph.graphdb.configuration.builder.GraphDatabaseConfigurationBuilder.build(GraphDatabaseConfigurationBuilder.java:51) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:161) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:132) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:112) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.initJanusGraph(AtlasJanusGraphDatabase.java:182) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:169) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraph(AtlasJanusGraphDatabase.java:278) > at > org.apache.atlas.repository.graph.AtlasGraphProvider.getGraphInstance(AtlasGraphProvider.java:52) > at > org.apache.atlas.repository.graph.AtlasGraphProvider.get(AtlasGraphProvider.java:98) > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918.CGLIB$get$1() > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918$$FastClassBySpringCGLIB$$71b13aef.invoke() > at > org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) > at > org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:358) > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918.get() > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:162) > at > org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:588) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1176) > at > org.s
[jira] [Commented] (ATLAS-4716) Backward compatibility : Atlas with Hbase version 1.4.x is failing to create table
[ https://issues.apache.org/jira/browse/ATLAS-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641813#comment-17641813 ] Jagadesh Kiran N commented on ATLAS-4716: - Closing the same > Backward compatibility : Atlas with Hbase version 1.4.x is failing to create > table > --- > > Key: ATLAS-4716 > URL: https://issues.apache.org/jira/browse/ATLAS-4716 > Project: Atlas > Issue Type: Bug > Reporter: Jagadesh Kiran N >Priority: Blocker > Attachments: MicrosoftTeams-image.png, > application-20221128-hbase-1.4.9.log, application-20221128-hbase-2.4.9.log, > atlas-application.properties, atlas-env.sh, hbase-site.xml > > > We are trying to deploy Atlas using docker containers, the below is the tech > stack used for the deployment > 1. Apache Atlas v2.2.0 (Downloaded from > https://downloads.apache.org/atlas/2.2.0/apache-atlas-2.2.0-sources.tar.gz), > compiled and created a docker image out of it. > 2. Solr v8.11.1 > 3. HBase (v1.4.9) > 4. Apache Kafka & Zookeeper (v2.6.1) > NOTE: Atlas Webservice was able to setup & start successfully without any > issues when HBase v2.4.9 version is used. The application.log > (application-20221128-hbase-2.4.9.log) is attached in drive link > > I checked it is just the difference of HBase version and all others remain > (atlas-application.properties, hbase-site.xml, etc.,) > > When we tried to deploy Atlas, we were facing the following issue. The > following is the stack trace of the error: > > 2022-11-28 06:20:12,162 DEBUG - [main:] ~ Substituted default CF name > "system_properties" with short form "s" to reduce HBase KeyValue size > (HBaseStoreManager:684) > 2022-11-28 06:20:12,527 WARN - [main:] ~ Unexpected exception during > getDeployment() (HBaseStoreManager:399) > java.lang.RuntimeException: > org.janusgraph.diskstorage.TemporaryBackendException: Temporary failure in > storage backend > at > org.janusgraph.diskstorage.hbase2.HBaseStoreManager.getDeployment(HBaseStoreManager.java:358) > at > org.janusgraph.diskstorage.hbase2.HBaseStoreManager.getFeatures(HBaseStoreManager.java:397) > at > org.janusgraph.graphdb.configuration.builder.GraphDatabaseConfigurationBuilder.build(GraphDatabaseConfigurationBuilder.java:51) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:161) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:132) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:112) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.initJanusGraph(AtlasJanusGraphDatabase.java:182) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:169) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraph(AtlasJanusGraphDatabase.java:278) > at > org.apache.atlas.repository.graph.AtlasGraphProvider.getGraphInstance(AtlasGraphProvider.java:52) > at > org.apache.atlas.repository.graph.AtlasGraphProvider.get(AtlasGraphProvider.java:98) > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918.CGLIB$get$1() > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918$$FastClassBySpringCGLIB$$71b13aef.invoke() > at > org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) > at > org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:358) > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918.get() > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:162) > at > org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:588) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1176) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(
[jira] [Commented] (ATLAS-4716) Backward compatibility : Atlas with Hbase version 1.4.x is failing to create table
[ https://issues.apache.org/jira/browse/ATLAS-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641417#comment-17641417 ] Jagadesh Kiran N commented on ATLAS-4716: - Janus 0.5.3 compatibilty with Hbase 1.x is not there ,it only supports Hbase 2.x > Backward compatibility : Atlas with Hbase version 1.4.x is failing to create > table > --- > > Key: ATLAS-4716 > URL: https://issues.apache.org/jira/browse/ATLAS-4716 > Project: Atlas > Issue Type: Bug > Reporter: Jagadesh Kiran N >Priority: Blocker > Attachments: application-20221128-hbase-1.4.9.log, > application-20221128-hbase-2.4.9.log, atlas-application.properties, > atlas-env.sh, hbase-site.xml > > > We are trying to deploy Atlas using docker containers, the below is the tech > stack used for the deployment > 1. Apache Atlas v2.2.0 (Downloaded from > https://downloads.apache.org/atlas/2.2.0/apache-atlas-2.2.0-sources.tar.gz), > compiled and created a docker image out of it. > 2. Solr v8.11.1 > 3. HBase (v1.4.9) > 4. Apache Kafka & Zookeeper (v2.6.1) > NOTE: Atlas Webservice was able to setup & start successfully without any > issues when HBase v2.4.9 version is used. The application.log > (application-20221128-hbase-2.4.9.log) is attached in drive link > > I checked it is just the difference of HBase version and all others remain > (atlas-application.properties, hbase-site.xml, etc.,) > > When we tried to deploy Atlas, we were facing the following issue. The > following is the stack trace of the error: > > 2022-11-28 06:20:12,162 DEBUG - [main:] ~ Substituted default CF name > "system_properties" with short form "s" to reduce HBase KeyValue size > (HBaseStoreManager:684) > 2022-11-28 06:20:12,527 WARN - [main:] ~ Unexpected exception during > getDeployment() (HBaseStoreManager:399) > java.lang.RuntimeException: > org.janusgraph.diskstorage.TemporaryBackendException: Temporary failure in > storage backend > at > org.janusgraph.diskstorage.hbase2.HBaseStoreManager.getDeployment(HBaseStoreManager.java:358) > at > org.janusgraph.diskstorage.hbase2.HBaseStoreManager.getFeatures(HBaseStoreManager.java:397) > at > org.janusgraph.graphdb.configuration.builder.GraphDatabaseConfigurationBuilder.build(GraphDatabaseConfigurationBuilder.java:51) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:161) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:132) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:112) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.initJanusGraph(AtlasJanusGraphDatabase.java:182) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:169) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraph(AtlasJanusGraphDatabase.java:278) > at > org.apache.atlas.repository.graph.AtlasGraphProvider.getGraphInstance(AtlasGraphProvider.java:52) > at > org.apache.atlas.repository.graph.AtlasGraphProvider.get(AtlasGraphProvider.java:98) > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918.CGLIB$get$1() > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918$$FastClassBySpringCGLIB$$71b13aef.invoke() > at > org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) > at > org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:358) > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918.get() > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:162) > at > org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:588) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1176) > at > org.s
[jira] [Updated] (ATLAS-4716) Backward compatibility : Atlas with Hbase version 1.4.x is failing to create table
[ https://issues.apache.org/jira/browse/ATLAS-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadesh Kiran N updated ATLAS-4716: Attachment: application-20221128-hbase-1.4.9.log application-20221128-hbase-2.4.9.log atlas-application.properties atlas-env.sh > Backward compatibility : Atlas with Hbase version 1.4.x is failing to create > table > --- > > Key: ATLAS-4716 > URL: https://issues.apache.org/jira/browse/ATLAS-4716 > Project: Atlas > Issue Type: Bug > Reporter: Jagadesh Kiran N >Priority: Blocker > Attachments: application-20221128-hbase-1.4.9.log, > application-20221128-hbase-2.4.9.log, atlas-application.properties, > atlas-env.sh, hbase-site.xml > > > We are trying to deploy Atlas using docker containers, the below is the tech > stack used for the deployment > 1. Apache Atlas v2.2.0 (Downloaded from > https://downloads.apache.org/atlas/2.2.0/apache-atlas-2.2.0-sources.tar.gz), > compiled and created a docker image out of it. > 2. Solr v8.11.1 > 3. HBase (v1.4.9) > 4. Apache Kafka & Zookeeper (v2.6.1) > NOTE: Atlas Webservice was able to setup & start successfully without any > issues when HBase v2.4.9 version is used. The application.log > (application-20221128-hbase-2.4.9.log) is attached in drive link > > I checked it is just the difference of HBase version and all others remain > (atlas-application.properties, hbase-site.xml, etc.,) > > When we tried to deploy Atlas, we were facing the following issue. The > following is the stack trace of the error: > > 2022-11-28 06:20:12,162 DEBUG - [main:] ~ Substituted default CF name > "system_properties" with short form "s" to reduce HBase KeyValue size > (HBaseStoreManager:684) > 2022-11-28 06:20:12,527 WARN - [main:] ~ Unexpected exception during > getDeployment() (HBaseStoreManager:399) > java.lang.RuntimeException: > org.janusgraph.diskstorage.TemporaryBackendException: Temporary failure in > storage backend > at > org.janusgraph.diskstorage.hbase2.HBaseStoreManager.getDeployment(HBaseStoreManager.java:358) > at > org.janusgraph.diskstorage.hbase2.HBaseStoreManager.getFeatures(HBaseStoreManager.java:397) > at > org.janusgraph.graphdb.configuration.builder.GraphDatabaseConfigurationBuilder.build(GraphDatabaseConfigurationBuilder.java:51) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:161) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:132) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:112) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.initJanusGraph(AtlasJanusGraphDatabase.java:182) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:169) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraph(AtlasJanusGraphDatabase.java:278) > at > org.apache.atlas.repository.graph.AtlasGraphProvider.getGraphInstance(AtlasGraphProvider.java:52) > at > org.apache.atlas.repository.graph.AtlasGraphProvider.get(AtlasGraphProvider.java:98) > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918.CGLIB$get$1() > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918$$FastClassBySpringCGLIB$$71b13aef.invoke() > at > org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) > at > org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:358) > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918.get() > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:162) > at > org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:588) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1176) > at > org.sprin
[jira] [Updated] (ATLAS-4716) Backward compatibility : Atlas with Hbase version 1.4.x is failing to create table
[ https://issues.apache.org/jira/browse/ATLAS-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadesh Kiran N updated ATLAS-4716: Attachment: hbase-site.xml > Backward compatibility : Atlas with Hbase version 1.4.x is failing to create > table > --- > > Key: ATLAS-4716 > URL: https://issues.apache.org/jira/browse/ATLAS-4716 > Project: Atlas > Issue Type: Bug > Reporter: Jagadesh Kiran N >Priority: Blocker > Attachments: application-20221128-hbase-1.4.9.log, > application-20221128-hbase-2.4.9.log, atlas-application.properties, > atlas-env.sh, hbase-site.xml > > > We are trying to deploy Atlas using docker containers, the below is the tech > stack used for the deployment > 1. Apache Atlas v2.2.0 (Downloaded from > https://downloads.apache.org/atlas/2.2.0/apache-atlas-2.2.0-sources.tar.gz), > compiled and created a docker image out of it. > 2. Solr v8.11.1 > 3. HBase (v1.4.9) > 4. Apache Kafka & Zookeeper (v2.6.1) > NOTE: Atlas Webservice was able to setup & start successfully without any > issues when HBase v2.4.9 version is used. The application.log > (application-20221128-hbase-2.4.9.log) is attached in drive link > > I checked it is just the difference of HBase version and all others remain > (atlas-application.properties, hbase-site.xml, etc.,) > > When we tried to deploy Atlas, we were facing the following issue. The > following is the stack trace of the error: > > 2022-11-28 06:20:12,162 DEBUG - [main:] ~ Substituted default CF name > "system_properties" with short form "s" to reduce HBase KeyValue size > (HBaseStoreManager:684) > 2022-11-28 06:20:12,527 WARN - [main:] ~ Unexpected exception during > getDeployment() (HBaseStoreManager:399) > java.lang.RuntimeException: > org.janusgraph.diskstorage.TemporaryBackendException: Temporary failure in > storage backend > at > org.janusgraph.diskstorage.hbase2.HBaseStoreManager.getDeployment(HBaseStoreManager.java:358) > at > org.janusgraph.diskstorage.hbase2.HBaseStoreManager.getFeatures(HBaseStoreManager.java:397) > at > org.janusgraph.graphdb.configuration.builder.GraphDatabaseConfigurationBuilder.build(GraphDatabaseConfigurationBuilder.java:51) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:161) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:132) > at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:112) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.initJanusGraph(AtlasJanusGraphDatabase.java:182) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:169) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraph(AtlasJanusGraphDatabase.java:278) > at > org.apache.atlas.repository.graph.AtlasGraphProvider.getGraphInstance(AtlasGraphProvider.java:52) > at > org.apache.atlas.repository.graph.AtlasGraphProvider.get(AtlasGraphProvider.java:98) > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918.CGLIB$get$1() > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918$$FastClassBySpringCGLIB$$71b13aef.invoke() > at > org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) > at > org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:358) > at > org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918.get() > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:162) > at > org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:588) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1176) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1071) > at
[jira] [Created] (ATLAS-4716) Backward compatibility : Atlas with Hbase version 1.4.x is failing to create table
Jagadesh Kiran N created ATLAS-4716: --- Summary: Backward compatibility : Atlas with Hbase version 1.4.x is failing to create table Key: ATLAS-4716 URL: https://issues.apache.org/jira/browse/ATLAS-4716 Project: Atlas Issue Type: Bug Reporter: Jagadesh Kiran N We are trying to deploy Atlas using docker containers, the below is the tech stack used for the deployment 1. Apache Atlas v2.2.0 (Downloaded from https://downloads.apache.org/atlas/2.2.0/apache-atlas-2.2.0-sources.tar.gz), compiled and created a docker image out of it. 2. Solr v8.11.1 3. HBase (v1.4.9) 4. Apache Kafka & Zookeeper (v2.6.1) NOTE: Atlas Webservice was able to setup & start successfully without any issues when HBase v2.4.9 version is used. The application.log (application-20221128-hbase-2.4.9.log) is attached in drive link I checked it is just the difference of HBase version and all others remain (atlas-application.properties, hbase-site.xml, etc.,) When we tried to deploy Atlas, we were facing the following issue. The following is the stack trace of the error: 2022-11-28 06:20:12,162 DEBUG - [main:] ~ Substituted default CF name "system_properties" with short form "s" to reduce HBase KeyValue size (HBaseStoreManager:684) 2022-11-28 06:20:12,527 WARN - [main:] ~ Unexpected exception during getDeployment() (HBaseStoreManager:399) java.lang.RuntimeException: org.janusgraph.diskstorage.TemporaryBackendException: Temporary failure in storage backend at org.janusgraph.diskstorage.hbase2.HBaseStoreManager.getDeployment(HBaseStoreManager.java:358) at org.janusgraph.diskstorage.hbase2.HBaseStoreManager.getFeatures(HBaseStoreManager.java:397) at org.janusgraph.graphdb.configuration.builder.GraphDatabaseConfigurationBuilder.build(GraphDatabaseConfigurationBuilder.java:51) at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:161) at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:132) at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:112) at org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.initJanusGraph(AtlasJanusGraphDatabase.java:182) at org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:169) at org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraph(AtlasJanusGraphDatabase.java:278) at org.apache.atlas.repository.graph.AtlasGraphProvider.getGraphInstance(AtlasGraphProvider.java:52) at org.apache.atlas.repository.graph.AtlasGraphProvider.get(AtlasGraphProvider.java:98) at org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918.CGLIB$get$1() at org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918$$FastClassBySpringCGLIB$$71b13aef.invoke() at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:358) at org.apache.atlas.repository.graph.AtlasGraphProvider$$EnhancerBySpringCGLIB$$72fdd918.get() at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:162) at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:588) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1176) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1071) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:511) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:481) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:312) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:308) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202) at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(Depen
