[jira] [Created] (ATLAS-1893) UI - Lineage support for IE-10 and onwards.
Nixon Rodrigues created ATLAS-1893: -- Summary: UI - Lineage support for IE-10 and onwards. Key: ATLAS-1893 URL: https://issues.apache.org/jira/browse/ATLAS-1893 Project: Atlas Issue Type: Bug Environment: IE Reporter: Nixon Rodrigues Assignee: Keval Bhatt Currently lineage is not working on IE. This fix will provide lineage support for browsers IE10 and onwards. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1512) Hive Hook fails due to - Table not found exception
[ https://issues.apache.org/jira/browse/ATLAS-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059455#comment-16059455 ] Nixon Rodrigues commented on ATLAS-1512: @Russel Anderson What is version of Hive in BigInsights 4.2.0.0 where you encountered this issue ? Let me know > Hive Hook fails due to - Table not found exception > -- > > Key: ATLAS-1512 > URL: https://issues.apache.org/jira/browse/ATLAS-1512 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-intg > Environment: newly built, and configured Apache Atlas .7.1rc3 > BigInsights 4.2.0.0 - > The example worked fine using Apache Atlas .7.0rc2 >Reporter: Russell Anderson >Priority: Critical > > After configuring Hive Hook: Ran the following Hive SQL command: > Create table sysibm.sparktest as select * from sysibm.sparktable; > -the table sysibm.sparktable exists > -the table system.sparktest is getting created as a result of this command. > -the table gets successfully created within the schema sysibm but the Hive > Hook does is not able deal with this correctly. > 2017-01-31 07:49:56,979 INFO metastore.HiveMetaStore > (HiveMetaStore.java:logIn\ > fo(746)) - 6: get_table : db=sysibm tbl=sparktest > 2017-01-31 07:49:56,980 INFO HiveMetaStore.audit > (HiveMetaStore.java:logAuditE\ > vent(371)) - ugi=hiveip=unknown-ip-addr cmd=get_table : db=sysibm > tbl=\ > sparktest > 2017-01-31 07:49:56,984 ERROR metadata.Hive (Hive.java:getTable(1119)) - > Table \ > sparktest not found: sysibm.sparktest table not found > 2017-01-31 07:49:56,984 ERROR hook.HiveHook (HiveHook.java:run(207)) - Atlas > ho\ > ok failed due to error > java.lang.reflect.UndeclaredThrowableException > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInform\ > ation.java:1672) > at org.apache.atlas.hive.hook.HiveHook$2.run(HiveHook.java:197) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:5\ > 11) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor\ > .java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecuto\ > r.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.apache.hadoop.hive.ql.metadata.InvalidTableException: Table > not \ > found sparktest > at org.apache.hadoop.hive.ql.metadata.Hive.getTable(Hive.java:1120) > at org.apache.hadoop.hive.ql.metadata.Hive.getTable(Hive.java:1090) > at > org.apache.atlas.hive.hook.HiveHook.createOrUpdateEntities(HiveHook.\ > java:559) > at > org.apache.atlas.hive.hook.HiveHook.createOrUpdateEntities(HiveHook.\ > java:581) > at > org.apache.atlas.hive.hook.HiveHook.processHiveEntity(HiveHook.java:\ > 669) > at > org.apache.atlas.hive.hook.HiveHook.registerProcess(HiveHook.java:64\ > 9) > at org.apache.atlas.hive.hook.HiveHook.collect(HiveHook.java:270) > at org.apache.atlas.hive.hook.HiveHook.access$200(HiveHook.java:85) > at org.apache.atlas.hive.hook.HiveHook$2$1.run(HiveHook.java:200) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInform\ > ation.java:1657) > ... 6 more > 2017-01-31 07:49:57,029 INFO log.PerfLogger > (PerfLogger.java:PerfLogEnd(148)) \ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (ATLAS-1512) Hive Hook fails due to - Table not found exception
[ https://issues.apache.org/jira/browse/ATLAS-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059455#comment-16059455 ] Nixon Rodrigues edited comment on ATLAS-1512 at 6/22/17 2:22 PM: - [~r...@us.ibm.com] What is version of Hive in BigInsights 4.2.0.0 where you encountered this issue ? Let me know was (Author: nixonrodrigues): @Russel Anderson What is version of Hive in BigInsights 4.2.0.0 where you encountered this issue ? Let me know > Hive Hook fails due to - Table not found exception > -- > > Key: ATLAS-1512 > URL: https://issues.apache.org/jira/browse/ATLAS-1512 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-intg > Environment: newly built, and configured Apache Atlas .7.1rc3 > BigInsights 4.2.0.0 - > The example worked fine using Apache Atlas .7.0rc2 >Reporter: Russell Anderson >Priority: Critical > > After configuring Hive Hook: Ran the following Hive SQL command: > Create table sysibm.sparktest as select * from sysibm.sparktable; > -the table sysibm.sparktable exists > -the table system.sparktest is getting created as a result of this command. > -the table gets successfully created within the schema sysibm but the Hive > Hook does is not able deal with this correctly. > 2017-01-31 07:49:56,979 INFO metastore.HiveMetaStore > (HiveMetaStore.java:logIn\ > fo(746)) - 6: get_table : db=sysibm tbl=sparktest > 2017-01-31 07:49:56,980 INFO HiveMetaStore.audit > (HiveMetaStore.java:logAuditE\ > vent(371)) - ugi=hiveip=unknown-ip-addr cmd=get_table : db=sysibm > tbl=\ > sparktest > 2017-01-31 07:49:56,984 ERROR metadata.Hive (Hive.java:getTable(1119)) - > Table \ > sparktest not found: sysibm.sparktest table not found > 2017-01-31 07:49:56,984 ERROR hook.HiveHook (HiveHook.java:run(207)) - Atlas > ho\ > ok failed due to error > java.lang.reflect.UndeclaredThrowableException > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInform\ > ation.java:1672) > at org.apache.atlas.hive.hook.HiveHook$2.run(HiveHook.java:197) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:5\ > 11) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor\ > .java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecuto\ > r.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.apache.hadoop.hive.ql.metadata.InvalidTableException: Table > not \ > found sparktest > at org.apache.hadoop.hive.ql.metadata.Hive.getTable(Hive.java:1120) > at org.apache.hadoop.hive.ql.metadata.Hive.getTable(Hive.java:1090) > at > org.apache.atlas.hive.hook.HiveHook.createOrUpdateEntities(HiveHook.\ > java:559) > at > org.apache.atlas.hive.hook.HiveHook.createOrUpdateEntities(HiveHook.\ > java:581) > at > org.apache.atlas.hive.hook.HiveHook.processHiveEntity(HiveHook.java:\ > 669) > at > org.apache.atlas.hive.hook.HiveHook.registerProcess(HiveHook.java:64\ > 9) > at org.apache.atlas.hive.hook.HiveHook.collect(HiveHook.java:270) > at org.apache.atlas.hive.hook.HiveHook.access$200(HiveHook.java:85) > at org.apache.atlas.hive.hook.HiveHook$2$1.run(HiveHook.java:200) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInform\ > ation.java:1657) > ... 6 more > 2017-01-31 07:49:57,029 INFO log.PerfLogger > (PerfLogger.java:PerfLogEnd(148)) \ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (ATLAS-1512) Hive Hook fails due to - Table not found exception
[ https://issues.apache.org/jira/browse/ATLAS-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059455#comment-16059455 ] Nixon Rodrigues edited comment on ATLAS-1512 at 6/23/17 7:01 AM: - [~r...@us.ibm.com] What is version of Hive in BigInsights 4.2.0.0 where you encountered this issue? Please make sure to use the same Hive version while building Atlas Hive hook, in addons/*/pom.xml files. was (Author: nixonrodrigues): [~r...@us.ibm.com] What is version of Hive in BigInsights 4.2.0.0 where you encountered this issue ? Let me know > Hive Hook fails due to - Table not found exception > -- > > Key: ATLAS-1512 > URL: https://issues.apache.org/jira/browse/ATLAS-1512 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-intg > Environment: newly built, and configured Apache Atlas .7.1rc3 > BigInsights 4.2.0.0 - > The example worked fine using Apache Atlas .7.0rc2 >Reporter: Russell Anderson >Priority: Critical > > After configuring Hive Hook: Ran the following Hive SQL command: > Create table sysibm.sparktest as select * from sysibm.sparktable; > -the table sysibm.sparktable exists > -the table system.sparktest is getting created as a result of this command. > -the table gets successfully created within the schema sysibm but the Hive > Hook does is not able deal with this correctly. > 2017-01-31 07:49:56,979 INFO metastore.HiveMetaStore > (HiveMetaStore.java:logIn\ > fo(746)) - 6: get_table : db=sysibm tbl=sparktest > 2017-01-31 07:49:56,980 INFO HiveMetaStore.audit > (HiveMetaStore.java:logAuditE\ > vent(371)) - ugi=hiveip=unknown-ip-addr cmd=get_table : db=sysibm > tbl=\ > sparktest > 2017-01-31 07:49:56,984 ERROR metadata.Hive (Hive.java:getTable(1119)) - > Table \ > sparktest not found: sysibm.sparktest table not found > 2017-01-31 07:49:56,984 ERROR hook.HiveHook (HiveHook.java:run(207)) - Atlas > ho\ > ok failed due to error > java.lang.reflect.UndeclaredThrowableException > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInform\ > ation.java:1672) > at org.apache.atlas.hive.hook.HiveHook$2.run(HiveHook.java:197) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:5\ > 11) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor\ > .java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecuto\ > r.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.apache.hadoop.hive.ql.metadata.InvalidTableException: Table > not \ > found sparktest > at org.apache.hadoop.hive.ql.metadata.Hive.getTable(Hive.java:1120) > at org.apache.hadoop.hive.ql.metadata.Hive.getTable(Hive.java:1090) > at > org.apache.atlas.hive.hook.HiveHook.createOrUpdateEntities(HiveHook.\ > java:559) > at > org.apache.atlas.hive.hook.HiveHook.createOrUpdateEntities(HiveHook.\ > java:581) > at > org.apache.atlas.hive.hook.HiveHook.processHiveEntity(HiveHook.java:\ > 669) > at > org.apache.atlas.hive.hook.HiveHook.registerProcess(HiveHook.java:64\ > 9) > at org.apache.atlas.hive.hook.HiveHook.collect(HiveHook.java:270) > at org.apache.atlas.hive.hook.HiveHook.access$200(HiveHook.java:85) > at org.apache.atlas.hive.hook.HiveHook$2$1.run(HiveHook.java:200) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInform\ > ation.java:1657) > ... 6 more > 2017-01-31 07:49:57,029 INFO log.PerfLogger > (PerfLogger.java:PerfLogEnd(148)) \ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-1896) Add Cross Origin [CORS] headers for Atlas
Nixon Rodrigues created ATLAS-1896: -- Summary: Add Cross Origin [CORS] headers for Atlas Key: ATLAS-1896 URL: https://issues.apache.org/jira/browse/ATLAS-1896 Project: Atlas Issue Type: Bug Reporter: Nixon Rodrigues Add Cross Origin [CORS] headers for Atlas, make it configurable from atlas-application properties -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1766) Atlas with Kafka SASL_SSL protocol
[ https://issues.apache.org/jira/browse/ATLAS-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-1766: --- Attachment: ATLAS-1766-9.patch > Atlas with Kafka SASL_SSL protocol > -- > > Key: ATLAS-1766 > URL: https://issues.apache.org/jira/browse/ATLAS-1766 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.7-incubating >Reporter: Sandeep Nemuri >Assignee: Nixon Rodrigues > Attachments: ATLAS-1766.1.patch, ATLAS-1766-9.patch > > > Creating this jira to add support to Kafka SASL_SSL protocol for Atlas. > Atlas is currently using old consumer api which doesn't support SSL > protocols. To support SSL protocol the consumer code should be re-written in > new consumer api. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-1512) Hive Hook fails due to - Table not found exception
[ https://issues.apache.org/jira/browse/ATLAS-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-1512. Resolution: Information Provided [~r...@us.ibm.com], Resolving this issue, can be reopen if you still face this issue. # Please make sure to use the same Hive version while building Atlas Hive hook, in addons/*/pom.xml files. > Hive Hook fails due to - Table not found exception > -- > > Key: ATLAS-1512 > URL: https://issues.apache.org/jira/browse/ATLAS-1512 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-intg > Environment: newly built, and configured Apache Atlas .7.1rc3 > BigInsights 4.2.0.0 - > The example worked fine using Apache Atlas .7.0rc2 >Reporter: Russell Anderson >Priority: Critical > > After configuring Hive Hook: Ran the following Hive SQL command: > Create table sysibm.sparktest as select * from sysibm.sparktable; > -the table sysibm.sparktable exists > -the table system.sparktest is getting created as a result of this command. > -the table gets successfully created within the schema sysibm but the Hive > Hook does is not able deal with this correctly. > 2017-01-31 07:49:56,979 INFO metastore.HiveMetaStore > (HiveMetaStore.java:logIn\ > fo(746)) - 6: get_table : db=sysibm tbl=sparktest > 2017-01-31 07:49:56,980 INFO HiveMetaStore.audit > (HiveMetaStore.java:logAuditE\ > vent(371)) - ugi=hiveip=unknown-ip-addr cmd=get_table : db=sysibm > tbl=\ > sparktest > 2017-01-31 07:49:56,984 ERROR metadata.Hive (Hive.java:getTable(1119)) - > Table \ > sparktest not found: sysibm.sparktest table not found > 2017-01-31 07:49:56,984 ERROR hook.HiveHook (HiveHook.java:run(207)) - Atlas > ho\ > ok failed due to error > java.lang.reflect.UndeclaredThrowableException > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInform\ > ation.java:1672) > at org.apache.atlas.hive.hook.HiveHook$2.run(HiveHook.java:197) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:5\ > 11) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor\ > .java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecuto\ > r.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.apache.hadoop.hive.ql.metadata.InvalidTableException: Table > not \ > found sparktest > at org.apache.hadoop.hive.ql.metadata.Hive.getTable(Hive.java:1120) > at org.apache.hadoop.hive.ql.metadata.Hive.getTable(Hive.java:1090) > at > org.apache.atlas.hive.hook.HiveHook.createOrUpdateEntities(HiveHook.\ > java:559) > at > org.apache.atlas.hive.hook.HiveHook.createOrUpdateEntities(HiveHook.\ > java:581) > at > org.apache.atlas.hive.hook.HiveHook.processHiveEntity(HiveHook.java:\ > 669) > at > org.apache.atlas.hive.hook.HiveHook.registerProcess(HiveHook.java:64\ > 9) > at org.apache.atlas.hive.hook.HiveHook.collect(HiveHook.java:270) > at org.apache.atlas.hive.hook.HiveHook.access$200(HiveHook.java:85) > at org.apache.atlas.hive.hook.HiveHook$2$1.run(HiveHook.java:200) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInform\ > ation.java:1657) > ... 6 more > 2017-01-31 07:49:57,029 INFO log.PerfLogger > (PerfLogger.java:PerfLogEnd(148)) \ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-1766) Atlas with Kafka SASL_SSL protocol
[ https://issues.apache.org/jira/browse/ATLAS-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-1766. Resolution: Fixed Thanks [~madhan.neethiraj] for commit, Thanks [~sarath.ku...@gmail.com],[~apoorvnaik],[~suma.shivaprasad] & [~madhan.neethiraj] inputs & reviews Patch commited on the following branch. * master :- http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/0e7f8ea4 * 0.8-incubating :- http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/7ec95fe7 > Atlas with Kafka SASL_SSL protocol > -- > > Key: ATLAS-1766 > URL: https://issues.apache.org/jira/browse/ATLAS-1766 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.7-incubating >Reporter: Sandeep Nemuri >Assignee: Nixon Rodrigues > Attachments: ATLAS-1766.1.patch, ATLAS-1766-9.patch > > > Creating this jira to add support to Kafka SASL_SSL protocol for Atlas. > Atlas is currently using old consumer api which doesn't support SSL > protocols. To support SSL protocol the consumer code should be re-written in > new consumer api. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (ATLAS-1766) Atlas with Kafka SASL_SSL protocol
[ https://issues.apache.org/jira/browse/ATLAS-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16072005#comment-16072005 ] Nixon Rodrigues edited comment on ATLAS-1766 at 7/3/17 7:26 AM: Thanks [~madhan.neethiraj] for commit, Thanks [~sarath.ku...@gmail.com],[~apoorvnaik],[~suma.shivaprasad] & [~madhan.neethiraj] for inputs & review. Patch commited on the following branch. * master :- http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/0e7f8ea4 * 0.8-incubating :- http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/7ec95fe7 was (Author: nixonrodrigues): Thanks [~madhan.neethiraj] for commit, Thanks [~sarath.ku...@gmail.com],[~apoorvnaik],[~suma.shivaprasad] & [~madhan.neethiraj] inputs & reviews Patch commited on the following branch. * master :- http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/0e7f8ea4 * 0.8-incubating :- http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/7ec95fe7 > Atlas with Kafka SASL_SSL protocol > -- > > Key: ATLAS-1766 > URL: https://issues.apache.org/jira/browse/ATLAS-1766 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.7-incubating >Reporter: Sandeep Nemuri >Assignee: Nixon Rodrigues > Attachments: ATLAS-1766.1.patch, ATLAS-1766-9.patch > > > Creating this jira to add support to Kafka SASL_SSL protocol for Atlas. > Atlas is currently using old consumer api which doesn't support SSL > protocols. To support SSL protocol the consumer code should be re-written in > new consumer api. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-1908) Updating old Kafka consumer api properties to reflect change in new KafkaConsumer configs for Atlas.
Nixon Rodrigues created ATLAS-1908: -- Summary: Updating old Kafka consumer api properties to reflect change in new KafkaConsumer configs for Atlas. Key: ATLAS-1908 URL: https://issues.apache.org/jira/browse/ATLAS-1908 Project: Atlas Issue Type: Bug Reporter: Nixon Rodrigues In ATLAS-1766, the old Kafka consumer api was updated with new Kafka consumer api. Due to this update, there were changes in configs. New property: atlas.kafka.session.timeout.ms=3 Renamed property: atlas.kafka.auto.commit.enable=false to atlas.kafka.enable.auto.commit=false New default value: atlas.kafka.auto.offset.reset=smallest to atlas.kafka.auto.offset.reset=earliest Need to handle old configs, so that Kafka consumer starts gracefully even if new configs are not added explicitly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ATLAS-1908) Updating old Kafka consumer api properties to reflect change in new KafkaConsumer configs for Atlas.
[ https://issues.apache.org/jira/browse/ATLAS-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues reassigned ATLAS-1908: -- Assignee: Nixon Rodrigues > Updating old Kafka consumer api properties to reflect change in new > KafkaConsumer configs for Atlas. > > > Key: ATLAS-1908 > URL: https://issues.apache.org/jira/browse/ATLAS-1908 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues > Attachments: ATLAS-1908.patch > > > In ATLAS-1766, the old Kafka consumer api was updated with new Kafka consumer > api. > Due to this update, there were changes in configs. > > New property: > atlas.kafka.session.timeout.ms=3 > > Renamed property: > atlas.kafka.auto.commit.enable=false to atlas.kafka.enable.auto.commit=false > > New default value: > atlas.kafka.auto.offset.reset=smallest to > atlas.kafka.auto.offset.reset=earliest > Need to handle old configs, so that Kafka consumer starts gracefully even if > new configs are not added explicitly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1908) Updating old Kafka consumer api properties to reflect change in new KafkaConsumer configs for Atlas.
[ https://issues.apache.org/jira/browse/ATLAS-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-1908: --- Attachment: ATLAS-1908.patch > Updating old Kafka consumer api properties to reflect change in new > KafkaConsumer configs for Atlas. > > > Key: ATLAS-1908 > URL: https://issues.apache.org/jira/browse/ATLAS-1908 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues > Attachments: ATLAS-1908.patch > > > In ATLAS-1766, the old Kafka consumer api was updated with new Kafka consumer > api. > Due to this update, there were changes in configs. > > New property: > atlas.kafka.session.timeout.ms=3 > > Renamed property: > atlas.kafka.auto.commit.enable=false to atlas.kafka.enable.auto.commit=false > > New default value: > atlas.kafka.auto.offset.reset=smallest to > atlas.kafka.auto.offset.reset=earliest > Need to handle old configs, so that Kafka consumer starts gracefully even if > new configs are not added explicitly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1906) Atlas client should support setting hadoop-jwt token in header
[ https://issues.apache.org/jira/browse/ATLAS-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-1906: --- Attachment: ATLAS-1906.patch > Atlas client should support setting hadoop-jwt token in header > -- > > Key: ATLAS-1906 > URL: https://issues.apache.org/jira/browse/ATLAS-1906 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Hemanth Yamijala >Assignee: Apoorv Naik > Attachments: > 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch, > ATLAS-1906.patch > > > In ATLAS-1767, support was added to make the Atlas REST API calls take a > hadoop-jwt token coming from Knox SSO and authenticate the user. > This works perfectly when using a vanilla HTTP client. We have found it > convenient to use the Atlas client Java binding for our work. However, it > does not seem to support setting the hadoop-jwt token. Hence, we don't seem > to be able to use it with a Knox SSO enabled Atlas server for API calls. > Could this support be added please? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1906) Atlas client should support setting hadoop-jwt token in header
[ https://issues.apache.org/jira/browse/ATLAS-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16072837#comment-16072837 ] Nixon Rodrigues commented on ATLAS-1906: Currently Atlas Client supports UGI & Basic Auth, as part of this jira i have overloaded the Atlas Client constructor to support Knox SSO cookie by adding below constructor. AtlasClient(atlasURL, cookieName, CookieValue, path, domain); AtlasClient(atlasURL, Cookie); Added patch ATLAS-1906.patch for it. > Atlas client should support setting hadoop-jwt token in header > -- > > Key: ATLAS-1906 > URL: https://issues.apache.org/jira/browse/ATLAS-1906 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Hemanth Yamijala >Assignee: Apoorv Naik > Attachments: > 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch, > ATLAS-1906.patch > > > In ATLAS-1767, support was added to make the Atlas REST API calls take a > hadoop-jwt token coming from Knox SSO and authenticate the user. > This works perfectly when using a vanilla HTTP client. We have found it > convenient to use the Atlas client Java binding for our work. However, it > does not seem to support setting the hadoop-jwt token. Hence, we don't seem > to be able to use it with a Knox SSO enabled Atlas server for API calls. > Could this support be added please? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1906) Atlas client should support setting hadoop-jwt token in header
[ https://issues.apache.org/jira/browse/ATLAS-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-1906: --- Attachment: ATLAS-1906.1.patch This patch ATLAS-1906.1.patch includes setHadoopJWTCookie method in AtlasBaseClient, this method can be used to update the fresh hadoopJWT cookie when old cookie is expired instead creating the new object of AtlasClient. > Atlas client should support setting hadoop-jwt token in header > -- > > Key: ATLAS-1906 > URL: https://issues.apache.org/jira/browse/ATLAS-1906 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Hemanth Yamijala >Assignee: Apoorv Naik > Attachments: > 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch, > ATLAS-1906.1.patch, ATLAS-1906.patch > > > In ATLAS-1767, support was added to make the Atlas REST API calls take a > hadoop-jwt token coming from Knox SSO and authenticate the user. > This works perfectly when using a vanilla HTTP client. We have found it > convenient to use the Atlas client Java binding for our work. However, it > does not seem to support setting the hadoop-jwt token. Hence, we don't seem > to be able to use it with a Knox SSO enabled Atlas server for API calls. > Could this support be added please? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1906) Atlas client should support setting hadoop-jwt token in header
[ https://issues.apache.org/jira/browse/ATLAS-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-1906: --- Attachment: ATLAS-1906.2.patch > Atlas client should support setting hadoop-jwt token in header > -- > > Key: ATLAS-1906 > URL: https://issues.apache.org/jira/browse/ATLAS-1906 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Hemanth Yamijala >Assignee: Apoorv Naik > Attachments: > 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch, > ATLAS-1906.1.patch, ATLAS-1906.2.patch, ATLAS-1906.patch > > > In ATLAS-1767, support was added to make the Atlas REST API calls take a > hadoop-jwt token coming from Knox SSO and authenticate the user. > This works perfectly when using a vanilla HTTP client. We have found it > convenient to use the Atlas client Java binding for our work. However, it > does not seem to support setting the hadoop-jwt token. Hence, we don't seem > to be able to use it with a Knox SSO enabled Atlas server for API calls. > Could this support be added please? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1906) Atlas client should support setting hadoop-jwt token in header
[ https://issues.apache.org/jira/browse/ATLAS-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-1906: --- Attachment: ATLAS-1906.3.patch > Atlas client should support setting hadoop-jwt token in header > -- > > Key: ATLAS-1906 > URL: https://issues.apache.org/jira/browse/ATLAS-1906 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Hemanth Yamijala >Assignee: Apoorv Naik > Attachments: > 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch, > ATLAS-1906.1.patch, ATLAS-1906.2.patch, ATLAS-1906.3.patch, ATLAS-1906.patch > > > In ATLAS-1767, support was added to make the Atlas REST API calls take a > hadoop-jwt token coming from Knox SSO and authenticate the user. > This works perfectly when using a vanilla HTTP client. We have found it > convenient to use the Atlas client Java binding for our work. However, it > does not seem to support setting the hadoop-jwt token. Hence, we don't seem > to be able to use it with a Knox SSO enabled Atlas server for API calls. > Could this support be added please? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1906) Atlas client should support setting hadoop-jwt token in header
[ https://issues.apache.org/jira/browse/ATLAS-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16076141#comment-16076141 ] Nixon Rodrigues commented on ATLAS-1906: This patch ATLAS-1906.3.patch includes changes to handle review comments from David & Apoorv. > Atlas client should support setting hadoop-jwt token in header > -- > > Key: ATLAS-1906 > URL: https://issues.apache.org/jira/browse/ATLAS-1906 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Hemanth Yamijala >Assignee: Apoorv Naik > Attachments: > 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch, > ATLAS-1906.1.patch, ATLAS-1906.2.patch, ATLAS-1906.3.patch, ATLAS-1906.patch > > > In ATLAS-1767, support was added to make the Atlas REST API calls take a > hadoop-jwt token coming from Knox SSO and authenticate the user. > This works perfectly when using a vanilla HTTP client. We have found it > convenient to use the Atlas client Java binding for our work. However, it > does not seem to support setting the hadoop-jwt token. Hence, we don't seem > to be able to use it with a Knox SSO enabled Atlas server for API calls. > Could this support be added please? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-1928) [[[[[@##HELPLINEUSA 1-866-866-1752&&&)))) D-Link support email address %% D-Link Router Tech @@@ Support Number ##$$$$$
[ https://issues.apache.org/jira/browse/ATLAS-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-1928. Resolution: Invalid > [@##HELPLINEUSA 1-866-866-1752&&& D-Link support email address %% > D-Link Router Tech @@@ Support Number ##$ > --- > > Key: ATLAS-1928 > URL: https://issues.apache.org/jira/browse/ATLAS-1928 > Project: Atlas > Issue Type: Bug > Components: atlas-intg > Environment: @@D-Link Router customer care phone number@@ > --D-Link Router customer service billing--- > !!D-Link Router customer service email address!!! > D-Link Router >Reporter: johnson >Priority: Critical > Labels: !!D-Link, !!D-Link, ###D-Link, > support, $$$D-Link, D-Link, ((D-Link, --D-Link, @@D-Link, D-Link, > Router, Router, address, address!!!, billing---, care, chat, contact, > customer, desk, email, for, free, gD-Link, help, in, internet, > issue, live, number, number33, number@@, number, > numbers, phone, secure%ty, security, service, service$$$, > service***, services, support, tech, technical, telephone, toll, us@, > usa, usa)Z) > > @@D-Link Router customer care phone number@@ > --D-Link Router customer service billing--- > !!D-Link Router customer service email address!!! > D-Link Router customer service live chat > D-Link Router customer service telephone number > D-Link Router customer support usa phone number > ###D-Link Router help desk support phone number free in usa > D-Link Router phone number customer services us@ > D-Link Router phone number support > $$$D-Link Router support phone number > D-Link Router tech support phone number free in usa > D-Link Router tech support phone number > D-Link Router technical support customer service*** > D-Link Router technical support number > D-Link Router telephone number > D-Link Router toll free customer care number > ((D-Link Router toll free number in usa)Z) > D-Link Router contact phone number in usa > D-Link Router customer service number > D-Link Router customer service phone number > D-Link Router customer service telephone number > D-Link Router customer support number > D-Link Router customer support phone number > D-Link Router customer support phone number > D-Link Router help desk phone number in usa > D-Link Router phone number > D-Link Router phone number support for technical issue in usa > D-Link Router support phone number > D-Link Router technical support help desk phone number > D-Link Router technical support number > D-Link Router technical support phone number > D-Link customer service number33 > D-Link customer service telephone number > gD-Link customer services email > D-Link customer support email address > D-Link customer support number > D-Link customer support phone number > D-Link customer service phone number > D-Link internet security contact phone number > D-Link internet security customer service phone number > D-Link internet security phone number > D-Link internet secure%ty help phone number > D-Link internet security phone number in usa > D-Link internet security support phone number > D-Link internet security technical support > D-Link phone number customer service$$$ > D-Link phone numbers customer support > D-Link phone support number > D-Link security contact phone number > D-Link security phone number customer service > D-Link security support phone number > !!D-Link support contact number > D-Link support email address > D-Link support phone number -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-1929) [[[[[@##HELPLINEUSA 1-866-866-1752&&&)))) Motorolasupport email address %% MotorolaRouter Tech @@@ Support Number ##$$$$$
[ https://issues.apache.org/jira/browse/ATLAS-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-1929. Resolution: Invalid > [@##HELPLINEUSA 1-866-866-1752&&& Motorolasupport email address %% > MotorolaRouter Tech @@@ Support Number ##$ > - > > Key: ATLAS-1929 > URL: https://issues.apache.org/jira/browse/ATLAS-1929 > Project: Atlas > Issue Type: Bug > Components: atlas-webui > Environment: @HELPLINE@!! 1-866-866-1752 MotorolaRouter Support > Number%% MotorolaRouter Tech Support Number > @@MotorolaRouter customer care phone number@@ > --MotorolaRouter customer service billing--- > !!MotorolaRouter customer service email address!!! > MotorolaRouter customer >Reporter: johnson >Priority: Critical > Labels: !!MotorolaRouter, ###MotorolaRouter, support, > $$$MotorolaRouter, MotorolaRouter, ((MotorolaRouter, > --MotorolaRouter, @@MotorolaRouter, MotorolaRouter, Motorolacustomer, > Motorolainternet, address, address!!!, billing---, care, chat, contact, > customer, desk, email, for, free, gMotorolacustomer, help, in, > issue, live, number, number33, number@@, phone, > secure%ty, security, service, service***, services, support, tech, > technical, telephone, toll, us@, usa, usa)Z) > > @@MotorolaRouter customer care phone number@@ > --MotorolaRouter customer service billing--- > !!MotorolaRouter customer service email address!!! > MotorolaRouter customer service live chat > MotorolaRouter customer service telephone number > MotorolaRouter customer support usa phone number > ###MotorolaRouter help desk support phone number free in usa > MotorolaRouter phone number customer services us@ > MotorolaRouter phone number support > $$$MotorolaRouter support phone number > MotorolaRouter tech support phone number free in usa > MotorolaRouter tech support phone number > MotorolaRouter technical support customer service*** > MotorolaRouter technical support number > MotorolaRouter telephone number > MotorolaRouter toll free customer care number > ((MotorolaRouter toll free number in usa)Z) > MotorolaRouter contact phone number in usa > MotorolaRouter customer service number > MotorolaRouter customer service phone number > MotorolaRouter customer service telephone number > MotorolaRouter customer support number > MotorolaRouter customer support phone number > MotorolaRouter customer support phone number > MotorolaRouter help desk phone number in usa > MotorolaRouter phone number > MotorolaRouter phone number support for technical issue in usa > MotorolaRouter support phone number > MotorolaRouter technical support help desk phone number > MotorolaRouter technical support number > MotorolaRouter technical support phone number > Motorolacustomer service number33 > Motorolacustomer service telephone number > gMotorolacustomer services email > Motorolacustomer support email address > Motorolacustomer support number > Motorolacustomer support phone number > Motorolacustomer service phone number > Motorolainternet security contact phone number > Motorolainternet security customer service phone number > Motorolainternet security phone number > Motorolainternet secure%ty help phone number -- This message was sent by Atlassian JIRA (v6.4.14#64029)
dev@atlas.apache.org
[ https://issues.apache.org/jira/browse/ATLAS-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-1930. Resolution: Invalid > Justin Langer$$$Call US!!!1.866.866.1752!@!)) Belkin Router tech > support number Belkin Router support& > -- > > Key: ATLAS-1930 > URL: https://issues.apache.org/jira/browse/ATLAS-1930 > Project: Atlas > Issue Type: Bug > Components: atlas-intg > Environment: Belkin Router phone number > Belkin Router online %%%support > Belkin customer service number > Belkin tech support center > Belkin customer service > $Belkin customer care number usa > Belkin customer number > @Belkin customer support number > Belkin customer care number >Reporter: johnson > Labels: $Belkin, %%%support, @Belkin, > Belkin, Router, care, center, customer, number, online, phone, service, > support, tech, usa > > %service phone number Call US!!!1-866-866-1752Belkin Router tech support > number Belkin Router customer > service phone number((())) Call US!!!1-866-866-1752Belkin Router tech > support number Belkin Router customer > service phone& number Call US!!!1-866-866-1752Belkin Router tech > support number Belkin Router customer > !!service phone number Call US!!!1-866-866-1752Belkin Router tech support > number Belkin Router customer > service phone number Contact@%1-866-866-1752@% Belkin Router tech support > number Belkin Router tech support phone number *Belkin Router customer > service phone number. > Belkin Router Router customer service number$$ > Belkin customer service phone number > Belkin Router Router technical support number > ContactBelkin Router support > Belkin Router phone number > Belkin Router online %%%support > Belkin customer service number > Belkin tech support center > Belkin customer service > $Belkin customer care number usa > Belkin customer number > @Belkin customer support number > Belkin customer care number > Belkin customer care toll free number > Belkin tech support > Belkin technical support > Belkin Router support > Belkin Router tech support > Belkin support center > Belkin^.com customer service > Belkin Router customer care number > 333Belkin customer care > Belkin phone number > phone number for Belkin customer service > Belkin phone support > rrrBelkin phone number tech support > Belkin support phone number > contact Belkin by phone77# > Belkin contact phone number > Belkin helpline phone number > Belkin Router phone > ###Belkin Router for phone -- This message was sent by Atlassian JIRA (v6.4.14#64029)
dev@atlas.apache.org
[ https://issues.apache.org/jira/browse/ATLAS-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-1931. Resolution: Invalid > Justin Langer$$$Call US!!!1.866.866.1752!@!)) Asus Router tech > support number Asus Router support& > -- > > Key: ATLAS-1931 > URL: https://issues.apache.org/jira/browse/ATLAS-1931 > Project: Atlas > Issue Type: Bug > Components: atlas-core > Environment: %service phone number Call US!!!1-866-866-1752Asus > Router tech support number Asus Router customer > service phone number((())) Call US!!!1-866-866-1752Asus Router tech > support number Asus Router customer > service phone& number Call US!!!1-866-866-1752Asus Router tech > support number Asus Router customer >Reporter: johnson > Labels: !!service, ###Asus, $Asus, > %%%support, %service, *Asus, 333Asus, > @Asus, Asus, Asus^.com, Call, Contact@%1-866-866-1752@%, > ContactAsus, Router, US!!!1-866-866-1752Asus, by, care, center, contact, > customer, for, free, helpline, number, number$$, number((())), > number., online, phone, phone&, phone77#, > phone, rrrAsus, service, support, support, > tech, technical, toll, usa > > %service phone number Call US!!!1-866-866-1752Asus Router tech support > number Asus Router customer > service phone number((())) Call US!!!1-866-866-1752Asus Router tech > support number Asus Router customer > service phone& number Call US!!!1-866-866-1752Asus Router tech > support number Asus Router customer > !!service phone number Call US!!!1-866-866-1752Asus Router tech support > number Asus Router customer > service phone number Contact@%1-866-866-1752@% Asus Router tech support > number Asus Router tech support phone number *Asus Router customer > service phone number. > Asus Router Router customer service number$$ > Asus customer service phone number > Asus Router Router technical support number > ContactAsus Router support > Asus Router phone number > Asus Router online %%%support > Asus customer service number > Asus tech support center > Asus customer service > $Asus customer care number usa > Asus customer number > @Asus customer support number > Asus customer care number > Asus customer care toll free number > Asus tech support > Asus technical support > Asus Router support > Asus Router tech support > Asus support center > Asus^.com customer service > Asus Router customer care number > 333Asus customer care > Asus phone number > phone number for Asus customer service > Asus phone support > rrrAsus phone number tech support > Asus support phone number > contact Asus by phone77# > Asus contact phone number > Asus helpline phone number > Asus Router phone > ###Asus Router for phone -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-1933) [[[[[@##HELPLINEUSA 1-866-866-1752&&&)))) Netgear support email address %% NetgearRouter Tech @@@ Support Number ##$$$$$
[ https://issues.apache.org/jira/browse/ATLAS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-1933. Resolution: Invalid > [@##HELPLINEUSA 1-866-866-1752&&& Netgear support email address %% > NetgearRouter Tech @@@ Support Number ##$ > > > Key: ATLAS-1933 > URL: https://issues.apache.org/jira/browse/ATLAS-1933 > Project: Atlas > Issue Type: Bug > Components: atlas-webui > Environment: @HELPLINE@!! 1-866-866-1752 Netgear Router Support > Number%% NetgearRouter Tech Support Number > @@NetgearRouter customer care phone number@@ > --NetgearRouter customer service billing--- > !!NetgearRouter customer service email address!!! > NetgearRouter customer service live chat >Reporter: johnson > Labels: !!Netgearsupport, !!NetgearRouter, > ###NetgearRouter, support, $$$NetgearRouter, NetgearRouter, > ((NetgearRouter, --NetgearRouter, @@NetgearRouter, NetgearRouter, > Netgearcustomer, Netgearinternet, Netgearphone, Netgearsecurity, > Netgearsupport, address, address!!!, billing---, care, chat, contact, > customer, desk, email, for, free, gNetgearcustomer, help, in, > issue, live, number, number33, number@@, number, > numbers, phone, secure%ty, security, service, service$$$, > service***, services, support, tech, technical, telephone, toll, us@, > usa, usa)Z) > > @@NetgearRouter customer care phone number@@ > --NetgearRouter customer service billing--- > !!NetgearRouter customer service email address!!! > NetgearRouter customer service live chat > NetgearRouter customer service telephone number > NetgearRouter customer support usa phone number > ###NetgearRouter help desk support phone number free in usa > NetgearRouter phone number customer services us@ > NetgearRouter phone number support > $$$NetgearRouter support phone number > NetgearRouter tech support phone number free in usa > NetgearRouter tech support phone number > NetgearRouter technical support customer service*** > NetgearRouter technical support number > NetgearRouter telephone number > NetgearRouter toll free customer care number > ((NetgearRouter toll free number in usa)Z) > NetgearRouter contact phone number in usa > NetgearRouter customer service number > NetgearRouter customer service phone number > NetgearRouter customer service telephone number > NetgearRouter customer support number > NetgearRouter customer support phone number > NetgearRouter customer support phone number > NetgearRouter help desk phone number in usa > NetgearRouter phone number > NetgearRouter phone number support for technical issue in usa > NetgearRouter support phone number > NetgearRouter technical support help desk phone number > NetgearRouter technical support number > NetgearRouter technical support phone number > Netgearcustomer service number33 > Netgearcustomer service telephone number > gNetgearcustomer services email > Netgearcustomer support email address > Netgearcustomer support number > Netgearcustomer support phone number > Netgearcustomer service phone number > Netgearinternet security contact phone number > Netgearinternet security customer service phone number > Netgearinternet security phone number > Netgearinternet secure%ty help phone number > Netgearinternet security phone number in usa > Netgearinternet security support phone number > Netgearinternet security technical support > Netgearphone number customer service$$$ > Netgearphone numbers customer support > Netgearphone support number > Netgearsecurity contact phone number > Netgearsecurity phone number customer service > Netgearsecurity support phone number > !!Netgearsupport contact number > Netgearsupport email address > Netgearsupport phone number > Netgearsupport telephone number -- This message was sent by Atlassian JIRA (v6.4.14#64029)
dev@atlas.apache.org
[ https://issues.apache.org/jira/browse/ATLAS-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-1934. Resolution: Invalid > MCdonald$$$Call US!!!1.866.866.1752!@!)) Cisco Router tech support > number Cisco Router support& > --- > > Key: ATLAS-1934 > URL: https://issues.apache.org/jira/browse/ATLAS-1934 > Project: Atlas > Issue Type: Bug > Components: atlas-core > Environment: Cisco Router support > Cisco Router tech support > Cisco support center > Cisco^.com customer service > Cisco Router customer care number > 333Cisco customer care > Cisco phone number > phone number for Cisco customer service > Cisco phone support > rrrCisco phone number tech support > Cisco support phone number > contact Cisco by phone77# > Cisco contact phone number > Cisco helpline phone number > Cisco Router phone > ###Cisco Router for phone >Reporter: johnson >Priority: Critical > Labels: ###Cisco, 333Cisco, Cisco, > Cisco^.com, Router, by, care, center, contact, customer, for, > helpline, number, phone, phone77#, phone, > rrrCisco, service, support, support, tech > > %service phone number Call US!!!1-866-866-1752Cisco Router tech support > number Cisco Router customer > service phone number((())) Call US!!!1-866-866-1752Cisco Router tech > support number Cisco Router customer > service phone& number Call US!!!1-866-866-1752Cisco Router tech > support number Cisco Router customer > !!service phone number Call US!!!1-866-866-1752Cisco Router tech support > number Cisco Router customer > service phone number Contact@%1-866-866-1752@% Cisco Router tech support > number Cisco Router tech support phone number *Cisco Router customer > service phone number. > Cisco Router Router customer service number$$ > Cisco customer service phone number > Cisco Router Router technical support number > ContactCisco Router support > Cisco Router phone number > Cisco Router online %%%support > Cisco customer service number > Cisco tech support center > Cisco customer service > $Cisco customer care number usa > Cisco customer number > @Cisco customer support number > Cisco customer care number > Cisco customer care toll free number > Cisco tech support > Cisco technical support > Cisco Router support > Cisco Router tech support > Cisco support center > Cisco^.com customer service > Cisco Router customer care number > 333Cisco customer care > Cisco phone number > phone number for Cisco customer service > Cisco phone support > rrrCisco phone number tech support > Cisco support phone number > contact Cisco by phone77# > Cisco contact phone number > Cisco helpline phone number > Cisco Router phone > ###Cisco Router for phone -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ATLAS-1906) Atlas client should support setting hadoop-jwt token in header
[ https://issues.apache.org/jira/browse/ATLAS-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues reassigned ATLAS-1906: -- Assignee: Nixon Rodrigues (was: Apoorv Naik) > Atlas client should support setting hadoop-jwt token in header > -- > > Key: ATLAS-1906 > URL: https://issues.apache.org/jira/browse/ATLAS-1906 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Hemanth Yamijala >Assignee: Nixon Rodrigues > Attachments: > 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch, > ATLAS-1906.1.patch, ATLAS-1906.2.patch, ATLAS-1906.3.patch, ATLAS-1906.patch > > > In ATLAS-1767, support was added to make the Atlas REST API calls take a > hadoop-jwt token coming from Knox SSO and authenticate the user. > This works perfectly when using a vanilla HTTP client. We have found it > convenient to use the Atlas client Java binding for our work. However, it > does not seem to support setting the hadoop-jwt token. Hence, we don't seem > to be able to use it with a Knox SSO enabled Atlas server for API calls. > Could this support be added please? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1906) Atlas client should support setting hadoop-jwt token in header
[ https://issues.apache.org/jira/browse/ATLAS-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-1906: --- Fix Version/s: 0.8.1-incubating 0.9-incubating > Atlas client should support setting hadoop-jwt token in header > -- > > Key: ATLAS-1906 > URL: https://issues.apache.org/jira/browse/ATLAS-1906 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Hemanth Yamijala >Assignee: Nixon Rodrigues > Fix For: 0.9-incubating, 0.8.1-incubating > > Attachments: > 0001-ATLAS-1906-Support-for-custom-header-s-in-Atlas-clie.patch, > ATLAS-1906.1.patch, ATLAS-1906.2.patch, ATLAS-1906.3.patch, ATLAS-1906.patch > > > In ATLAS-1767, support was added to make the Atlas REST API calls take a > hadoop-jwt token coming from Knox SSO and authenticate the user. > This works perfectly when using a vanilla HTTP client. We have found it > convenient to use the Atlas client Java binding for our work. However, it > does not seem to support setting the hadoop-jwt token. Hence, we don't seem > to be able to use it with a Knox SSO enabled Atlas server for API calls. > Could this support be added please? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-1940) Atlas server fails to initialize types on startup from graph store due to duplicate type registered.
Nixon Rodrigues created ATLAS-1940:
--
Summary: Atlas server fails to initialize types on startup from
graph store due to duplicate type registered.
Key: ATLAS-1940
URL: https://issues.apache.org/jira/browse/ATLAS-1940
Project: Atlas
Issue Type: Bug
Components: atlas-intg
Affects Versions: 0.8-incubating
Reporter: Nixon Rodrigues
Assignee: Nixon Rodrigues
Priority: Blocker
Fix For: 0.9-incubating, 0.8.1-incubating
Types are not getting restored from typesRegistry during Atlas startup due
duplicate type issue.
Below is exception trace.
{code}
2017-07-07 13:35:23,088 INFO - [main:] ~ Restoring type CLASS.Process.null
(GraphBackedTypeStore:267)
2017-07-07 13:35:23,099 INFO - [main:] ~ Restoring type
CLASS.falcon_process.null (GraphBackedTypeStore:267)
2017-07-07 13:35:23,122 INFO - [main:] ~ Restoring type TRAIT.Metric.Metric
Trait (GraphBackedTypeStore:267)
2017-07-07 13:35:23,132 INFO - [main:] ~ Restoring type
CLASS.Referenceable.null (GraphBackedTypeStore:267)
2017-07-07 13:35:23,140 INFO - [main:] ~ Restoring type
CLASS.hive_storagedesc.null (GraphBackedTypeStore:267)
2017-07-07 13:35:23,203 INFO - [main:] ~ Restoring type CLASS.hive_table.null
(GraphBackedTypeStore:267)
2017-07-07 13:35:23,276 INFO - [main:] ~ Restoring type
CLASS.falcon_feed_creation.null (GraphBackedTypeStore:267)
2017-07-07 13:35:23,288 INFO - [main:] ~ Restoring type
CLASS.sqoop_dbdatastore.null (GraphBackedTypeStore:267)
2017-07-07 13:35:23,399 INFO - [main:] ~ Number of types got from transient
type system: 49 (DefaultMetadataService:168)
2017-07-07 13:35:23,406 INFO - [main:] ~ Restored type system from the store
(DefaultMetadataService:161)
2017-07-07 13:35:23,407 INFO - [main:] ~ Global indexes already exist for
graph (GraphBackedSearchIndexer:141)
2017-07-07 13:35:23,753 WARN - [main:] ~ Invalid constraint ownedRef for
attribute hive_storagedesc.serdeInfo (AtlasTypeDefGraphStore:689)
2017-07-07 13:35:23,754 WARN - [main:] ~ Invalid constraint ownedRef for
attribute hive_table.aliases (AtlasTypeDefGraphStore:689)
2017-07-07 13:35:23,759 ERROR - [main:] ~ failed to initialize types from graph
store (AtlasTypeDefGraphStoreV1:77)
org.apache.atlas.exception.AtlasBaseException: Given type TaxonomyTerm already
exists
at
org.apache.atlas.type.AtlasTypeRegistry$AtlasTransientTypeRegistry.addTypeWithNoRefResolve(AtlasTypeRegistry.java:573)
at
org.apache.atlas.type.AtlasTypeRegistry$AtlasTransientTypeRegistry.addTypesWithNoRefResolve(AtlasTypeRegistry.java:611)
at
org.apache.atlas.type.AtlasTypeRegistry$AtlasTransientTypeRegistry.addTypes(AtlasTypeRegistry.java:407)
at
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.init(AtlasTypeDefGraphStore.java:105)
at
org.apache.atlas.repository.store.graph.v1.AtlasTypeDefGraphStoreV1.init(AtlasTypeDefGraphStoreV1.java:107)
at
org.apache.atlas.repository.store.graph.v1.AtlasTypeDefGraphStoreV1.(AtlasTypeDefGraphStoreV1.java:75)
at
org.apache.atlas.repository.store.graph.v1.AtlasTypeDefGraphStoreV1$$EnhancerByGuice$$21ccc5be.()
at
org.apache.atlas.repository.store.graph.v1.AtlasTypeDefGraphStoreV1$$EnhancerByGuice$$21ccc5be$$FastClassByGuice$$a11fb32d.newInstance()
at
com.google.inject.internal.ProxyFactory$ProxyConstructor.newInstance(ProxyFactory.java:265)
at
com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:111)
at
com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:90)
at
com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:268)
at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:56)
at
com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1092)
at
com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
at
com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:194)
at
com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
at
com.google.inject.internal.InternalInjectorCreator$1.call(InternalInjectorCreator.java:205)
at
com.google.inject.internal.InternalInjectorCreator$1.call(InternalInjectorCreator.java:199)
at
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1085)
at
com.google.inject.internal.InternalInjectorCreator.loadEagerSingletons(InternalInjectorCreator.java:199)
at
com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:180)
at
com.google.inject.int
[jira] [Commented] (ATLAS-1893) UI - Lineage support for IE-10 and onwards.
[ https://issues.apache.org/jira/browse/ATLAS-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083619#comment-16083619 ] Nixon Rodrigues commented on ATLAS-1893: [~kevalbhatt], Found issue in lineage. In IE-10 the hover of lineage doesn't appear. so canceling this patch. > UI - Lineage support for IE-10 and onwards. > --- > > Key: ATLAS-1893 > URL: https://issues.apache.org/jira/browse/ATLAS-1893 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 0.9-incubating > Environment: IE >Reporter: Nixon Rodrigues >Assignee: Keval Bhatt > Fix For: 0.8-incubating, 0.9-incubating > > Attachments: ATLAS-1893.patch > > > Currently lineage is not working on IE. > This fix will provide lineage support for browsers IE10 and onwards. > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1893) UI - Lineage support for IE-10 and onwards.
[ https://issues.apache.org/jira/browse/ATLAS-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-1893: --- Attachment: Lineage-IE-issue.jpg > UI - Lineage support for IE-10 and onwards. > --- > > Key: ATLAS-1893 > URL: https://issues.apache.org/jira/browse/ATLAS-1893 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 0.9-incubating > Environment: IE >Reporter: Nixon Rodrigues >Assignee: Keval Bhatt > Fix For: 0.8-incubating, 0.9-incubating > > Attachments: ATLAS-1893.patch, Lineage-IE-issue.jpg > > > Currently lineage is not working on IE. > This fix will provide lineage support for browsers IE10 and onwards. > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (ATLAS-1893) UI - Lineage support for IE-10 and onwards.
[ https://issues.apache.org/jira/browse/ATLAS-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083619#comment-16083619 ] Nixon Rodrigues edited comment on ATLAS-1893 at 7/12/17 8:06 AM: - [~kevalbhatt], Found issue in lineage. In IE-10 the hover of lineage doesn't appear. so canceling this patch. !Lineage-IE-issue.jpg|thumbnail! was (Author: nixonrodrigues): [~kevalbhatt], Found issue in lineage. In IE-10 the hover of lineage doesn't appear. so canceling this patch. > UI - Lineage support for IE-10 and onwards. > --- > > Key: ATLAS-1893 > URL: https://issues.apache.org/jira/browse/ATLAS-1893 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 0.9-incubating > Environment: IE >Reporter: Nixon Rodrigues >Assignee: Keval Bhatt > Fix For: 0.8-incubating, 0.9-incubating > > Attachments: ATLAS-1893.patch, Lineage-IE-issue.jpg > > > Currently lineage is not working on IE. > This fix will provide lineage support for browsers IE10 and onwards. > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1896) Add Cross Origin [CORS] headers for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083785#comment-16083785 ] Nixon Rodrigues commented on ATLAS-1896: Thank Ruchi for the patch will commit it shortly. > Add Cross Origin [CORS] headers for Atlas > -- > > Key: ATLAS-1896 > URL: https://issues.apache.org/jira/browse/ATLAS-1896 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Ruchi Solani > Attachments: 0001-ATLAS-1896.patch > > > Add Cross Origin [CORS] headers for Atlas, make it configurable from > atlas-application properties -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1896) Add Cross Origin [CORS] headers for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083839#comment-16083839 ] Nixon Rodrigues commented on ATLAS-1896: Committed the patch to following branches * master - https://git1-us-west.apache.org/repos/asf/incubator-atlas/repo?p=incubator-atlas.git;a=commit;h=40d909ef8726b807a263ff8f8be57150e51f910d * 0.8-inbuating - https://git1-us-west.apache.org/repos/asf/incubator-atlas/repo?p=incubator-atlas.git;a=commit;h=ee3e9a8da38bc3e742a1f4daf6069d9cd575ceea > Add Cross Origin [CORS] headers for Atlas > -- > > Key: ATLAS-1896 > URL: https://issues.apache.org/jira/browse/ATLAS-1896 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Ruchi Solani > Attachments: 0001-ATLAS-1896.patch > > > Add Cross Origin [CORS] headers for Atlas, make it configurable from > atlas-application properties -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1944) NotificationHookConsumer throws exception while shutting down the consumer thread
[
https://issues.apache.org/jira/browse/ATLAS-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16085289#comment-16085289
]
Nixon Rodrigues commented on ATLAS-1944:
+1 for the patch, changes LGTM
> NotificationHookConsumer throws exception while shutting down the consumer
> thread
> -
>
> Key: ATLAS-1944
> URL: https://issues.apache.org/jira/browse/ATLAS-1944
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Ayub Pathan
>Assignee: Ashutosh Mestry
>Priority: Critical
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1944.patch
>
>
> NotificationHookConsumer throws below exception while shutting down the
> consumer thread, this issue is possibly after this commit.
> https://github.com/apache/incubator-atlas/commit/0e7f8ea4603c858cc295259bbd1a22314b732f62
> CC [~nixonrodrigues]
> {noformat}
> 2017-07-12 01:26:09,743 WARN - [pool-1-thread-1:] ~ Error stopping service
> org.apache.atlas.notification.NotificationHookConsumer (Services:69)
> java.util.ConcurrentModificationException: KafkaConsumer is not safe for
> multi-threaded access
> at
> org.apache.kafka.clients.consumer.KafkaConsumer.acquire(KafkaConsumer.java:1557)
> at
> org.apache.kafka.clients.consumer.KafkaConsumer.close(KafkaConsumer.java:1467)
> at
> org.apache.atlas.kafka.AtlasKafkaConsumer.close(AtlasKafkaConsumer.java:88)
> at
> org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.stop(NotificationHookConsumer.java:384)
> at
> org.apache.atlas.notification.NotificationHookConsumer.stopConsumerThreads(NotificationHookConsumer.java:172)
> at
> org.apache.atlas.notification.NotificationHookConsumer.stop(NotificationHookConsumer.java:155)
> at org.apache.atlas.service.Services.stop(Services.java:67)
> 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.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(InitDestroyAnnotationBeanPostProcessor.java:366)
> at
> org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeDestroyMethods(InitDestroyAnnotationBeanPostProcessor.java:325)
> at
> org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeDestruction(InitDestroyAnnotationBeanPostProcessor.java:154)
> at
> org.springframework.beans.factory.support.DisposableBeanAdapter.destroy(DisposableBeanAdapter.java:253)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroyBean(DefaultSingletonBeanRegistry.java:578)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingleton(DefaultSingletonBeanRegistry.java:554)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.destroySingleton(DefaultListableBeanFactory.java:961)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingletons(DefaultSingletonBeanRegistry.java:523)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.destroySingletons(DefaultListableBeanFactory.java:968)
> at
> org.springframework.context.support.AbstractApplicationContext.destroyBeans(AbstractApplicationContext.java:1033)
> at
> org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:1009)
> at
> org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:961)
> at
> org.springframework.web.context.ContextLoader.closeWebApplicationContext(ContextLoader.java:583)
> at
> org.springframework.web.context.ContextLoaderListener.contextDestroyed(ContextLoaderListener.java:116)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextDestroyed(ContextHandler.java:808)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextDestroyed(ServletContextHandler.java:457)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStop(ContextHandler.java:842)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.doStop(ServletContextHandler.java:215)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStop(WebAppContext.java:529)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.
[jira] [Updated] (ATLAS-1908) Updating old Kafka consumer api properties to reflect change in new KafkaConsumer configs for Atlas.
[ https://issues.apache.org/jira/browse/ATLAS-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-1908: --- Attachment: ATLAS-1908-1.patch > Updating old Kafka consumer api properties to reflect change in new > KafkaConsumer configs for Atlas. > > > Key: ATLAS-1908 > URL: https://issues.apache.org/jira/browse/ATLAS-1908 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues > Attachments: ATLAS-1908-1.patch, ATLAS-1908.patch > > > In ATLAS-1766, the old Kafka consumer api was updated with new Kafka consumer > api. > Due to this update, there were changes in configs. > > New property: > atlas.kafka.session.timeout.ms=3 > > Renamed property: > atlas.kafka.auto.commit.enable=false to atlas.kafka.enable.auto.commit=false > > New default value: > atlas.kafka.auto.offset.reset=smallest to > atlas.kafka.auto.offset.reset=earliest > Need to handle old configs, so that Kafka consumer starts gracefully even if > new configs are not added explicitly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1940) Atlas server fails to initialize types on startup from graph store due to duplicate type registered.
[
https://issues.apache.org/jira/browse/ATLAS-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087453#comment-16087453
]
Nixon Rodrigues commented on ATLAS-1940:
[~ayubkhan], Not sure whether this issue similiar to ATLAS-1472, but fix for
this issue is to remove the duplicate types in this patch.
> Atlas server fails to initialize types on startup from graph store due to
> duplicate type registered.
>
>
> Key: ATLAS-1940
> URL: https://issues.apache.org/jira/browse/ATLAS-1940
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 0.8-incubating
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Blocker
> Fix For: 0.9-incubating, 0.8.1-incubating
>
>
> Types are not getting restored from typesRegistry during Atlas startup due
> duplicate type issue.
> Below is exception trace.
> {code}
> 2017-07-07 13:35:23,088 INFO - [main:] ~ Restoring type CLASS.Process.null
> (GraphBackedTypeStore:267)
> 2017-07-07 13:35:23,099 INFO - [main:] ~ Restoring type
> CLASS.falcon_process.null (GraphBackedTypeStore:267)
> 2017-07-07 13:35:23,122 INFO - [main:] ~ Restoring type TRAIT.Metric.Metric
> Trait (GraphBackedTypeStore:267)
> 2017-07-07 13:35:23,132 INFO - [main:] ~ Restoring type
> CLASS.Referenceable.null (GraphBackedTypeStore:267)
> 2017-07-07 13:35:23,140 INFO - [main:] ~ Restoring type
> CLASS.hive_storagedesc.null (GraphBackedTypeStore:267)
> 2017-07-07 13:35:23,203 INFO - [main:] ~ Restoring type
> CLASS.hive_table.null (GraphBackedTypeStore:267)
> 2017-07-07 13:35:23,276 INFO - [main:] ~ Restoring type
> CLASS.falcon_feed_creation.null (GraphBackedTypeStore:267)
> 2017-07-07 13:35:23,288 INFO - [main:] ~ Restoring type
> CLASS.sqoop_dbdatastore.null (GraphBackedTypeStore:267)
> 2017-07-07 13:35:23,399 INFO - [main:] ~ Number of types got from transient
> type system: 49 (DefaultMetadataService:168)
> 2017-07-07 13:35:23,406 INFO - [main:] ~ Restored type system from the store
> (DefaultMetadataService:161)
> 2017-07-07 13:35:23,407 INFO - [main:] ~ Global indexes already exist for
> graph (GraphBackedSearchIndexer:141)
> 2017-07-07 13:35:23,753 WARN - [main:] ~ Invalid constraint ownedRef for
> attribute hive_storagedesc.serdeInfo (AtlasTypeDefGraphStore:689)
> 2017-07-07 13:35:23,754 WARN - [main:] ~ Invalid constraint ownedRef for
> attribute hive_table.aliases (AtlasTypeDefGraphStore:689)
> 2017-07-07 13:35:23,759 ERROR - [main:] ~ failed to initialize types from
> graph store (AtlasTypeDefGraphStoreV1:77)
> org.apache.atlas.exception.AtlasBaseException: Given type TaxonomyTerm
> already exists
> at
> org.apache.atlas.type.AtlasTypeRegistry$AtlasTransientTypeRegistry.addTypeWithNoRefResolve(AtlasTypeRegistry.java:573)
> at
> org.apache.atlas.type.AtlasTypeRegistry$AtlasTransientTypeRegistry.addTypesWithNoRefResolve(AtlasTypeRegistry.java:611)
> at
> org.apache.atlas.type.AtlasTypeRegistry$AtlasTransientTypeRegistry.addTypes(AtlasTypeRegistry.java:407)
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.init(AtlasTypeDefGraphStore.java:105)
> at
> org.apache.atlas.repository.store.graph.v1.AtlasTypeDefGraphStoreV1.init(AtlasTypeDefGraphStoreV1.java:107)
> at
> org.apache.atlas.repository.store.graph.v1.AtlasTypeDefGraphStoreV1.(AtlasTypeDefGraphStoreV1.java:75)
> at
> org.apache.atlas.repository.store.graph.v1.AtlasTypeDefGraphStoreV1$$EnhancerByGuice$$21ccc5be.()
> at
> org.apache.atlas.repository.store.graph.v1.AtlasTypeDefGraphStoreV1$$EnhancerByGuice$$21ccc5be$$FastClassByGuice$$a11fb32d.newInstance()
> at
> com.google.inject.internal.ProxyFactory$ProxyConstructor.newInstance(ProxyFactory.java:265)
> at
> com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:111)
> at
> com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:90)
> at
> com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:268)
> at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:56)
> at
> com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
> at
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1092)
> at
> com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
> at
> com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:194)
> at
> com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
> at
> com.google.inject.internal.Int
[jira] [Updated] (ATLAS-1940) Atlas server fails to initialize types on startup from graph store due to duplicate type registered.
[
https://issues.apache.org/jira/browse/ATLAS-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues updated ATLAS-1940:
---
Attachment: ATLAS-1940.patch
> Atlas server fails to initialize types on startup from graph store due to
> duplicate type registered.
>
>
> Key: ATLAS-1940
> URL: https://issues.apache.org/jira/browse/ATLAS-1940
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 0.8-incubating
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Blocker
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1940.patch
>
>
> Types are not getting restored from typesRegistry during Atlas startup due
> duplicate type issue.
> Below is exception trace.
> {code}
> 2017-07-07 13:35:23,088 INFO - [main:] ~ Restoring type CLASS.Process.null
> (GraphBackedTypeStore:267)
> 2017-07-07 13:35:23,099 INFO - [main:] ~ Restoring type
> CLASS.falcon_process.null (GraphBackedTypeStore:267)
> 2017-07-07 13:35:23,122 INFO - [main:] ~ Restoring type TRAIT.Metric.Metric
> Trait (GraphBackedTypeStore:267)
> 2017-07-07 13:35:23,132 INFO - [main:] ~ Restoring type
> CLASS.Referenceable.null (GraphBackedTypeStore:267)
> 2017-07-07 13:35:23,140 INFO - [main:] ~ Restoring type
> CLASS.hive_storagedesc.null (GraphBackedTypeStore:267)
> 2017-07-07 13:35:23,203 INFO - [main:] ~ Restoring type
> CLASS.hive_table.null (GraphBackedTypeStore:267)
> 2017-07-07 13:35:23,276 INFO - [main:] ~ Restoring type
> CLASS.falcon_feed_creation.null (GraphBackedTypeStore:267)
> 2017-07-07 13:35:23,288 INFO - [main:] ~ Restoring type
> CLASS.sqoop_dbdatastore.null (GraphBackedTypeStore:267)
> 2017-07-07 13:35:23,399 INFO - [main:] ~ Number of types got from transient
> type system: 49 (DefaultMetadataService:168)
> 2017-07-07 13:35:23,406 INFO - [main:] ~ Restored type system from the store
> (DefaultMetadataService:161)
> 2017-07-07 13:35:23,407 INFO - [main:] ~ Global indexes already exist for
> graph (GraphBackedSearchIndexer:141)
> 2017-07-07 13:35:23,753 WARN - [main:] ~ Invalid constraint ownedRef for
> attribute hive_storagedesc.serdeInfo (AtlasTypeDefGraphStore:689)
> 2017-07-07 13:35:23,754 WARN - [main:] ~ Invalid constraint ownedRef for
> attribute hive_table.aliases (AtlasTypeDefGraphStore:689)
> 2017-07-07 13:35:23,759 ERROR - [main:] ~ failed to initialize types from
> graph store (AtlasTypeDefGraphStoreV1:77)
> org.apache.atlas.exception.AtlasBaseException: Given type TaxonomyTerm
> already exists
> at
> org.apache.atlas.type.AtlasTypeRegistry$AtlasTransientTypeRegistry.addTypeWithNoRefResolve(AtlasTypeRegistry.java:573)
> at
> org.apache.atlas.type.AtlasTypeRegistry$AtlasTransientTypeRegistry.addTypesWithNoRefResolve(AtlasTypeRegistry.java:611)
> at
> org.apache.atlas.type.AtlasTypeRegistry$AtlasTransientTypeRegistry.addTypes(AtlasTypeRegistry.java:407)
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.init(AtlasTypeDefGraphStore.java:105)
> at
> org.apache.atlas.repository.store.graph.v1.AtlasTypeDefGraphStoreV1.init(AtlasTypeDefGraphStoreV1.java:107)
> at
> org.apache.atlas.repository.store.graph.v1.AtlasTypeDefGraphStoreV1.(AtlasTypeDefGraphStoreV1.java:75)
> at
> org.apache.atlas.repository.store.graph.v1.AtlasTypeDefGraphStoreV1$$EnhancerByGuice$$21ccc5be.()
> at
> org.apache.atlas.repository.store.graph.v1.AtlasTypeDefGraphStoreV1$$EnhancerByGuice$$21ccc5be$$FastClassByGuice$$a11fb32d.newInstance()
> at
> com.google.inject.internal.ProxyFactory$ProxyConstructor.newInstance(ProxyFactory.java:265)
> at
> com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:111)
> at
> com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:90)
> at
> com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:268)
> at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:56)
> at
> com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
> at
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1092)
> at
> com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
> at
> com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:194)
> at
> com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
> at
> com.google.inject.internal.InternalInjectorCreator$1.call(InternalInjectorCreator.java:205)
> at
> com.google.inject.internal.InternalInjectorC
[jira] [Updated] (ATLAS-1908) Updating old Kafka consumer api properties to reflect change in new KafkaConsumer configs for Atlas.
[ https://issues.apache.org/jira/browse/ATLAS-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-1908: --- Attachment: ATLAS-1908.2.patch > Updating old Kafka consumer api properties to reflect change in new > KafkaConsumer configs for Atlas. > > > Key: ATLAS-1908 > URL: https://issues.apache.org/jira/browse/ATLAS-1908 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues > Attachments: ATLAS-1908-1.patch, ATLAS-1908.2.patch, ATLAS-1908.patch > > > In ATLAS-1766, the old Kafka consumer api was updated with new Kafka consumer > api. > Due to this update, there were changes in configs. > > New property: > atlas.kafka.session.timeout.ms=3 > > Renamed property: > atlas.kafka.auto.commit.enable=false to atlas.kafka.enable.auto.commit=false > > New default value: > atlas.kafka.auto.offset.reset=smallest to > atlas.kafka.auto.offset.reset=earliest > Need to handle old configs, so that Kafka consumer starts gracefully even if > new configs are not added explicitly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1908) Updating old Kafka consumer api properties to reflect change in new KafkaConsumer configs for Atlas.
[ https://issues.apache.org/jira/browse/ATLAS-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088707#comment-16088707 ] Nixon Rodrigues commented on ATLAS-1908: Added NotificationConsumer with new interface to avoid Ranger compile time issue. Please review [^ATLAS-1908.2.patch] > Updating old Kafka consumer api properties to reflect change in new > KafkaConsumer configs for Atlas. > > > Key: ATLAS-1908 > URL: https://issues.apache.org/jira/browse/ATLAS-1908 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues > Attachments: ATLAS-1908-1.patch, ATLAS-1908.2.patch, ATLAS-1908.patch > > > In ATLAS-1766, the old Kafka consumer api was updated with new Kafka consumer > api. > Due to this update, there were changes in configs. > > New property: > atlas.kafka.session.timeout.ms=3 > > Renamed property: > atlas.kafka.auto.commit.enable=false to atlas.kafka.enable.auto.commit=false > > New default value: > atlas.kafka.auto.offset.reset=smallest to > atlas.kafka.auto.offset.reset=earliest > Need to handle old configs, so that Kafka consumer starts gracefully even if > new configs are not added explicitly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ATLAS-1985) Regression : Basic/DSL Query fired on PASSIVE server redirects to ACTIVE server , adding an extra "amp;" to the parameters
[
https://issues.apache.org/jira/browse/ATLAS-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues reassigned ATLAS-1985:
--
Assignee: Nixon Rodrigues
> Regression : Basic/DSL Query fired on PASSIVE server redirects to ACTIVE
> server , adding an extra "amp;" to the parameters
> --
>
> Key: ATLAS-1985
> URL: https://issues.apache.org/jira/browse/ATLAS-1985
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Sharmadha Sainath
>Assignee: Nixon Rodrigues
>Priority: Critical
>
> 1. Fired the query
> {code}
> http://PassiveHost:21000/api/atlas/discovery/search/fulltext?limit=100&query=hive_table
> {code}
> The query failed with
> {code}
> {
> error: "dslQuery cannot be null cannot be null"
> }
> {code}
> The redirected URL is :
> {code}
> http://activehost:21000/api/atlas/discovery/search/fulltext?limit=100&query=hive_table
> {code}
> Redirection adds an extra "amp;" and ignores rest of the query after the
> first parameter.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-1985) Regression : Basic/DSL Query fired on PASSIVE server redirects to ACTIVE server , adding an extra "amp;" to the parameters
[
https://issues.apache.org/jira/browse/ATLAS-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues updated ATLAS-1985:
---
Attachment: ATLAS-1985.patch
> Regression : Basic/DSL Query fired on PASSIVE server redirects to ACTIVE
> server , adding an extra "amp;" to the parameters
> --
>
> Key: ATLAS-1985
> URL: https://issues.apache.org/jira/browse/ATLAS-1985
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Sharmadha Sainath
>Assignee: Nixon Rodrigues
>Priority: Critical
> Attachments: ATLAS-1985.patch
>
>
> 1. Fired the query
> {code}
> http://PassiveHost:21000/api/atlas/discovery/search/fulltext?limit=100&query=hive_table
> {code}
> The query failed with
> {code}
> {
> error: "dslQuery cannot be null cannot be null"
> }
> {code}
> The redirected URL is :
> {code}
> http://activehost:21000/api/atlas/discovery/search/fulltext?limit=100&query=hive_table
> {code}
> Redirection adds an extra "amp;" and ignores rest of the query after the
> first parameter.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ATLAS-1985) Regression : Basic/DSL Query fired on PASSIVE server redirects to ACTIVE server , adding an extra "amp;" to the parameters
[
https://issues.apache.org/jira/browse/ATLAS-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099898#comment-16099898
]
Nixon Rodrigues commented on ATLAS-1985:
This patch [^ATLAS-1985.patch] provide fix for url-encoding in Activeserver
Filter where URL was encoded wrongly with HtmlQuoting.quoteHtmlChars method
which is primarily meant for htmltext encoding.
Instead of using HtmlQuoting.quoteHtmlChars method used URLEncode.encode method
to encode the URL.
> Regression : Basic/DSL Query fired on PASSIVE server redirects to ACTIVE
> server , adding an extra "amp;" to the parameters
> --
>
> Key: ATLAS-1985
> URL: https://issues.apache.org/jira/browse/ATLAS-1985
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Sharmadha Sainath
>Assignee: Nixon Rodrigues
>Priority: Critical
> Attachments: ATLAS-1985.patch
>
>
> 1. Fired the query
> {code}
> http://PassiveHost:21000/api/atlas/discovery/search/fulltext?limit=100&query=hive_table
> {code}
> The query failed with
> {code}
> {
> error: "dslQuery cannot be null cannot be null"
> }
> {code}
> The redirected URL is :
> {code}
> http://activehost:21000/api/atlas/discovery/search/fulltext?limit=100&query=hive_table
> {code}
> Redirection adds an extra "amp;" and ignores rest of the query after the
> first parameter.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-1951) Regression: Any REST API request without user credentials results in 302 redirect to login.jsp. Actually, the correct response should be 401.
[
https://issues.apache.org/jira/browse/ATLAS-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues updated ATLAS-1951:
---
Attachment: ATLAS-1951.patch
[~apoorvnaik],
Can you please review and test this fix.
>From my end i have tested it on browser / chrome rest client and curl client.
> Regression: Any REST API request without user credentials results in 302
> redirect to login.jsp. Actually, the correct response should be 401.
> -
>
> Key: ATLAS-1951
> URL: https://issues.apache.org/jira/browse/ATLAS-1951
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Ayub Pathan
>Priority: Critical
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1951.patch
>
>
> Regression: Any REST API request to atlas without user credentials results in
> 302 redirect( login.jsp), but the actual response code should be 401
> unauthorized.
> This issue could have been introduced as part of new spring changes.
> For example:
> {noformat}
> curl -v -X GET "http://ctr-e133-1493418528701-181199-01-02.hwx.site:21000";
> * Rebuilt URL to:
> http://ctr-e133-1493418528701-181199-01-02.hwx.site:21000/
> * Trying 172.27.56.2...
> * Connected to ctr-e133-1493418528701-181199-01-02.hwx.site (172.27.56.2)
> port 21000 (#0)
> > GET / HTTP/1.1
> > Host: ctr-e133-1493418528701-181199-01-02.hwx.site:21000
> > User-Agent: curl/7.43.0
> > Accept: */*
> >
> < HTTP/1.1 302 Found
> < Date: Fri, 14 Jul 2017 11:16:42 GMT
> < Set-Cookie: ATLASSESSIONID=1i0rxnm66dd3h17xyhvstk0vck;Path=/;HttpOnly
> < Expires: Thu, 01 Jan 1970 00:00:00 GMT
> < X-Frame-Options: DENY
> < Location:
> http://ctr-e133-1493418528701-181199-01-02.hwx.site:21000/login.jsp
> < Content-Length: 0
> < Server: Jetty(9.2.12.v20150709)
> <
> * Connection #0 to host ctr-e133-1493418528701-181199-01-02.hwx.site left
> intact
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (ATLAS-1951) Regression: Any REST API request without user credentials results in 302 redirect to login.jsp. Actually, the correct response should be 401.
[
https://issues.apache.org/jira/browse/ATLAS-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues reassigned ATLAS-1951:
--
Assignee: Nixon Rodrigues
> Regression: Any REST API request without user credentials results in 302
> redirect to login.jsp. Actually, the correct response should be 401.
> -
>
> Key: ATLAS-1951
> URL: https://issues.apache.org/jira/browse/ATLAS-1951
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Ayub Pathan
>Assignee: Nixon Rodrigues
>Priority: Critical
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1951.patch
>
>
> Regression: Any REST API request to atlas without user credentials results in
> 302 redirect( login.jsp), but the actual response code should be 401
> unauthorized.
> This issue could have been introduced as part of new spring changes.
> For example:
> {noformat}
> curl -v -X GET "http://ctr-e133-1493418528701-181199-01-02.hwx.site:21000";
> * Rebuilt URL to:
> http://ctr-e133-1493418528701-181199-01-02.hwx.site:21000/
> * Trying 172.27.56.2...
> * Connected to ctr-e133-1493418528701-181199-01-02.hwx.site (172.27.56.2)
> port 21000 (#0)
> > GET / HTTP/1.1
> > Host: ctr-e133-1493418528701-181199-01-02.hwx.site:21000
> > User-Agent: curl/7.43.0
> > Accept: */*
> >
> < HTTP/1.1 302 Found
> < Date: Fri, 14 Jul 2017 11:16:42 GMT
> < Set-Cookie: ATLASSESSIONID=1i0rxnm66dd3h17xyhvstk0vck;Path=/;HttpOnly
> < Expires: Thu, 01 Jan 1970 00:00:00 GMT
> < X-Frame-Options: DENY
> < Location:
> http://ctr-e133-1493418528701-181199-01-02.hwx.site:21000/login.jsp
> < Content-Length: 0
> < Server: Jetty(9.2.12.v20150709)
> <
> * Connection #0 to host ctr-e133-1493418528701-181199-01-02.hwx.site left
> intact
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-2673) DSL query fired on PASSIVE server redirects to ACTIVE server with wrong encoding
Nixon Rodrigues created ATLAS-2673:
--
Summary: DSL query fired on PASSIVE server redirects to ACTIVE
server with wrong encoding
Key: ATLAS-2673
URL: https://issues.apache.org/jira/browse/ATLAS-2673
Project: Atlas
Issue Type: Bug
Components: atlas-webui
Affects Versions: 1.0.0-alpha
Reporter: Nixon Rodrigues
Assignee: Nixon Rodrigues
Fix For: 1.0.0
DSL query :
{code}
/api/atlas/v2/search/dsl?typeName=hive_table&query=name="weather2"
{code}
fired on PASSIVE server redirects to ACTIVE server as
{code}
/api/atlas/v2/search/dsl?limit=25&offset=0&query=name=%2522weather2%2522&typeName=hive_table
{code}
fails with
{code}
{
errorCode: "ATLAS-400-00-059",
errorMessage: "Invalid DSL query: `hive_table` name=%22weather2%22 | Reason:
DSL Semantic Error - weather2 type not found, DSL Semantic Error - weather2
type not found, DSL Semantic Error - 22 type not found, DSL Semantic Error - 22
type not found. Please refer to Atlas DSL grammar for more information"
}
{code}
Attaching the complete exception stack trace from ACTIVE server logs .
Issue not seen with Basic search.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2673) DSL query fired on PASSIVE server redirects to ACTIVE server with wrong encoding
[
https://issues.apache.org/jira/browse/ATLAS-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues updated ATLAS-2673:
---
Attachment: ATLAS-2673.patch
> DSL query fired on PASSIVE server redirects to ACTIVE server with wrong
> encoding
>
>
> Key: ATLAS-2673
> URL: https://issues.apache.org/jira/browse/ATLAS-2673
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 1.0.0-alpha
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2673.patch
>
>
> DSL query :
> {code}
> /api/atlas/v2/search/dsl?typeName=hive_table&query=name="weather2"
> {code}
> fired on PASSIVE server redirects to ACTIVE server as
> {code}
> /api/atlas/v2/search/dsl?limit=25&offset=0&query=name=%2522weather2%2522&typeName=hive_table
> {code}
> fails with
> {code}
> {
> errorCode: "ATLAS-400-00-059",
> errorMessage: "Invalid DSL query: `hive_table` name=%22weather2%22 | Reason:
> DSL Semantic Error - weather2 type not found, DSL Semantic Error - weather2
> type not found, DSL Semantic Error - 22 type not found, DSL Semantic Error -
> 22 type not found. Please refer to Atlas DSL grammar for more information"
> }
> {code}
> Attaching the complete exception stack trace from ACTIVE server logs .
> Issue not seen with Basic search.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2463) Documentation for Atlas authorization at instance level
[ https://issues.apache.org/jira/browse/ATLAS-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2463: --- Attachment: (was: ATLAS-2463.patch) > Documentation for Atlas authorization at instance level > --- > > Key: ATLAS-2463 > URL: https://issues.apache.org/jira/browse/ATLAS-2463 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2463) Documentation for Atlas authorization at instance level
[ https://issues.apache.org/jira/browse/ATLAS-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2463: --- Attachment: ATLAS-2463.2.patch > Documentation for Atlas authorization at instance level > --- > > Key: ATLAS-2463 > URL: https://issues.apache.org/jira/browse/ATLAS-2463 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-2463.2.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2718) Documentation for Atlas Ranger authorization.
Nixon Rodrigues created ATLAS-2718: -- Summary: Documentation for Atlas Ranger authorization. Key: ATLAS-2718 URL: https://issues.apache.org/jira/browse/ATLAS-2718 Project: Atlas Issue Type: New Feature Reporter: Nixon Rodrigues Assignee: Nixon Rodrigues Fix For: 1.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2718) Documentation for Atlas Ranger authorization.
[ https://issues.apache.org/jira/browse/ATLAS-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2718: --- Attachment: ATLAS-2718.patch > Documentation for Atlas Ranger authorization. > - > > Key: ATLAS-2718 > URL: https://issues.apache.org/jira/browse/ATLAS-2718 > Project: Atlas > Issue Type: New Feature >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-2718.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2718) Documentation for Atlas Ranger authorization.
[ https://issues.apache.org/jira/browse/ATLAS-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2718: --- Attachment: (was: ATLAS-2718.patch) > Documentation for Atlas Ranger authorization. > - > > Key: ATLAS-2718 > URL: https://issues.apache.org/jira/browse/ATLAS-2718 > Project: Atlas > Issue Type: New Feature >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2718) Documentation for Atlas Ranger authorization.
[ https://issues.apache.org/jira/browse/ATLAS-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2718: --- Attachment: ATLAS-2718.patch > Documentation for Atlas Ranger authorization. > - > > Key: ATLAS-2718 > URL: https://issues.apache.org/jira/browse/ATLAS-2718 > Project: Atlas > Issue Type: New Feature >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-2718.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2730) Invalid timezone / start time / end time is accepted by classification API
Nixon Rodrigues created ATLAS-2730: -- Summary: Invalid timezone / start time / end time is accepted by classification API Key: ATLAS-2730 URL: https://issues.apache.org/jira/browse/ATLAS-2730 Project: Atlas Issue Type: New Feature Affects Versions: 1.0.0 Reporter: Nixon Rodrigues Assignee: Nixon Rodrigues Fix For: trunk -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2730) Invalid timezone / start time / end time is accepted by classification API
[ https://issues.apache.org/jira/browse/ATLAS-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2730: --- Issue Type: Bug (was: New Feature) > Invalid timezone / start time / end time is accepted by classification API > -- > > Key: ATLAS-2730 > URL: https://issues.apache.org/jira/browse/ATLAS-2730 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2731) UI : attributes on table's detailsPage buffers forever due no access on that entity type
Nixon Rodrigues created ATLAS-2731: -- Summary: UI : attributes on table's detailsPage buffers forever due no access on that entity type Key: ATLAS-2731 URL: https://issues.apache.org/jira/browse/ATLAS-2731 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 1.0.0 Reporter: Nixon Rodrigues Fix For: trunk 1. Create a Resource based policy for Atlas in Ranger with Entity-id as qualifiedName of a table, with all permissions , entity-type= * ,entity-classification=* for "admin" user. (Attached the screenshot of the policy) 2. Log into Atlas as admin and access table's detailsPage. 3. db attribute value keeps loading forever and there is an "admin is not authorized to perform read entity: guid=" error notification. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2730) Invalid timezone / start time / end time is accepted by classification API
[ https://issues.apache.org/jira/browse/ATLAS-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2730: --- Attachment: ATLAS-2730.patch > Invalid timezone / start time / end time is accepted by classification API > -- > > Key: ATLAS-2730 > URL: https://issues.apache.org/jira/browse/ATLAS-2730 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: trunk > > Attachments: ATLAS-2730.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2730) Invalid timezone / start time / end time is accepted by classification API
[ https://issues.apache.org/jira/browse/ATLAS-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2730: --- Attachment: ATLAS-2730-2.patch > Invalid timezone / start time / end time is accepted by classification API > -- > > Key: ATLAS-2730 > URL: https://issues.apache.org/jira/browse/ATLAS-2730 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: trunk > > Attachments: ATLAS-2730-2.patch, ATLAS-2730.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2730) Invalid timezone / start time / end time is accepted by classification API
[ https://issues.apache.org/jira/browse/ATLAS-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2730: --- Attachment: ATLAS-2730-3.patch > Invalid timezone / start time / end time is accepted by classification API > -- > > Key: ATLAS-2730 > URL: https://issues.apache.org/jira/browse/ATLAS-2730 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: trunk > > Attachments: ATLAS-2730-2.patch, ATLAS-2730-3.patch, ATLAS-2730.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2742) Timezone is set to blank when not set while saving classification to entities
Nixon Rodrigues created ATLAS-2742: -- Summary: Timezone is set to blank when not set while saving classification to entities Key: ATLAS-2742 URL: https://issues.apache.org/jira/browse/ATLAS-2742 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 1.0.0 Reporter: Nixon Rodrigues Fix For: 1.1.0, 2.0.0 Attachments: Timezone-set-blank.png Steps:- Apply classification to an entity. Check Add validity period option. Select only start datetime and end datetime without selecting timezone. Go to entity page on classification and edit classification and check timezone value set. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2742) UI : Timezone is set to blank when not set while saving classification to entities
[ https://issues.apache.org/jira/browse/ATLAS-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2742: --- Summary: UI : Timezone is set to blank when not set while saving classification to entities (was: Timezone is set to blank when not set while saving classification to entities) > UI : Timezone is set to blank when not set while saving classification to > entities > -- > > Key: ATLAS-2742 > URL: https://issues.apache.org/jira/browse/ATLAS-2742 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Nixon Rodrigues >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: Timezone-set-blank.png > > > Steps:- > Apply classification to an entity. > Check Add validity period option. > Select only start datetime and end datetime without selecting timezone. > Go to entity page on classification and edit classification and check > timezone value set. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2742) UI : Timezone is set to blank when not set while saving classification to entities
[ https://issues.apache.org/jira/browse/ATLAS-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16504238#comment-16504238 ] Nixon Rodrigues commented on ATLAS-2742: Thanks [~abhib4] for the patch +1 for the patch. LGTM. > UI : Timezone is set to blank when not set while saving classification to > entities > -- > > Key: ATLAS-2742 > URL: https://issues.apache.org/jira/browse/ATLAS-2742 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Nixon Rodrigues >Assignee: Abhishek Kadam >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2742.patch, Timezone-set-blank.png > > > Steps:- > Apply classification to an entity. > Check Add validity period option. > Select only start datetime and end datetime without selecting timezone. > Go to entity page on classification and edit classification and check > timezone value set. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2743) Create UI renders Name and QualifiedName attribute textfield twice for Avrotype.
Nixon Rodrigues created ATLAS-2743: -- Summary: Create UI renders Name and QualifiedName attribute textfield twice for Avrotype. Key: ATLAS-2743 URL: https://issues.apache.org/jira/browse/ATLAS-2743 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0 Reporter: Nixon Rodrigues Fix For: 1.1.0, 2.0.0 Attachments: Avro-Type.png !Avro-Type.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2743) Create Entity UI renders Name and QualifiedName attribute textfield twice for Avrotype.
[ https://issues.apache.org/jira/browse/ATLAS-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2743: --- Summary: Create Entity UI renders Name and QualifiedName attribute textfield twice for Avrotype. (was: Create UI renders Name and QualifiedName attribute textfield twice for Avrotype.) > Create Entity UI renders Name and QualifiedName attribute textfield twice for > Avrotype. > --- > > Key: ATLAS-2743 > URL: https://issues.apache.org/jira/browse/ATLAS-2743 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Nixon Rodrigues >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: Avro-Type.png > > > !Avro-Type.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2744) Update Atlas website with Downloads page to include Release notes
Nixon Rodrigues created ATLAS-2744: -- Summary: Update Atlas website with Downloads page to include Release notes Key: ATLAS-2744 URL: https://issues.apache.org/jira/browse/ATLAS-2744 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0 Reporter: Nixon Rodrigues Fix For: 1.1.0 * I think it will be useful to rename 'Releases' menu as 'Downloads' and link it to Downloads page. And this page will be updated to include Release notes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2744) Update Atlas website with Downloads page to include Release notes
[ https://issues.apache.org/jira/browse/ATLAS-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2744: --- Description: * I think it will be useful to rename 'Releases' menu as 'Downloads' and link it to Downloads page. And this page will be updated to include Release notes. * Update all URLs to use https - which will result in red-rose for all links. was: * I think it will be useful to rename 'Releases' menu as 'Downloads' and link it to Downloads page. And this page will be updated to include Release notes. > Update Atlas website with Downloads page to include Release notes > -- > > Key: ATLAS-2744 > URL: https://issues.apache.org/jira/browse/ATLAS-2744 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Nixon Rodrigues >Priority: Major > Fix For: 1.1.0 > > > * I think it will be useful to rename 'Releases' menu as 'Downloads' and > link it to Downloads page. And this page will be updated to include Release > notes. > * Update all URLs to use https - which will result in red-rose for all links. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2743) Create Entity UI renders Name and QualifiedName attribute textfield twice for Avrotype.
[ https://issues.apache.org/jira/browse/ATLAS-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2743: --- Attachment: ATLAS-2743.patch > Create Entity UI renders Name and QualifiedName attribute textfield twice for > Avrotype. > --- > > Key: ATLAS-2743 > URL: https://issues.apache.org/jira/browse/ATLAS-2743 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Nixon Rodrigues >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2743.patch, Avro-Type.png > > > !Avro-Type.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2743) Create Entity UI renders Name and QualifiedName attribute textfield twice for Avrotype.
[
https://issues.apache.org/jira/browse/ATLAS-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16504553#comment-16504553
]
Nixon Rodrigues commented on ATLAS-2743:
Removing 'Asset' as superType from Avro type from model JSON resolves the
duplicate rendering issue.
Below is diff from patch
ATLAS-2743.patch^!/jira/images/icons/link_attachment_7.gif|width=7,height=7! ^
for review
{noformat}
diff --git a/addons/models/1000-Hadoop/1065-avro_model.json
b/addons/models/1000-Hadoop/1065-avro_model.json
index 3eaddfb38..17fba8bb1 100644
--- a/addons/models/1000-Hadoop/1065-avro_model.json
+++ b/addons/models/1000-Hadoop/1065-avro_model.json
@@ -7,7 +7,7 @@
"name": "avro_type",
"description": "Atlas Type representing Abstract Avro Type",
"superTypes": [
-"DataSet", "Asset"
+"DataSet"
],
{noformat}
> Create Entity UI renders Name and QualifiedName attribute textfield twice for
> Avrotype.
> ---
>
> Key: ATLAS-2743
> URL: https://issues.apache.org/jira/browse/ATLAS-2743
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Nixon Rodrigues
>Priority: Major
> Fix For: 1.1.0, 2.0.0
>
> Attachments: ATLAS-2743.patch, Avro-Type.png
>
>
> !Avro-Type.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-2743) Create Entity UI renders Name and QualifiedName attribute textfield twice for Avrotype.
[
https://issues.apache.org/jira/browse/ATLAS-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16504553#comment-16504553
]
Nixon Rodrigues edited comment on ATLAS-2743 at 6/7/18 11:40 AM:
-
Removing 'Asset' as superType from Avro type from model JSON resolves the
duplicate rendering issue.
Below is diff from patch ATLAS-2743.patch for review
{noformat}
diff --git a/addons/models/1000-Hadoop/1065-avro_model.json
b/addons/models/1000-Hadoop/1065-avro_model.json
index 3eaddfb38..17fba8bb1 100644
--- a/addons/models/1000-Hadoop/1065-avro_model.json
+++ b/addons/models/1000-Hadoop/1065-avro_model.json
@@ -7,7 +7,7 @@
"name": "avro_type",
"description": "Atlas Type representing Abstract Avro Type",
"superTypes": [
-"DataSet", "Asset"
+"DataSet"
],
{noformat}
was (Author: nixonrodrigues):
Removing 'Asset' as superType from Avro type from model JSON resolves the
duplicate rendering issue.
Below is diff from patch
ATLAS-2743.patch^!/jira/images/icons/link_attachment_7.gif|width=7,height=7! ^
for review
{noformat}
diff --git a/addons/models/1000-Hadoop/1065-avro_model.json
b/addons/models/1000-Hadoop/1065-avro_model.json
index 3eaddfb38..17fba8bb1 100644
--- a/addons/models/1000-Hadoop/1065-avro_model.json
+++ b/addons/models/1000-Hadoop/1065-avro_model.json
@@ -7,7 +7,7 @@
"name": "avro_type",
"description": "Atlas Type representing Abstract Avro Type",
"superTypes": [
-"DataSet", "Asset"
+"DataSet"
],
{noformat}
> Create Entity UI renders Name and QualifiedName attribute textfield twice for
> Avrotype.
> ---
>
> Key: ATLAS-2743
> URL: https://issues.apache.org/jira/browse/ATLAS-2743
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Nixon Rodrigues
>Priority: Major
> Fix For: 1.1.0, 2.0.0
>
> Attachments: ATLAS-2743.patch, Avro-Type.png
>
>
> !Avro-Type.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (ATLAS-2743) Create Entity UI renders Name and QualifiedName attribute textfield twice for Avrotype.
[ https://issues.apache.org/jira/browse/ATLAS-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues reassigned ATLAS-2743: -- Assignee: Nixon Rodrigues > Create Entity UI renders Name and QualifiedName attribute textfield twice for > Avrotype. > --- > > Key: ATLAS-2743 > URL: https://issues.apache.org/jira/browse/ATLAS-2743 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2743.patch, Avro-Type.png > > > !Avro-Type.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (ATLAS-2730) Invalid timezone / start time / end time is accepted by classification API
[ https://issues.apache.org/jira/browse/ATLAS-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues reopened ATLAS-2730: Currently, timezone which is not null and not valid was treated as default system timezone. So reopening the issue. > Invalid timezone / start time / end time is accepted by classification API > -- > > Key: ATLAS-2730 > URL: https://issues.apache.org/jira/browse/ATLAS-2730 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2730-2.patch, ATLAS-2730-3.patch, ATLAS-2730.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2730) Invalid timezone / start time / end time is accepted by classification API
[ https://issues.apache.org/jira/browse/ATLAS-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16505903#comment-16505903 ] Nixon Rodrigues commented on ATLAS-2730: I have added patch to add validation on timezone. Review Request. https://reviews.apache.org/r/67499/ > Invalid timezone / start time / end time is accepted by classification API > -- > > Key: ATLAS-2730 > URL: https://issues.apache.org/jira/browse/ATLAS-2730 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2730-2.patch, ATLAS-2730-3.patch, ATLAS-2730.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2762) UI: In Relationship UI Tab , when a relationshipdef between entities is DELETED , the entity is also set to DELETED
[ https://issues.apache.org/jira/browse/ATLAS-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2762: --- Attachment: ATLAS-2762.patch > UI: In Relationship UI Tab , when a relationshipdef between entities is > DELETED , the entity is also set to DELETED > --- > > Key: ATLAS-2762 > URL: https://issues.apache.org/jira/browse/ATLAS-2762 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Abhishek Kadam >Assignee: Abhishek Kadam >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2762.patch > > > Created a hive table and dropped the table. > In the Relationship Tab of table's detailsPage, on clicking the "db" vertex, > it is shown as DELETED but the db is actually ACTIVE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2762) UI: In Relationship UI Tab , when a relationshipdef between entities is DELETED , the entity is also set to DELETED
[ https://issues.apache.org/jira/browse/ATLAS-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16519016#comment-16519016 ] Nixon Rodrigues commented on ATLAS-2762: Review request includes serverside change to provide entityStatus to fix this issue. https://reviews.apache.org/r/67682/ > UI: In Relationship UI Tab , when a relationshipdef between entities is > DELETED , the entity is also set to DELETED > --- > > Key: ATLAS-2762 > URL: https://issues.apache.org/jira/browse/ATLAS-2762 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Abhishek Kadam >Assignee: Abhishek Kadam >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2762.patch > > > Created a hive table and dropped the table. > In the Relationship Tab of table's detailsPage, on clicking the "db" vertex, > it is shown as DELETED but the db is actually ACTIVE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2762) UI: In Relationship UI Tab , when a relationshipdef between entities is DELETED , the entity is also set to DELETED
[ https://issues.apache.org/jira/browse/ATLAS-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2762: --- Attachment: ATLAS-2762-2.patch > UI: In Relationship UI Tab , when a relationshipdef between entities is > DELETED , the entity is also set to DELETED > --- > > Key: ATLAS-2762 > URL: https://issues.apache.org/jira/browse/ATLAS-2762 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Abhishek Kadam >Assignee: Abhishek Kadam >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2762-2.patch, ATLAS-2762.patch > > > Created a hive table and dropped the table. > In the Relationship Tab of table's detailsPage, on clicking the "db" vertex, > it is shown as DELETED but the db is actually ACTIVE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2762) UI: In Relationship UI Tab , when a relationshipdef between entities is DELETED , the entity is also set to DELETED
[ https://issues.apache.org/jira/browse/ATLAS-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16519356#comment-16519356 ] Nixon Rodrigues commented on ATLAS-2762: [~abhib4] thanks for the UI fix, it looks good ,i have updated the your patch on review https://reviews.apache.org/r/67682/ > UI: In Relationship UI Tab , when a relationshipdef between entities is > DELETED , the entity is also set to DELETED > --- > > Key: ATLAS-2762 > URL: https://issues.apache.org/jira/browse/ATLAS-2762 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Abhishek Kadam >Assignee: Abhishek Kadam >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2762-2.patch, ATLAS-2762-3.patch, ATLAS-2762.patch > > > Created a hive table and dropped the table. > In the Relationship Tab of table's detailsPage, on clicking the "db" vertex, > it is shown as DELETED but the db is actually ACTIVE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-2762) UI: In Relationship UI Tab , when a relationshipdef between entities is DELETED , the entity is also set to DELETED
[ https://issues.apache.org/jira/browse/ATLAS-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16519356#comment-16519356 ] Nixon Rodrigues edited comment on ATLAS-2762 at 6/21/18 1:19 PM: - [~abhib4] thanks for the UI fix, it looks good, I have updated the patch on review [https://reviews.apache.org/r/67682/] was (Author: nixonrodrigues): [~abhib4] thanks for the UI fix, it looks good ,i have updated the your patch on review https://reviews.apache.org/r/67682/ > UI: In Relationship UI Tab , when a relationshipdef between entities is > DELETED , the entity is also set to DELETED > --- > > Key: ATLAS-2762 > URL: https://issues.apache.org/jira/browse/ATLAS-2762 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Abhishek Kadam >Assignee: Abhishek Kadam >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2762-2.patch, ATLAS-2762-3.patch, ATLAS-2762.patch > > > Created a hive table and dropped the table. > In the Relationship Tab of table's detailsPage, on clicking the "db" vertex, > it is shown as DELETED but the db is actually ACTIVE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2764) Time Bound classification : Few timezones throw "Invalid timezone exception"
Nixon Rodrigues created ATLAS-2764: -- Summary: Time Bound classification : Few timezones throw "Invalid timezone exception" Key: ATLAS-2764 URL: https://issues.apache.org/jira/browse/ATLAS-2764 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0 Reporter: Nixon Rodrigues Assignee: Abhishek Kadam Fix For: 1.1.0, 2.0.0 Folllowing timezones from UI are missing in java timezone and throw INVALID timezone exception America/Punta_Arenas Asia/Atyrau Asia/Famagusta Asia/Yangon Europe/Saratov ROC It would be good to load timezone TimeZone.getAvailableIDs() on UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2764) Time Bound classification : Few timezones throw "Invalid timezone exception"
[ https://issues.apache.org/jira/browse/ATLAS-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-2764. Resolution: Fixed [~abhib4] Thanks for the patch. Committed patch on following branches. * master - http://git-wip-us.apache.org/repos/asf/atlas/commit/f37f3de7 * branch-1.0 - http://git-wip-us.apache.org/repos/asf/atlas/commit/be4c0c03 > Time Bound classification : Few timezones throw "Invalid timezone exception" > > > Key: ATLAS-2764 > URL: https://issues.apache.org/jira/browse/ATLAS-2764 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Nixon Rodrigues >Assignee: Abhishek Kadam >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2764.patch > > > Folllowing timezones from UI are missing in java timezone and throw INVALID > timezone exception > America/Punta_Arenas > Asia/Atyrau > Asia/Famagusta > Asia/Yangon > Europe/Saratov > ROC > It would be good to load timezone TimeZone.getAvailableIDs() on UI. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2766) UI - Turn off hyperlinks for entities with no entity-read access in search result display
Nixon Rodrigues created ATLAS-2766: -- Summary: UI - Turn off hyperlinks for entities with no entity-read access in search result display Key: ATLAS-2766 URL: https://issues.apache.org/jira/browse/ATLAS-2766 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 1.0.0 Reporter: Nixon Rodrigues Assignee: Abhishek Kadam Fix For: 1.1.0, 2.0.0 When ATLAS-2765 will be in place, the search result will have “-1” as guid for entities on which the user doesn’t have ‘entity-read’ permission. UI will not hyperlink ‘Name’ column for such result entries. This will prevent the user from clicking the link to go to entity details page and not able to tag term/classification. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2436) Docker to build Atlas
[ https://issues.apache.org/jira/browse/ATLAS-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-2436. Resolution: Duplicate [~bosco] , docker file for Atlas is handled in ATLAS-2012 https://github.com/apache/atlas/commit/c6155816c51ebdbce8bef0069a8bccca1418c7d0 There is also Atlas image on docker hub submitted in the community bolkedebruin/atlas-for-docker > Docker to build Atlas > - > > Key: ATLAS-2436 > URL: https://issues.apache.org/jira/browse/ATLAS-2436 > Project: Atlas > Issue Type: Improvement >Reporter: Don Bosco Durai >Priority: Trivial > Original Estimate: 48h > Remaining Estimate: 48h > > It would be good have Docker image to build Apache Atlas. This can contain > the required Java version and any dependencies. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2768) UI - If a classification is deleted then to it appears on the UI until the page is not reloaded
[ https://issues.apache.org/jira/browse/ATLAS-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-2768. Resolution: Fixed Fix Version/s: 1.1.0 > UI - If a classification is deleted then to it appears on the UI until the > page is not reloaded > --- > > Key: ATLAS-2768 > URL: https://issues.apache.org/jira/browse/ATLAS-2768 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Tejas Rawool >Assignee: Abhishek Kadam >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: SS12.png > > > Steps to reproduce:- > Go to Classification tab and create an classification > > Expected:- > Success message would appear and classification would be deleted > > Error:- > Success message appears but the classification is not deleted from UI -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2768) UI - If a classification is deleted then to it appears on the UI until the page is not reloaded
[ https://issues.apache.org/jira/browse/ATLAS-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16552562#comment-16552562 ] Nixon Rodrigues commented on ATLAS-2768: Fix is already committed in ATLAS-2767. > UI - If a classification is deleted then to it appears on the UI until the > page is not reloaded > --- > > Key: ATLAS-2768 > URL: https://issues.apache.org/jira/browse/ATLAS-2768 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Tejas Rawool >Assignee: Abhishek Kadam >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: SS12.png > > > Steps to reproduce:- > Go to Classification tab and create an classification > > Expected:- > Success message would appear and classification would be deleted > > Error:- > Success message appears but the classification is not deleted from UI -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1165) The "\" character in tag name is causing issue in loading tag attribute page with entities.
[ https://issues.apache.org/jira/browse/ATLAS-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-1165. Resolution: Cannot Reproduce > The "\" character in tag name is causing issue in loading tag attribute page > with entities. > --- > > Key: ATLAS-1165 > URL: https://issues.apache.org/jira/browse/ATLAS-1165 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Priority: Major > > When tag is created with \ in it , the "\" character in tag name is causing > issue in loading tag attribute page with entities. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2125) Atlas UI doesn't show any fields in Schema tab for Hive table entity type
[
https://issues.apache.org/jira/browse/ATLAS-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues resolved ATLAS-2125.
Resolution: Cannot Reproduce
> Atlas UI doesn't show any fields in Schema tab for Hive table entity type
> --
>
> Key: ATLAS-2125
> URL: https://issues.apache.org/jira/browse/ATLAS-2125
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ramesh Mani
>Priority: Major
> Attachments: hive-table-schema.png
>
>
> Atlas UI doesn't show any fields in Schema tab for Hive table entity type. It
> is empty
> {code:java}
> create table if not exists employee_partitioned
> (
> name string,
> work_place ARRAY,
> sex_age STRUCT,
> skills_score MAP,
> depart_title MAP>
> )
> comment 'This is an partitioned table'
> partitioned by (Year int, Month int)
> row format delimited
> fields terminated by '|'
> collection items terminated by ','
> map keys terminated by ':'
> stored as textfile;
> load data local inpath '/tmp/emp.txt' overwrite into table
> employee_partitioned partition ( Year=2016, Month=12)
> emp.txt data
> Sam|Fremont,CA|Male,35|DB:822|Product:Developer,Test:Lead
> Will|Vancouver,BC|Male,26|perl:822|Product:Lead,Test:Lead
> Lucy|New York, NY|Female,27|Sales:89,HR:96|Sales:Lead
> Sandra|Raleigh, NC|Female,29|Python:89,HR:96|COE:Architect,Test:Lead
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ATLAS-2795) Non-resolvable parent POM for org.apache.atlas:atlas-migration-exporter while Compiling on branch0.8
Nixon Rodrigues created ATLAS-2795:
--
Summary: Non-resolvable parent POM for
org.apache.atlas:atlas-migration-exporter while Compiling on branch0.8
Key: ATLAS-2795
URL: https://issues.apache.org/jira/browse/ATLAS-2795
Project: Atlas
Issue Type: Bug
Affects Versions: 0.8.2
Reporter: Nixon Rodrigues
{noformat}
/atlas/softwares/atlas_master$ mvn clean [INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for
org.apache.atlas:atlas-migration-exporter:[unknown-version]: Could not find
artifact org.apache.atlas:apache-atlas:pom:0.8.3-SNAPSHOT and
'parent.relativePath' points at wrong local POM @ line 24, column 13 @ [ERROR]
The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project
org.apache.atlas:atlas-migration-exporter:[unknown-version]
(/home/kapildeo/atlas/softwares/atlas_master/tools/atlas-migration-exporter/pom.xml)
has 1 error [ERROR] Non-resolvable parent POM for
org.apache.atlas:atlas-migration-exporter:[unknown-version]: Could not find
artifact org.apache.atlas:apache-atlas:pom:0.8.3-SNAPSHOT and
'parent.relativePath' points at wrong local POM @ line 24, column 13 -> [Help
2] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug
logging. [ERROR] [ERROR] For more information about the errors and po
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ATLAS-2793) Enhance AtlasClient to use UGI's authentication method to initialize URL connection handler
[ https://issues.apache.org/jira/browse/ATLAS-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562068#comment-16562068 ] Nixon Rodrigues commented on ATLAS-2793: +1 for the patch. > Enhance AtlasClient to use UGI's authentication method to initialize URL > connection handler > > > Key: ATLAS-2793 > URL: https://issues.apache.org/jira/browse/ATLAS-2793 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 0.8.2, 1.0.0 >Reporter: Sarath Subramanian >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 0.8.3, 1.1.0, 2.0.0 > > Attachments: ATLAS-2793.patch > > > Currently the atlas client checks if kerberos authentication is enabled using > a property - *atlas.authentication.method.kerberos=true* > The client needs to be updated to inspect the UGI's authentication method > (SIMPLE or KERBEROS) and initialize the right URL Connection Handler if the > above property is not set. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2795) Non-resolvable parent POM for org.apache.atlas:atlas-migration-exporter while Compiling on branch0.8
[
https://issues.apache.org/jira/browse/ATLAS-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues updated ATLAS-2795:
---
Description:
{noformat}
/atlas/softwares/atlas_master$ mvn clean [INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for
org.apache.atlas:atlas-migration-exporter:[unknown-version]: Could not find
artifact org.apache.atlas:apache-atlas:pom:0.8.3-SNAPSHOT and
'parent.relativePath' points at wrong local POM @ line 24, column 13 @ [ERROR]
The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project
org.apache.atlas:atlas-migration-exporter:[unknown-version]
(/home/kapildeo/atlas/softwares/atlas_master/tools/atlas-migration-exporter/pom.xml)
has 1 error [ERROR] Non-resolvable parent POM for
org.apache.atlas:atlas-migration-exporter:[unknown-version]: Could not find
artifact org.apache.atlas:apache-atlas:pom:0.8.3-SNAPSHOT and
'parent.relativePath' points at wrong local POM @ line 24, column 13 -> [Help
2] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug
logging. [ERROR] [ERROR] For more information about the errors and po
{noformat}
This issue is happening with Maven version 3.5.3
was:
{noformat}
/atlas/softwares/atlas_master$ mvn clean [INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for
org.apache.atlas:atlas-migration-exporter:[unknown-version]: Could not find
artifact org.apache.atlas:apache-atlas:pom:0.8.3-SNAPSHOT and
'parent.relativePath' points at wrong local POM @ line 24, column 13 @ [ERROR]
The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project
org.apache.atlas:atlas-migration-exporter:[unknown-version]
(/home/kapildeo/atlas/softwares/atlas_master/tools/atlas-migration-exporter/pom.xml)
has 1 error [ERROR] Non-resolvable parent POM for
org.apache.atlas:atlas-migration-exporter:[unknown-version]: Could not find
artifact org.apache.atlas:apache-atlas:pom:0.8.3-SNAPSHOT and
'parent.relativePath' points at wrong local POM @ line 24, column 13 -> [Help
2] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug
logging. [ERROR] [ERROR] For more information about the errors and po
{noformat}
> Non-resolvable parent POM for org.apache.atlas:atlas-migration-exporter while
> Compiling on branch0.8
>
>
> Key: ATLAS-2795
> URL: https://issues.apache.org/jira/browse/ATLAS-2795
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8.2
>Reporter: Nixon Rodrigues
>Assignee: Vishal Suvagia
>Priority: Major
>
> {noformat}
> /atlas/softwares/atlas_master$ mvn clean [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-resolvable parent POM for
> org.apache.atlas:atlas-migration-exporter:[unknown-version]: Could not find
> artifact org.apache.atlas:apache-atlas:pom:0.8.3-SNAPSHOT and
> 'parent.relativePath' points at wrong local POM @ line 24, column 13 @
> [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The
> project org.apache.atlas:atlas-migration-exporter:[unknown-version]
> (/home/kapildeo/atlas/softwares/atlas_master/tools/atlas-migration-exporter/pom.xml)
> has 1 error [ERROR] Non-resolvable parent POM for
> org.apache.atlas:atlas-migration-exporter:[unknown-version]: Could not find
> artifact org.apache.atlas:apache-atlas:pom:0.8.3-SNAPSHOT and
> 'parent.relativePath' points at wrong local POM @ line 24, column 13 -> [Help
> 2] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven
> with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full
> debug logging. [ERROR] [ERROR] For more information about the errors and po
> {noformat}
>
> This issue is happening with Maven version 3.5.3
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ATLAS-2809) Updates to SimpleAuthorizer for Relationship endpoints
Nixon Rodrigues created ATLAS-2809:
--
Summary: Updates to SimpleAuthorizer for Relationship endpoints
Key: ATLAS-2809
URL: https://issues.apache.org/jira/browse/ATLAS-2809
Project: Atlas
Issue Type: Bug
Affects Versions: 1.0.0
Reporter: Nixon Rodrigues
Assignee: Nixon Rodrigues
Fix For: 1.1.0
Following permission needs to be updated in atlas-simple-authz.json
{noformat}
"relationshipPermissions": [
{
"privileges": [ ".*" ],
"relationshipTypes": [ ".*" ],
"endOneEntityType": [ ".*" ],
"endOneEntityId": [ ".*" ],
"endOneEntityClassification": [ ".*" ],
"endTwoEntityType": [ ".*" ],
"endTwoEntityId": [ ".*" ],
"endTwoEntityClassification": [ ".*" ]
}
]
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2809) Updates to SimpleAuthorizer for Relationship endpoints
[
https://issues.apache.org/jira/browse/ATLAS-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues updated ATLAS-2809:
---
Attachment: ATLAS-2809.patch
> Updates to SimpleAuthorizer for Relationship endpoints
> --
>
> Key: ATLAS-2809
> URL: https://issues.apache.org/jira/browse/ATLAS-2809
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 1.1.0
>
> Attachments: ATLAS-2809.patch
>
>
> Following permission needs to be updated in atlas-simple-authz.json
> {noformat}
> "relationshipPermissions": [
> {
> "privileges": [ ".*" ],
> "relationshipTypes": [ ".*" ],
> "endOneEntityType": [ ".*" ],
> "endOneEntityId": [ ".*" ],
> "endOneEntityClassification": [ ".*" ],
> "endTwoEntityType": [ ".*" ],
> "endTwoEntityId": [ ".*" ],
> "endTwoEntityClassification": [ ".*" ]
> }
> ]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (ATLAS-2809) Updates to SimpleAuthorizer for Relationship endpoints
[
https://issues.apache.org/jira/browse/ATLAS-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues reopened ATLAS-2809:
Found issues in quick-start.py due to typo's in relationPermission in
atlas-simple-policy.json.
> Updates to SimpleAuthorizer for Relationship endpoints
> --
>
> Key: ATLAS-2809
> URL: https://issues.apache.org/jira/browse/ATLAS-2809
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 1.1.0, 2.0.0
>
> Attachments: ATLAS-2809-2.patch, ATLAS-2809.patch
>
>
> Following permission needs to be updated in atlas-simple-authz.json
> {noformat}
> "relationshipPermissions": [
> {
> "privileges": [ ".*" ],
> "relationshipTypes": [ ".*" ],
> "endOneEntityType": [ ".*" ],
> "endOneEntityId": [ ".*" ],
> "endOneEntityClassification": [ ".*" ],
> "endTwoEntityType": [ ".*" ],
> "endTwoEntityId": [ ".*" ],
> "endTwoEntityClassification": [ ".*" ]
> }
> ]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2809) Updates to SimpleAuthorizer for Relationship endpoints
[
https://issues.apache.org/jira/browse/ATLAS-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues updated ATLAS-2809:
---
Attachment: ATLAS-2809-2.patch
> Updates to SimpleAuthorizer for Relationship endpoints
> --
>
> Key: ATLAS-2809
> URL: https://issues.apache.org/jira/browse/ATLAS-2809
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 1.1.0, 2.0.0
>
> Attachments: ATLAS-2809-2.patch, ATLAS-2809.patch
>
>
> Following permission needs to be updated in atlas-simple-authz.json
> {noformat}
> "relationshipPermissions": [
> {
> "privileges": [ ".*" ],
> "relationshipTypes": [ ".*" ],
> "endOneEntityType": [ ".*" ],
> "endOneEntityId": [ ".*" ],
> "endOneEntityClassification": [ ".*" ],
> "endTwoEntityType": [ ".*" ],
> "endTwoEntityId": [ ".*" ],
> "endTwoEntityClassification": [ ".*" ]
> }
> ]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-2809) Updates to SimpleAuthorizer for Relationship endpoints
[
https://issues.apache.org/jira/browse/ATLAS-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16573097#comment-16573097
]
Nixon Rodrigues edited comment on ATLAS-2809 at 8/8/18 12:03 PM:
-
Found issues in quick-start.py due to typo's in relationPermission in
atlas-simple-policy.json.
so reopening this JIRA.
was (Author: nixonrodrigues):
Found issues in quick-start.py due to typo's in relationPermission in
atlas-simple-policy.json.
> Updates to SimpleAuthorizer for Relationship endpoints
> --
>
> Key: ATLAS-2809
> URL: https://issues.apache.org/jira/browse/ATLAS-2809
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 1.1.0, 2.0.0
>
> Attachments: ATLAS-2809-2.patch, ATLAS-2809.patch
>
>
> Following permission needs to be updated in atlas-simple-authz.json
> {noformat}
> "relationshipPermissions": [
> {
> "privileges": [ ".*" ],
> "relationshipTypes": [ ".*" ],
> "endOneEntityType": [ ".*" ],
> "endOneEntityId": [ ".*" ],
> "endOneEntityClassification": [ ".*" ],
> "endTwoEntityType": [ ".*" ],
> "endTwoEntityId": [ ".*" ],
> "endTwoEntityClassification": [ ".*" ]
> }
> ]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ATLAS-2821) Update old atlas-simple-authz-policy.json file with relationship permission attributes
Nixon Rodrigues created ATLAS-2821: -- Summary: Update old atlas-simple-authz-policy.json file with relationship permission attributes Key: ATLAS-2821 URL: https://issues.apache.org/jira/browse/ATLAS-2821 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 1.0.0 Reporter: Nixon Rodrigues Assignee: Nixon Rodrigues Fix For: 1.1.0 This utility will update old atlas-simple-authz-policy.json policy file with relationship default permission attributes for ROLE_ADMIN and DATA_STEWARD. Usage : ./atlas_update_simple_auth_json.py -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2821) Update old atlas-simple-authz-policy.json file with relationship permission attributes
[ https://issues.apache.org/jira/browse/ATLAS-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2821: --- Attachment: ATLAS-2821.patch > Update old atlas-simple-authz-policy.json file with relationship permission > attributes > -- > > Key: ATLAS-2821 > URL: https://issues.apache.org/jira/browse/ATLAS-2821 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 1.1.0 > > Attachments: ATLAS-2821.patch > > > This utility will update old atlas-simple-authz-policy.json policy file with > relationship default permission attributes for ROLE_ADMIN and DATA_STEWARD. > > Usage : ./atlas_update_simple_auth_json.py -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2824) Atlas to configure & support Trusted Knox Proxy
Nixon Rodrigues created ATLAS-2824: -- Summary: Atlas to configure & support Trusted Knox Proxy Key: ATLAS-2824 URL: https://issues.apache.org/jira/browse/ATLAS-2824 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Nixon Rodrigues Assignee: Nixon Rodrigues -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2824) Atlas to configure & support Trusted Knox Proxy
[ https://issues.apache.org/jira/browse/ATLAS-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2824: --- Attachment: ATLAS-2824.patch > Atlas to configure & support Trusted Knox Proxy > > > Key: ATLAS-2824 > URL: https://issues.apache.org/jira/browse/ATLAS-2824 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 1.1.0 > > Attachments: ATLAS-2824.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2832) Replace Titan with JanusGraph in the architecture diagram
[ https://issues.apache.org/jira/browse/ATLAS-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2832: --- Fix Version/s: 1.1.0 > Replace Titan with JanusGraph in the architecture diagram > - > > Key: ATLAS-2832 > URL: https://issues.apache.org/jira/browse/ATLAS-2832 > Project: Atlas > Issue Type: Task >Reporter: Jerry He >Assignee: Abhishek Kadam >Priority: Minor > Fix For: 1.1.0 > > Attachments: ATLAS-2832.patch > > > In Atlas 1.0, the graph backend is JanusGraph. We should replace Titan with > JanusGraph in this diagram https://atlas.apache.org/Architecture.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2832) Replace Titan with JanusGraph in the architecture diagram
[ https://issues.apache.org/jira/browse/ATLAS-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-2832: --- Fix Version/s: 2.0.0 > Replace Titan with JanusGraph in the architecture diagram > - > > Key: ATLAS-2832 > URL: https://issues.apache.org/jira/browse/ATLAS-2832 > Project: Atlas > Issue Type: Task >Reporter: Jerry He >Assignee: Abhishek Kadam >Priority: Minor > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2832.patch > > > In Atlas 1.0, the graph backend is JanusGraph. We should replace Titan with > JanusGraph in this diagram https://atlas.apache.org/Architecture.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-2832) Replace Titan with JanusGraph in the architecture diagram
[ https://issues.apache.org/jira/browse/ATLAS-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588877#comment-16588877 ] Nixon Rodrigues edited comment on ATLAS-2832 at 8/22/18 1:56 PM: - Thanks [~jinghe] for filing this issue. Image with change for JanusGraph is committed on branch-1.0 and master [https://git1-us-west.apache.org/repos/asf?p=atlas.git;a=blob;f=docs/src/site/resources/images/twiki/architecture.png;hb=165d6cfc] was (Author: nixonrodrigues): Image with change for JanusGraph is committed on branch-1.0 and master https://git1-us-west.apache.org/repos/asf?p=atlas.git;a=blob;f=docs/src/site/resources/images/twiki/architecture.png;hb=165d6cfc > Replace Titan with JanusGraph in the architecture diagram > - > > Key: ATLAS-2832 > URL: https://issues.apache.org/jira/browse/ATLAS-2832 > Project: Atlas > Issue Type: Task >Reporter: Jerry He >Assignee: Abhishek Kadam >Priority: Minor > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2832.patch > > > In Atlas 1.0, the graph backend is JanusGraph. We should replace Titan with > JanusGraph in this diagram https://atlas.apache.org/Architecture.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2820) UI : Add replication audits tab for AtlasCluster entity to show Export & Import audit
[ https://issues.apache.org/jira/browse/ATLAS-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590015#comment-16590015 ] Nixon Rodrigues commented on ATLAS-2820: +1 for the patch. > UI : Add replication audits tab for AtlasCluster entity to show Export & > Import audit > - > > Key: ATLAS-2820 > URL: https://issues.apache.org/jira/browse/ATLAS-2820 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.8.3 >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 0.8.3 > > Attachments: ATLAS-2820-1.patch, ATLAS-2820-WIP.patch, > ATLAS-2820.patch > > > Add Replication Audits tab in detail page if entity typename is > "*AtlasCluster*". > inside tab show list of audits in table structure using this new API. > /api/atlas/admin/expimp/audit?sourceClusterName= -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2828) DOCUMENTATION - architecture diagram still shows Titan instead of Janus
[ https://issues.apache.org/jira/browse/ATLAS-2828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16591580#comment-16591580 ] Nixon Rodrigues commented on ATLAS-2828: [~toopt4] , the image in documentation will be released on the website in upcoming 1.1.0 release soon. > DOCUMENTATION - architecture diagram still shows Titan instead of Janus > --- > > Key: ATLAS-2828 > URL: https://issues.apache.org/jira/browse/ATLAS-2828 > Project: Atlas > Issue Type: Improvement >Reporter: t oo >Priority: Trivial > > Image in this link still shows 'Titan' instead of 'Janus': > https://atlas.apache.org/Architecture.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
