[jira] [Commented] (ATLAS-145) DSL - Fix back reference DSL to gremlin translation issues

[Suma Shivaprasad (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14743407#comment-14743407
 ] 

Suma Shivaprasad commented on ATLAS-145:


We need to change the DSL to gremlin  translation here to 

g.V.has("typeName","DB").as("db").in("Table.db").back("db").and(_()has("name", 
T.eq, "Reporting")).map().toList()




> DSL - Fix back reference DSL to gremlin translation issues
> --
>
> Key: ATLAS-145
> URL: https://issues.apache.org/jira/browse/ATLAS-145
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>
> GremlinQuery.scala
> /*
>  * TODO
>  * Translation Issues:
>  * 1. back references in filters. For e.g. testBackreference: 'DB as db 
> Table where (db.name = "Reporting")'
>  *this is translated to:
>  * 
> g.V.has("typeName","DB").as("db").in("Table.db").and(_().back("db").has("name",
>  T.eq, "Reporting")).map().toList()
>  * But the '_().back("db") within the and is ignored, the has condition 
> is applied on the current element.
>  * The solution is to to do predicate pushdown and apply the filter 
> immediately on top of the referred Expression.
>  */



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ATLAS-145) DSL - Fix back reference DSL to gremlin translation issues

[Suma Shivaprasad (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14743407#comment-14743407
 ] 

Suma Shivaprasad edited comment on ATLAS-145 at 9/14/15 11:50 AM:
--

We need to change the DSL to gremlin  translation here to 

g.V.has("typeName","DB").as("db").in("Table.db").back("db").and(_()has("name", 
T.eq, "Reporting")).map().toList()


Working query: 
g.V().has("__typeName", 
"DB").as("db1").in("__Table.db").back("db1").and(_().has("DB.name", T.eq, 
"Reporting")).map.toList()




was (Author: suma.shivaprasad):
We need to change the DSL to gremlin  translation here to 

g.V.has("typeName","DB").as("db").in("Table.db").back("db").and(_()has("name", 
T.eq, "Reporting")).map().toList()




> DSL - Fix back reference DSL to gremlin translation issues
> --
>
> Key: ATLAS-145
> URL: https://issues.apache.org/jira/browse/ATLAS-145
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>
> GremlinQuery.scala
> /*
>  * TODO
>  * Translation Issues:
>  * 1. back references in filters. For e.g. testBackreference: 'DB as db 
> Table where (db.name = "Reporting")'
>  *this is translated to:
>  * 
> g.V.has("typeName","DB").as("db").in("Table.db").and(_().back("db").has("name",
>  T.eq, "Reporting")).map().toList()
>  * But the '_().back("db") within the and is ignored, the has condition 
> is applied on the current element.
>  * The solution is to to do predicate pushdown and apply the filter 
> immediately on top of the referred Expression.
>  */



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ATLAS-145) DSL - Fix back reference DSL to gremlin translation issues

[Suma Shivaprasad (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14743407#comment-14743407
 ] 

Suma Shivaprasad edited comment on ATLAS-145 at 9/14/15 11:52 AM:
--

We need to change the DSL to gremlin  translation here to 

g.V.has("typeName","DB").as("db").in("Table.db").back("db").and(_()has("name", 
T.eq, "Reporting")).map().toList()


Working query: 
g.V().has("__typeName", 
"DB").as("db1").in("__Table.db").back("db1").and(_().has("DB.name", T.eq, 
"Reporting")).map.toList()

discoveryService.searchByGremlin("L:{_var_0 = [] as 
Set;g.V().has(\"__typeName\", 
\"DB\").fill(_var_0);g.V().has(\"__superTypeNames\", 
\"DB\").fill(_var_0);_var_0._().as(\"db1\").in(\"__Table.db\").back(\"db1\").and(_().has(\"DB.name\",
 T.eq, \"Reporting\")).map.toList()}") works



was (Author: suma.shivaprasad):
We need to change the DSL to gremlin  translation here to 

g.V.has("typeName","DB").as("db").in("Table.db").back("db").and(_()has("name", 
T.eq, "Reporting")).map().toList()


Working query: 
g.V().has("__typeName", 
"DB").as("db1").in("__Table.db").back("db1").and(_().has("DB.name", T.eq, 
"Reporting")).map.toList()



> DSL - Fix back reference DSL to gremlin translation issues
> --
>
> Key: ATLAS-145
> URL: https://issues.apache.org/jira/browse/ATLAS-145
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>
> GremlinQuery.scala
> /*
>  * TODO
>  * Translation Issues:
>  * 1. back references in filters. For e.g. testBackreference: 'DB as db 
> Table where (db.name = "Reporting")'
>  *this is translated to:
>  * 
> g.V.has("typeName","DB").as("db").in("Table.db").and(_().back("db").has("name",
>  T.eq, "Reporting")).map().toList()
>  * But the '_().back("db") within the and is ignored, the has condition 
> is applied on the current element.
>  * The solution is to to do predicate pushdown and apply the filter 
> immediately on top of the referred Expression.
>  */



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ATLAS-145) DSL - Fix back reference DSL to gremlin translation issues

[Suma Shivaprasad (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14743407#comment-14743407
 ] 

Suma Shivaprasad edited comment on ATLAS-145 at 9/14/15 11:53 AM:
--

We need to change the DSL to gremlin  translation here to 

g.V.has("typeName","DB").as("db").in("Table.db").back("db").and(_()has("name", 
T.eq, "Reporting")).map().toList()


Working query: 
g.V().has("__typeName", 
"DB").as("db1").in("__Table.db").back("db1").and(_().has("DB.name", T.eq, 
"Reporting")).map.toList()

discoveryService.searchByGremlin(
{noformat}
"L:{_var_0 = [] as Set;g.V().has(\"__typeName\", 
\"DB\").fill(_var_0);g.V().has(\"__superTypeNames\", 
\"DB\").fill(_var_0);_var_0._().as(\"db1\").in(\"__Table.db\").back(\"db1\").and(_().has(\"DB.name\",
 T.eq, \"Reporting\")).map.toList()}")
{noformat}
 works



was (Author: suma.shivaprasad):
We need to change the DSL to gremlin  translation here to 

g.V.has("typeName","DB").as("db").in("Table.db").back("db").and(_()has("name", 
T.eq, "Reporting")).map().toList()


Working query: 
g.V().has("__typeName", 
"DB").as("db1").in("__Table.db").back("db1").and(_().has("DB.name", T.eq, 
"Reporting")).map.toList()

discoveryService.searchByGremlin("L:{_var_0 = [] as 
Set;g.V().has(\"__typeName\", 
\"DB\").fill(_var_0);g.V().has(\"__superTypeNames\", 
\"DB\").fill(_var_0);_var_0._().as(\"db1\").in(\"__Table.db\").back(\"db1\").and(_().has(\"DB.name\",
 T.eq, \"Reporting\")).map.toList()}") works


> DSL - Fix back reference DSL to gremlin translation issues
> --
>
> Key: ATLAS-145
> URL: https://issues.apache.org/jira/browse/ATLAS-145
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>
> GremlinQuery.scala
> /*
>  * TODO
>  * Translation Issues:
>  * 1. back references in filters. For e.g. testBackreference: 'DB as db 
> Table where (db.name = "Reporting")'
>  *this is translated to:
>  * 
> g.V.has("typeName","DB").as("db").in("Table.db").and(_().back("db").has("name",
>  T.eq, "Reporting")).map().toList()
>  * But the '_().back("db") within the and is ignored, the has condition 
> is applied on the current element.
>  * The solution is to to do predicate pushdown and apply the filter 
> immediately on top of the referred Expression.
>  */



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-162) Full text search

[darshan kumar (JIRA)]

darshan kumar created ATLAS-162:
---

 Summary: Full text search 
 Key: ATLAS-162
 URL: https://issues.apache.org/jira/browse/ATLAS-162
 Project: Atlas
  Issue Type: Task
Reporter: darshan kumar
Assignee: darshan kumar






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-156) Login Screen

[Anilsg (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14743841#comment-14743841
 ] 

Anilsg commented on ATLAS-156:
--

Please Do Apply the patch for  "[ATLAS-155,HDPDGI-154]- resolved merge conflict 
- image does not show… " 
Then Do apply the Login patch "[ATLAS-156, HDPDGI-88_1] Login Screen "

> Login Screen
> 
>
> Key: ATLAS-156
> URL: https://issues.apache.org/jira/browse/ATLAS-156
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.6-incubating
>Reporter: Anilsg
>  Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-156-v0.patch
>
>
> Login Screen



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 38341: Provide Entity Change Notification

[Shwetha GS]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/38341/#review98834
---



notification/src/main/java/org/apache/atlas/notification/entity/Entity.java 
(line 25)


Users are already exposed to the type system and its classes. Referenceable 
in this case. We can use that itself instead of adding another interface



repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java 
(line 469)


Move to another file



repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java 
(line 473)


Everywhere else, jettison json is used. Lets re-use it


- Shwetha GS


On Sept. 14, 2015, 4:08 a.m., Tom Beerbower wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/38341/
> ---
> 
> (Updated Sept. 14, 2015, 4:08 a.m.)
> 
> 
> Review request for atlas, John Speidel and Shwetha GS.
> 
> 
> Bugs: ATLAS-158
> https://issues.apache.org/jira/browse/ATLAS-158
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Add entity change notification to Atlas based using the existing 
> atlas-notification module.
> 
> First cut at a patch for the Atlas entity change notification.  Note that at 
> a minimum additional unit tests are required.  I'm putting up the review to 
> get some initial feedback.
> 
> 
> Diffs
> -
> 
>   notification/src/main/java/org/apache/atlas/notification/entity/Entity.java 
> PRE-CREATION 
>   
> notification/src/main/java/org/apache/atlas/notification/entity/EntityChangeConsumer.java
>  PRE-CREATION 
>   
> notification/src/main/java/org/apache/atlas/notification/entity/EntityChangeListener.java
>  PRE-CREATION 
>   
> notification/src/main/java/org/apache/atlas/notification/entity/EntityImpl.java
>  PRE-CREATION 
>   
> notification/src/main/java/org/apache/atlas/notification/entity/EntityNotification.java
>  PRE-CREATION 
>   notification/src/main/java/org/apache/atlas/notification/entity/Trait.java 
> PRE-CREATION 
>   
> notification/src/main/java/org/apache/atlas/notification/entity/TraitImpl.java
>  PRE-CREATION 
>   
> notification/src/test/java/org/apache/atlas/notification/entity/EntityImplTest.java
>  PRE-CREATION 
>   
> notification/src/test/java/org/apache/atlas/notification/entity/TraitImplTest.java
>  PRE-CREATION 
>   repository/pom.xml 8e4d0f3 
>   repository/src/main/java/org/apache/atlas/RepositoryMetadataModule.java 
> fbd01de 
>   
> repository/src/main/java/org/apache/atlas/listener/EntityChangeListener.java 
> f58d6de 
>   
> repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java
>  56168db 
> 
> Diff: https://reviews.apache.org/r/38341/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> All existing tests pass.
> 
> New unit tests added (more required).
> 
> 
> Thanks,
> 
> Tom Beerbower
> 
>

[jira] [Commented] (ATLAS-156) Login Screen

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14743818#comment-14743818
 ] 

ASF GitHub Bot commented on ATLAS-156:
--

GitHub user AnilGayakwad opened a pull request:

https://github.com/apache/incubator-atlas/pull/10

[ATLAS-156, HDPDGI-88_1] Login Screen



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MPR-Global/incubator-atlas HDPDGI-88_1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/10.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #10


commit e5830233c95e2e859ed1fd62de82102c87633374
Author: DarshanKumar 
Date:   2015-09-12T06:15:00Z

[ATLAS-155,HDPDGI-154]- resolved merge conflict - image does not show up on 
dashboard

commit 6cd91bcdc9080065b424c5ea12e2f6ba1c9e4f1b
Author: Vishal Kadam 
Date:   2015-09-13T03:33:46Z

[ATLAS-156,HDPDGI-88_1] Login Screen




> Login Screen
> 
>
> Key: ATLAS-156
> URL: https://issues.apache.org/jira/browse/ATLAS-156
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.6-incubating
>Reporter: Anilsg
> Fix For: 0.6-incubating
>
>
> Login Screen



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 38341: Provide Entity Change Notification

[John Speidel]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/38341/#review98843
---

Ship it!


Looks good.
Not really an issue with this patch as much as the existing code, I am a little 
concerned about the use of a single exception type "AtlasException" everywhere. 
Using a single exception type results in the loss of context when an exception 
occurs and will likely result in messy, incomplete or even incorrect error 
handling in the future.
This was an issue in Ambari and would we should start thinking about this early 
on in this project before we get to a point where we can't change it.


notification/src/main/java/org/apache/atlas/notification/entity/EntityChangeConsumer.java
 (line 62)


description missing regarding when this exception will be thrown



notification/src/main/java/org/apache/atlas/notification/entity/EntityChangeConsumer.java
 (line 136)


Consider using parameterized logging args which would allow for the removal 
of the if(isLevel) check.

LOG.debug("Logging event for entity : guid={} : operation={} : values={}", 
entity.getId(), operationType, values);



notification/src/main/java/org/apache/atlas/notification/entity/EntityChangeConsumer.java
 (line 153)


default block with log message?



notification/src/main/java/org/apache/atlas/notification/entity/EntityImpl.java 
(line 83)


Could any of these fields be null?  If not, the constructor doesn't enforce 
this invariant.



notification/src/main/java/org/apache/atlas/notification/entity/EntityImpl.java 
(line 90)


could any of these fields be null?



repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java 
(line 601)


seems odd that an exception is thrown from this method?


- John Speidel


On Sept. 14, 2015, 4:08 a.m., Tom Beerbower wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/38341/
> ---
> 
> (Updated Sept. 14, 2015, 4:08 a.m.)
> 
> 
> Review request for atlas, John Speidel and Shwetha GS.
> 
> 
> Bugs: ATLAS-158
> https://issues.apache.org/jira/browse/ATLAS-158
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Add entity change notification to Atlas based using the existing 
> atlas-notification module.
> 
> First cut at a patch for the Atlas entity change notification.  Note that at 
> a minimum additional unit tests are required.  I'm putting up the review to 
> get some initial feedback.
> 
> 
> Diffs
> -
> 
>   notification/src/main/java/org/apache/atlas/notification/entity/Entity.java 
> PRE-CREATION 
>   
> notification/src/main/java/org/apache/atlas/notification/entity/EntityChangeConsumer.java
>  PRE-CREATION 
>   
> notification/src/main/java/org/apache/atlas/notification/entity/EntityChangeListener.java
>  PRE-CREATION 
>   
> notification/src/main/java/org/apache/atlas/notification/entity/EntityImpl.java
>  PRE-CREATION 
>   
> notification/src/main/java/org/apache/atlas/notification/entity/EntityNotification.java
>  PRE-CREATION 
>   notification/src/main/java/org/apache/atlas/notification/entity/Trait.java 
> PRE-CREATION 
>   
> notification/src/main/java/org/apache/atlas/notification/entity/TraitImpl.java
>  PRE-CREATION 
>   
> notification/src/test/java/org/apache/atlas/notification/entity/EntityImplTest.java
>  PRE-CREATION 
>   
> notification/src/test/java/org/apache/atlas/notification/entity/TraitImplTest.java
>  PRE-CREATION 
>   repository/pom.xml 8e4d0f3 
>   repository/src/main/java/org/apache/atlas/RepositoryMetadataModule.java 
> fbd01de 
>   
> repository/src/main/java/org/apache/atlas/listener/EntityChangeListener.java 
> f58d6de 
>   
> repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java
>  56168db 
> 
> Diff: https://reviews.apache.org/r/38341/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> All existing tests pass.
> 
> New unit tests added (more required).
> 
> 
> Thanks,
> 
> Tom Beerbower
> 
>

[jira] [Updated] (ATLAS-163) New Trait UI (Tag)

[Erik Bergenholtz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erik Bergenholtz updated ATLAS-163:
---
Priority: Critical  (was: Major)

> New Trait UI (Tag)
> --
>
> Key: ATLAS-163
> URL: https://issues.apache.org/jira/browse/ATLAS-163
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Vishal Kadam
>Priority: Critical
> Fix For: 0.6-incubating
>
> Attachments: TagDefinition.png
>
>
> Atlas needs a UI to create new Tag definitions.
> See attached screen-shots.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-163) New Trait UI (Tag)

[Erik Bergenholtz (JIRA)]

Erik Bergenholtz created ATLAS-163:
--

 Summary: New Trait UI (Tag)
 Key: ATLAS-163
 URL: https://issues.apache.org/jira/browse/ATLAS-163
 Project: Atlas
  Issue Type: Improvement
Affects Versions: 0.6-incubating
Reporter: Erik Bergenholtz
Assignee: Vishal Kadam
 Fix For: 0.6-incubating


Atlas needs a UI to create new Tag definitions.

See attached screen-shots.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-163) New Trait UI (Tag)

[Erik Bergenholtz (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14744182#comment-14744182
 ] 

Erik Bergenholtz commented on ATLAS-163:


To create a Tag definition, make the following API call [example]:

{code}
POST http://c6401.ambari.apache.org:21000/api/atlas/types
{
  "enumTypes":[

  ],
  "structTypes":[

  ],
  "traitTypes":[
{
  "superTypes":[

  ],
  "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.TraitType",
  "typeName”:"PII",
  "attributeDefinitions":[
{
  "name":"name",
  "dataTypeName":"string",
  "multiplicity":"optional",
  "isComposite":false,
  "isUnique":false,
  "isIndexable":true,
  "reverseAttributeName":null
},
{
  "name":"description",
  "dataTypeName":"string",
  "multiplicity":"optional",
  "isComposite":false,
  "isUnique":false,
  "isIndexable":true,
  "reverseAttributeName":null
}
  ]
}
  ],
  "classTypes":[

  ]
}

{code}
Another example JSON body which creates a tag that inherits from another tag:
{code}
  "enumTypes":[

  ],
  "structTypes":[

  ],
  "traitTypes":[
{
  "superTypes":[
  “PII"
  ],
  "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.TraitType",
  "typeName":"Sub",
  "attributeDefinitions":[
{
  "name":"property1",
  "dataTypeName":"string",
  "multiplicity":"optional",
  "isComposite":false,
  "isUnique":false,
  "isIndexable":true,
  "reverseAttributeName":null
},
{
  "name":"property2",
  "dataTypeName":"string",
  "multiplicity":"optional",
  "isComposite":false,
  "isUnique":false,
  "isIndexable":true,
  "reverseAttributeName":null
}
  ]
}
  ],
  "classTypes":[

  ]
}
{code}

To Associate a trait with an Entity, here’s an example call:

{code}
POST 
http://c6401.ambari.apache.org:21000/api/atlas/entities/068c092f-7e49-4f48-b34e-86908cd6c3f6/traits
{
  "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
  "typeName":"Sub",
  "values":{
"name":"Test Traitx",
"description":"Test Traitx",   
"property1":"v1",
"property2":"v2"   
  }
}

> New Trait UI (Tag)
> --
>
> Key: ATLAS-163
> URL: https://issues.apache.org/jira/browse/ATLAS-163
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Vishal Kadam
> Fix For: 0.6-incubating
>
> Attachments: TagDefinition.png
>
>
> Atlas needs a UI to create new Tag definitions.
> See attached screen-shots.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ATLAS-163) New Trait UI (Tag)

[Erik Bergenholtz (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14744182#comment-14744182
 ] 

Erik Bergenholtz edited comment on ATLAS-163 at 9/14/15 8:22 PM:
-

To create a Tag definition, make the following API call [example]:

{code}
POST http://c6401.ambari.apache.org:21000/api/atlas/types
{
  "enumTypes":[

  ],
  "structTypes":[

  ],
  "traitTypes":[
{
  "superTypes":[

  ],
  "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.TraitType",
  "typeName”:"PII",
  "attributeDefinitions":[
{
  "name":"name",
  "dataTypeName":"string",
  "multiplicity":"optional",
  "isComposite":false,
  "isUnique":false,
  "isIndexable":true,
  "reverseAttributeName":null
},
{
  "name":"description",
  "dataTypeName":"string",
  "multiplicity":"optional",
  "isComposite":false,
  "isUnique":false,
  "isIndexable":true,
  "reverseAttributeName":null
}
  ]
}
  ],
  "classTypes":[

  ]
}

{code}
Another example JSON body which creates a tag that inherits from another tag:
{code}
  "enumTypes":[

  ],
  "structTypes":[

  ],
  "traitTypes":[
{
  "superTypes":[
  “PII"
  ],
  "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.TraitType",
  "typeName":"Sub",
  "attributeDefinitions":[
{
  "name":"property1",
  "dataTypeName":"string",
  "multiplicity":"optional",
  "isComposite":false,
  "isUnique":false,
  "isIndexable":true,
  "reverseAttributeName":null
},
{
  "name":"property2",
  "dataTypeName":"string",
  "multiplicity":"optional",
  "isComposite":false,
  "isUnique":false,
  "isIndexable":true,
  "reverseAttributeName":null
}
  ]
}
  ],
  "classTypes":[

  ]
}
{code}

To Associate a trait with an Entity, here’s an example call:

{code}
POST 
http://c6401.ambari.apache.org:21000/api/atlas/entities/068c092f-7e49-4f48-b34e-86908cd6c3f6/traits
{
  "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
  "typeName":"Sub",
  "values":{
"name":"Test Traitx",
"description":"Test Traitx",   
"property1":"v1",
"property2":"v2"   
  }
}
{code}


was (Author: bergenholtz):
To create a Tag definition, make the following API call [example]:

{code}
POST http://c6401.ambari.apache.org:21000/api/atlas/types
{
  "enumTypes":[

  ],
  "structTypes":[

  ],
  "traitTypes":[
{
  "superTypes":[

  ],
  "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.TraitType",
  "typeName”:"PII",
  "attributeDefinitions":[
{
  "name":"name",
  "dataTypeName":"string",
  "multiplicity":"optional",
  "isComposite":false,
  "isUnique":false,
  "isIndexable":true,
  "reverseAttributeName":null
},
{
  "name":"description",
  "dataTypeName":"string",
  "multiplicity":"optional",
  "isComposite":false,
  "isUnique":false,
  "isIndexable":true,
  "reverseAttributeName":null
}
  ]
}
  ],
  "classTypes":[

  ]
}

{code}
Another example JSON body which creates a tag that inherits from another tag:
{code}
  "enumTypes":[

  ],
  "structTypes":[

  ],
  "traitTypes":[
{
  "superTypes":[
  “PII"
  ],
  "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.TraitType",
  "typeName":"Sub",
  "attributeDefinitions":[
{
  "name":"property1",
  "dataTypeName":"string",
  "multiplicity":"optional",
  "isComposite":false,
  "isUnique":false,
  "isIndexable":true,
  "reverseAttributeName":null
},
{
  "name":"property2",
  "dataTypeName":"string",
  "multiplicity":"optional",
  "isComposite":false,
  "isUnique":false,
  "isIndexable":true,
  "reverseAttributeName":null
}
  ]
}
  ],
  "classTypes":[

  ]
}
{code}

To Associate a trait with an Entity, here’s an example call:

{code}
POST 
http://c6401.ambari.apache.org:21000/api/atlas/entities/068c092f-7e49-4f48-b34e-86908cd6c3f6/traits
{
  "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
  "typeName":"Sub",
  "values":{
"name":"Test Traitx",
"description":"Test Traitx",   
"property1":"v1",
"property2":"v2"   
  }
}

> New Trait UI (Tag)
> --
>
> Key: ATLAS-163
> URL: https://issues.apache.org/jira/browse/ATLAS-163
> Project: Atlas
>  Issue Type: Improvement
>Affects 

[jira] [Updated] (ATLAS-164) DFS addon for Atlas

[JIRA]

 [ 
https://issues.apache.org/jira/browse/ATLAS-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rémy SAISSY updated ATLAS-164:
--
Attachment: ATLAS-164.15092015.patch

> DFS addon for Atlas
> ---
>
> Key: ATLAS-164
> URL: https://issues.apache.org/jira/browse/ATLAS-164
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.6-incubating
>Reporter: Rémy SAISSY
> Attachments: ATLAS-164.15092015.patch
>
>
> Hi,
> I have wrote an addon for sending DFS metadata into Atlas.
> The patch is attached.
> However, I have a hard time getting the unit tests working properly thus some 
> advices would be welcome.
> Thanks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-166) DSL - Fix select with joins

[Suma Shivaprasad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Suma Shivaprasad updated ATLAS-166:
---
Description: 
"Table as t, sd, Column as c where t.name=\"sales_fact\" select c.name as 
colName, c.dataType as colType"

is translated to 

{noformat}
L:{_var_0 = [] as Set;g.V().has("__typeName", 
"Table").fill(_var_0);g.V().has("__superTypeNames", 
"Table").fill(_var_0);_var_0._().as("t").out("__Table.sd").in("__Column.sd").as("c").and(_().back("t").has("Table.name",
 T.eq, 
"sales_fact")).as("_src1").select(["c"]){[it."Column.name",it."Column.dataType"]}.toList()}
{noformat}

Even after fix for ATLAS-144  which fixes the back reference , select (["c"]) 
doesnt work and throws an error
{noformat} 
L:{_var_0 = [] as Set;g.V().has("__typeName", 
"Table").fill(_var_0);g.V().has("__superTypeNames", 
"Table").fill(_var_0);_var_0._().as("t").out("__Table.sd").in("__Column.sd").as("c").back("t")
 and(_().has("Table.name", T.eq, 
"sales_fact")).as("_src1").select(["c"]){[it."Column.name",it."Column.dataType"]}.toList()}
{noformat}

  was:
"Table as t, sd, Column as c where t.name=\"sales_fact\" select c.name as 
colName, c.dataType as colType"

is translated to 

{noformat}
L:{_var_0 = [] as Set;g.V().has("__typeName", 
"Table").fill(_var_0);g.V().has("__superTypeNames", 
"Table").fill(_var_0);_var_0._().as("t").out("__Table.sd").in("__Column.sd").as("c").and(_().back("t").has("Table.name",
 T.eq, 
"sales_fact")).as("_src1").select(["c"]){[it."Column.name",it."Column.dataType"]}.toList()}
{noformat}

Even after fix for ATLAS-144,
{noformat} 
L:{_var_0 = [] as Set;g.V().has("__typeName", 
"Table").fill(_var_0);g.V().has("__superTypeNames", 
"Table").fill(_var_0);_var_0._().as("t").out("__Table.sd").in("__Column.sd").as("c").back("t")
 and(_().has("Table.name", T.eq, 
"sales_fact")).as("_src1").select(["c"]){[it."Column.name",it."Column.dataType"]}.toList()}
{noformat}


> DSL - Fix select with joins
> ---
>
> Key: ATLAS-166
> URL: https://issues.apache.org/jira/browse/ATLAS-166
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>
> "Table as t, sd, Column as c where t.name=\"sales_fact\" select c.name as 
> colName, c.dataType as colType"
> is translated to 
> {noformat}
> L:{_var_0 = [] as Set;g.V().has("__typeName", 
> "Table").fill(_var_0);g.V().has("__superTypeNames", 
> "Table").fill(_var_0);_var_0._().as("t").out("__Table.sd").in("__Column.sd").as("c").and(_().back("t").has("Table.name",
>  T.eq, 
> "sales_fact")).as("_src1").select(["c"]){[it."Column.name",it."Column.dataType"]}.toList()}
> {noformat}
> Even after fix for ATLAS-144  which fixes the back reference , select (["c"]) 
> doesnt work and throws an error
> {noformat} 
> L:{_var_0 = [] as Set;g.V().has("__typeName", 
> "Table").fill(_var_0);g.V().has("__superTypeNames", 
> "Table").fill(_var_0);_var_0._().as("t").out("__Table.sd").in("__Column.sd").as("c").back("t")
>  and(_().has("Table.name", T.eq, 
> "sales_fact")).as("_src1").select(["c"]){[it."Column.name",it."Column.dataType"]}.toList()}
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-166) DSL - Fix select with joins

[Suma Shivaprasad (JIRA)]

Suma Shivaprasad created ATLAS-166:
--

 Summary: DSL - Fix select with joins
 Key: ATLAS-166
 URL: https://issues.apache.org/jira/browse/ATLAS-166
 Project: Atlas
  Issue Type: Bug
Reporter: Suma Shivaprasad


"Table as t, sd, Column as c where t.name=\"sales_fact\" select c.name as 
colName, c.dataType as colType"

is translated to 

{noformat}
L:{_var_0 = [] as Set;g.V().has("__typeName", 
"Table").fill(_var_0);g.V().has("__superTypeNames", 
"Table").fill(_var_0);_var_0._().as("t").out("__Table.sd").in("__Column.sd").as("c").and(_().back("t").has("Table.name",
 T.eq, 
"sales_fact")).as("_src1").select(["c"]){[it."Column.name",it."Column.dataType"]}.toList()}
{noformat}

Even after fix for ATLAS-144,
{noformat} 
L:{_var_0 = [] as Set;g.V().has("__typeName", 
"Table").fill(_var_0);g.V().has("__superTypeNames", 
"Table").fill(_var_0);_var_0._().as("t").out("__Table.sd").in("__Column.sd").as("c").back("t")
 and(_().has("Table.name", T.eq, 
"sales_fact")).as("_src1").select(["c"]){[it."Column.name",it."Column.dataType"]}.toList()}
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-159) UI generated files should be target

[Vishal Kadam (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14744821#comment-14744821
 ] 

Vishal Kadam commented on ATLAS-159:


If final goal is to add all this files under war generate by webapp, then isn't 
it good to have it under same umbrella? Otherwise it will create unnecessary 
module dependency.

> UI generated files should be target
> ---
>
> Key: ATLAS-159
> URL: https://issues.apache.org/jira/browse/ATLAS-159
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Sanjay Patel
>Priority: Blocker
>
> All the downloaded/generated files(like folders lib, node, node_modules etc) 
> from UI plugins should be in target so that mvn clean can clean up these 
> files. Build is broken because of this: 
> https://builds.apache.org/job/apache-atlas-nightly/72/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-30) GraphBackedDiscoveryServiceTest.testSearchByDSLQueries

[Suma Shivaprasad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Suma Shivaprasad updated ATLAS-30:
--
Summary: GraphBackedDiscoveryServiceTest.testSearchByDSLQueries  (was: 
GraphBackedDiscoveryServiceTest.testSearchByDSLQueries and 
GraphRepoMapperScaleTest.testSearchIndex should assert on number of results per 
query)

> GraphBackedDiscoveryServiceTest.testSearchByDSLQueries
> --
>
> Key: ATLAS-30
> URL: https://issues.apache.org/jira/browse/ATLAS-30
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
>
> Currently , the tests are accepting only the input query in the dataprovider, 
> they should accept both input query and expected number of rows. 
> Also all the queries running are returning query 0 rows. This needs to be 
> investigated and fixed.
> query [from DB] returned [0] rows
> query [DB] returned [0] rows
> query [DB where DB.name="Reporting"] returned [0] rows
> query [DB DB.name = "Reporting"] returned [0] rows
> query [DB where DB.name="Reporting" select name, owner] returned [0] rows
> query [DB has name] returned [0] rows
> query [DB, Table] returned [0] rows
> query [DB is JdbcAccess] returned [0] rows
> query [from Table] returned [0] rows
> query [Table] returned [0] rows
> query [Table is Dimension] returned [0] rows
> query [Column where Column isa PII] returned [0] rows
> query [View is Dimension] returned [0] rows
> query [Column select Column.name] returned [0] rows
> query [Column select name] returned [0] rows
> query [Column where Column.name="customer_id"] returned [0] rows
> query [from Table select Table.name] returned [0] rows
> query [DB where (name = "Reporting")] returned [0] rows
> query [DB where (name = "Reporting") select name as _col_0, owner as _col_1] 
> returned [0] rows
> query [DB where DB is JdbcAccess] returned [0] rows
> query [DB where DB has name] returned [0] rows
> query [DB Table] returned [0] rows
> query [DB where DB has name] returned [0] rows
> query [DB as db1 Table where (db1.name = "Reporting")] returned [0] rows
> query [DB where (name = "Reporting") select name as _col_0, (createTime + 1) 
> as _col_1 ] returned [0] rows
> query [Table where (name = "sales_fact" and created > 
> "2014-01-01T00:00:00.000Z" ) select name as _col_0, created as _col_1 ] 
> returned [0] rows
> query [Table where (name = "sales_fact" and created > 
> "2014-12-11T02:35:58.440Z" ) select name as _col_0, created as _col_1 ] 
> returned [0] rows
> query [Dimension] returned [0] rows
> query [JdbcAccess] returned [0] rows
> query [ETL] returned [0] rows
> query [Metric] returned [0] rows
> query [PII] returned [0] rows
> query [Table LoadProcess outputTable] returned [0] rows
> query [Table loop (LoadProcess outputTable)] returned [0] rows
> query [Table as _loop0 loop (LoadProcess outputTable) withPath] returned [0] 
> rows
> query [Table as src loop (LoadProcess outputTable) as dest select src.name as 
> srcTable, dest.name as destTable withPath] returned [0] rows
> query [Table as t, sd, Column as c where t.name="sales_fact" select c.name as 
> colName, c.dataType as colType] returned [0] rows
> query [Table where name='sales_fact', db where name='Reporting'] returned [0] 
> rows



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-165) GraphRepoMapperScaleTest.testSearchIndex - fix asserts

[Suma Shivaprasad (JIRA)]

Suma Shivaprasad created ATLAS-165:
--

 Summary: GraphRepoMapperScaleTest.testSearchIndex - fix asserts
 Key: ATLAS-165
 URL: https://issues.apache.org/jira/browse/ATLAS-165
 Project: Atlas
  Issue Type: Bug
Reporter: Suma Shivaprasad






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-165) GraphRepoMapperScaleTest.testSearchIndex - fix asserts

[Suma Shivaprasad (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14744801#comment-14744801
 ] 

Suma Shivaprasad commented on ATLAS-165:


GraphRepoMapperScaleTest is returning 0 rows for indexQuery . This needs to be 
investigated and asserts need to be fixed for number of results, types returned 
etc

> GraphRepoMapperScaleTest.testSearchIndex - fix asserts
> --
>
> Key: ATLAS-165
> URL: https://issues.apache.org/jira/browse/ATLAS-165
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-159) UI generated files should be target

[Shwetha G S (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14744820#comment-14744820
 ] 

Shwetha G S commented on ATLAS-159:
---

No, lets create a pom.xml in dashboard and move plugins in dashboard's pom.xml. 
You can then generate these files under dashboard/target

> UI generated files should be target
> ---
>
> Key: ATLAS-159
> URL: https://issues.apache.org/jira/browse/ATLAS-159
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Sanjay Patel
>Priority: Blocker
>
> All the downloaded/generated files(like folders lib, node, node_modules etc) 
> from UI plugins should be in target so that mvn clean can clean up these 
> files. Build is broken because of this: 
> https://builds.apache.org/job/apache-atlas-nightly/72/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-159) UI generated files should be target

[Shwetha G S (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14744836#comment-14744836
 ] 

Shwetha G S commented on ATLAS-159:
---

UI plugin fails sometimes and re-run goes through fine
{nofomat}
[INFO] --- frontend-maven-plugin:0.0.23:grunt (grunt dist) @ atlas-webapp ---
[INFO] Running 'grunt build --no-color' in 
/Users/sshivalingamurthy/git/atlas/dashboard
[INFO] Running "copy:dist" (copy) task
[INFO] Created 19 directories, copied 25 files
[INFO]
[INFO] Running "minify" task
[INFO]
[INFO] Running "shell:min" (shell) task
[ERROR] Error: Could not find or load main class 
org.angularjs.closurerunner.NgClosureRunner
[INFO] Warning: Command failed: Error: Could not find or load main class 
org.angularjs.closurerunner.NgClosureRunner
[INFO]  Use --force to continue.
[INFO]
[INFO] Aborted due to warnings.
[INFO] 
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Atlas Web Application ... FAILURE [ 32.434 s]
[INFO] Apache Atlas Documentation . SKIPPED
[INFO] Apache Atlas Hive Bridge ... SKIPPED
[INFO] Apache Atlas Distribution .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 33.691 s
[INFO] Finished at: 2015-09-15T10:30:23+05:30
[INFO] Final Memory: 69M/556M
[INFO] 
[ERROR] Failed to execute goal 
com.github.eirslett:frontend-maven-plugin:0.0.23:grunt (grunt dist) on project 
atlas-webapp: Failed to run task: 'grunt build --no-color' failed. (error code 
6) -> [Help 1]
[ERROR]
{noformat}

> UI generated files should be target
> ---
>
> Key: ATLAS-159
> URL: https://issues.apache.org/jira/browse/ATLAS-159
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Sanjay Patel
>Priority: Blocker
>
> All the downloaded/generated files(like folders lib, node, node_modules etc) 
> from UI plugins should be in target so that mvn clean can clean up these 
> files. Build is broken because of this: 
> https://builds.apache.org/job/apache-atlas-nightly/72/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ATLAS-159) UI generated files should be target

[Shwetha G S (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14744836#comment-14744836
 ] 

Shwetha G S edited comment on ATLAS-159 at 9/15/15 5:04 AM:


UI plugin fails sometimes and re-run goes through fine
{code}
[INFO] --- frontend-maven-plugin:0.0.23:grunt (grunt dist) @ atlas-webapp ---
[INFO] Running 'grunt build --no-color' in 
/Users/sshivalingamurthy/git/atlas/dashboard
[INFO] Running "copy:dist" (copy) task
[INFO] Created 19 directories, copied 25 files
[INFO]
[INFO] Running "minify" task
[INFO]
[INFO] Running "shell:min" (shell) task
[ERROR] Error: Could not find or load main class 
org.angularjs.closurerunner.NgClosureRunner
[INFO] Warning: Command failed: Error: Could not find or load main class 
org.angularjs.closurerunner.NgClosureRunner
[INFO]  Use --force to continue.
[INFO]
[INFO] Aborted due to warnings.
[INFO] 
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Atlas Web Application ... FAILURE [ 32.434 s]
[INFO] Apache Atlas Documentation . SKIPPED
[INFO] Apache Atlas Hive Bridge ... SKIPPED
[INFO] Apache Atlas Distribution .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 33.691 s
[INFO] Finished at: 2015-09-15T10:30:23+05:30
[INFO] Final Memory: 69M/556M
[INFO] 
[ERROR] Failed to execute goal 
com.github.eirslett:frontend-maven-plugin:0.0.23:grunt (grunt dist) on project 
atlas-webapp: Failed to run task: 'grunt build --no-color' failed. (error code 
6) -> [Help 1]
[ERROR]
{code}


was (Author: shwethags):
UI plugin fails sometimes and re-run goes through fine
{nofomat}
[INFO] --- frontend-maven-plugin:0.0.23:grunt (grunt dist) @ atlas-webapp ---
[INFO] Running 'grunt build --no-color' in 
/Users/sshivalingamurthy/git/atlas/dashboard
[INFO] Running "copy:dist" (copy) task
[INFO] Created 19 directories, copied 25 files
[INFO]
[INFO] Running "minify" task
[INFO]
[INFO] Running "shell:min" (shell) task
[ERROR] Error: Could not find or load main class 
org.angularjs.closurerunner.NgClosureRunner
[INFO] Warning: Command failed: Error: Could not find or load main class 
org.angularjs.closurerunner.NgClosureRunner
[INFO]  Use --force to continue.
[INFO]
[INFO] Aborted due to warnings.
[INFO] 
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Atlas Web Application ... FAILURE [ 32.434 s]
[INFO] Apache Atlas Documentation . SKIPPED
[INFO] Apache Atlas Hive Bridge ... SKIPPED
[INFO] Apache Atlas Distribution .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 33.691 s
[INFO] Finished at: 2015-09-15T10:30:23+05:30
[INFO] Final Memory: 69M/556M
[INFO] 
[ERROR] Failed to execute goal 
com.github.eirslett:frontend-maven-plugin:0.0.23:grunt (grunt dist) on project 
atlas-webapp: Failed to run task: 'grunt build --no-color' failed. (error code 
6) -> [Help 1]
[ERROR]
{noformat}

> UI generated files should be target
> ---
>
> Key: ATLAS-159
> URL: https://issues.apache.org/jira/browse/ATLAS-159
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Sanjay Patel
>Priority: Blocker
>
> All the downloaded/generated files(like folders lib, node, node_modules etc) 
> from UI plugins should be in target so that mvn clean can clean up these 
> files. Build is broken because of this: 
> https://builds.apache.org/job/apache-atlas-nightly/72/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (ATLAS-163) New Trait UI (Tag)

[darshan kumar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

darshan kumar reassigned ATLAS-163:
---

Assignee: darshan kumar  (was: Vishal Kadam)

> New Trait UI (Tag)
> --
>
> Key: ATLAS-163
> URL: https://issues.apache.org/jira/browse/ATLAS-163
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: darshan kumar
>Priority: Critical
> Fix For: 0.6-incubating
>
> Attachments: TagDefinition.png
>
>
> Atlas needs a UI to create new Tag definitions.
> See attached screen-shots.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (ATLAS-159) UI generated files should be target

[Sanjay Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjay Patel reassigned ATLAS-159:
--

Assignee: Sanjay Patel

> UI generated files should be target
> ---
>
> Key: ATLAS-159
> URL: https://issues.apache.org/jira/browse/ATLAS-159
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Sanjay Patel
>Priority: Blocker
>
> All the downloaded/generated files(like folders lib, node, node_modules etc) 
> from UI plugins should be in target so that mvn clean can clean up these 
> files. Build is broken because of this: 
> https://builds.apache.org/job/apache-atlas-nightly/72/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-167) DSL -Query Parsing of longs is incorrect

[Suma Shivaprasad (JIRA)]

Suma Shivaprasad created ATLAS-167:
--

 Summary: DSL -Query Parsing of longs is incorrect
 Key: ATLAS-167
 URL: https://issues.apache.org/jira/browse/ATLAS-167
 Project: Atlas
  Issue Type: Bug
Reporter: Suma Shivaprasad


{noformat}
Executing dslQuery = DB where DB.name="Reporting" and DB.createTime < 
1442295333994
org.apache.atlas.discovery.DiscoveryException: Invalid expression : DB where 
DB.name="Reporting" and DB.createTime < 1442295333994
at 
org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.evaluate(GraphBackedDiscoveryService.java:140)
at 
org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.searchByDSL(GraphBackedDiscoveryService.java:124)
at 
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:41)
at 
org.apache.atlas.discovery.GraphBackedDiscoveryServiceTest.testSearchByDSLQueries(GraphBackedDiscoveryServiceTest.java:253)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
at 
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
at org.testng.TestRunner.privateRun(TestRunner.java:757)
at org.testng.TestRunner.run(TestRunner.java:608)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
at org.testng.TestNG.run(TestNG.java:999)
at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:111)
at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:203)
at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:174)
at org.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:125)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
Caused by: java.lang.NumberFormatException: For input string: "1442295333994"
at 
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:495)
at java.lang.Integer.parseInt(Integer.java:527)
at 
org.apache.atlas.typesystem.types.DataTypes$IntType.convert(DataTypes.java:217)
at 
org.apache.atlas.typesystem.types.DataTypes$IntType.convert(DataTypes.java:199)
at 
org.apache.atlas.query.Expressions$Literal.(Expressions.scala:467)
at org.apache.atlas.query.Expressions$.literal(Expressions.scala:491)
at org.apache.atlas.query.Expressions$.int(Expressions.scala:499)
at 
org.apache.atlas.query.QueryParser$$anonfun$literal$2$$anonfun$apply$52.apply(QueryParser.scala:247)
at 
org.apache.atlas.query.QueryParser$$anonfun$literal$2$$anonfun$apply$52.apply(QueryParser.scala:247)
at scala.util.parsing.combinator.Parsers$Success.map(Parsers.scala:136)
at scala.util.parsing.combinator.Parsers$Success.map(Parsers.scala:135)
at 
scala.util.parsing.combinator.Parsers$Parser$$anonfun$map$1.apply(Parsers.scala:242)
at 
scala.util.parsing.combinator.Parsers$Parser$$anonfun$map$1.apply(Parsers.scala:242)
at 
scala.util.parsing.combinator.Parsers$$anon$3.apply(Parsers.scala:222)
at 
scala.util.parsing.combinator.Parsers$Parser$$anonfun$append$1$$anonfun$apply$2.apply(Parsers.scala:254)
at 
scala.util.parsing.combinator.Parsers$Parser$$anonfun$append$1$$anonfun$apply$2.apply(Parsers.scala:254)
at 

[jira] [Updated] (ATLAS-163) New Trait UI (Tag)

[Erik Bergenholtz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erik Bergenholtz updated ATLAS-163:
---
Attachment: TagDefinition.png

> New Trait UI (Tag)
> --
>
> Key: ATLAS-163
> URL: https://issues.apache.org/jira/browse/ATLAS-163
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Vishal Kadam
> Fix For: 0.6-incubating
>
> Attachments: TagDefinition.png
>
>
> Atlas needs a UI to create new Tag definitions.
> See attached screen-shots.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-159) UI generated files should be target

[Shwetha G S (JIRA)]

Shwetha G S created ATLAS-159:
-

 Summary: UI generated files should be target
 Key: ATLAS-159
 URL: https://issues.apache.org/jira/browse/ATLAS-159
 Project: Atlas
  Issue Type: Bug
Reporter: Shwetha G S
Priority: Blocker


All the downloaded/generated files(like folders lib, node, node_modules etc) 
from UI plugins should be in target so that mvn clean can clean up these files. 
Build is broken because of this: 
https://builds.apache.org/job/apache-atlas-nightly/72/





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-132) Search Controller Optimization

[Anilsg (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14743916#comment-14743916
 ] 

Anilsg commented on ATLAS-132:
--

http://162.212.133.190:3125/#!/search

> Search Controller Optimization
> --
>
> Key: ATLAS-132
> URL: https://issues.apache.org/jira/browse/ATLAS-132
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.5.1-incubating
>Reporter: Erik Bergenholtz
>Assignee: Rohit
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-132-v0.patch
>
>
> Search Controller currently makes multiple calls. This can and should be 
> optimized as a single API call.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-156) Login Screen

[Anilsg (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14743918#comment-14743918
 ] 

Anilsg commented on ATLAS-156:
--

http://162.212.133.190:3088/#!/login

> Login Screen
> 
>
> Key: ATLAS-156
> URL: https://issues.apache.org/jira/browse/ATLAS-156
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.6-incubating
>Reporter: Anilsg
>  Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-156-v0.patch
>
>
> Login Screen



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-132) Search Controller Optimization

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14743903#comment-14743903
 ] 

ASF GitHub Bot commented on ATLAS-132:
--

GitHub user AnilGayakwad opened a pull request:

https://github.com/apache/incubator-atlas/pull/11

[ATLAS-132, HDPDGI-125] - Search Controller Optimization



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MPR-Global/incubator-atlas HDPDGI-125_1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/11.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #11


commit 1a458eecac69cc443383dc2c9f856b925481090d
Author: Anilsg 
Date:   2015-09-13T16:00:24Z

[ATLAS-132, HDPDGI-125] - Search Controller Optimization




> Search Controller Optimization
> --
>
> Key: ATLAS-132
> URL: https://issues.apache.org/jira/browse/ATLAS-132
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.5.1-incubating
>Reporter: Erik Bergenholtz
>Assignee: Rohit
> Fix For: 0.6-incubating
>
>
> Search Controller currently makes multiple calls. This can and should be 
> optimized as a single API call.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-159) UI generated files should be target

[Vishal Kadam (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14743968#comment-14743968
 ] 

Vishal Kadam commented on ATLAS-159:


Should we move content of dashboard to 
https://github.com/apache/incubator-atlas/tree/master/webapp/src/main/webapp 
and then use target folder of webapp for all runtime dependencies like lib, 
node, node_module & bower related folder?

> UI generated files should be target
> ---
>
> Key: ATLAS-159
> URL: https://issues.apache.org/jira/browse/ATLAS-159
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Priority: Blocker
>
> All the downloaded/generated files(like folders lib, node, node_modules etc) 
> from UI plugins should be in target so that mvn clean can clean up these 
> files. Build is broken because of this: 
> https://builds.apache.org/job/apache-atlas-nightly/72/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-atlas pull request: [ATLAS-156, HDPDGI-88_1] Login Scree...

[AnilGayakwad]

GitHub user AnilGayakwad opened a pull request:

https://github.com/apache/incubator-atlas/pull/10

[ATLAS-156, HDPDGI-88_1] Login Screen



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MPR-Global/incubator-atlas HDPDGI-88_1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/10.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #10


commit e5830233c95e2e859ed1fd62de82102c87633374
Author: DarshanKumar 
Date:   2015-09-12T06:15:00Z

[ATLAS-155,HDPDGI-154]- resolved merge conflict - image does not show up on 
dashboard

commit 6cd91bcdc9080065b424c5ea12e2f6ba1c9e4f1b
Author: Vishal Kadam 
Date:   2015-09-13T03:33:46Z

[ATLAS-156,HDPDGI-88_1] Login Screen




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-atlas pull request: [ATLAS-132, HDPDGI-125] - Search Con...

[AnilGayakwad]

GitHub user AnilGayakwad opened a pull request:

https://github.com/apache/incubator-atlas/pull/11

[ATLAS-132, HDPDGI-125] - Search Controller Optimization



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MPR-Global/incubator-atlas HDPDGI-125_1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-atlas/pull/11.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #11


commit 1a458eecac69cc443383dc2c9f856b925481090d
Author: Anilsg 
Date:   2015-09-13T16:00:24Z

[ATLAS-132, HDPDGI-125] - Search Controller Optimization




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ATLAS-107) UI: Create Entities

[darshan kumar (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14743992#comment-14743992
 ] 

darshan kumar commented on ATLAS-107:
-

http://162.212.133.190:3113/#!/search [please click on plus sign  ], please 
review and team working on UI mockup.

Please let me know to send patch for this build.Thanks 

> UI: Create Entities
> ---
>
> Key: ATLAS-107
> URL: https://issues.apache.org/jira/browse/ATLAS-107
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.5.1-incubating
>Reporter: Erik Bergenholtz
>Assignee: darshan kumar
> Fix For: 0.6-incubating
>
>
> The Atlas UI needs to provide a means by which new Entities can be created 
> associated with known SuperTypes such as DB, Table, LoadProcess and Column.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (ATLAS-30) GraphBackedDiscoveryServiceTest.testSearchByDSLQueries and GraphRepoMapperScaleTest.testSearchIndex should assert on number of results per query

[Suma Shivaprasad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Suma Shivaprasad reassigned ATLAS-30:
-

Assignee: Suma Shivaprasad  (was: sandeep samudrala)

> GraphBackedDiscoveryServiceTest.testSearchByDSLQueries and 
> GraphRepoMapperScaleTest.testSearchIndex should assert on number of results 
> per query
> 
>
> Key: ATLAS-30
> URL: https://issues.apache.org/jira/browse/ATLAS-30
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
>
> Currently , the tests are accepting only the input query in the dataprovider, 
> they should accept both input query and expected number of rows. 
> Also all the queries running are returning query 0 rows. This needs to be 
> investigated and fixed.
> query [from DB] returned [0] rows
> query [DB] returned [0] rows
> query [DB where DB.name="Reporting"] returned [0] rows
> query [DB DB.name = "Reporting"] returned [0] rows
> query [DB where DB.name="Reporting" select name, owner] returned [0] rows
> query [DB has name] returned [0] rows
> query [DB, Table] returned [0] rows
> query [DB is JdbcAccess] returned [0] rows
> query [from Table] returned [0] rows
> query [Table] returned [0] rows
> query [Table is Dimension] returned [0] rows
> query [Column where Column isa PII] returned [0] rows
> query [View is Dimension] returned [0] rows
> query [Column select Column.name] returned [0] rows
> query [Column select name] returned [0] rows
> query [Column where Column.name="customer_id"] returned [0] rows
> query [from Table select Table.name] returned [0] rows
> query [DB where (name = "Reporting")] returned [0] rows
> query [DB where (name = "Reporting") select name as _col_0, owner as _col_1] 
> returned [0] rows
> query [DB where DB is JdbcAccess] returned [0] rows
> query [DB where DB has name] returned [0] rows
> query [DB Table] returned [0] rows
> query [DB where DB has name] returned [0] rows
> query [DB as db1 Table where (db1.name = "Reporting")] returned [0] rows
> query [DB where (name = "Reporting") select name as _col_0, (createTime + 1) 
> as _col_1 ] returned [0] rows
> query [Table where (name = "sales_fact" and created > 
> "2014-01-01T00:00:00.000Z" ) select name as _col_0, created as _col_1 ] 
> returned [0] rows
> query [Table where (name = "sales_fact" and created > 
> "2014-12-11T02:35:58.440Z" ) select name as _col_0, created as _col_1 ] 
> returned [0] rows
> query [Dimension] returned [0] rows
> query [JdbcAccess] returned [0] rows
> query [ETL] returned [0] rows
> query [Metric] returned [0] rows
> query [PII] returned [0] rows
> query [Table LoadProcess outputTable] returned [0] rows
> query [Table loop (LoadProcess outputTable)] returned [0] rows
> query [Table as _loop0 loop (LoadProcess outputTable) withPath] returned [0] 
> rows
> query [Table as src loop (LoadProcess outputTable) as dest select src.name as 
> srcTable, dest.name as destTable withPath] returned [0] rows
> query [Table as t, sd, Column as c where t.name="sales_fact" select c.name as 
> colName, c.dataType as colType] returned [0] rows
> query [Table where name='sales_fact', db where name='Reporting'] returned [0] 
> rows



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Review Request 38341: Provide Entity Change Notification

[Tom Beerbower]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/38341/
---

Review request for atlas, John Speidel and Shwetha GS.


Bugs: ATLAS-158
https://issues.apache.org/jira/browse/ATLAS-158


Repository: atlas


Description
---

Add entity change notification to Atlas based using the existing 
atlas-notification module.

First cut at a patch for the Atlas entity change notification.  Note that at a 
minimum additional unit tests are required.  I'm putting up the review to get 
some initial feedback.


Diffs
-

  notification/src/main/java/org/apache/atlas/notification/entity/Entity.java 
PRE-CREATION 
  
notification/src/main/java/org/apache/atlas/notification/entity/EntityChangeConsumer.java
 PRE-CREATION 
  
notification/src/main/java/org/apache/atlas/notification/entity/EntityChangeListener.java
 PRE-CREATION 
  
notification/src/main/java/org/apache/atlas/notification/entity/EntityImpl.java 
PRE-CREATION 
  
notification/src/main/java/org/apache/atlas/notification/entity/EntityNotification.java
 PRE-CREATION 
  notification/src/main/java/org/apache/atlas/notification/entity/Trait.java 
PRE-CREATION 
  
notification/src/main/java/org/apache/atlas/notification/entity/TraitImpl.java 
PRE-CREATION 
  
notification/src/test/java/org/apache/atlas/notification/entity/EntityImplTest.java
 PRE-CREATION 
  
notification/src/test/java/org/apache/atlas/notification/entity/TraitImplTest.java
 PRE-CREATION 
  repository/pom.xml 8e4d0f3 
  repository/src/main/java/org/apache/atlas/RepositoryMetadataModule.java 
fbd01de 
  repository/src/main/java/org/apache/atlas/listener/EntityChangeListener.java 
f58d6de 
  
repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java 
56168db 

Diff: https://reviews.apache.org/r/38341/diff/


Testing
---

mvn clean test

All existing tests pass.

New unit tests added (more required).


Thanks,

Tom Beerbower

[jira] [Created] (ATLAS-160) Move UI plugins from webapp to dashboard module

[Shwetha G S (JIRA)]

Shwetha G S created ATLAS-160:
-

 Summary: Move UI plugins from webapp to dashboard module
 Key: ATLAS-160
 URL: https://issues.apache.org/jira/browse/ATLAS-160
 Project: Atlas
  Issue Type: Bug
Reporter: Shwetha G S


Currently, the UI plugins are defined in webapp's pom.xml. They should be 
executed as part of dashboard module instead - new pom can be created in 
dashboard and plugins can be moved there



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-117) Build fails on the latest commit

[Shwetha G S (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14742995#comment-14742995
 ] 

Shwetha G S commented on ATLAS-117:
---

InstallationSteps was removed from root folder as there is already 
docs/InstallationSteps.twiki - they looked like duplicates and were out of sync

> Build fails on the latest commit
> 
>
> Key: ATLAS-117
> URL: https://issues.apache.org/jira/browse/ATLAS-117
> Project: Atlas
>  Issue Type: Bug
>Reporter: David Kaspar
>Assignee: Aaron Dossett
> Fix For: trunk
>
> Attachments: ATLAS-117-2.patch, ATLAS-117-3.patch, ATLAS-117-4.patch, 
> ATLAS-117-v5.patch, ATLAS-117.patch
>
>
> Build fails when building the latest commit 
> 48343db999b495458409644c8b9d2fd0bd9fa99d:
> {code}
> [INFO] Scanning for projects...
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.atlas:atlas-webapp:war:0.6-incubating-SNAPSHOT
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.mojo:keytool-maven-plugin is missing. @ 
> org.apache.atlas:atlas-webapp:[unknown-version], 
> /Users/MYSELF/Projects/External/incubator-atlas/webapp/pom.xml, line 309, 
> column 21
> [WARNING] 
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING] 
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING] 
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] apache-atlas
> [INFO] Apache Atlas Typesystem
> [INFO] Apache Atlas Client
> [INFO] Apache Atlas Notification
> [INFO] Apache Atlas Repository
> [INFO] Apache Atlas Web Application
> [INFO] Apache Atlas Documentation
> [INFO] Apache Atlas Hive Bridge
> [INFO]
>  
> [INFO] 
> 
> [INFO] Building apache-atlas 0.6-incubating-SNAPSHOT
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ apache-atlas ---
> [INFO] Deleting /Users/MYSELF/Projects/External/incubator-atlas/target
> [INFO] Deleting /Users/MYSELF/Projects/External/incubator-atlas (includes = 
> [**/*.pyc], excludes = [])
> [INFO] 
> [INFO] --- buildnumber-maven-plugin:1.0:create (default) @ apache-atlas ---
> [INFO] Checking for local modifications: skipped.
> [INFO] Updating project files from SCM: skipped.
> [WARNING] Cannot get the revision information from the scm repository, 
> proceeding with revision of release : 
> No such provider: 'https'.
> [INFO] Storing buildNumber: release at timestamp: 1440071695692
> [WARNING] Cannot get the branch information from the scm repository, 
> proceeding with UNKNOWN_BRANCH : 
> No such provider: 'https'.
> [INFO] Storing buildScmBranch: UNKNOWN_BRANCH
> [INFO] 
> [INFO] --- maven-remote-resources-plugin:1.4:process (default) @ apache-atlas 
> ---
> [INFO] 
> [INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ 
> apache-atlas ---
> [INFO] No sources to compile
> [INFO] 
> [INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
> apache-atlas ---
> [INFO] No sources to compile
> [INFO] 
> [INFO] --- exec-maven-plugin:1.2.1:exec (python-test) @ apache-atlas ---
> test_jar_java_lookups_fail (TestMetadata.TestMetadata) ... ok
> test_jar_java_lookups_succeed_from_path (TestMetadata.TestMetadata) ... ok
> test_main (TestMetadata.TestMetadata) ... Apache Atlas Server started!!!
> ok
> --
> Ran 3 tests in 0.003s
> OK
> [INFO] 
> [INFO] --- maven-site-plugin:3.2:attach-descriptor (attach-descriptor) @ 
> apache-atlas ---
> [INFO] 
> [INFO] --- maven-assembly-plugin:2.2.1:single (default) @ apache-atlas ---
> [INFO] Reading assembly descriptor: src/main/assemblies/standalone-package.xml
> [INFO] Reading assembly descriptor: src/main/assemblies/src-package.xml
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] apache-atlas ... FAILURE [  1.773 
> s]
> [INFO] Apache Atlas Typesystem  SKIPPED
> [INFO] Apache Atlas Client  SKIPPED
> [INFO] Apache Atlas Notification .. SKIPPED
> [INFO] Apache Atlas Repository  SKIPPED
> [INFO] Apache Atlas Web Application ... SKIPPED
> [INFO] Apache Atlas Documentation . SKIPPED
> [INFO] Apache Atlas Hive Bridge ... 

[jira] [Created] (ATLAS-161) How does atlas capture lineage

[Jason Xing (JIRA)]

Jason Xing created ATLAS-161:


 Summary: How does atlas capture lineage
 Key: ATLAS-161
 URL: https://issues.apache.org/jira/browse/ATLAS-161
 Project: Atlas
  Issue Type: Wish
Reporter: Jason Xing






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)