[jira] [Created] (ATLAS-1423) AtlasClient can't be created without atlas-application.properties file
Shwetha G S created ATLAS-1423:
--
Summary: AtlasClient can't be created without
atlas-application.properties file
Key: ATLAS-1423
URL: https://issues.apache.org/jira/browse/ATLAS-1423
Project: Atlas
Issue Type: Bug
Reporter: Shwetha G S
For an external project which requires AtlasClient, creating AtlasClient
requires atlas-application.properties file in its classpath even though no
properties are required from that file:
{noformat}
org.apache.atlas.AtlasException: Failed to load application properties
at
org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:92)
at
org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:59)
at
org.apache.atlas.utils.AuthenticationUtil.isKerberosAuthenticationEnabled(AuthenticationUtil.java:41)
at org.apache.atlas.AtlasClient.getClient(AtlasClient.java:240)
at org.apache.atlas.AtlasClient.initializeState(AtlasClient.java:206)
at org.apache.atlas.AtlasClient.(AtlasClient.java:160)
{noformat}
Even adding empty properties file fails:
{noformat}
org.apache.atlas.AtlasException: Failed to load JAAS application properties:
configuration NULL or empty!
at
org.apache.atlas.security.InMemoryJAASConfiguration.init(InMemoryJAASConfiguration.java:174)
at
org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:60)
at
org.apache.atlas.AtlasClient.getClientProperties(AtlasClient.java:342)
at org.apache.atlas.AtlasClient.initializeState(AtlasClient.java:205)
at org.apache.atlas.AtlasClient.(AtlasClient.java:160)
{noformat}
Adding a random property to properties file works
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-1384) Can you please upgrade to scala 2.11.7
[ https://issues.apache.org/jira/browse/ATLAS-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15753325#comment-15753325 ] Shwetha G S commented on ATLAS-1384: Atlas uses scala version 2.11.8: https://github.com/apache/incubator-atlas/blob/master/pom.xml#L448. Do you mean downgrade to 2.11.7? > Can you please upgrade to scala 2.11.7 > -- > > Key: ATLAS-1384 > URL: https://issues.apache.org/jira/browse/ATLAS-1384 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.7-incubating, 0.8-incubating >Reporter: John Mattucci > > Can you please upgrade to scala version 2.11.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-1383) fdsfdf
[ https://issues.apache.org/jira/browse/ATLAS-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-1383. Resolution: Invalid > fdsfdf > -- > > Key: ATLAS-1383 > URL: https://issues.apache.org/jira/browse/ATLAS-1383 > Project: Atlas > Issue Type: Bug >Reporter: paldheeru39 > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1284) Fix order by clause to be able to order on super type attributes and with alias.
[ https://issues.apache.org/jira/browse/ATLAS-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15711075#comment-15711075 ] Shwetha G S commented on ATLAS-1284: This query type can be fixed in another jira as well, please file a bug for it so that its tracked > Fix order by clause to be able to order on super type attributes and with > alias. > > > Key: ATLAS-1284 > URL: https://issues.apache.org/jira/browse/ATLAS-1284 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Neeru Gupta >Assignee: Neeru Gupta > > Noticed issues with order by to work with alias and while sorting on super > type attributes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1325) Fix Apache Build failure due to Rat check on log files
[ https://issues.apache.org/jira/browse/ATLAS-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15700992#comment-15700992 ] Shwetha G S commented on ATLAS-1325: +1 > Fix Apache Build failure due to Rat check on log files > --- > > Key: ATLAS-1325 > URL: https://issues.apache.org/jira/browse/ATLAS-1325 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Attachments: ATLAS-1325.patch > > > Build failed on Apache Nightly runs due to a log file inside project > directory. > [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.7:check > (rat-check) on project apache-atlas: Too many unapproved licenses: 1 -> [Help > 1] > Exclude log files from Rat check -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1333) Storm Hook fails to capture the topology
[ https://issues.apache.org/jira/browse/ATLAS-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15700987#comment-15700987 ] Shwetha G S commented on ATLAS-1333: +1 > Storm Hook fails to capture the topology > > > Key: ATLAS-1333 > URL: https://issues.apache.org/jira/browse/ATLAS-1333 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Fix For: 0.8-incubating > > Attachments: ATLAS-1333.patch > > > Storm hook does not capture the submitted topology. There is a conflict in > the different versions of JSON4s libraries which are pulled in. Further, > Storm IT is failing due to non registry of storm_topology type at the time of > Atlas bootstrap. > Below is the error when a topology is submit: > 4865 [main] INFO o.a.a.h.AtlasHook - Adding entity for type: storm_topology > Exception in thread "main" java.lang.NoSuchMethodError: > scala.collection.immutable.$colon$colon.hd$1()Ljava/lang/Object; > at org.json4s.MonadicJValue.$bslash(MonadicJValue.scala:18) > at > org.json4s.Extraction$ClassInstanceBuilder$$anonfun$14.apply(Extraction.scala:482) > at > org.json4s.Extraction$ClassInstanceBuilder$$anonfun$14.apply(Extraction.scala:482) > at > scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234) > at > scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234) > at > scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59) > at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:48) > at scala.collection.TraversableLike$class.map(TraversableLike.scala:234) > at scala.collection.AbstractTraversable.map(Traversable.scala:104) > at > org.json4s.Extraction$ClassInstanceBuilder.org$json4s$Extraction$ClassInstanceBuilder$$instantiate(Extraction.scala:470) > at > org.json4s.Extraction$ClassInstanceBuilder$$anonfun$result$6.apply(Extraction.scala:515) > at > org.json4s.Extraction$ClassInstanceBuilder$$anonfun$result$6.apply(Extraction.scala:512) > at > org.json4s.Extraction$.org$json4s$Extraction$$customOrElse(Extraction.scala:524) > at > org.json4s.Extraction$ClassInstanceBuilder.result(Extraction.scala:512) > at org.json4s.Extraction$.extract(Extraction.scala:351) > at > org.json4s.Extraction$ClassInstanceBuilder.org$json4s$Extraction$ClassInstanceBuilder$$mkWithTypeHint(Extraction.scala:507) > at > org.json4s.Extraction$ClassInstanceBuilder$$anonfun$result$6.apply(Extraction.scala:514) > at > org.json4s.Extraction$ClassInstanceBuilder$$anonfun$result$6.apply(Extraction.scala:512) > at > org.json4s.Extraction$.org$json4s$Extraction$$customOrElse(Extraction.scala:524) > at > org.json4s.Extraction$ClassInstanceBuilder.result(Extraction.scala:512) > at org.json4s.Extraction$.extract(Extraction.scala:351) > at org.json4s.Extraction$.extract(Extraction.scala:42) > at > org.json4s.ExtractableJsonAstNode.extract(ExtractableJsonAstNode.scala:21) > at org.json4s.native.Serialization$.read(Serialization.scala:71) > at > org.apache.atlas.typesystem.json.InstanceSerialization$.fromJsonReferenceable(InstanceSerialization.scala:371) > at > org.apache.atlas.typesystem.json.InstanceSerialization.fromJsonReferenceable(InstanceSerialization.scala) > at > org.apache.atlas.notification.hook.HookNotification$EntityCreateRequest.(HookNotification.java:152) > at org.apache.atlas.hook.AtlasHook.notifyEntities(AtlasHook.java:100) > at > org.apache.atlas.storm.hook.StormAtlasHook.notify(StormAtlasHook.java:102) > at > org.apache.atlas.storm.hook.StormAtlasHook.notify(StormAtlasHook.java:57) > at > org.apache.storm.StormSubmitter.invokeSubmitterHook(StormSubmitter.java:358) > at > org.apache.storm.StormSubmitter.submitTopologyAs(StormSubmitter.java:273) > at > org.apache.storm.StormSubmitter.submitTopology(StormSubmitter.java:384) > at > org.apache.storm.StormSubmitter.submitTopology(StormSubmitter.java:161) > at storm.starter.WordCountTopology.main(WordCountTopology.java:77) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1291) Type "hive_column_lineage" not present in hive_model.json
[ https://issues.apache.org/jira/browse/ATLAS-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15700984#comment-15700984 ] Shwetha G S commented on ATLAS-1291: +1 > Type "hive_column_lineage" not present in hive_model.json > - > > Key: ATLAS-1291 > URL: https://issues.apache.org/jira/browse/ATLAS-1291 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Attachments: ATLAS-1291.patch > > > Type "hive_column_lineage" was generated in HiveDataModelGenerator.java. > The above file has been deprecated and the types are now registered from > hive_model.json inside models directory. > This file does not contain the type definition JSON for type > "hive_column_lineage". Due to this, column level lineage hook messages are > failing to be registered with Atlas. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1296) Replace org.apache.log4j.DailyRollingFileAppender
[ https://issues.apache.org/jira/browse/ATLAS-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1296: --- Assignee: (was: Shwetha G S) > Replace org.apache.log4j.DailyRollingFileAppender > - > > Key: ATLAS-1296 > URL: https://issues.apache.org/jira/browse/ATLAS-1296 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > > From the documentation of org.apache.log4j.DailyRollingFileAppender - > https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/DailyRollingFileAppender.html: > DailyRollingFileAppender has been observed to exhibit synchronization issues > and data loss. The log4j extras companion includes alternatives which should > be considered for new deployments and which are discussed in the > documentation for org.apache.log4j.rolling.RollingFileAppender. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1116) Performance monitoring of backend methods in API requests
[ https://issues.apache.org/jira/browse/ATLAS-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1116: --- Attachment: ATLAS-1116-v3.patch Aspectj plugin disabled by default. Added instructions on how to enable instrumentation at compile time and to disable metrics at runtime when atlas is already instrumented. > Performance monitoring of backend methods in API requests > - > > Key: ATLAS-1116 > URL: https://issues.apache.org/jira/browse/ATLAS-1116 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-1116-v2.patch, ATLAS-1116-v3.patch, > ATLAS-1116.patch > > > Time taken by methods used in API calls for add/update/delete entities and > traits need to be monitored for performance -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-1299) The project org.apache.atlas:atlas-hbase-client-shaded - build error
[ https://issues.apache.org/jira/browse/ATLAS-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S reassigned ATLAS-1299: -- Assignee: Shwetha G S (was: Qiang Zhang) > The project org.apache.atlas:atlas-hbase-client-shaded - build error > > > Key: ATLAS-1299 > URL: https://issues.apache.org/jira/browse/ATLAS-1299 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating > Environment: Centos 6.7;jdk 1.7.0_95;maven 3.3.9 >Reporter: Qiang Zhang >Assignee: Shwetha G S >Priority: Critical > Labels: patch > Fix For: 0.8-incubating > > Attachments: ATLAS-1299.patch > > > Repetition of steps: > 1. Run command:git clone > https://git-wip-us.apache.org/repos/asf/incubator-atlas.git; > 2. Run command in the root path of atlas:export MAVEN_OPTS="-Xmx1536m > -XX:MaxPermSize=512m" && mvn clean package -Pdist -DskipTests. > Result: > [ERROR] The build could not read 2 projects -> [Help 1] > [ERROR] > [ERROR] The project > org.apache.atlas:atlas-hbase-client-shaded:[unknown-version] > (/home/pengjianhua/opensource/incubator-atlas/shaded/hbase-client-shaded/pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM for > org.apache.atlas:atlas-hbase-client-shaded:[unknown-version]: Could not find > artifact org.apache.atlas:apache-atlas:pom:0.8-incubating-SNAPSHOT and > 'parent.relativePath' points at wrong local POM @ line 22, column 13 -> [Help > 2] > [ERROR] > [ERROR] The project > org.apache.atlas:atlas-hbase-server-shaded:[unknown-version] > (/home/pengjianhua/opensource/incubator-atlas/shaded/hbase-server-shaded/pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM for > org.apache.atlas:atlas-hbase-server-shaded:[unknown-version]: Could not find > artifact org.apache.atlas:apache-atlas:pom:0.8-incubating-SNAPSHOT and > 'parent.relativePath' points at wrong local POM @ line 22, column 13 -> [Help > 2] > [ERROR] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-1299) The project org.apache.atlas:atlas-hbase-client-shaded - build error
[ https://issues.apache.org/jira/browse/ATLAS-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-1299. Resolution: Fixed Fix Version/s: 0.8-incubating > The project org.apache.atlas:atlas-hbase-client-shaded - build error > > > Key: ATLAS-1299 > URL: https://issues.apache.org/jira/browse/ATLAS-1299 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating > Environment: Centos 6.7;jdk 1.7.0_95;maven 3.3.9 >Reporter: Qiang Zhang >Assignee: Shwetha G S >Priority: Critical > Labels: patch > Fix For: 0.8-incubating > > Attachments: ATLAS-1299.patch > > > Repetition of steps: > 1. Run command:git clone > https://git-wip-us.apache.org/repos/asf/incubator-atlas.git; > 2. Run command in the root path of atlas:export MAVEN_OPTS="-Xmx1536m > -XX:MaxPermSize=512m" && mvn clean package -Pdist -DskipTests. > Result: > [ERROR] The build could not read 2 projects -> [Help 1] > [ERROR] > [ERROR] The project > org.apache.atlas:atlas-hbase-client-shaded:[unknown-version] > (/home/pengjianhua/opensource/incubator-atlas/shaded/hbase-client-shaded/pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM for > org.apache.atlas:atlas-hbase-client-shaded:[unknown-version]: Could not find > artifact org.apache.atlas:apache-atlas:pom:0.8-incubating-SNAPSHOT and > 'parent.relativePath' points at wrong local POM @ line 22, column 13 -> [Help > 2] > [ERROR] > [ERROR] The project > org.apache.atlas:atlas-hbase-server-shaded:[unknown-version] > (/home/pengjianhua/opensource/incubator-atlas/shaded/hbase-server-shaded/pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM for > org.apache.atlas:atlas-hbase-server-shaded:[unknown-version]: Could not find > artifact org.apache.atlas:apache-atlas:pom:0.8-incubating-SNAPSHOT and > 'parent.relativePath' points at wrong local POM @ line 22, column 13 -> [Help > 2] > [ERROR] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1299) The project org.apache.atlas:atlas-hbase-client-shaded - build error
[ https://issues.apache.org/jira/browse/ATLAS-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1299: --- Summary: The project org.apache.atlas:atlas-hbase-client-shaded - build error (was: The project org.apache.atlas:atlas-hbase-client-shaded:[unknown-version] (/xx/xx/incubator-atlas/shaded/hbase-client-shaded/pom.xml) has 1 error) > The project org.apache.atlas:atlas-hbase-client-shaded - build error > > > Key: ATLAS-1299 > URL: https://issues.apache.org/jira/browse/ATLAS-1299 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating > Environment: Centos 6.7;jdk 1.7.0_95;maven 3.3.9 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Critical > Labels: patch > Attachments: ATLAS-1299.patch > > > Repetition of steps: > 1. Run command:git clone > https://git-wip-us.apache.org/repos/asf/incubator-atlas.git; > 2. Run command in the root path of atlas:export MAVEN_OPTS="-Xmx1536m > -XX:MaxPermSize=512m" && mvn clean package -Pdist -DskipTests. > Result: > [ERROR] The build could not read 2 projects -> [Help 1] > [ERROR] > [ERROR] The project > org.apache.atlas:atlas-hbase-client-shaded:[unknown-version] > (/home/pengjianhua/opensource/incubator-atlas/shaded/hbase-client-shaded/pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM for > org.apache.atlas:atlas-hbase-client-shaded:[unknown-version]: Could not find > artifact org.apache.atlas:apache-atlas:pom:0.8-incubating-SNAPSHOT and > 'parent.relativePath' points at wrong local POM @ line 22, column 13 -> [Help > 2] > [ERROR] > [ERROR] The project > org.apache.atlas:atlas-hbase-server-shaded:[unknown-version] > (/home/pengjianhua/opensource/incubator-atlas/shaded/hbase-server-shaded/pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM for > org.apache.atlas:atlas-hbase-server-shaded:[unknown-version]: Could not find > artifact org.apache.atlas:apache-atlas:pom:0.8-incubating-SNAPSHOT and > 'parent.relativePath' points at wrong local POM @ line 22, column 13 -> [Help > 2] > [ERROR] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1299) The project org.apache.atlas:atlas-hbase-client-shaded:[unknown-version] (/xx/xx/incubator-atlas/shaded/hbase-client-shaded/pom.xml) has 1 error
[ https://issues.apache.org/jira/browse/ATLAS-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15673408#comment-15673408 ] Shwetha G S commented on ATLAS-1299: [~zhangqiang2], since its a blocker, picked it up, sorry > The project org.apache.atlas:atlas-hbase-client-shaded:[unknown-version] > (/xx/xx/incubator-atlas/shaded/hbase-client-shaded/pom.xml) has 1 error > > > Key: ATLAS-1299 > URL: https://issues.apache.org/jira/browse/ATLAS-1299 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating > Environment: Centos 6.7;jdk 1.7.0_95;maven 3.3.9 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Critical > Labels: patch > Attachments: ATLAS-1299.patch > > > Repetition of steps: > 1. Run command:git clone > https://git-wip-us.apache.org/repos/asf/incubator-atlas.git; > 2. Run command in the root path of atlas:export MAVEN_OPTS="-Xmx1536m > -XX:MaxPermSize=512m" && mvn clean package -Pdist -DskipTests. > Result: > [ERROR] The build could not read 2 projects -> [Help 1] > [ERROR] > [ERROR] The project > org.apache.atlas:atlas-hbase-client-shaded:[unknown-version] > (/home/pengjianhua/opensource/incubator-atlas/shaded/hbase-client-shaded/pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM for > org.apache.atlas:atlas-hbase-client-shaded:[unknown-version]: Could not find > artifact org.apache.atlas:apache-atlas:pom:0.8-incubating-SNAPSHOT and > 'parent.relativePath' points at wrong local POM @ line 22, column 13 -> [Help > 2] > [ERROR] > [ERROR] The project > org.apache.atlas:atlas-hbase-server-shaded:[unknown-version] > (/home/pengjianhua/opensource/incubator-atlas/shaded/hbase-server-shaded/pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM for > org.apache.atlas:atlas-hbase-server-shaded:[unknown-version]: Could not find > artifact org.apache.atlas:apache-atlas:pom:0.8-incubating-SNAPSHOT and > 'parent.relativePath' points at wrong local POM @ line 22, column 13 -> [Help > 2] > [ERROR] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1299) The project org.apache.atlas:atlas-hbase-client-shaded:[unknown-version] (/xx/xx/incubator-atlas/shaded/hbase-client-shaded/pom.xml) has 1 error
[ https://issues.apache.org/jira/browse/ATLAS-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1299: --- Attachment: ATLAS-1299.patch > The project org.apache.atlas:atlas-hbase-client-shaded:[unknown-version] > (/xx/xx/incubator-atlas/shaded/hbase-client-shaded/pom.xml) has 1 error > > > Key: ATLAS-1299 > URL: https://issues.apache.org/jira/browse/ATLAS-1299 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating > Environment: Centos 6.7;jdk 1.7.0_95;maven 3.3.9 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Critical > Labels: patch > Attachments: ATLAS-1299.patch > > > Repetition of steps: > 1. Run command:git clone > https://git-wip-us.apache.org/repos/asf/incubator-atlas.git; > 2. Run command in the root path of atlas:export MAVEN_OPTS="-Xmx1536m > -XX:MaxPermSize=512m" && mvn clean package -Pdist -DskipTests. > Result: > [ERROR] The build could not read 2 projects -> [Help 1] > [ERROR] > [ERROR] The project > org.apache.atlas:atlas-hbase-client-shaded:[unknown-version] > (/home/pengjianhua/opensource/incubator-atlas/shaded/hbase-client-shaded/pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM for > org.apache.atlas:atlas-hbase-client-shaded:[unknown-version]: Could not find > artifact org.apache.atlas:apache-atlas:pom:0.8-incubating-SNAPSHOT and > 'parent.relativePath' points at wrong local POM @ line 22, column 13 -> [Help > 2] > [ERROR] > [ERROR] The project > org.apache.atlas:atlas-hbase-server-shaded:[unknown-version] > (/home/pengjianhua/opensource/incubator-atlas/shaded/hbase-server-shaded/pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM for > org.apache.atlas:atlas-hbase-server-shaded:[unknown-version]: Could not find > artifact org.apache.atlas:apache-atlas:pom:0.8-incubating-SNAPSHOT and > 'parent.relativePath' points at wrong local POM @ line 22, column 13 -> [Help > 2] > [ERROR] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1299) The project org.apache.atlas:atlas-hbase-client-shaded:[unknown-version] (/xx/xx/incubator-atlas/shaded/hbase-client-shaded/pom.xml) has 1 error
[ https://issues.apache.org/jira/browse/ATLAS-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15672723#comment-15672723 ] Shwetha G S commented on ATLAS-1299: [~zhangqiang2], are you working on this? The issue was after my last commit, I can pick this up > The project org.apache.atlas:atlas-hbase-client-shaded:[unknown-version] > (/xx/xx/incubator-atlas/shaded/hbase-client-shaded/pom.xml) has 1 error > > > Key: ATLAS-1299 > URL: https://issues.apache.org/jira/browse/ATLAS-1299 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating > Environment: Centos 6.7;jdk 1.7.0_95;maven 3.3.9 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Critical > Labels: patch > > Repetition of steps: > 1. Run command:git clone > https://git-wip-us.apache.org/repos/asf/incubator-atlas.git; > 2. Run command in the root path of atlas:export MAVEN_OPTS="-Xmx1536m > -XX:MaxPermSize=512m" && mvn clean package -Pdist -DskipTests. > Result: > [ERROR] The build could not read 2 projects -> [Help 1] > [ERROR] > [ERROR] The project > org.apache.atlas:atlas-hbase-client-shaded:[unknown-version] > (/home/pengjianhua/opensource/incubator-atlas/shaded/hbase-client-shaded/pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM for > org.apache.atlas:atlas-hbase-client-shaded:[unknown-version]: Could not find > artifact org.apache.atlas:apache-atlas:pom:0.8-incubating-SNAPSHOT and > 'parent.relativePath' points at wrong local POM @ line 22, column 13 -> [Help > 2] > [ERROR] > [ERROR] The project > org.apache.atlas:atlas-hbase-server-shaded:[unknown-version] > (/home/pengjianhua/opensource/incubator-atlas/shaded/hbase-server-shaded/pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM for > org.apache.atlas:atlas-hbase-server-shaded:[unknown-version]: Could not find > artifact org.apache.atlas:apache-atlas:pom:0.8-incubating-SNAPSHOT and > 'parent.relativePath' points at wrong local POM @ line 22, column 13 -> [Help > 2] > [ERROR] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1296) Replace org.apache.log4j.DailyRollingFileAppender
Shwetha G S created ATLAS-1296: -- Summary: Replace org.apache.log4j.DailyRollingFileAppender Key: ATLAS-1296 URL: https://issues.apache.org/jira/browse/ATLAS-1296 Project: Atlas Issue Type: Bug Reporter: Shwetha G S Assignee: Shwetha G S >From the documentation of org.apache.log4j.DailyRollingFileAppender - >https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/DailyRollingFileAppender.html: DailyRollingFileAppender has been observed to exhibit synchronization issues and data loss. The log4j extras companion includes alternatives which should be considered for new deployments and which are discussed in the documentation for org.apache.log4j.rolling.RollingFileAppender. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-1246) Upgrade versions of dependencies
[ https://issues.apache.org/jira/browse/ATLAS-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15643747#comment-15643747 ] Shwetha G S edited comment on ATLAS-1246 at 11/16/16 7:10 AM: -- If the test in IntellijIdea fail with unable to access method com.google.common.base.Stopwatch, right click on modules titan0, shaded/hbase-client-shaded and shaded/hbase-server-shaded, goto Maven->Ignore Projects. On Atlas main module, right click, goto Maven->Reimport. The issue is because of IntellijIdea not handling shaded dependencies correctly - https://youtrack.jetbrains.com/issue/IDEA-126596 Build on command line works fine was (Author: shwethags): If the test in IntellijIdea fail with unable to access method com.google.common.base.Stopwatch, right click on modules titan0, shaded/hbase-client-shaded and shaded/hbase-server-shaded, goto Maven->Ignore Projects. On Atlas main module, right click, goto Maven->Reimport. The issue is because of IntellijIdea not handling shaded dependencies correctly Build on command line works fine > Upgrade versions of dependencies > > > Key: ATLAS-1246 > URL: https://issues.apache.org/jira/browse/ATLAS-1246 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-1246-v2.patch, ATLAS-1246-v3.patch, > ATLAS-1246-v4.patch, ATLAS-1246.patch > > > 1. Expose variables for setting zookeeper version > 2. Upgrade the versions of libraries -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1295) Build failure due to patch for ATLAS-1081
[ https://issues.apache.org/jira/browse/ATLAS-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15669364#comment-15669364 ] Shwetha G S commented on ATLAS-1295: The build has been broken since ATLAS-1272 commit. So, I didn't run the tests and missed this. Thanks Arpit for fixing it > Build failure due to patch for ATLAS-1081 > - > > Key: ATLAS-1295 > URL: https://issues.apache.org/jira/browse/ATLAS-1295 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Fix For: 0.8-incubating > > Attachments: ATLAS_1081_Fix.patch > > > A new parameter was introduced in the startup script and the same change > failed to propagate to the testmetadata.py , hence the tests are failing for > the module atlas-distro -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1246) Upgrade versions of dependencies
[ https://issues.apache.org/jira/browse/ATLAS-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1246: --- Attachment: ATLAS-1246-v4.patch > Upgrade versions of dependencies > > > Key: ATLAS-1246 > URL: https://issues.apache.org/jira/browse/ATLAS-1246 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-1246-v2.patch, ATLAS-1246-v3.patch, > ATLAS-1246-v4.patch, ATLAS-1246.patch > > > 1. Expose variables for setting zookeeper version > 2. Upgrade the versions of libraries -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1081) Atlas jetty server configuration
[ https://issues.apache.org/jira/browse/ATLAS-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15666216#comment-15666216 ] Shwetha G S commented on ATLAS-1081: If we don't have separate methods for getInt(), getLong(), the calling context has to type cast the return value and calling generic getProperty() that returns Object on underlying Configuration was causing some format exceptions > Atlas jetty server configuration > > > Key: ATLAS-1081 > URL: https://issues.apache.org/jira/browse/ATLAS-1081 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-1081-v2.patch, ATLAS-1081.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-1290) webapp: Integration test failures while trying to create hive_table without creating a reference to hive_db
[
https://issues.apache.org/jira/browse/ATLAS-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S resolved ATLAS-1290.
Resolution: Duplicate
> webapp: Integration test failures while trying to create hive_table without
> creating a reference to hive_db
> ---
>
> Key: ATLAS-1290
> URL: https://issues.apache.org/jira/browse/ATLAS-1290
> Project: Atlas
> Issue Type: Bug
>Reporter: Ayub Khan
>Assignee: Ayub Khan
>Priority: Blocker
>
> {noformat}
> Failed tests:
> EntityNotificationIT.testCreateEntity:85->BaseResourceIT.createInstance:114 »
> AtlasService
> EntityNotificationIT.testDeleteEntity:111->BaseResourceIT.createInstance:114
> » AtlasService
> NotificationHookConsumerIT.testCreateEntity:89->BaseResourceIT.waitFor:287 »
> ...
> NotificationHookConsumerIT.testDeleteByQualifiedName:164 » AtlasService
> Metada...
> NotificationHookConsumerIT.testMessageHandleFailureConsumerContinues:72->BaseResourceIT.waitFor:287
> »
> NotificationHookConsumerIT.testUpdateEntityFullUpdate:183 » AtlasService
> Metad...
> NotificationHookConsumerIT.testUpdateEntityPartial:111 » AtlasService
> Metadata...
> NotificationHookConsumerIT.testUpdatePartialUpdatingQualifiedName:136 »
> AtlasService
> DataSetLineageJerseyResourceIT.setUp:58->setupInstances:224->database:272->BaseResourceIT.createInstance:114
> » AtlasService
> EntityJerseyResourceIT.testDeleteEntitiesViaClientApi:874->BaseResourceIT.createInstance:114
> » AtlasService
> EntityJerseyResourceIT.testDeleteEntitiesViaRestApi:844->BaseResourceIT.createInstance:114
> » AtlasService
> EntityJerseyResourceIT.testDeleteEntityByUniqAttribute:903->BaseResourceIT.createInstance:114
> » AtlasService
> EntityJerseyResourceIT.testEntityDeduping:176 » AtlasService Metadata service
> ...
> EntityJerseyResourceIT.testGetEntityByAttribute:283->BaseResourceIT.createInstance:114
> » AtlasService
> EntityJerseyResourceIT.testRequestUser:138 » AtlasService Metadata service
> API...
> EntityJerseyResourceIT.testSubmitEntity:115->BaseResourceIT.createInstance:114
> » AtlasService
> EntityJerseyResourceIT.testSubmitEntityWithBadDateFormat:299 expected:
> but was:
> EntityJerseyResourceIT.testSubmitSingleEntity:156 expected:<201> but was:<400>
> Tests run: 82, Failures: 18, Errors: 0, Skipped: 27
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1292) Atlas webapp Integration Tests failing
[
https://issues.apache.org/jira/browse/ATLAS-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-1292:
---
Assignee: Ayub Khan
> Atlas webapp Integration Tests failing
> ---
>
> Key: ATLAS-1292
> URL: https://issues.apache.org/jira/browse/ATLAS-1292
> Project: Atlas
> Issue Type: Bug
>Reporter: Suma Shivaprasad
>Assignee: Ayub Khan
>Priority: Blocker
>
> {noformat}
> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.103 sec -
> in org.apache.atlas.web.resources.TypesJerseyResourceIT
> Results :
> Failed tests:
> EntityNotificationIT.testCreateEntity:85->BaseResourceIT.createInstance:114
> » AtlasService
>
> EntityNotificationIT.testDeleteEntity:111->BaseResourceIT.createInstance:114
> » AtlasService
> NotificationHookConsumerIT.testCreateEntity:89->BaseResourceIT.waitFor:287
> » ...
> NotificationHookConsumerIT.testDeleteByQualifiedName:164 » AtlasService
> Metada...
>
> NotificationHookConsumerIT.testMessageHandleFailureConsumerContinues:72->BaseResourceIT.waitFor:287
> »
> NotificationHookConsumerIT.testUpdateEntityFullUpdate:183 » AtlasService
> Metad...
> NotificationHookConsumerIT.testUpdateEntityPartial:111 » AtlasService
> Metadata...
> NotificationHookConsumerIT.testUpdatePartialUpdatingQualifiedName:136 »
> AtlasService
>
> DataSetLineageJerseyResourceIT.setUp:58->setupInstances:224->database:272->BaseResourceIT.createInstance:114
> » AtlasService
>
> EntityJerseyResourceIT.testDeleteEntitiesViaClientApi:874->BaseResourceIT.createInstance:114
> » AtlasService
>
> EntityJerseyResourceIT.testDeleteEntitiesViaRestApi:844->BaseResourceIT.createInstance:114
> » AtlasService
>
> EntityJerseyResourceIT.testDeleteEntityByUniqAttribute:903->BaseResourceIT.createInstance:114
> » AtlasService
> EntityJerseyResourceIT.testEntityDeduping:176 » AtlasService Metadata
> service ...
>
> EntityJerseyResourceIT.testGetEntityByAttribute:283->BaseResourceIT.createInstance:114
> » AtlasService
> EntityJerseyResourceIT.testRequestUser:138 » AtlasService Metadata service
> API...
>
> EntityJerseyResourceIT.testSubmitEntity:115->BaseResourceIT.createInstance:114
> » AtlasService
> EntityJerseyResourceIT.testSubmitEntityWithBadDateFormat:299
> expected: but was:
> EntityJerseyResourceIT.testSubmitSingleEntity:156 expected:<201> but
> was:<400>
>
> EntityLineageJerseyResourceIT.setUp:62->setupInstances:157->database:204->BaseResourceIT.createInstance:114
> » AtlasService
> TypedefsJerseyResourceIT.testCreate:86 » AtlasService Metadata service API
> org...
> TypedefsJerseyResourceIT.testDuplicateCreate:98 » AtlasService Metadata
> servic...
> TypedefsJerseyResourceIT.testListTypesByFilter:254 » AtlasService Metadata
> ser...
> TypedefsJerseyResourceIT.testUpdate:118 » AtlasService Metadata service API
> or...
> Tests run: 92, Failures: 23, Errors: 0, Skipped: 31
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-1116) Performance monitoring of backend methods in API requests
[
https://issues.apache.org/jira/browse/ATLAS-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15663483#comment-15663483
]
Shwetha G S commented on ATLAS-1116:
Exposes annotations @Monitored and @Loggable on methods.
@Monitored records how many times that method is called and total execution
time in that method. These metrics are aggregated at API level and are recorded
in metric.log(one log line per API call)
@Loggable logs at the beginning of the method and ending of the method with
arguments and return values
These annotations are injected using aspectj plugin at compile time, there is
no runtime overhead except for the method invocation
Example metrics collected:
entity submit - 2016-11-14 16:34:06,079 {GraphHelper.findVertex=[count=3,
totalTimeMSec=60], GraphHelper.setProperty=[count=15, totalTimeMSec=16],
GraphHelper.createVertexWithoutIdentity=[count=1, totalTimeMSec=2],
TypedInstanceToGraphMapper.createVerticesAndDiscoverInstances=[count=1,
totalTimeMSec=62],
TypedInstanceToGraphMapper.addOrUpdateAttributesAndTraits=[count=1,
totalTimeMSec=10], GraphHelper.getSingleValuedProperty=[count=33,
totalTimeMSec=3], GraphHelper.getProperty=[count=3, totalTimeMSec=0],
GraphToTypedInstanceMapper.mapVertexToInstance=[count=3, totalTimeMSec=2],
GraphToTyped
InstanceMapper.mapVertexToInstanceTraits=[count=3, totalTimeMSec=0],
GraphToTypedInstanceMapper.mapGraphToTypedInstance=[count=3, totalTimeMSec=6],
FullTextMapper.mapRecursive=[count=1, totalTimeMSec=3],
TypedInstanceToGraphMapper.mapTypedInstanceToGraph=[count=1, totalTimeMSec=81],
EntityR
esource.submit=[count=1, totalTimeMSec=892]}
search - 2016-11-14 16:34:18,817
{GraphHelper.getSingleValuedProperty=[count=544, totalTimeMSec=20],
GraphHelper.getProperty=[count=47, totalTimeMSec=0],
GraphHelper.getAdjacentEdgesByLabel=[count=18, totalTimeMSec=3],
GraphHelper.getEdgeForLabel=[count=18, totalTimeMSec=3],
GraphToTypedInstanceMapper.mapVertexToInstance=[count=70, totalTimeMSec=33],
GraphToTypedInstanceMapper.mapVertexToInstanceTraits=[count=47,
totalTimeMSec=5], GraphToTypedInstanceMapper.mapGraphToTypedInstance=[count=47,
totalTimeMSec=39], GraphHelper.getArrayElementsProperty=[count=10,
totalTimeMSec=0], MetadataDiscoveryResource.searchUsingQueryDSL=[count=1,
totalTimeMSec=249], MetadataDiscoveryResource.search=[count=1,
totalTimeMSec=249]}
> Performance monitoring of backend methods in API requests
> -
>
> Key: ATLAS-1116
> URL: https://issues.apache.org/jira/browse/ATLAS-1116
> Project: Atlas
> Issue Type: Bug
>Reporter: Vimal Sharma
>Assignee: Shwetha G S
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1116-v2.patch, ATLAS-1116.patch
>
>
> Time taken by methods used in API calls for add/update/delete entities and
> traits need to be monitored for performance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1116) Performance monitoring of backend methods in API requests
[ https://issues.apache.org/jira/browse/ATLAS-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1116: --- Attachment: ATLAS-1116-v2.patch > Performance monitoring of backend methods in API requests > - > > Key: ATLAS-1116 > URL: https://issues.apache.org/jira/browse/ATLAS-1116 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-1116-v2.patch, ATLAS-1116.patch > > > Time taken by methods used in API calls for add/update/delete entities and > traits need to be monitored for performance -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1246) Upgrade versions of dependencies
[ https://issues.apache.org/jira/browse/ATLAS-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1246: --- Attachment: ATLAS-1246-v3.patch mvn 3.3.x includes hbase and titan jars even though they are shaded and used as uber jar. So, excluding them explicitly in maven war plugin. I have verified this on the stack > Upgrade versions of dependencies > > > Key: ATLAS-1246 > URL: https://issues.apache.org/jira/browse/ATLAS-1246 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-1246-v2.patch, ATLAS-1246-v3.patch, > ATLAS-1246.patch > > > 1. Expose variables for setting zookeeper version > 2. Upgrade the versions of libraries -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1286) Visa Checkout Cordova Plugin
[ https://issues.apache.org/jira/browse/ATLAS-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15663150#comment-15663150 ] Shwetha G S commented on ATLAS-1286: Moving to Cordova project > Visa Checkout Cordova Plugin > > > Key: ATLAS-1286 > URL: https://issues.apache.org/jira/browse/ATLAS-1286 > Project: Atlas > Issue Type: Improvement >Reporter: Biranchi > > I am developing hybrid mobile app using html5 in cordova. > The Visa Checkout SDK is only available for native apps (iOS & Android). > I have tried using the sdk.js javascript library in the mobile app for visa > checkout process, but its not working. > I also found a note in the integration document which says “Note: –You must > host this page on a web server; otherwise, the lightbox and JavaScript > library may not perform as expected." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1279) Remove QueryPlan attribute from Hive Process entity
[ https://issues.apache.org/jira/browse/ATLAS-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15663125#comment-15663125 ] Shwetha G S commented on ATLAS-1279: +1 > Remove QueryPlan attribute from Hive Process entity > --- > > Key: ATLAS-1279 > URL: https://issues.apache.org/jira/browse/ATLAS-1279 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Attachments: ATLAS-1279-v2.patch, ATLAS-1279.patch > > > The attribute QueryPlan is a required attribute of a Hive Process entity. > This attribute is not used anywhere. Further due to API changes in Hive LLAP > version, there is conflict in function call to get JSON Plan of query. The > function calls in Hive 1.2 and Hive 2 have different method signature. > Since, QueryPlan is not used, it should be removed so that Atlas code is > consistent for Hive 1.x and Hive 2.x -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1081) Atlas jetty server configuration
[ https://issues.apache.org/jira/browse/ATLAS-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1081: --- Priority: Major (was: Critical) > Atlas jetty server configuration > > > Key: ATLAS-1081 > URL: https://issues.apache.org/jira/browse/ATLAS-1081 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-1081-v2.patch, ATLAS-1081.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-1284) Fix order by clause to be able to order on super type attributes and with alias.
[ https://issues.apache.org/jira/browse/ATLAS-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15656039#comment-15656039 ] Shwetha G S edited comment on ATLAS-1284 at 11/11/16 3:50 AM: -- order by using super type attribute should be working already. For example, 'hive_table orderby name', name here is in super type 'Asset'. I had created ATLAS-1007 to support order by alias, will resolve that as duplicate was (Author: shwethags): order by using super type attribute should be working already. For example, 'hive_table orderby name', name here is in super type 'Asset'. I had created ATLAS-1007 to support order by alias > Fix order by clause to be able to order on super type attributes and with > alias. > > > Key: ATLAS-1284 > URL: https://issues.apache.org/jira/browse/ATLAS-1284 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Neeru Gupta >Assignee: Neeru Gupta > > Noticed issues with order by to work with alias and while sorting on super > type attributes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-727) Enhance Atlas client to add support for offset while searching.
[ https://issues.apache.org/jira/browse/ATLAS-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-727. --- Resolution: Duplicate > Enhance Atlas client to add support for offset while searching. > --- > > Key: ATLAS-727 > URL: https://issues.apache.org/jira/browse/ATLAS-727 > Project: Atlas > Issue Type: Improvement >Reporter: Neeru Gupta >Assignee: Neeru Gupta > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1284) Fix order by clause to be able to order on super type attributes and with alias.
[ https://issues.apache.org/jira/browse/ATLAS-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15656039#comment-15656039 ] Shwetha G S commented on ATLAS-1284: order by using super type attribute should be working already. For example, 'hive_table orderby name', name here is in super type 'Asset'. I had created ATLAS-1007 to support order by alias > Fix order by clause to be able to order on super type attributes and with > alias. > > > Key: ATLAS-1284 > URL: https://issues.apache.org/jira/browse/ATLAS-1284 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Neeru Gupta >Assignee: Neeru Gupta > > Noticed issues with order by to work with alias and while sorting on super > type attributes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-693) Add titan 0.5.4 implemenation of graph database abstraction layer
[ https://issues.apache.org/jira/browse/ATLAS-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-693: -- Fix Version/s: (was: trunk) > Add titan 0.5.4 implemenation of graph database abstraction layer > - > > Key: ATLAS-693 > URL: https://issues.apache.org/jira/browse/ATLAS-693 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 0.6-incubating >Reporter: Jeffrey Hagelberg >Assignee: Jeffrey Hagelberg > Fix For: 0.8-incubating > > Attachments: rb47466.patch > > > In this task, we put in place the titan 0.5.4 implementation of the graph > database abstraction layer. As part of this effort, the existing "titan" > maven project will be merged into this new project, since it is specific to > titan 0.5.4. The maven projects in Atlas that depend on the "titan" will be > changed to depend on the new project. Direct dependencies on titan 0.5.4 > will be removed from all of the atlas projects. These projects will be > changed to depend on this new project instead. They will transitively obtain > the dependencies on titan 0.5.4 that they need. For this task, very little > of the existing Atlas java / scala code will be changed. The classes from in > the titan project will be moved verbatim into the new project. The only > other changes will be the addition of the new classes that implement the > abstraction layer interfaces. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-172) Be able to specify a description with a Trait definition
[ https://issues.apache.org/jira/browse/ATLAS-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-172: -- Fix Version/s: (was: trunk) 0.7-incubating > Be able to specify a description with a Trait definition > > > Key: ATLAS-172 > URL: https://issues.apache.org/jira/browse/ATLAS-172 > Project: Atlas > Issue Type: New Feature >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Neeru Gupta >Priority: Critical > Fix For: 0.7-incubating > > > It should be possible to be able to specify a description of a trait > definition at creation time of the that trait; not just as the time the trait > is associated with an entity. > The use case is: > A user creates multiple PII tags: > - PII-foo > - PII-bar > - PII-baz > Each tag should have an associated description with it so that the data > curator (associating the tag to the entity) will know which is the > appropriate tag to use. The name of the tag is often enough not enough > information to go on. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1081) Atlas jetty server configuration
[ https://issues.apache.org/jira/browse/ATLAS-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1081: --- Attachment: ATLAS-1081-v2.patch > Atlas jetty server configuration > > > Key: ATLAS-1081 > URL: https://issues.apache.org/jira/browse/ATLAS-1081 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S >Priority: Critical > Attachments: ATLAS-1081-v2.patch, ATLAS-1081.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-1247) Support for hive 2.x
[ https://issues.apache.org/jira/browse/ATLAS-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-1247. Resolution: Duplicate > Support for hive 2.x > > > Key: ATLAS-1247 > URL: https://issues.apache.org/jira/browse/ATLAS-1247 > Project: Atlas > Issue Type: Improvement >Reporter: Shwetha G S >Assignee: Vimal Sharma > Attachments: hive2_atlas.patch > > > Atlas hive hook works only with hive 1.x. Need support for hive 2.x -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1279) Remove QueryPlan attribute from Hive Process entity
[ https://issues.apache.org/jira/browse/ATLAS-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650674#comment-15650674 ] Shwetha G S commented on ATLAS-1279: 1. Removing required attribute queryPlan is not supported currently. So, instead of removing the attribute, set the value to 'not supported' for now. Also, file a bug to remove this attribute when attribute remove is supported. 2. HiveDataModelGenerator doesn't exist anymore, so rebase the patch 3. Update hive bridge documentation that column level lineage works only in hive 1.2.x server and atlas hive hook should also be compiled with hive 1.2.x > Remove QueryPlan attribute from Hive Process entity > --- > > Key: ATLAS-1279 > URL: https://issues.apache.org/jira/browse/ATLAS-1279 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Attachments: ATLAS-1279.patch > > > The attribute QueryPlan is a required attribute of a Hive Process entity. > This attribute is not used anywhere. Further due to API changes in Hive LLAP > version, there is conflict in function call to get JSON Plan of query. The > function calls in Hive 1.2 and Hive 2 have different method signature. > Since, QueryPlan is not used, it should be removed so that Atlas code is > consistent for Hive 1.x and Hive 2.x -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1081) Atlas jetty server configuration
[ https://issues.apache.org/jira/browse/ATLAS-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650528#comment-15650528 ] Shwetha G S commented on ATLAS-1081: https://wiki.eclipse.org/Jetty/Howto/High_Load > Atlas jetty server configuration > > > Key: ATLAS-1081 > URL: https://issues.apache.org/jira/browse/ATLAS-1081 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S >Priority: Critical > Attachments: ATLAS-1081.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-590) HBaseBasedAuditRepository.start() fails
[
https://issues.apache.org/jira/browse/ATLAS-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S resolved ATLAS-590.
---
Resolution: Not A Problem
With the latest atlas package from trunk, I don't see this error
> HBaseBasedAuditRepository.start() fails
> ---
>
> Key: ATLAS-590
> URL: https://issues.apache.org/jira/browse/ATLAS-590
> Project: Atlas
> Issue Type: Sub-task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>
> The application doesn't fail, but prints this warning. Need to investigate
> {noformat}
> 2016-03-23 11:01:45,496 WARN - [main:] ~ Failed to identify the fs of dir
> hdfs://localhost.localdomain:8020/apps/hbase/data/lib, ignored
> (DynamicClassLoader:106)
> java.io.IOException: No FileSystem for scheme: hdfs
> at
> org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:2644)
> at
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2651)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:92)
> at
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2687)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2669)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:371)
> at org.apache.hadoop.fs.Path.getFileSystem(Path.java:295)
> at
> org.apache.hadoop.hbase.util.DynamicClassLoader.(DynamicClassLoader.java:104)
> at
> org.apache.hadoop.hbase.protobuf.ProtobufUtil.(ProtobufUtil.java:241)
> at org.apache.hadoop.hbase.ClusterId.parseFrom(ClusterId.java:64)
> at
> org.apache.hadoop.hbase.zookeeper.ZKClusterId.readClusterIdZNode(ZKClusterId.java:75)
> at
> org.apache.hadoop.hbase.client.ZooKeeperRegistry.getClusterId(ZooKeeperRegistry.java:105)
> at
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.retrieveClusterId(ConnectionManager.java:879)
> at
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.(ConnectionManager.java:635)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> at
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:238)
> at
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:218)
> at
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:119)
> at
> org.apache.atlas.repository.audit.HBaseBasedAuditRepository.start(HBaseBasedAuditRepository.java:257)
> at org.apache.atlas.service.Services.start(Services.java:45)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.startServices(GuiceServletConfig.java:130)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:124)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
> at
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> at org.eclipse.jetty.server.Server.start(Server.java:387)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:93)
> at org.apache.atlas.Atlas.main(Atlas.java:107)
> 2016-03-23 11:01:45,555 INFO - [main:] ~ Checking if table
[jira] [Updated] (ATLAS-1276) webapp test failures
[
https://issues.apache.org/jira/browse/ATLAS-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-1276:
---
Description:
Failed tests:
QuickStartIT.runQuickStart:45 » AtlasService Metadata service API CREATE_TYPE
...
EntityNotificationIT.setUp:73->BaseResourceIT.createTypeDefinitions:191->BaseResourceIT.createType:100->BaseResourceIT.createType:105
» AtlasService
NotificationHookConsumerIT.setUp:48->BaseResourceIT.createTypeDefinitions:191->BaseResourceIT.createType:100->BaseResourceIT.createType:105
» AtlasService
DataSetLineageJerseyResourceIT.setUp:57->BaseResourceIT.createTypeDefinitions:191->BaseResourceIT.createType:100->BaseResourceIT.createType:105
» AtlasService
EntityJerseyResourceIT.setUp:104->BaseResourceIT.createTypeDefinitions:191->BaseResourceIT.createType:100->BaseResourceIT.createType:105
» AtlasService
Tests run: 86, Failures: 5, Errors: 0, Skipped: 58
Tests run: 34, Failures: 1, Errors: 0, Skipped: 33, Time elapsed: 1.593 sec <<<
FAILURE! - in org.apache.atlas.web.resources.EntityJerseyResourceIT
setUp(org.apache.atlas.web.resources.EntityJerseyResourceIT) Time elapsed:
1.446 sec <<< FAILURE!
org.apache.atlas.AtlasServiceException: Metadata service API CREATE_TYPE failed
with status 400 (Bad Request) Response Body ({"error":"Unknown datatype:
DataSet","stackTrace":"org.apache.atlas.typesystem.exception.TypeNotFoundException:
Unknown datatype: DataSet\n\tat
org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192)\n\tat
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.dataType(TypeSystem.java:398)\n\tat
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.validateSuperTypes(TypeSystem.java:460)\n\tat
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.validateAndSetupSuperTypes(TypeSystem.java:489)\n\tat
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.verifyTypes(TypeSystem.java:708)\n\tat
org.apache.atlas.typesystem.types.TypeSystem.createTransientTypeSystem(TypeSystem.java:346)\n\tat
org.apache.atlas.services.DefaultMetadataService.createOrUpdateTypes(DefaultMetadataService.java:189)\n\tat
org.apache.atlas.services.DefaultMetadataService.createType(DefaultMetadataService.java:180)\n\tat
org.apache.atlas.web.resources.TypesResource.submit(TypesResource.java:94)\n\tat
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n\tat
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
java.lang.reflect.Method.invoke(Method.java:497)\n\tat
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat
com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
[jira] [Created] (ATLAS-1276) webapp test failures
Shwetha G S created ATLAS-1276:
--
Summary: webapp test failures
Key: ATLAS-1276
URL: https://issues.apache.org/jira/browse/ATLAS-1276
Project: Atlas
Issue Type: Bug
Reporter: Shwetha G S
Priority: Blocker
Failed tests:
QuickStartIT.runQuickStart:45 » AtlasService Metadata service API CREATE_TYPE
...
EntityNotificationIT.setUp:73->BaseResourceIT.createTypeDefinitions:191->BaseResourceIT.createType:100->BaseResourceIT.createType:105
» AtlasService
NotificationHookConsumerIT.setUp:48->BaseResourceIT.createTypeDefinitions:191->BaseResourceIT.createType:100->BaseResourceIT.createType:105
» AtlasService
DataSetLineageJerseyResourceIT.setUp:57->BaseResourceIT.createTypeDefinitions:191->BaseResourceIT.createType:100->BaseResourceIT.createType:105
» AtlasService
EntityJerseyResourceIT.setUp:104->BaseResourceIT.createTypeDefinitions:191->BaseResourceIT.createType:100->BaseResourceIT.createType:105
» AtlasService
Tests run: 86, Failures: 5, Errors: 0, Skipped: 58
{noformat}
ests run: 34, Failures: 1, Errors: 0, Skipped: 33, Time elapsed: 1.593 sec <<<
FAILURE! - in org.apache.atlas.web.resources.EntityJerseyResourceIT
setUp(org.apache.atlas.web.resources.EntityJerseyResourceIT) Time elapsed:
1.446 sec <<< FAILURE!
org.apache.atlas.AtlasServiceException: Metadata service API CREATE_TYPE failed
with status 400 (Bad Request) Response Body ({"error":"Unknown datatype:
DataSet","stackTrace":"org.apache.atlas.typesystem.exception.TypeNotFoundException:
Unknown datatype: DataSet\n\tat
org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192)\n\tat
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.dataType(TypeSystem.java:398)\n\tat
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.validateSuperTypes(TypeSystem.java:460)\n\tat
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.validateAndSetupSuperTypes(TypeSystem.java:489)\n\tat
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.verifyTypes(TypeSystem.java:708)\n\tat
org.apache.atlas.typesystem.types.TypeSystem.createTransientTypeSystem(TypeSystem.java:346)\n\tat
org.apache.atlas.services.DefaultMetadataService.createOrUpdateTypes(DefaultMetadataService.java:189)\n\tat
org.apache.atlas.services.DefaultMetadataService.createType(DefaultMetadataService.java:180)\n\tat
org.apache.atlas.web.resources.TypesResource.submit(TypesResource.java:94)\n\tat
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n\tat
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
java.lang.reflect.Method.invoke(Method.java:497)\n\tat
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat
com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
[jira] [Commented] (ATLAS-1273) Test testOnChangeRefresh in DefaultMetadataServiceTest is failing
[ https://issues.apache.org/jira/browse/ATLAS-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15646943#comment-15646943 ] Shwetha G S commented on ATLAS-1273: +1 > Test testOnChangeRefresh in DefaultMetadataServiceTest is failing > - > > Key: ATLAS-1273 > URL: https://issues.apache.org/jira/browse/ATLAS-1273 > Project: Atlas > Issue Type: Bug >Affects Versions: trunk >Reporter: Vimal Sharma >Assignee: Ayub Khan > Fix For: trunk > > Attachments: ATLAS-1273.patch > > > Test testOnChangeRefresh in DefaultMetadataServiceTest fails with the below > message: > java.lang.AssertionError: Lists differ at element [1]: DataSet != > fetlclassification > Expected :DataSet > Actual :fetlclassification -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-1246) Upgrade versions of dependencies
[ https://issues.apache.org/jira/browse/ATLAS-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15643747#comment-15643747 ] Shwetha G S edited comment on ATLAS-1246 at 11/7/16 10:24 AM: -- If the test in IntellijIdea fail with unable to access method com.google.common.base.Stopwatch, right click on modules titan0, shaded/hbase-client-shaded and shaded/hbase-server-shaded, goto Maven->Ignore Projects. On Atlas main module, right click, goto Maven->Reimport. The issue is because of IntellijIdea not handling shaded dependencies correctly Build on command line works fine was (Author: shwethags): If the test in IntellijIdea fail with unable to access method com.google.common.base.Stopwatch, right click on modules titan0, shaded/hbase-client-shaded and shaded/hbase-server-shaded, goto Maven->Ignore Projects. On Atlas main module, right click, goto Maven->Reimport. Build on command line works fine > Upgrade versions of dependencies > > > Key: ATLAS-1246 > URL: https://issues.apache.org/jira/browse/ATLAS-1246 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-1246-v2.patch, ATLAS-1246.patch > > > 1. Expose variables for setting zookeeper version > 2. Upgrade the versions of libraries -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-1246) Upgrade versions of dependencies
[ https://issues.apache.org/jira/browse/ATLAS-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15643732#comment-15643732 ] Shwetha G S edited comment on ATLAS-1246 at 11/7/16 10:22 AM: -- 1. Changed scala version to 2.11 2. Changed guava version to 18.0. hbase and titan doesn't work with guava 18. In general, when hbase and titan versions are changed using properties, the guava versions that hbase, titan and atlas require may be incompatible and will fail at runtime. So, shaded the guava dependencies in hbase and titan NOTE: Test in repository is failing on trunk, tracked in ATLAS-1273 was (Author: shwethags): 1. Changed scala version to 2.11 2. Changed guava version to 18.0. hbase and titan doesn't work with guava 18. In general, when hbase and titan versions are changed using properties, the guava versions that hbase, titan and atlas require may be incompatible and will fail at runtime. So, shaded the guava dependencies in hbase and titan > Upgrade versions of dependencies > > > Key: ATLAS-1246 > URL: https://issues.apache.org/jira/browse/ATLAS-1246 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-1246-v2.patch, ATLAS-1246.patch > > > 1. Expose variables for setting zookeeper version > 2. Upgrade the versions of libraries -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1246) Upgrade versions of dependencies
[ https://issues.apache.org/jira/browse/ATLAS-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15643747#comment-15643747 ] Shwetha G S commented on ATLAS-1246: If the test in IntellijIdea fail with unable to access method com.google.common.base.Stopwatch, right click on modules titan0, shaded/hbase-client-shaded and shaded/hbase-server-shaded, goto Maven->Ignore Projects. On Atlas main module, right click, goto Maven->Reimport. Build on command line works fine > Upgrade versions of dependencies > > > Key: ATLAS-1246 > URL: https://issues.apache.org/jira/browse/ATLAS-1246 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-1246-v2.patch, ATLAS-1246.patch > > > 1. Expose variables for setting zookeeper version > 2. Upgrade the versions of libraries -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1246) Upgrade versions of dependencies
[ https://issues.apache.org/jira/browse/ATLAS-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1246: --- Attachment: ATLAS-1246-v2.patch 1. Changed scala version to 2.11 2. Changed guava version to 18.0. hbase and titan doesn't work with guava 18. In general, when hbase and titan versions are changed using properties, the guava versions that hbase, titan and atlas require may be incompatible and will fail at runtime. So, shaded the guava dependencies in hbase and titan > Upgrade versions of dependencies > > > Key: ATLAS-1246 > URL: https://issues.apache.org/jira/browse/ATLAS-1246 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-1246-v2.patch, ATLAS-1246.patch > > > 1. Expose variables for setting zookeeper version > 2. Upgrade the versions of libraries -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Deleted] (ATLAS-1270) Atlas web server allows user to browse webapp directory
[ https://issues.apache.org/jira/browse/ATLAS-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S deleted ATLAS-1270: --- > Atlas web server allows user to browse webapp directory > --- > > Key: ATLAS-1270 > URL: https://issues.apache.org/jira/browse/ATLAS-1270 > Project: Atlas > Issue Type: Bug >Reporter: Vipin Rathor > > Currently any (even non-authenticated) user can access the webapp directory > structure by pointing to URIs like http://localhost:21000/lib, > http://localhost:21000/js and http://localhost:21000/img > This could lead to some serious exploits. > As a fix, the embedded Jetty server (including the secure one) should disable > the directory listing. > I'm submitting a basic patch which I tested with non-secure embedded server > only. Since this is my first patch, I'm looking for any feedback so that I > can submit better patches in future. > Thanks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-541) Soft deletes
[ https://issues.apache.org/jira/browse/ATLAS-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-541. --- Resolution: Fixed Fix Version/s: 0.7-incubating > Soft deletes > > > Key: ATLAS-541 > URL: https://issues.apache.org/jira/browse/ATLAS-541 > Project: Atlas > Issue Type: New Feature >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.7-incubating > > > We don't have graph versioning currently and hard deletes are not acceptable > for data governance. This jira tracks the proposal for soft deletes which can > mark an entity as deleted and by default search should return only active > entities. However, there should be an option to retrieve deleted entities -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-676) Enforcing unique attribute values for struct/trait
[ https://issues.apache.org/jira/browse/ATLAS-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-676: -- Issue Type: Bug (was: Sub-task) Parent: (was: ATLAS-541) > Enforcing unique attribute values for struct/trait > -- > > Key: ATLAS-676 > URL: https://issues.apache.org/jira/browse/ATLAS-676 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > > In ATLAS-622, titan doesn't handle unique attributes anymore and it needs to > be handled manually. The jira takes care of enforcing uniqueness on first > unique attribute of the class type as part of entity de-duping. But > uniqueness on struct/trait attributes are not handled -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-538) Capture update delta details
[ https://issues.apache.org/jira/browse/ATLAS-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-538: -- Assignee: (was: Shwetha G S) > Capture update delta details > > > Key: ATLAS-538 > URL: https://issues.apache.org/jira/browse/ATLAS-538 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > > Atlas supports partial/full update which can take the entire entity. We need > to figure out the exact attributes updated for entity history -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-811) Entity delete should check for required reverse references - soft deletes
[ https://issues.apache.org/jira/browse/ATLAS-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-811: -- Assignee: (was: Shwetha G S) > Entity delete should check for required reverse references - soft deletes > - > > Key: ATLAS-811 > URL: https://issues.apache.org/jira/browse/ATLAS-811 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > > DeleteHandler.deleteEdgeBetweenVertices() checks for elements.size(). With > soft deletes, even the deleted elements are part of the array. It should > instead check for active elements -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-676) Enforcing unique attribute values for struct/trait
[ https://issues.apache.org/jira/browse/ATLAS-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-676: -- Assignee: (was: Shwetha G S) > Enforcing unique attribute values for struct/trait > -- > > Key: ATLAS-676 > URL: https://issues.apache.org/jira/browse/ATLAS-676 > Project: Atlas > Issue Type: Sub-task >Reporter: Shwetha G S > > In ATLAS-622, titan doesn't handle unique attributes anymore and it needs to > be handled manually. The jira takes care of enforcing uniqueness on first > unique attribute of the class type as part of entity de-duping. But > uniqueness on struct/trait attributes are not handled -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-609) Secure calls to HBase
[ https://issues.apache.org/jira/browse/ATLAS-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-609. --- Resolution: Fixed Configuration.twiki contains configurations required for secure hbase > Secure calls to HBase > - > > Key: ATLAS-609 > URL: https://issues.apache.org/jira/browse/ATLAS-609 > Project: Atlas > Issue Type: Sub-task >Reporter: Shwetha G S >Assignee: Shwetha G S > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-538) Capture update delta details
[ https://issues.apache.org/jira/browse/ATLAS-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-538: -- Issue Type: Bug (was: Sub-task) Parent: (was: ATLAS-493) > Capture update delta details > > > Key: ATLAS-538 > URL: https://issues.apache.org/jira/browse/ATLAS-538 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > > Atlas supports partial/full update which can take the entire entity. We need > to figure out the exact attributes updated for entity history -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1063) Re-visit the defaults for search APIs
[ https://issues.apache.org/jira/browse/ATLAS-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1063: --- Assignee: (was: Shwetha G S) > Re-visit the defaults for search APIs > - > > Key: ATLAS-1063 > URL: https://issues.apache.org/jira/browse/ATLAS-1063 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > > Currently, search API defaults (default limit and max limit) are set to 100 > and 1 respectively. These defaults are less. For default heap of 1GB, > figure out the right defaults -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1179) Hive hook test failure
[
https://issues.apache.org/jira/browse/ATLAS-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-1179:
---
Assignee: (was: Shwetha G S)
> Hive hook test failure
> --
>
> Key: ATLAS-1179
> URL: https://issues.apache.org/jira/browse/ATLAS-1179
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Priority: Critical
> Attachments: hive-bridge-20161007-jonesn.tar.gz
>
>
> Trunk build fails:
> {noformat}
> HiveHookIT.testAlterTableDropColumn:996 expected:<1> but was:<2>
>
> HiveHookIT.testCreateExternalTable:218->HiveITBase.assertTableIsRegistered:154->HiveITBase.assertEntityIsRegistered:160->HiveITBase.waitFor:204
> Assertions failed. Failing after waiting for timeout 8 msecs
>
> HiveHookIT.testInsertIntoTempTable:690->validateProcess:518->validateProcess:498->assertProcessIsRegistered:1662->HiveITBase.assertEntityIsRegistered:160->HiveITBase.waitFor:204
> Assertions failed. Failing after waiting for timeout 8 msecs
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-1246) Upgrade versions of dependencies
[ https://issues.apache.org/jira/browse/ATLAS-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15629445#comment-15629445 ] Shwetha G S commented on ATLAS-1246: Where did you see this error? The patch worked for me, it probably needs rebase Atlas had explicit dependency on guava and hbase requires guava as well. If these two versions have conflict, atlas server fails a runtime. So, removed the explicit dependency on guava and instead made atlas use the same guava version as hbase's so that the failure happens at compile time instead > Upgrade versions of dependencies > > > Key: ATLAS-1246 > URL: https://issues.apache.org/jira/browse/ATLAS-1246 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-1246.patch > > > 1. Expose variables for setting zookeeper version > 2. Upgrade the versions of libraries -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1247) Support for hive 2.x
[ https://issues.apache.org/jira/browse/ATLAS-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1247: --- Attachment: hive2_atlas.patch > Support for hive 2.x > > > Key: ATLAS-1247 > URL: https://issues.apache.org/jira/browse/ATLAS-1247 > Project: Atlas > Issue Type: Improvement >Reporter: Shwetha G S >Assignee: Vimal Sharma > Attachments: hive2_atlas.patch > > > Atlas hive hook works only with hive 1.x. Need support for hive 2.x -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1247) Support for hive 2.x
[ https://issues.apache.org/jira/browse/ATLAS-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15610942#comment-15610942 ] Shwetha G S commented on ATLAS-1247: Did the atlas hive hook work with hive 2.1.0? If it didn't work, you can try to figure out the issues. Another is to change hive.version in hive-bridge/pom.xml to 2.1.0 and make sure the tests pass. Vimal had an initial patch, attaching here > Support for hive 2.x > > > Key: ATLAS-1247 > URL: https://issues.apache.org/jira/browse/ATLAS-1247 > Project: Atlas > Issue Type: Improvement >Reporter: Shwetha G S >Assignee: Vimal Sharma > Attachments: hive2_atlas.patch > > > Atlas hive hook works only with hive 1.x. Need support for hive 2.x -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-1116) Performance monitoring of backend methods in API requests
[ https://issues.apache.org/jira/browse/ATLAS-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S reassigned ATLAS-1116: -- Assignee: Shwetha G S (was: Vimal Sharma) > Performance monitoring of backend methods in API requests > - > > Key: ATLAS-1116 > URL: https://issues.apache.org/jira/browse/ATLAS-1116 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-1116.patch > > > Time taken by methods used in API calls for add/update/delete entities and > traits need to be monitored for performance -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1246) Upgrade versions of dependencies
[ https://issues.apache.org/jira/browse/ATLAS-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1246: --- Attachment: ATLAS-1246.patch > Upgrade versions of dependencies > > > Key: ATLAS-1246 > URL: https://issues.apache.org/jira/browse/ATLAS-1246 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Attachments: ATLAS-1246.patch > > > 1. Expose variables for setting zookeeper version > 2. Upgrade the versions of libraries -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1246) Upgrade versions of dependencies
Shwetha G S created ATLAS-1246: -- Summary: Upgrade versions of dependencies Key: ATLAS-1246 URL: https://issues.apache.org/jira/browse/ATLAS-1246 Project: Atlas Issue Type: Bug Reporter: Shwetha G S Assignee: Shwetha G S Attachments: ATLAS-1246.patch 1. Expose variables for setting zookeeper version 2. Upgrade the versions of libraries -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-1231) Happiness
[ https://issues.apache.org/jira/browse/ATLAS-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-1231. Resolution: Invalid > Happiness > - > > Key: ATLAS-1231 > URL: https://issues.apache.org/jira/browse/ATLAS-1231 > Project: Atlas > Issue Type: Improvement >Reporter: Lior Katz >Priority: Critical > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1182) Hive Column level lineage docs
[ https://issues.apache.org/jira/browse/ATLAS-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588234#comment-15588234 ] Shwetha G S commented on ATLAS-1182: The build works for me with mvn 3.2.5. Whats the error that you see with mvn 3.2.3? > Hive Column level lineage docs > -- > > Key: ATLAS-1182 > URL: https://issues.apache.org/jira/browse/ATLAS-1182 > Project: Atlas > Issue Type: Improvement >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Fix For: 0.8-incubating > > Attachments: ATLAS-1182-v1.patch, ATLAS-1182.patch, > column_lineage_ex1.png > > > Add column level lineage details to Atlas documentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1207) Dataset exists query in lineage APIs takes longer
[
https://issues.apache.org/jira/browse/ATLAS-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-1207:
---
Attachment: ATLAS-1207-v2.patch
Fixed. Also changed the tests to catch this issue (the tests had both the name
and qualifiedName same)
> Dataset exists query in lineage APIs takes longer
> -
>
> Key: ATLAS-1207
> URL: https://issues.apache.org/jira/browse/ATLAS-1207
> Project: Atlas
> Issue Type: Bug
>Reporter: Sharmadha Sainath
>Assignee: Shwetha G S
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1207-v2.patch, ATLAS-1207.patch
>
>
> Hive_column now extends DataSet. Lineage Service uses the DSL query Dataset
> where __guid = which maps to the gremlin query g.V().has(supertype,
> Dataset).has(__guid, ). Since the first filter is on type which returns
> many vertices, this query is slow. Supertypes is a list property and not sure
> how adding combined index will work. This can be replaced with graph query
> directly like
> {code}
> titanGraph.query().has(Constants.GUID_PROPERTY_KEY, guid)
> .has(Constants.SUPER_TYPES_PROPERTY_KEY,
> AtlasClient.DATA_SET_SUPER_TYPE)
> {code}
> Thanks [~ssainath] for helping to test this
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-1207) Dataset exists query in lineage APIs takes longer
[
https://issues.apache.org/jira/browse/ATLAS-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15581881#comment-15581881
]
Shwetha G S commented on ATLAS-1207:
The attached patch replaces DSL query with direct graph query
> Dataset exists query in lineage APIs takes longer
> -
>
> Key: ATLAS-1207
> URL: https://issues.apache.org/jira/browse/ATLAS-1207
> Project: Atlas
> Issue Type: Bug
>Reporter: Sharmadha Sainath
>Assignee: Shwetha G S
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1207.patch
>
>
> Hive_column now extends DataSet. Lineage Service uses the DSL query Dataset
> where __guid = which maps to the gremlin query g.V().has(supertype,
> Dataset).has(__guid, ). Since the first filter is on type which returns
> many vertices, this query is slow. Supertypes is a list property and not sure
> how adding combined index will work. This can be replaced with graph query
> directly like
> {code}
> titanGraph.query().has(Constants.GUID_PROPERTY_KEY, guid)
> .has(Constants.SUPER_TYPES_PROPERTY_KEY,
> AtlasClient.DATA_SET_SUPER_TYPE)
> {code}
> Thanks [~ssainath] for helping to test this
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1207) Dataset exists query in lineage APIs takes longer
[
https://issues.apache.org/jira/browse/ATLAS-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-1207:
---
Attachment: ATLAS-1207.patch
> Dataset exists query in lineage APIs takes longer
> -
>
> Key: ATLAS-1207
> URL: https://issues.apache.org/jira/browse/ATLAS-1207
> Project: Atlas
> Issue Type: Bug
>Reporter: Sharmadha Sainath
>Assignee: Shwetha G S
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1207.patch
>
>
> Hive_column now extends DataSet. Lineage Service uses the DSL query Dataset
> where __guid = which maps to the gremlin query g.V().has(supertype,
> Dataset).has(__guid, ). Since the first filter is on type which returns
> many vertices, this query is slow. Supertypes is a list property and not sure
> how adding combined index will work. This can be replaced with graph query
> directly like
> {code}
> titanGraph.query().has(Constants.GUID_PROPERTY_KEY, guid)
> .has(Constants.SUPER_TYPES_PROPERTY_KEY,
> AtlasClient.DATA_SET_SUPER_TYPE)
> {code}
> Thanks [~ssainath] for helping to test this
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1221) build failure in windows SyntaxError: invalid syntax
[ https://issues.apache.org/jira/browse/ATLAS-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1221: --- Attachment: ATLAS-1221-v2.patch +1, here is the patch that applies > build failure in windows SyntaxError: invalid syntax > - > > Key: ATLAS-1221 > URL: https://issues.apache.org/jira/browse/ATLAS-1221 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating > Environment: window7(64) +maven3.2.5+git+python3.5(64)+jdk1.7.80 >Reporter: zhangqiang2 >Assignee: zhangqiang2 >Priority: Critical > Labels: build > Attachments: ATLAS-1221-v2.patch, ATLAS-1221.patch > > > Traceback (most recent call last): > File "unitTests.py", line 118, in > main() > File "unitTests.py", line 87, in main > suite = all_tests_suite() > File "unitTests.py", line 78, in all_tests_suite > suite = unittest.TestLoader().loadTestsFromNames(tests_list) > File "c:\python\lib\unittest\loader.py", line 219, in loadTestsFromNames > suites = [self.loadTestsFromName(name, module) for name in names] > File "c:\python\lib\unittest\loader.py", line 219, in > suites = [self.loadTestsFromName(name, module) for name in names] > File "c:\python\lib\unittest\loader.py", line 153, in loadTestsFromName > module = __import__(module_name) > File > "E:\GITProject-bak\incubator-atlas-eclipse\distro\src\test\python\scripts\TestMetadata.py", > line 26, in > import atlas_config as mc > File > "E:\GITProject-bak\incubator-atlas-eclipse\distro\src\bin\atlas_config.py", > line 135 > except OSError, e: > ^ > SyntaxError: invalid syntax > [INFO] > > [INFO] Reactor Summary: > [INFO] > [INFO] apache-atlas ... SUCCESS [ 19.819 > s] > [INFO] Apache Atlas Common SUCCESS [ 23.974 > s] > [INFO] Apache Atlas Typesystem SUCCESS [ 44.967 > s] > [INFO] Apache Atlas Client SUCCESS [ 26.070 > s] > [INFO] Apache Atlas Server API SUCCESS [ 18.260 > s] > [INFO] Apache Atlas Notification .. SUCCESS [ 24.818 > s] > [INFO] Apache Atlas Graph Database Projects ... SUCCESS [ 1.996 > s] > [INFO] Apache Atlas Graph Database API SUCCESS [ 12.466 > s] > [INFO] Graph Database Common Code . SUCCESS [ 12.562 > s] > [INFO] Apache Atlas Titan 0.5.4 Graph DB Impl . SUCCESS [ 52.199 > s] > [INFO] Apache Atlas Repository SUCCESS [ 53.281 > s] > [INFO] Apache Atlas Authorization . SUCCESS [ 14.496 > s] > [INFO] Apache Atlas Business Catalog .. SUCCESS [ 19.184 > s] > [INFO] Apache Atlas UI SUCCESS [13:55 > min] > [INFO] Apache Atlas Web Application ... SUCCESS [02:13 > min] > [INFO] Apache Atlas Documentation . SUCCESS [ 14.923 > s] > [INFO] Apache Atlas FileSystem Model .. SUCCESS [01:04 > min] > [INFO] Apache Atlas Plugin Classloader SUCCESS [ 12.809 > s] > [INFO] Apache Atlas Hive Bridge Shim .. SUCCESS [ 16.498 > s] > [INFO] Apache Atlas Hive Bridge ... SUCCESS [02:23 > min] > [INFO] Apache Atlas Falcon Bridge Shim SUCCESS [ 17.179 > s] > [INFO] Apache Atlas Falcon Bridge . SUCCESS [02:11 > min] > [INFO] Apache Atlas Sqoop Bridge Shim . SUCCESS [ 7.781 > s] > [INFO] Apache Atlas Sqoop Bridge .. SUCCESS [02:14 > min] > [INFO] Apache Atlas Storm Bridge Shim . SUCCESS [ 9.031 > s] > [INFO] Apache Atlas Storm Bridge .. SUCCESS [02:17 > min] > [INFO] Apache Atlas Distribution .. FAILURE [ 8.631 > s] > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 33:15 min > [INFO] Finished at: 2016-10-12T09:06:02+08:00 > [INFO] Final Memory: 159M/857M > [INFO] > > [WARNING] The requested profile "env-common" could not be activated because > it does not exist. > [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec > (python-test) on project atlas-distro: Command execution failed. Proce > exited with an error: 1 (Exit value: 1) -> [Help 1] >
[jira] [Commented] (ATLAS-1220) when i execute bin/atlas_start.py found HTTP ERROR: 503
[ https://issues.apache.org/jira/browse/ATLAS-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15581219#comment-15581219 ] Shwetha G S commented on ATLAS-1220: The error is because of issue in starting embedded zookeeper and kafka. Can you enable debug logs to get more details? Atlas requires kafka for hook integration and entity notifications. If you are running with external hbase and solr, you need to configure external kafka endpoints as well. Can you attach the atlas configuration that you are using? > when i execute bin/atlas_start.py found HTTP ERROR: 503 > - > > Key: ATLAS-1220 > URL: https://issues.apache.org/jira/browse/ATLAS-1220 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating > Environment: > hadoop2.6.0+hbase1.1.5+solr5.5.2+zookeeper3.4.8+hive1.2.1+redhat6.5 >Reporter: zhangqiang2 > > 2016-10-11 10:01:06,739 INFO - [main:] ~ Initializing type system for the > first time. (DefaultMetadataService:162) > 2016-10-11 10:01:07,495 WARN - [main:] ~ class fs_path already registered, > ignoring types in /home/hong/atlas/atlas-0.7/models/fs_model.json > (ReservedTypesRegistrar:89) > 2016-10-11 10:01:07,615 WARN - [main:] ~ class hive_process already > registered, ignoring types in > /home/hong/atlas/atlas-0.7/models/hive_model.json (ReservedTypesRegistrar:89) > 2016-10-11 10:01:07,654 WARN - [main:] ~ class falcon_feed_replication > already registered, ignoring types in > /home/hong/atlas/atlas-0.7/models/falcon_model.json > (ReservedTypesRegistrar:89) > 2016-10-11 10:01:07,675 WARN - [main:] ~ class sqoop_process already > registered, ignoring types in > /home/hong/atlas/atlas-0.7/models/sqoop_model.json (ReservedTypesRegistrar:89) > 2016-10-11 10:01:07,707 WARN - [main:] ~ class storm_topology already > registered, ignoring types in > /home/hong/atlas/atlas-0.7/models/storm_model.json (ReservedTypesRegistrar:89) > 2016-10-11 10:01:07,707 INFO - [main:] ~ Restored type system from the store > (DefaultMetadataService:173) > 2016-10-11 10:01:07,709 INFO - [main:] ~ Guice modules loaded > (GuiceServletConfig:120) > 2016-10-11 10:01:07,714 INFO - [main:] ~ Starting services > (GuiceServletConfig:140) > 2016-10-11 10:01:07,764 WARN - [main-SendThread(dap241:9026):] ~ Session 0x0 > for server null, unexpected error, closing socket connection and attempting > reconnect (ClientCnxn$SendThread:1102) > java.net.ConnectException: 拒绝连接 > at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) > at > sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744) > at > org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361) > at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081) > 2016-10-11 10:01:07,803 INFO - [main:] ~ HA is disabled. Hence creating > table on startup. (HBaseBasedAuditRepository:287) > 2016-10-11 10:01:07,803 INFO - [main:] ~ Checking if table > apache_atlas_entity_audit exists (HBaseBasedAuditRepository:249) > 2016-10-11 10:01:07,816 INFO - [main:] ~ Table apache_atlas_entity_audit > exists (HBaseBasedAuditRepository:258) > 2016-10-11 10:01:07,816 INFO - [main:] ~ HA is not enabled, no need to start > leader election service (ActiveInstanceElectorService:101) > 2016-10-11 10:01:08,875 WARN - > [NIOServerCxn.Factory:dap241/10.43.182.241:9026:] ~ Exception causing close > of session 0x0 due to java.io.IOException: ZooKeeperServer not running > (NIOServerCnxn:362) > 2016-10-11 10:01:10,139 WARN - > [NIOServerCxn.Factory:dap241/10.43.182.241:9026:] ~ Exception causing close > of session 0x0 due to java.io.IOException: ZooKeeperServer not running > (NIOServerCnxn:362) > 2016-10-11 10:01:12,293 WARN - > [NIOServerCxn.Factory:dap241/10.43.182.241:9026:] ~ Exception causing close > of session 0x0 due to java.io.IOException: ZooKeeperServer not running > (NIOServerCnxn:362) > 2016-10-11 10:01:14,756 FATAL - [main:] ~ Fatal error during KafkaServer > startup. Prepare to shutdown (Logging$class:116) > org.I0Itec.zkclient.exception.ZkTimeoutException: Unable to connect to > zookeeper server within timeout: 500 > at org.I0Itec.zkclient.ZkClient.connect(ZkClient.java:1232) > at org.I0Itec.zkclient.ZkClient.(ZkClient.java:156) > at org.I0Itec.zkclient.ZkClient.(ZkClient.java:130) > at kafka.utils.ZkUtils$.createZkClientAndConnection(ZkUtils.scala:75) > at kafka.utils.ZkUtils$.apply(ZkUtils.scala:57) > at kafka.server.KafkaServer.initZk(KafkaServer.scala:294) > at kafka.server.KafkaServer.startup(KafkaServer.scala:180) > at > org.apache.atlas.kafka.KafkaNotification.startKafka(KafkaNotification.java:352) > at > org.apache.atlas.kafka.KafkaNotification.start(KafkaNotification.java:145) >
[jira] [Commented] (ATLAS-1222) DSL query support to filter deleted entities
[ https://issues.apache.org/jira/browse/ATLAS-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15581212#comment-15581212 ] Shwetha G S commented on ATLAS-1222: __status = 'ACTIVE' as filter in the DSL query filters deleted entities > DSL query support to filter deleted entities > > > Key: ATLAS-1222 > URL: https://issues.apache.org/jira/browse/ATLAS-1222 > Project: Atlas > Issue Type: Bug >Affects Versions: trunk >Reporter: Ayub Khan > Fix For: trunk > > > Currently, through UI/API, there is no way to filter entities that are > deleted. > Also, there is no way to query for fields in a complex structure(only simple > fields are supported. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-1216) Please delete this issue - JIRA is sooooo weird to use
[ https://issues.apache.org/jira/browse/ATLAS-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-1216. Resolution: Invalid > Please delete this issue - JIRA is so weird to use > -- > > Key: ATLAS-1216 > URL: https://issues.apache.org/jira/browse/ATLAS-1216 > Project: Atlas > Issue Type: Task >Reporter: Ronald Feicht >Priority: Trivial > > I cannot find the button where I may delete my own issue, so, sorry for one > of you guys having to do it for me. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1182) Hive Column level lineage docs
[ https://issues.apache.org/jira/browse/ATLAS-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15554214#comment-15554214 ] Shwetha G S commented on ATLAS-1182: Can you also add details of hive version that column level lineage works with (hive 1.2.x + hive patch)? > Hive Column level lineage docs > -- > > Key: ATLAS-1182 > URL: https://issues.apache.org/jira/browse/ATLAS-1182 > Project: Atlas > Issue Type: Improvement >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Fix For: 0.8-incubating > > Attachments: ATLAS-1182.patch, column_lineage_ex1.png > > > Add column level lineage details to Atlas documentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-197) Add build instructions in top level dir
[ https://issues.apache.org/jira/browse/ATLAS-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551084#comment-15551084 ] Shwetha G S commented on ATLAS-197: --- Yes, makes sense to add local reference or give minimal build instructions at README and add link as well for detailed instructions > Add build instructions in top level dir > --- > > Key: ATLAS-197 > URL: https://issues.apache.org/jira/browse/ATLAS-197 > Project: Atlas > Issue Type: Wish >Affects Versions: trunk >Reporter: Nigel Jones >Priority: Minor > > In early Atlas code we had a file (names something like Installation Steps) > in the top level directory which directed the developer who'd downloaded the > code from github as to how to build. > However since the docs are now in twiki those build instructions are only > found several layers deep, and with twiki markup > jonesn@jonesn-ThinkPad-W530:~/atlas/incubator-atlas$ find . -type f -print | > xargs -n50 grep -y "mvn clean install" > ./docs/src/site/twiki/InstallationSteps.twiki:export MAVEN_OPTS="-Xmx1024m > -XX:MaxPermSize=256m" && mvn clean install > A pointer to the user to read this file, or a quick summary should be added > to the root -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-961) DataSetLineageJerseyResourceIT.setUp fails
[
https://issues.apache.org/jira/browse/ATLAS-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S resolved ATLAS-961.
---
Resolution: Duplicate
> DataSetLineageJerseyResourceIT.setUp fails
> --
>
> Key: ATLAS-961
> URL: https://issues.apache.org/jira/browse/ATLAS-961
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>
> mvn clean install -rf :atlas-webapp -Dit.test=DataSetLineageJerseyResourceIT
> -DskipUTs
> {noformat}
> Tests run: 9, Failures: 1, Errors: 0, Skipped: 8, Time elapsed: 3.716 sec <<<
> FAILURE! - in org.apache.atlas.web.resources.DataSetLineageJerseyResourceIT
> setUp(org.apache.atlas.web.resources.DataSetLineageJerseyResourceIT) Time
> elapsed: 3.666 sec <<< FAILURE!
> org.apache.atlas.AtlasServiceException: Metadata service API CREATE_ENTITY
> failed with status 400(Bad Request) Response Body ({"error":"Unknown
> datatype:
> Fact","stackTrace":"org.apache.atlas.typesystem.exception.TypeNotFoundException:
> Unknown datatype: Fact\n\tat
> org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:178)\n\tat
>
> org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.getDataType(TypeSystem.java:649)\n\tat
>
> org.apache.atlas.typesystem.types.ClassType.createInstanceWithTraits(ClassType.java:182)\n\tat
>
> org.apache.atlas.typesystem.types.ClassType.convert(ClassType.java:125)\n\tat
> org.apache.atlas.services.DefaultMetadataService.getTypedReferenceableInstance(DefaultMetadataService.java:374)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.deserializeClassInstances(DefaultMetadataService.java:350)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:331)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:125)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
> java.lang.reflect.Method.invoke(Method.java:606)\n\tat
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
> javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
>
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
>
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
>
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
>
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)\n\tat
> com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)\n\tat
> com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)\n\tat
> com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)\n\tat
>
[jira] [Updated] (ATLAS-1208) DSL query optimisation
[
https://issues.apache.org/jira/browse/ATLAS-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-1208:
---
Assignee: (was: Shwetha G S)
> DSL query optimisation
> --
>
> Key: ATLAS-1208
> URL: https://issues.apache.org/jira/browse/ATLAS-1208
> Project: Atlas
> Issue Type: Bug
>Reporter: Sharmadha Sainath
> Fix For: 0.8-incubating
>
>
> DSL queries always have the type. The DSL query is transformed into gremlin
> of the form: {{g.V().has(type, ).has(name, )}}. This is not
> efficient as the first has clause returns many vertices. Instead, if we
> generate the gremlin query as {{g.V().has(name, ).has(type, )}},
> the query should execute faster as the first predicate will filter more
> vertices
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-1208) DSL query optimisation
Shwetha G S created ATLAS-1208:
--
Summary: DSL query optimisation
Key: ATLAS-1208
URL: https://issues.apache.org/jira/browse/ATLAS-1208
Project: Atlas
Issue Type: Bug
Reporter: Sharmadha Sainath
Fix For: 0.8-incubating
DSL queries always have the type. The DSL query is transformed into gremlin of
the form: {{g.V().has(type, ).has(name, )}}. This is not efficient
as the first has clause returns many vertices. Instead, if we generate the
gremlin query as {{g.V().has(name, ).has(type, )}}, the query
should execute faster as the first predicate will filter more vertices
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-1207) Dataset exists query in lineage APIs takes longer
Shwetha G S created ATLAS-1207:
--
Summary: Dataset exists query in lineage APIs takes longer
Key: ATLAS-1207
URL: https://issues.apache.org/jira/browse/ATLAS-1207
Project: Atlas
Issue Type: Bug
Reporter: Sharmadha Sainath
Assignee: Shwetha G S
Fix For: 0.8-incubating
Hive_column now extends DataSet. Lineage Service uses the DSL query Dataset
where __guid = which maps to the gremlin query g.V().has(supertype,
Dataset).has(__guid, ). Since the first filter is on type which returns
many vertices, this query is slow. Supertypes is a list property and not sure
how adding combined index will work. This can be replaced with graph query
directly like
{code}
titanGraph.query().has(Constants.GUID_PROPERTY_KEY, guid)
.has(Constants.SUPER_TYPES_PROPERTY_KEY,
AtlasClient.DATA_SET_SUPER_TYPE)
{code}
Thanks [~ssainath] for helping to test this
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1205) Improve atlas build time
[ https://issues.apache.org/jira/browse/ATLAS-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1205: --- Attachment: ATLAS-1205.patch 1. Moved copy jars to dist profile as the copied jars are required only for atlas package. Atlas package is built only in dist profile, and copying jars is not useful otherwise 2. Moved scala plugin to specific modules 3. Removed building zip package, as there is already tag.gz package built > Improve atlas build time > > > Key: ATLAS-1205 > URL: https://issues.apache.org/jira/browse/ATLAS-1205 > Project: Atlas > Issue Type: Improvement >Reporter: Shwetha G S >Assignee: Shwetha G S >Priority: Minor > Fix For: 0.8-incubating > > Attachments: ATLAS-1205.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1205) Improve atlas build time
Shwetha G S created ATLAS-1205: -- Summary: Improve atlas build time Key: ATLAS-1205 URL: https://issues.apache.org/jira/browse/ATLAS-1205 Project: Atlas Issue Type: Improvement Reporter: Shwetha G S Assignee: Shwetha G S Priority: Minor Fix For: 0.8-incubating -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1203) 'Invalid type definition' due to no new types to be created at startup
[
https://issues.apache.org/jira/browse/ATLAS-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-1203:
---
Summary: 'Invalid type definition' due to no new types to be created at
startup (was: 'Invalid type definition' error during startup)
> 'Invalid type definition' due to no new types to be created at startup
> --
>
> Key: ATLAS-1203
> URL: https://issues.apache.org/jira/browse/ATLAS-1203
> Project: Atlas
> Issue Type: Bug
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
> Attachments: ATLAS-1203.patch
>
>
> After the fix for ATLAS-1184, following exception/error is seen in Atlas
> server logs during startup:
> {code}
> 2016-10-01 05:55:27,437 INFO - [main:] ~ Initializing type system for the
> first time. (DefaultMetadataService:165)
> 2016-10-01 05:55:27,751 ERROR - [main:] ~ Unable to deserialize json={
> "enumTypes":[
> ],
> "structTypes":[
> ],
> "traitTypes":[
> ],
> "classTypes":[
> ]
> } (DefaultMetadataService:286)
> java.lang.IllegalArgumentException: Invalid type definition
> at
> org.apache.atlas.services.DefaultMetadataService.validateTypeDefinition(DefaultMetadataService.java:282)
> at
> org.apache.atlas.services.DefaultMetadataService.createOrUpdateTypes(DefaultMetadataService.java:244)
> at
> org.apache.atlas.services.DefaultMetadataService.createType(DefaultMetadataService.java:239)
> at
> org.apache.atlas.services.ReservedTypesRegistrar.registerType(ReservedTypesRegistrar.java:124)
> at
> org.apache.atlas.services.ReservedTypesRegistrar.registerTypes(ReservedTypesRegistrar.java:69)
> at
> org.apache.atlas.services.DefaultMetadataService.restoreTypeSystem(DefaultMetadataService.java:170)
> at
> org.apache.atlas.services.DefaultMetadataService.(DefaultMetadataService.java:153)
> at
> org.apache.atlas.services.DefaultMetadataService.(DefaultMetadataService.java:118)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> ...
> ...
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:93)
> at org.apache.atlas.Atlas.main(Atlas.java:118)
> 2016-10-01 05:55:27,762 INFO - [main:] ~ Restoring type system from the
> store (DefaultMetadataService:162)
> 2016-10-01 05:55:27,770 INFO - [main:] ~ Restoring type CLASS.fs_path.null
> (GraphBackedTypeStore:243)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-1203) 'Invalid type definition' error during startup
[
https://issues.apache.org/jira/browse/ATLAS-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15540307#comment-15540307
]
Shwetha G S commented on ATLAS-1203:
+1
> 'Invalid type definition' error during startup
> --
>
> Key: ATLAS-1203
> URL: https://issues.apache.org/jira/browse/ATLAS-1203
> Project: Atlas
> Issue Type: Bug
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
> Attachments: ATLAS-1203.patch
>
>
> After the fix for ATLAS-1184, following exception/error is seen in Atlas
> server logs during startup:
> {code}
> 2016-10-01 05:55:27,437 INFO - [main:] ~ Initializing type system for the
> first time. (DefaultMetadataService:165)
> 2016-10-01 05:55:27,751 ERROR - [main:] ~ Unable to deserialize json={
> "enumTypes":[
> ],
> "structTypes":[
> ],
> "traitTypes":[
> ],
> "classTypes":[
> ]
> } (DefaultMetadataService:286)
> java.lang.IllegalArgumentException: Invalid type definition
> at
> org.apache.atlas.services.DefaultMetadataService.validateTypeDefinition(DefaultMetadataService.java:282)
> at
> org.apache.atlas.services.DefaultMetadataService.createOrUpdateTypes(DefaultMetadataService.java:244)
> at
> org.apache.atlas.services.DefaultMetadataService.createType(DefaultMetadataService.java:239)
> at
> org.apache.atlas.services.ReservedTypesRegistrar.registerType(ReservedTypesRegistrar.java:124)
> at
> org.apache.atlas.services.ReservedTypesRegistrar.registerTypes(ReservedTypesRegistrar.java:69)
> at
> org.apache.atlas.services.DefaultMetadataService.restoreTypeSystem(DefaultMetadataService.java:170)
> at
> org.apache.atlas.services.DefaultMetadataService.(DefaultMetadataService.java:153)
> at
> org.apache.atlas.services.DefaultMetadataService.(DefaultMetadataService.java:118)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> ...
> ...
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:93)
> at org.apache.atlas.Atlas.main(Atlas.java:118)
> 2016-10-01 05:55:27,762 INFO - [main:] ~ Restoring type system from the
> store (DefaultMetadataService:162)
> 2016-10-01 05:55:27,770 INFO - [main:] ~ Restoring type CLASS.fs_path.null
> (GraphBackedTypeStore:243)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-694) Update Atlas code to use abstraction layer
[ https://issues.apache.org/jira/browse/ATLAS-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-694: -- Attachment: ATLAS-694.patch re-based patch > Update Atlas code to use abstraction layer > -- > > Key: ATLAS-694 > URL: https://issues.apache.org/jira/browse/ATLAS-694 > Project: Atlas > Issue Type: Sub-task >Reporter: Jeffrey Hagelberg >Assignee: Jeffrey Hagelberg > Attachments: ATLAS-694.patch, rb47810.patch > > > In this task, we will update Atlas to replace the direct usage of titan > classes with usage of the equivalent interfaces in the abstraction layer. At > this point, there will be no options to configure the abstraction layer > implementation that gets used. Atlas will be hard-coded to use the titan > 0.5.4 implementation. It will also continue to have a compile time > dependency on the titan 0.5.4 graph database implementation. When this task > is complete, Atlas will only be accessing titan through the abstraction layer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1183) UI: help link should point to atlas website
[ https://issues.apache.org/jira/browse/ATLAS-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529316#comment-15529316 ] Shwetha G S commented on ATLAS-1183: Couldn't verify because of issue detailed ATLAS-1199. Will commit post ATLAS-1199 fix > UI: help link should point to atlas website > --- > > Key: ATLAS-1183 > URL: https://issues.apache.org/jira/browse/ATLAS-1183 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Keval Bhatt > Fix For: 0.8-incubating > > Attachments: ATLAS-1183.patch > > > Help link points to > https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=ATLAS=Atlas+Home > which requires login. Instead, link to http://atlas.incubator.apache.org/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1199) Atlas UI not loading after fresh build due jquery-asBreadcrumbs plugin changes.
[ https://issues.apache.org/jira/browse/ATLAS-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529300#comment-15529300 ] Shwetha G S commented on ATLAS-1199: Is this issue after ATLAS-1142 commit? > Atlas UI not loading after fresh build due jquery-asBreadcrumbs plugin > changes. > --- > > Key: ATLAS-1199 > URL: https://issues.apache.org/jira/browse/ATLAS-1199 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: Keval Bhatt >Priority: Blocker > Fix For: 0.7-incubating > > > Atlas UI not loading after fresh build due jquery-asBreadcrumbs plugin > changes. > Found following error in browser console > Overrides.js:22 Uncaught TypeError: Cannot set property > 'generateChildrenInfo' of undefined > GET http://localhost:21000/js/libs/jquery-asBreadcrumbs/css/asBreadcrumbs.css > 404 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1183) UI: help link should point to atlas website
[ https://issues.apache.org/jira/browse/ATLAS-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528663#comment-15528663 ] Shwetha G S commented on ATLAS-1183: +1 > UI: help link should point to atlas website > --- > > Key: ATLAS-1183 > URL: https://issues.apache.org/jira/browse/ATLAS-1183 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Keval Bhatt > Fix For: 0.8-incubating > > Attachments: ATLAS-1183.patch > > > Help link points to > https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=ATLAS=Atlas+Home > which requires login. Instead, link to http://atlas.incubator.apache.org/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1174) Framework to apply updates to types in the type-system
[
https://issues.apache.org/jira/browse/ATLAS-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528662#comment-15528662
]
Shwetha G S commented on ATLAS-1174:
Committing this now, don't see the patch file for position attribute that you
added earlier. You can file a jira for it
> Framework to apply updates to types in the type-system
> --
>
> Key: ATLAS-1174
> URL: https://issues.apache.org/jira/browse/ATLAS-1174
> Project: Atlas
> Issue Type: New Feature
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Labels: feature, patch
> Attachments: ATLAS-1174.patch
>
>
> 1. Introduce "version" attribute to all types in the type-system, this helps
> to track changes made to the default types (hive, sqoop, falcon and storm
> types) and user created types. If version is not mentioned during creation of
> a type, default version "1.0" is assigned (optional attribute).
> 2. Using the version attributed for types, introduce a patch framework for
> type system. This framework applies patches to a type using its version
> number and can be used during upgrade - add new attributes to an existing
> types and it will be run during atlas startup.
> The sequence of steps:
> a. During atlas startup, check $ATLAS_HOME/models/patches directory for
> any available patch files (json files). If there any patch files handle them.
> b. Sample patch json file looks like:
> {
> "patches": [
> {
> "action": "ADD_ATTRIBUTE",
> "typeName": "hive_column",
> "applyToVersion": "1.0",
> "updateToVersion": "2.0",
> "actionParams": [
> { "name": "position",
> "dataTypeName": "int",
> "multiplicity": "optional",
> "isComposite": false,
> "isUnique": false,
> "isIndexable": false,
> "reverseAttributeName": null
> } ]
> } ]
> }
> c. The framework updates the type in "typeName" for the matching version
> number and after applying the patch, update the version to the one mentioned
> in "updateToVersion"
> d. The json file can have more than one action (array of actions).
> e. There can be multiple patch json files in the directory and are
> applied in the sort order of the filename. eg:
> 001-hive_column_add_position.json
> 002-hive_column_add_anotherattribute.json
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-1178) APIs in DefaultMetadataService should return POJOs
[ https://issues.apache.org/jira/browse/ATLAS-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15522127#comment-15522127 ] Shwetha G S commented on ATLAS-1178: DefaultMetadataService is the API internal to the service. server-api module has only the server side APIs and not exposed to clients. So, lets leave DefaultMetadataService in server-api DefaultMetadataService handles both type and entities related APIs, and hence the name MetadataService Yes, the plan is to remove json awareness from MetadataService, and the serialisation/deserialisation should be transparent to even the rest APIs and should be handled by jersey automatically. Yes, this is to avoid the extra json processing. EntityResult is already a POJO > APIs in DefaultMetadataService should return POJOs > -- > > Key: ATLAS-1178 > URL: https://issues.apache.org/jira/browse/ATLAS-1178 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > > DefaultMetadataService APIs accept/return json strings and the rest APIs end > up serialising and deserialising everytime. DefaultMetadataService APIs are > internal APIs and should accept/return POJOs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1184) ReservedTypesRegistrar checks for existence of 1st class type
[ https://issues.apache.org/jira/browse/ATLAS-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15509686#comment-15509686 ] Shwetha G S commented on ATLAS-1184: Looks like ReservedTypesRegistrar uses internal APIs directly. It should just be a utility which uses rest APIs so that its audited > ReservedTypesRegistrar checks for existence of 1st class type > - > > Key: ATLAS-1184 > URL: https://issues.apache.org/jira/browse/ATLAS-1184 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Vimal Sharma > > ReservedTypesRegistrar registers the models for supported integrations like > hive, falcon, sqoop and storm. ReservedTypesRegistrar reads the model files > and registers the types defined in the model file. The check thats done to > verify if the model is already registered - checks for existence of first > class type. This will not work if we add more class types to the existing > model or modify the existing type to add optional attributes. > ReservedTypesRegistrar should check for every type in the model file. Also, > ReservedTypesRegistrar should do type update which does create if not exists, > and update if exists -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1185) UI: columns attribute displayed for all entities
[ https://issues.apache.org/jira/browse/ATLAS-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-1185: --- Attachment: Screen Shot 2016-09-21 at 5.06.29 PM.png > UI: columns attribute displayed for all entities > > > Key: ATLAS-1185 > URL: https://issues.apache.org/jira/browse/ATLAS-1185 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S > Attachments: Screen Shot 2016-09-21 at 5.06.29 PM.png > > > In the entity details page, columns attribute is displayed without any value. > Looks like this is shown for all entity types -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1185) UI: columns attribute displayed for all entities
Shwetha G S created ATLAS-1185: -- Summary: UI: columns attribute displayed for all entities Key: ATLAS-1185 URL: https://issues.apache.org/jira/browse/ATLAS-1185 Project: Atlas Issue Type: Bug Reporter: Shwetha G S Attachments: Screen Shot 2016-09-21 at 5.06.29 PM.png In the entity details page, columns attribute is displayed without any value. Looks like this is shown for all entity types -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1184) ReservedTypesRegistrar checks for existence of 1st class type
Shwetha G S created ATLAS-1184: -- Summary: ReservedTypesRegistrar checks for existence of 1st class type Key: ATLAS-1184 URL: https://issues.apache.org/jira/browse/ATLAS-1184 Project: Atlas Issue Type: Bug Reporter: Shwetha G S ReservedTypesRegistrar registers the models for supported integrations like hive, falcon, sqoop and storm. ReservedTypesRegistrar reads the model files and registers the types defined in the model file. The check thats done to verify if the model is already registered - checks for existence of first class type. This will not work if we add more class types to the existing model or modify the existing type to add optional attributes. ReservedTypesRegistrar should check for every type in the model file. Also, ReservedTypesRegistrar should do type update which does create if not exists, and update if exists -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1183) UI: help link should point to atlas website
Shwetha G S created ATLAS-1183: -- Summary: UI: help link should point to atlas website Key: ATLAS-1183 URL: https://issues.apache.org/jira/browse/ATLAS-1183 Project: Atlas Issue Type: Bug Reporter: Shwetha G S Fix For: 0.8-incubating Help link points to https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=ATLAS=Atlas+Home which requires login. Instead, link to http://atlas.incubator.apache.org/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1175) Type updates should allow removal of optional attributes
[ https://issues.apache.org/jira/browse/ATLAS-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15509085#comment-15509085 ] Shwetha G S commented on ATLAS-1175: Removing the optional attribute is not an issue as it doesn't surface in entity definition. The issue is if the user adds the removed attribute again - in this case, the entities which had the values for old attribute will re-surface again, which is not right. > Type updates should allow removal of optional attributes > > > Key: ATLAS-1175 > URL: https://issues.apache.org/jira/browse/ATLAS-1175 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating, 0.8-incubating >Reporter: Suma Shivaprasad >Assignee: Sarath Subramanian > > Currently optional attributes are not allowed to be removed from a given > type. This should be allowed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1145) Storm hook with kafka topic and hive bolt picks wrong hive table name
[ https://issues.apache.org/jira/browse/ATLAS-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15505532#comment-15505532 ] Shwetha G S commented on ATLAS-1145: Hemanth has one - https://github.com/yhemanth/storm-samples > Storm hook with kafka topic and hive bolt picks wrong hive table name > -- > > Key: ATLAS-1145 > URL: https://issues.apache.org/jira/browse/ATLAS-1145 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Sarath Subramanian > > Storm hook with kafka topic and hive bolt picks kafka topic name as hive > table name -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-1142) Lineage UI Improvement.
[ https://issues.apache.org/jira/browse/ATLAS-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502454#comment-15502454 ] Shwetha G S edited comment on ATLAS-1142 at 9/19/16 6:27 AM: - +1, Committed to master. Thanks Keval was (Author: shwethags): Committed to master. Thanks Keval > Lineage UI Improvement. > --- > > Key: ATLAS-1142 > URL: https://issues.apache.org/jira/browse/ATLAS-1142 > Project: Atlas > Issue Type: Improvement >Reporter: Nixon Rodrigues >Assignee: Keval Bhatt >Priority: Minor > Fix For: 0.8-incubating > > Attachments: ATLAS-1142.1.patch, ATLAS-1142.patch, Screen Shot > 2016-09-15 at 2.16.57 PM.png > > > Following improvement to be done in Lineage UI & entity detail page > * Lineage UI should be resizable. > * All the nodes to be shown in format *name (typename)* -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-712) Support getTrait() API
[ https://issues.apache.org/jira/browse/ATLAS-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-712. --- Resolution: Fixed Fix Version/s: 0.8-incubating Committed to master. Thanks Vimal for the patch, thanks Suma for the review > Support getTrait() API > -- > > Key: ATLAS-712 > URL: https://issues.apache.org/jira/browse/ATLAS-712 > Project: Atlas > Issue Type: Improvement >Reporter: Suma Shivaprasad >Assignee: Vimal Sharma > Fix For: 0.8-incubating > > Attachments: ATLAS-712-v2.patch, ATLAS-712-v3.patch, > ATLAS-712-v4.patch, ATLAS-712.patch > > > Given entity id and trait name, support rest API that returns the trait > instance for the entity. Currently, the other way of getting it is > getEntity() which returns full entity with all trait instances -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-712) Support getTrait() API
[ https://issues.apache.org/jira/browse/ATLAS-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-712: -- Attachment: ATLAS-712-v4.patch Attached patch with the minor fix for commit > Support getTrait() API > -- > > Key: ATLAS-712 > URL: https://issues.apache.org/jira/browse/ATLAS-712 > Project: Atlas > Issue Type: Improvement >Reporter: Suma Shivaprasad >Assignee: Vimal Sharma > Fix For: 0.8-incubating > > Attachments: ATLAS-712-v2.patch, ATLAS-712-v3.patch, > ATLAS-712-v4.patch, ATLAS-712.patch > > > Given entity id and trait name, support rest API that returns the trait > instance for the entity. Currently, the other way of getting it is > getEntity() which returns full entity with all trait instances -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-1179) Hive hook test failure
[
https://issues.apache.org/jira/browse/ATLAS-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S reassigned ATLAS-1179:
--
Assignee: Shwetha G S
> Hive hook test failure
> --
>
> Key: ATLAS-1179
> URL: https://issues.apache.org/jira/browse/ATLAS-1179
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Critical
>
> The build fails:
> {noformat}
> HiveHookIT.testAlterTableDropColumn:996 expected:<1> but was:<2>
>
> HiveHookIT.testCreateExternalTable:218->HiveITBase.assertTableIsRegistered:154->HiveITBase.assertEntityIsRegistered:160->HiveITBase.waitFor:204
> Assertions failed. Failing after waiting for timeout 8 msecs
>
> HiveHookIT.testInsertIntoTempTable:690->validateProcess:518->validateProcess:498->assertProcessIsRegistered:1662->HiveITBase.assertEntityIsRegistered:160->HiveITBase.waitFor:204
> Assertions failed. Failing after waiting for timeout 8 msecs
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-1179) Hive hook test failure
Shwetha G S created ATLAS-1179:
--
Summary: Hive hook test failure
Key: ATLAS-1179
URL: https://issues.apache.org/jira/browse/ATLAS-1179
Project: Atlas
Issue Type: Bug
Reporter: Shwetha G S
The build fails:
{noformat}
HiveHookIT.testAlterTableDropColumn:996 expected:<1> but was:<2>
HiveHookIT.testCreateExternalTable:218->HiveITBase.assertTableIsRegistered:154->HiveITBase.assertEntityIsRegistered:160->HiveITBase.waitFor:204
Assertions failed. Failing after waiting for timeout 8 msecs
HiveHookIT.testInsertIntoTempTable:690->validateProcess:518->validateProcess:498->assertProcessIsRegistered:1662->HiveITBase.assertEntityIsRegistered:160->HiveITBase.waitFor:204
Assertions failed. Failing after waiting for timeout 8 msecs
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-1155) Errors in Eclipse when I bring in the latest code
[ https://issues.apache.org/jira/browse/ATLAS-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502363#comment-15502363 ] Shwetha G S commented on ATLAS-1155: +1 > Errors in Eclipse when I bring in the latest code > - > > Key: ATLAS-1155 > URL: https://issues.apache.org/jira/browse/ATLAS-1155 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating >Reporter: David Radley >Assignee: David Radley > Fix For: 0.8-incubating > > Attachments: atlas1155.patch > > > I have brought the latest atlas code into an Eclipse environment and see an > error in GraphBackedDiscoveryService, > line 154 > scala.collection.immutable.List.empty()); it says method empty is ambiguous. > if I replace this expression with null it complies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1134) Full text search for "id" shows the blank screen in some case
[ https://issues.apache.org/jira/browse/ATLAS-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492818#comment-15492818 ] Shwetha G S commented on ATLAS-1134: I got the screen with 'No Record found!'. When does this issue happen? > Full text search for "id" shows the blank screen in some case > - > > Key: ATLAS-1134 > URL: https://issues.apache.org/jira/browse/ATLAS-1134 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Attachments: ATLAS-1134.patch > > > Step to reproduce - > 1.Search for "id" in full text. > 2.In case of entity Id is null, it doesn't shows the result, loader is > display on screen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
