date:20170222


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

Keval Bhatt commented on ATLAS-1562:


Fix committed in master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/c74ba142

> Not able to delete hbase_column_family once associated to the hbase_table.
> --
>
> Key: ATLAS-1562
> URL: https://issues.apache.org/jira/browse/ATLAS-1562
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>
> Created 
> 1. hbase_table "table1"
> 2. hbase_column_family "colfam1" wit hbase_table as "table1"
> 3. Edited "table1" and added  "colfam1" . Column family is added. 
> 4. Edited "table1" and removed "colfam1". Column family is not removed and 
> still associated to table1.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1564) EntityResource v1 should start routing its calls to v2 EntityREST

2017-02-22 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian updated ATLAS-1564:
--
Attachment: ATLAS-1564.3.patch

> EntityResource v1 should start routing its calls to v2 EntityREST
> -
>
> Key: ATLAS-1564
> URL: https://issues.apache.org/jira/browse/ATLAS-1564
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Attachments: ATLAS-1564.3.patch
>
>
> With the v2 implementation of EntityREST ready, we must start routing all v1 
> entity CRUD calls to start using v2 APIs in EntityREST. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1564) EntityResource v1 should start routing its calls to v2 EntityREST

2017-02-22 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian commented on ATLAS-1564:
---

[~davidrad], Agreed. We should start deprecating V1 entities apis soon. I will 
not be routing v1 glossary calls to v2, but I think we must support existing 
customers who might have applications depending on V1 entity apis. 

> EntityResource v1 should start routing its calls to v2 EntityREST
> -
>
> Key: ATLAS-1564
> URL: https://issues.apache.org/jira/browse/ATLAS-1564
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>
> With the v2 implementation of EntityREST ready, we must start routing all v1 
> entity CRUD calls to start using v2 APIs in EntityREST. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1564) EntityResource v1 should start routing its calls to v2 EntityREST

2017-02-22 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian commented on ATLAS-1564:
---

Review Link : https://reviews.apache.org/r/56969/

> EntityResource v1 should start routing its calls to v2 EntityREST
> -
>
> Key: ATLAS-1564
> URL: https://issues.apache.org/jira/browse/ATLAS-1564
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>
> With the v2 implementation of EntityREST ready, we must start routing all v1 
> entity CRUD calls to start using v2 APIs in EntityREST. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Review Request 56969: [ATLAS-1564] : EntityResource v1 should start routing its calls to v2 EntityREST

2017-02-22 Thread Sarath Subramanian


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

Review request for atlas, Apoorv Naik, Ashutosh Mestry, Madhan Neethiraj, Suma 
Shivaprasad, and Vimal Sharma.


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


Repository: atlas


Description
---

With the v2 implementation of EntityREST ready, we must start routing all v1 
entity CRUD calls to start using v2 APIs in EntityREST.


Diffs
-

  client/src/main/java/org/apache/atlas/AtlasClient.java 13896ce 
  
repository/src/main/java/org/apache/atlas/repository/converters/AtlasEntityFormatConverter.java
 1ce6168 
  
repository/src/main/java/org/apache/atlas/repository/converters/AtlasFormatConverter.java
 9d0d7f4 
  
repository/src/main/java/org/apache/atlas/repository/converters/AtlasInstanceConverter.java
 e14fafb 
  
repository/src/main/java/org/apache/atlas/repository/converters/AtlasObjectIdConverter.java
 a5ab8d7 
  
repository/src/main/java/org/apache/atlas/repository/converters/AtlasStructFormatConverter.java
 6b6ee01 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/AtlasEntityStore.java
 3a037cc 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityStoreV1.java
 bbfc3e5 
  server-api/src/main/java/org/apache/atlas/services/MetadataService.java 
e0fb66c 
  typesystem/src/main/java/org/apache/atlas/typesystem/Referenceable.java 
8cad2f8 
  typesystem/src/main/java/org/apache/atlas/typesystem/types/ClassType.java 
2f2b090 
  webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java 
f59cd9d 
  webapp/src/test/java/org/apache/atlas/web/resources/EntityResourceTest.java 
3fe8e11 

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


Testing
---

mvn clean package - all tests passed.


Thanks,

Sarath Subramanian

[jira] [Resolved] (ATLAS-1476) Create Entity via UI : Unable to add the same column again after deleting the column from the table


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

Keval Bhatt resolved ATLAS-1476.

Resolution: Fixed

> Create Entity via UI : Unable to add the same column again after deleting the 
> column from the table
> ---
>
> Key: ATLAS-1476
> URL: https://issues.apache.org/jira/browse/ATLAS-1476
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>
> 1.Created a hive_table test_table (created using Create Entity ) with column 
> column1(also created using Create Entity).
> 2.Clicked on edit button of the test_table and removed column1.
> 3.In schema tab of the hive_table, column1 is shown DELETED.
> 4.Created another hive_column column1 with same name and qualified name.
> 5.Tried to add the hive_column column1(newly created) to the test_table. 
> 'Edit Entity' window of test_table still has the deleted hive_column and not 
> able to add the new hive_column column1.
> This is possible with hive CLI :
> 1. create table table1(id int,name string)
> 2. alter table table1 replace columns(name string)  >>> id is DELETED
> 3. alter table table1 replace columns(id int,name string) >>> 2 ids are 
> present , one ACTIVE,one DELETED



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Review Request 56963: DSL queries returns wrong object when filter traverses edges



> On Feb. 23, 2017, 2:28 a.m., Suma Shivaprasad wrote:
> > Ship It!

I'm seeing a couple new test failures in webapp with this fix.  I'll 
investigate those tomorrow and keep you updated.


- Jeff


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


On Feb. 23, 2017, 1:51 a.m., Jeff Hagelberg wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/56963/
> ---
> 
> (Updated Feb. 23, 2017, 1:51 a.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-1589
> https://issues.apache.org/jira/browse/ATLAS-1589
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> In Atlas 0.7, the following DSL query returns hive_table entities whose 
> db.name=’default’.
> api/atlas/discovery/search/dsl?limit=25=hive_table+db.name%3D%27default%27
> 
> However, with the latest Atlas in master, the query returns the hive_db 
> entity, instead of hive_table entities.
> 
> 
> Diffs
> -
> 
>   repository/src/main/scala/org/apache/atlas/query/GremlinQuery.scala 
> 2863aca1a1bfa7cd200230b314ddb9954266fe87 
>   
> repository/src/test/java/org/apache/atlas/discovery/GraphBackedDiscoveryServiceTest.java
>  ffda9849e9632bff6764aed70c76a2f50f493d0d 
> 
> Diff: https://reviews.apache.org/r/56963/diff/
> 
> 
> Testing
> ---
> 
> Ran repository tests, everything passed on Windows except the expected hbase 
> tests.  Running full test suite on Linux.
> 
> 
> Thanks,
> 
> Jeff Hagelberg
> 
>

Podling Report Reminder - March 2017

2017-02-22 Thread johndament

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 15 March 2017, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, March 01).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://wiki.apache.org/incubator/March2017

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Review Request 56963: DSL queries returns wrong object when filter traverses edges

2017-02-22 Thread Suma Shivaprasad


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


Ship it!




Ship It!

- Suma Shivaprasad


On Feb. 23, 2017, 1:51 a.m., Jeff Hagelberg wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/56963/
> ---
> 
> (Updated Feb. 23, 2017, 1:51 a.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-1589
> https://issues.apache.org/jira/browse/ATLAS-1589
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> In Atlas 0.7, the following DSL query returns hive_table entities whose 
> db.name=’default’.
> api/atlas/discovery/search/dsl?limit=25=hive_table+db.name%3D%27default%27
> 
> However, with the latest Atlas in master, the query returns the hive_db 
> entity, instead of hive_table entities.
> 
> 
> Diffs
> -
> 
>   repository/src/main/scala/org/apache/atlas/query/GremlinQuery.scala 
> 2863aca1a1bfa7cd200230b314ddb9954266fe87 
>   
> repository/src/test/java/org/apache/atlas/discovery/GraphBackedDiscoveryServiceTest.java
>  ffda9849e9632bff6764aed70c76a2f50f493d0d 
> 
> Diff: https://reviews.apache.org/r/56963/diff/
> 
> 
> Testing
> ---
> 
> Ran repository tests, everything passed on Windows except the expected hbase 
> tests.  Running full test suite on Linux.
> 
> 
> Thanks,
> 
> Jeff Hagelberg
> 
>

Build failed in Jenkins: apache-atlas-nightly #638

2017-02-22 Thread Apache Jenkins Server

See 


Changes:

[madhan] ATLAS-1573: Full text mapping for Entity store V2

--
[...truncated 488.63 KB...]
127.0.0.1 - - [23/Feb/2017:01:51:04 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:04 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:04 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:04 +] "GET 
/api/atlas/lineage/hive/table/sales_fact_monthly_mvZadsmyeloS/inputs/graph 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:06 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_fact_monthly_mvZadsmyeloS
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:06 +] "GET 
/api/atlas/lineage/aef1d4db-8bb3-4fa9-9a04-f7ba5e248f36/inputs/graph HTTP/1.1" 
200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:08 +] "GET 
/api/atlas/lineage/hive/table/sales_factCdIasWmA9n/outputs/graph HTTP/1.1" 200 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:10 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_factCdIasWmA9n
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:10 +] "GET 
/api/atlas/lineage/18ea05d2-fb64-42dd-89cc-1e4cdb4620eb/outputs/graph HTTP/1.1" 
200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:11 +] "GET 
/api/atlas/lineage/hive/table/sales_factCdIasWmA9n/schema HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:12 +] "GET 
/api/atlas/lineage/hive/table/SalesUdcbSeXJPQ/schema HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:12 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_factCdIasWmA9n
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:12 +] "GET 
/api/atlas/lineage/18ea05d2-fb64-42dd-89cc-1e4cdb4620eb/schema HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:12 +] "GET 
/api/atlas/lineage/hive/table/blah/schema HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:12 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_fact_monthly_mvtfVSyx9rO0
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:12 +] "GET 
/api/atlas/v2/lineage/263160aa-c729-43b4-8e04-91d438e03b53?direction=INPUT=5
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:13 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_fact_monthly_mvtfVSyx9rO0
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:13 +] "GET 
/api/atlas/v2/lineage/263160aa-c729-43b4-8e04-91d438e03b53?direction=BOTH=5
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:16 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_factGLvCbaOu2c
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:16 +] "GET 
/api/atlas/v2/lineage/18e4da8e-089c-494c-a220-10cc69cbf686?direction=OUTPUT=5
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.605 sec - 
in org.apache.atlas.web.resources.EntityLineageJerseyResourceIT
Running org.apache.atlas.CredentialProviderUtilityIT
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.757 sec - in 
org.apache.atlas.CredentialProviderUtilityIT
Running org.apache.atlas.notification.EntityNotificationIT
127.0.0.1 - - [23/Feb/2017:01:51:23 +] "GET /api/atlas/types/tableType 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:23 +] "GET /api/atlas/types/serdeType 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:23 +] "GET /api/atlas/types/classification 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:23 +] "GET /api/atlas/types/hive_db_v1 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:24 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:25 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:26 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:26 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:26 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:26 +] "POST 
/api/atlas/entities/d56c5690-a890-4fdb-b7a6-9d91e8b1ee59/traits HTTP/1.1" 201 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:26 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [23/Feb/2017:01:51:26 +] "POST 
/api/atlas/entities/d56c5690-a890-4fdb-b7a6-9d91e8b1ee59/traits HTTP/1.1" 201 - 
"-" "Java/1.7.0_80"
127.0.0.1 - -

Review Request 56963: DSL queries returns wrong object when filter traverses edges


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

Review request for atlas.


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


Repository: atlas


Description
---

In Atlas 0.7, the following DSL query returns hive_table entities whose 
db.name=’default’.
api/atlas/discovery/search/dsl?limit=25=hive_table+db.name%3D%27default%27

However, with the latest Atlas in master, the query returns the hive_db entity, 
instead of hive_table entities.


Diffs
-

  repository/src/main/scala/org/apache/atlas/query/GremlinQuery.scala 
2863aca1a1bfa7cd200230b314ddb9954266fe87 
  
repository/src/test/java/org/apache/atlas/discovery/GraphBackedDiscoveryServiceTest.java
 ffda9849e9632bff6764aed70c76a2f50f493d0d 

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


Testing
---

Ran repository tests, everything passed on Windows except the expected hbase 
tests.  Running full test suite on Linux.


Thanks,

Jeff Hagelberg

[jira] [Updated] (ATLAS-1589) DSL queries returns wrong object when filter traverses edges


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

Jeffrey Hagelberg updated ATLAS-1589:
-
Description: 
In Atlas 0.7, the following DSL query returns hive_table entities whose 
db.name=’default’.
api/atlas/discovery/search/dsl?limit=25=hive_table+db.name%3D%27default%27
 
However, with the latest Atlas in master, the query returns the hive_db entity, 
instead of hive_table entities.

> DSL queries returns wrong object when filter traverses edges
> 
>
> Key: ATLAS-1589
> URL: https://issues.apache.org/jira/browse/ATLAS-1589
> Project: Atlas
>  Issue Type: Bug
>Reporter: Jeffrey Hagelberg
>Assignee: Jeffrey Hagelberg
>
> In Atlas 0.7, the following DSL query returns hive_table entities whose 
> db.name=’default’.
> api/atlas/discovery/search/dsl?limit=25=hive_table+db.name%3D%27default%27
>  
> However, with the latest Atlas in master, the query returns the hive_db 
> entity, instead of hive_table entities.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (ATLAS-1589) DSL queries returns wrong object when filter traverses edges

Jeffrey Hagelberg created ATLAS-1589:


 Summary: DSL queries returns wrong object when filter traverses 
edges
 Key: ATLAS-1589
 URL: https://issues.apache.org/jira/browse/ATLAS-1589
 Project: Atlas
  Issue Type: Bug
Reporter: Jeffrey Hagelberg
Assignee: Jeffrey Hagelberg






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1573) Regression : Full text search returns empty results for any query


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

Madhan Neethiraj updated ATLAS-1573:

Attachment: ATLAS-1573.patch

Patch from [~apoorvnaik] is attached.

> Regression : Full text search returns empty results for any query
> -
>
> Key: ATLAS-1573
> URL: https://issues.apache.org/jira/browse/ATLAS-1573
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Blocker
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1573.patch
>
>
> DSL search works fine.Any Full text search is not yielding any result. GET 
> response of the Full text search is empty.
> Both v2 entity API response and old API response are empty
> {code}
> /api/atlas/v2/search/fulltext?limit=25=topic1
> /api/atlas/discovery/search/fulltext?query=topic1
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (ATLAS-1573) Regression : Full text search returns empty results for any query


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

Madhan Neethiraj reassigned ATLAS-1573:
---

Assignee: Apoorv Naik

> Regression : Full text search returns empty results for any query
> -
>
> Key: ATLAS-1573
> URL: https://issues.apache.org/jira/browse/ATLAS-1573
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Blocker
> Fix For: 0.8-incubating
>
>
> DSL search works fine.Any Full text search is not yielding any result. GET 
> response of the Full text search is empty.
> Both v2 entity API response and old API response are empty
> {code}
> /api/atlas/v2/search/fulltext?limit=25=topic1
> /api/atlas/discovery/search/fulltext?query=topic1
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Review Request 56953: ATLAS-1573: FullText mapper for EntityStore V2

2017-02-22 Thread Madhan Neethiraj


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


Ship it!




Ship It!

- Madhan Neethiraj


On Feb. 22, 2017, 10:46 p.m., Apoorv Naik wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/56953/
> ---
> 
> (Updated Feb. 22, 2017, 10:46 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Sarath 
> Subramanian, Suma Shivaprasad, and Vimal Sharma.
> 
> 
> Bugs: ATLAS-1573
> https://issues.apache.org/jira/browse/ATLAS-1573
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Adding FullText mapping support for EntityStore V2
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/FullTextMapper.java
>  b988b427 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityChangeNotifier.java
>  a532f31b 
> 
> Diff: https://reviews.apache.org/r/56953/diff/
> 
> 
> Testing
> ---
> 
> Verified full text is getting set for the created/updated entity.
> Text search from UI shows the entity in the result.
> Gremlin search using the entity GUID shows that the vertex has entityText 
> property set.
> 
> mvn clean package executes successfully.
> 
> 
> Thanks,
> 
> Apoorv Naik
> 
>

[jira] [Assigned] (ATLAS-1588) ExportService is not compatible with Tinkerpop 3


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

Ashutosh Mestry reassigned ATLAS-1588:
--

Assignee: Ashutosh Mestry

> ExportService is not compatible with Tinkerpop 3
> 
>
> Key: ATLAS-1588
> URL: https://issues.apache.org/jira/browse/ATLAS-1588
> Project: Atlas
>  Issue Type: Bug
>Reporter: Jeffrey Hagelberg
>Assignee: Ashutosh Mestry
>
> The ExportService needs to be changed to generate gremlin using 
> GremlinExpressionFactory so that it works with backends that require 
> TinkerPop 3.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (ATLAS-1588) ExportService is not compatible with Tinkerpop 3


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

Ashutosh Mestry edited comment on ATLAS-1588 at 2/22/17 11:54 PM:
--

Got it! I will proceed with the implementation that is already committed. 
Thanks!


was (Author: ashutoshm):
Got it! I will proceed with the implementation that is already committed. 
Thanks!

> ExportService is not compatible with Tinkerpop 3
> 
>
> Key: ATLAS-1588
> URL: https://issues.apache.org/jira/browse/ATLAS-1588
> Project: Atlas
>  Issue Type: Bug
>Reporter: Jeffrey Hagelberg
>Assignee: Ashutosh Mestry
>
> The ExportService needs to be changed to generate gremlin using 
> GremlinExpressionFactory so that it works with backends that require 
> TinkerPop 3.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1588) ExportService is not compatible with Tinkerpop 3


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

Ashutosh Mestry commented on ATLAS-1588:


Got it! I will proceed with the implementation that is already committed. 
Thanks!

> ExportService is not compatible with Tinkerpop 3
> 
>
> Key: ATLAS-1588
> URL: https://issues.apache.org/jira/browse/ATLAS-1588
> Project: Atlas
>  Issue Type: Bug
>Reporter: Jeffrey Hagelberg
>Assignee: Ashutosh Mestry
>
> The ExportService needs to be changed to generate gremlin using 
> GremlinExpressionFactory so that it works with backends that require 
> TinkerPop 3.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (ATLAS-1588) ExportService is not compatible with Tinkerpop 3


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

Jeffrey Hagelberg edited comment on ATLAS-1588 at 2/22/17 11:51 PM:


[~guptaneeru] is working on contributing the TItan 1 implementation.  It's 
under review now.  I would expect it to be done either this week or early next 
week.  Neeru might be able to give a more concrete estimate.  To be clear, 
though, I don't think that does any refactoring of GremlinExpressionFactory.


was (Author: jnhagelb):
[~guptaneeru] is working on contributing the TItan 1 implementation.  It's 
under review now.  I would expect it to be done either this week or early next 
week.  Neeru might be able to give a more concrete estimate.

> ExportService is not compatible with Tinkerpop 3
> 
>
> Key: ATLAS-1588
> URL: https://issues.apache.org/jira/browse/ATLAS-1588
> Project: Atlas
>  Issue Type: Bug
>Reporter: Jeffrey Hagelberg
>
> The ExportService needs to be changed to generate gremlin using 
> GremlinExpressionFactory so that it works with backends that require 
> TinkerPop 3.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1552) Auto reverse reference update in V2 code path

2017-02-22 Thread David Kantor (JIRA)


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

David Kantor updated ATLAS-1552:

Attachment: rb56860.patch

> Auto reverse reference update in V2 code path
> -
>
> Key: ATLAS-1552
> URL: https://issues.apache.org/jira/browse/ATLAS-1552
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.8-incubating
>Reporter: David Kantor
>Assignee: David Kantor
> Attachments: rb56860.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1588) ExportService is not compatible with Tinkerpop 3


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

Jeffrey Hagelberg commented on ATLAS-1588:
--

[~guptaneeru] is working on contributing the TItan 1 implementation.  It's 
under review now.  I would expect it to be done either this week or early next 
week.  Neeru might be able to give a more concrete estimate.

> ExportService is not compatible with Tinkerpop 3
> 
>
> Key: ATLAS-1588
> URL: https://issues.apache.org/jira/browse/ATLAS-1588
> Project: Atlas
>  Issue Type: Bug
>Reporter: Jeffrey Hagelberg
>
> The ExportService needs to be changed to generate gremlin using 
> GremlinExpressionFactory so that it works with backends that require 
> TinkerPop 3.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Review Request 56860: ATLAS-1552 auto update of inverse references in V2 code path

2017-02-22 Thread David Kantor


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

Review request for atlas.


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


Repository: atlas


Description
---

Automatic update of inverse references in V2 (V1?) code path.


Diffs
-

  intg/src/test/java/org/apache/atlas/TestUtilsV2.java 
84e17cb364fbf6d07b2211d85e336d8146fdb684 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasGraphUtilsV1.java
 49d5a080158e3e54fd917a13f743f1cf495e66b0 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/EntityGraphMapper.java
 09f69dbe6f519d84ae8e223532fc5adaa411ed9b 
  
repository/src/test/java/org/apache/atlas/repository/store/graph/v1/AtlasDeleteHandlerV1Test.java
 555f0acc22c4bec67f1a2a4064acad66e939747a 
  
repository/src/test/java/org/apache/atlas/repository/store/graph/v1/InverseReferenceUpdateHardDeleteV1Test.java
 PRE-CREATION 
  
repository/src/test/java/org/apache/atlas/repository/store/graph/v1/InverseReferenceUpdateSoftDeleteV1Test.java
 PRE-CREATION 
  
repository/src/test/java/org/apache/atlas/repository/store/graph/v1/InverseReferenceUpdateV1Test.java
 PRE-CREATION 

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


Testing
---

Ran all unit and integration tests with no regressions.


Thanks,

David Kantor

Re: Review Request 56724: ATLAS-1390: Add IBM Graph Support

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

(Updated Feb. 22, 2017, 11:44 p.m.)

Review request for atlas, David Kantor and Neeru Gupta.

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

Repository: atlas

Description (updated)
---

This work item adds IBM Graph as a graph database that can be used by Atlas.
There are some limitations of this implementation. These are documented in the
readme.txt under graphdb\ibm-graph. The code here is the result of many months
of development effort. It was contributed to by myself, Dave Kantor, Neeru
Gupta, and Marcin Lewandowski. It was developed on our private fork of Atlas
and is now being added to the public Atlas so that others can benefit from it.

IBM Graph is a cloud based graph based on Titan 1. It is a little different
from Titan though in that all of the interactions with it requires calling a
REST API. This implementation is optimized to make as few REST API calls as
possible by combining the update operations into a single Gremlin script that
gets sent when the transaction is committed. It also has full multi-tenancy
support, although in this JIRA we have not put in the plumbing that allows
Atlas to make use of it. For the mult-user support, each thread has its own
transaction associated with it. We followed the Titan semantics -- vertex
queries executed in the context of a transaction take into account uncommitted
changes. Pure gremlin queries do not, and will only reflect committed changes.

IBM Graph also has some restrictions that a normal Titan instance would not.
Because it is a shared environment, there is a restriction that only queries
with an initial indexed predicate will run. Any query that requires a full
graph scan is rejected. Many of the tests in Atlas attempt to do a graph scan.
These tests have been changed so that they are skipped when ibm-graph is being
used as the graph backend.

Note that this implementation depends on Tinkerpop 3 classes, which require
Java 8. To manage the java version dependency, we're following a similar route
to what we did for Titan 1 support. If Java 7 is being used, the ibm-graph code
is not compiled, but we still create a jar file which is basically empty. This
is needed so that there is a jar in place to satisfy the maven dependency on
the ibm-graph implementation in the graphdb-impls project. If Java 8 is being
used, the ibm-graph code is compiled. The tests in the ibm-graph project are
only run if the ibm-graph profile is enabled though.

By default, Titan 0.5.4 is still used by Atlas. To use the ibm-graph
implemention, you need to run with java 8, enable the ibm-graph profile, and
add properties to your settings.xml to configure the IBM Graph service. This
is described in the readme.

Diffs
-

common/src/main/java/org/apache/atlas/GraphInitializationException.java
PRE-CREATION
common/src/main/java/org/apache/atlas/groovy/LiteralExpression.java
14074994f7fe06fc6a076cedb833a7de2f85e096

common/src/main/java/org/apache/atlas/groovy/VariableAssignmentExpression.java
1aa74435d59dfb4d8d3077febe794c5b1780a824
distro/pom.xml c0090ae2a86faa0b697bbdd1156323ac9f944772
distro/src/conf/atlas-application.properties
b2b8e74590c572a0a63f145e1ac9c6a3cc38f677
distro/src/conf/credentials.json PRE-CREATION
distro/src/main/assemblies/standalone-package.xml
215cb2368cf15f5fc0bd3ece19f2db330cc56b6b
graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasGraph.java
f7e5c5cec1bf134e58ff5de8986a38580fe082e3

graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/GraphDatabase.java
3dfc6e8de56780895bfdb47926f3c7a2ff858f67
graphdb/graphdb-impls/pom.xml 57b5137178dd179f86edb9a7af4f260b4b7d0ece
graphdb/ibm-graph/pom.xml PRE-CREATION
graphdb/ibm-graph/readme-mt-support.txt PRE-CREATION
graphdb/ibm-graph/readme.txt PRE-CREATION

graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/AtlasPropertyKeyToPropertyKey.java
PRE-CREATION

graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/ElementDeletedCheckingInvocationHandler.java
PRE-CREATION

graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/GraphPerTenantStrategy.java
PRE-CREATION

graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/GraphReadLockInvocationHandler.java
PRE-CREATION

graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/IBMGraphDatabase.java
PRE-CREATION
graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/IBMGraphEdge.java
PRE-CREATION

graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/IBMGraphElement.java
PRE-CREATION
graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/IBMGraphGraph.java
PRE-CREATION

Re: Review Request 56724: ATLAS-1390: Add IBM Graph Support

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

(Updated Feb. 22, 2017, 11:36 p.m.)

Review request for atlas, David Kantor and Neeru Gupta.

Changes
---

removed unused code.

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

Repository: atlas

Description
---

Note that this implementation depends on Tinkerpop 3 classes, which require
Java 8. To manage to java dependency, we're following a similar route to what
we did for Titan 1 support. If Java 7 is being used, the ibm-graph code is not
compiled, but we still create a jar file which is basically empty. This is
needed so that there is a jar in place to satisfy the maven dependency on the
ibm-graph implementation in the graphdb-impls project. If Java 8 is being
used, the ibm-graph code is compiled. The tests in the ibm-graph project are
only run if the ibm-graph profile is enabled though.

Diffs (updated)
-

common/src/main/java/org/apache/atlas/GraphInitializationException.java
PRE-CREATION
common/src/main/java/org/apache/atlas/groovy/LiteralExpression.java
14074994f7fe06fc6a076cedb833a7de2f85e096

graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/AtlasPropertyKeyToPropertyKey.java
PRE-CREATION

graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/ElementDeletedCheckingInvocationHandler.java
PRE-CREATION

graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/GraphPerTenantStrategy.java
PRE-CREATION

graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/GraphReadLockInvocationHandler.java
PRE-CREATION

graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/IBMGraphDatabase.java
PRE-CREATION
graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/IBMGraphEdge.java
PRE-CREATION

graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/IBMGraphElement.java
PRE-CREATION
graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/IBMGraphGraph.java
PRE-CREATION

[jira] [Updated] (ATLAS-1390) IBM Graph implementation of graph DB abstraction


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

Jeffrey Hagelberg updated ATLAS-1390:
-
Attachment: rb56724.patch

> IBM Graph implementation of graph DB abstraction
> 
>
> Key: ATLAS-1390
> URL: https://issues.apache.org/jira/browse/ATLAS-1390
> Project: Atlas
>  Issue Type: New Feature
>Reporter: David Kantor
>Assignee: Jeffrey Hagelberg
> Attachments: rb56724.patch
>
>
> Support running Atlas against IBM Graph as the graph backend via IBM Graph 
> implementation of the graph DB abstraction.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Review Request 56724: ATLAS-1390: Add IBM Graph Support

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

(Updated Feb. 22, 2017, 11:02 p.m.)

Review request for atlas, David Kantor and Neeru Gupta.

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

Repository: atlas

Description
---

Diffs
-

common/src/main/java/org/apache/atlas/GraphInitializationException.java
PRE-CREATION
common/src/main/java/org/apache/atlas/groovy/LiteralExpression.java
14074994f7fe06fc6a076cedb833a7de2f85e096

graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/AtlasPropertyKeyToPropertyKey.java
PRE-CREATION

graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/ElementDeletedCheckingInvocationHandler.java
PRE-CREATION

graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/GraphPerTenantStrategy.java
PRE-CREATION

graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/GraphReadLockInvocationHandler.java
PRE-CREATION

graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/IBMGraphDatabase.java
PRE-CREATION
graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/IBMGraphEdge.java
PRE-CREATION

graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/IBMGraphElement.java
PRE-CREATION
graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/IBMGraphGraph.java
PRE-CREATION

graphdb/ibm-graph/src/main/java/org/apache/atlas/ibmgraph/IBMGraphGraphQuery.java

Re: Review Request 56953: ATLAS-1573: FullText mapper for EntityStore V2


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

(Updated Feb. 22, 2017, 10:46 p.m.)


Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Sarath 
Subramanian, Suma Shivaprasad, and Vimal Sharma.


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


Repository: atlas


Description
---

Adding FullText mapping support for EntityStore V2


Diffs (updated)
-

  
repository/src/main/java/org/apache/atlas/repository/graph/FullTextMapper.java 
b988b427 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityChangeNotifier.java
 a532f31b 

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


Testing
---

Verified full text is getting set for the created/updated entity.
Text search from UI shows the entity in the result.
Gremlin search using the entity GUID shows that the vertex has entityText 
property set.

mvn clean package executes successfully.


Thanks,

Apoorv Naik

[jira] [Commented] (ATLAS-1588) ExportService is not compatible with Tinkerpop 3


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

Ashutosh Mestry commented on ATLAS-1588:


Thanks! I will wait until the commit. What would be ETA for this? I took at 
stab at this and realized that I needed the FieldInfo to create a 'has' 
expression.

> ExportService is not compatible with Tinkerpop 3
> 
>
> Key: ATLAS-1588
> URL: https://issues.apache.org/jira/browse/ATLAS-1588
> Project: Atlas
>  Issue Type: Bug
>Reporter: Jeffrey Hagelberg
>
> The ExportService needs to be changed to generate gremlin using 
> GremlinExpressionFactory so that it works with backends that require 
> TinkerPop 3.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (ATLAS-1588) ExportService is not compatible with Tinkerpop 3


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

Jeffrey Hagelberg edited comment on ATLAS-1588 at 2/22/17 9:49 PM:
---

[~ashutoshm] - If you could address it, that would be good.  We're in the 
process of doing final testing of both the titan1 and ibm-graph implementations 
of the graph abstraction layer, which both use TP 3.  Hopefully those will be 
committed fairly soon.  Until this is done, the ExportService won't be usable 
with either of those backends.  Using GremlinExpressionFactory.INSTANCE seems 
to be a good choice since it already has logic for generating gremlin that 
works with TP2 or TP3.  A lot of the logic in there is geared towards what the 
DSL translator needs, though.  There might need to be some refactoring needed, 
for example a method to create a has expression that does not require a 
FieldInfo and GraphPersistenceStrategies object to be on hand :-)


was (Author: jnhagelb):
[~ashustariov] - If you could address it, that would be good.  We're in the 
process of doing final testing of both the titan1 and ibm-graph implementations 
of the graph abstraction layer, which both use TP 3.  Hopefully those will be 
committed fairly soon.  Until this is done, the ExportService won't be usable 
with either of those backends.  Using GremlinExpressionFactory.INSTANCE seems 
to be a good choice since it already has logic for generating gremlin that 
works with TP2 or TP3.  A lot of the logic in there is geared towards what the 
DSL translator needs, though.  There might need to be some refactoring needed, 
for example a method to create a has expression that does not require a 
FieldInfo and GraphPersistenceStrategies object to be on hand :-)

> ExportService is not compatible with Tinkerpop 3
> 
>
> Key: ATLAS-1588
> URL: https://issues.apache.org/jira/browse/ATLAS-1588
> Project: Atlas
>  Issue Type: Bug
>Reporter: Jeffrey Hagelberg
>
> The ExportService needs to be changed to generate gremlin using 
> GremlinExpressionFactory so that it works with backends that require 
> TinkerPop 3.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1588) ExportService is not compatible with Tinkerpop 3


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

Jeffrey Hagelberg commented on ATLAS-1588:
--

It may make sense to wait until at least the titan1 backend has been committed 
before looking at this though.  Otherwise there won't really be a way to test 
the changes.

> ExportService is not compatible with Tinkerpop 3
> 
>
> Key: ATLAS-1588
> URL: https://issues.apache.org/jira/browse/ATLAS-1588
> Project: Atlas
>  Issue Type: Bug
>Reporter: Jeffrey Hagelberg
>
> The ExportService needs to be changed to generate gremlin using 
> GremlinExpressionFactory so that it works with backends that require 
> TinkerPop 3.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1588) ExportService is not compatible with Tinkerpop 3


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

Jeffrey Hagelberg commented on ATLAS-1588:
--

[~ashustariov] - If you could address it, that would be good.  We're in the 
process of doing final testing of both the titan1 and ibm-graph implementations 
of the graph abstraction layer, which both use TP 3.  Hopefully those will be 
committed fairly soon.  Until this is done, the ExportService won't be usable 
with either of those backends.  Using GremlinExpressionFactory.INSTANCE seems 
to be a good choice since it already has logic for generating gremlin that 
works with TP2 or TP3.  A lot of the logic in there is geared towards what the 
DSL translator needs, though.  There might need to be some refactoring needed, 
for example a method to create a has expression that does not require a 
FieldInfo and GraphPersistenceStrategies object to be on hand :-)

> ExportService is not compatible with Tinkerpop 3
> 
>
> Key: ATLAS-1588
> URL: https://issues.apache.org/jira/browse/ATLAS-1588
> Project: Atlas
>  Issue Type: Bug
>Reporter: Jeffrey Hagelberg
>
> The ExportService needs to be changed to generate gremlin using 
> GremlinExpressionFactory so that it works with backends that require 
> TinkerPop 3.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Review Request 56953: ATLAS-1573: FullText mapper for EntityStore V2


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

Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Sarath 
Subramanian, Suma Shivaprasad, and Vimal Sharma.


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


Repository: atlas


Description
---

Adding FullText mapping support for EntityStore V2


Diffs
-

  
repository/src/main/java/org/apache/atlas/repository/graph/FullTextMapper.java 
b988b427 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityChangeNotifier.java
 a532f31b 

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


Testing
---

Verified full text is getting set for the created/updated entity.
Text search from UI shows the entity in the result.
Gremlin search using the entity GUID shows that the vertex has entityText 
property set.

mvn clean package executes successfully.


Thanks,

Apoorv Naik

[jira] [Commented] (ATLAS-1588) ExportService is not compatible with Tinkerpop 3


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

Ashutosh Mestry commented on ATLAS-1588:


Jeffrey: Are you expecting us to address this? If yes, should 
GremlinExpressionFactory.INSTANCE be used to construct the expression?

> ExportService is not compatible with Tinkerpop 3
> 
>
> Key: ATLAS-1588
> URL: https://issues.apache.org/jira/browse/ATLAS-1588
> Project: Atlas
>  Issue Type: Bug
>Reporter: Jeffrey Hagelberg
>
> The ExportService needs to be changed to generate gremlin using 
> GremlinExpressionFactory so that it works with backends that require 
> TinkerPop 3.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Build failed in Jenkins: apache-atlas-nightly #637

2017-02-22 Thread Apache Jenkins Server

See 


Changes:

[madhan] ATLAS-1567: exclude hadoop-common library in Falcon hook packaging, as

[madhan] ATLAS-1575: fix for UI issue in create/edit of hive_table entity

[madhan] ATLAS-1585 : Search result page should show the entityType for each

--
[...truncated 484.96 KB...]
127.0.0.1 - - [22/Feb/2017:19:29:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:33 +] "GET 
/api/atlas/lineage/hive/table/sales_fact_monthly_mvF2kYI1mhDg/inputs/graph 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:35 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_fact_monthly_mvF2kYI1mhDg
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:35 +] "GET 
/api/atlas/lineage/98bd01db-82d3-4361-a30c-0b48f012d935/inputs/graph HTTP/1.1" 
200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:36 +] "GET 
/api/atlas/lineage/hive/table/sales_factHrP4ilXzNa/outputs/graph HTTP/1.1" 200 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:39 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_factHrP4ilXzNa
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:39 +] "GET 
/api/atlas/lineage/d88f9c2f-c5c1-4dde-9e1e-3255a1fbad77/outputs/graph HTTP/1.1" 
200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:40 +] "GET 
/api/atlas/lineage/hive/table/sales_factHrP4ilXzNa/schema HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:40 +] "GET 
/api/atlas/lineage/hive/table/SaleseIB79HV1jX/schema HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:40 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_factHrP4ilXzNa
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:40 +] "GET 
/api/atlas/lineage/d88f9c2f-c5c1-4dde-9e1e-3255a1fbad77/schema HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:41 +] "GET 
/api/atlas/lineage/hive/table/blah/schema HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:41 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_fact_monthly_mvfuoMIRtPK1
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:41 +] "GET 
/api/atlas/v2/lineage/b9232fbf-4dd8-42cf-bb0a-d990adeb4a01?direction=INPUT=5
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:43 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_fact_monthly_mvfuoMIRtPK1
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:43 +] "GET 
/api/atlas/v2/lineage/b9232fbf-4dd8-42cf-bb0a-d990adeb4a01?direction=BOTH=5
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:45 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_factCZImplSXNM
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:45 +] "GET 
/api/atlas/v2/lineage/37a6f99d-c98f-4305-a3d5-9f5ed5b5d7ea?direction=OUTPUT=5
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 18.259 sec - 
in org.apache.atlas.web.resources.EntityLineageJerseyResourceIT
Running org.apache.atlas.CredentialProviderUtilityIT
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.537 sec - in 
org.apache.atlas.CredentialProviderUtilityIT
Running org.apache.atlas.notification.EntityNotificationIT
127.0.0.1 - - [22/Feb/2017:19:29:52 +] "GET /api/atlas/types/tableType 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:52 +] "GET /api/atlas/types/serdeType 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:52 +] "GET /api/atlas/types/classification 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:52 +] "GET /api/atlas/types/hive_db_v1 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:53 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:54 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:55 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:55 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:55 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:55 +] "POST 
/api/atlas/entities/617c20d1-082c-46b9-b37c-16d48e806a55/traits HTTP/1.1" 201 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:19:29:55 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"

[jira] [Updated] (ATLAS-1579) EntityLineageSevice Fails with TP3


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

Jeffrey Hagelberg updated ATLAS-1579:
-
Summary: EntityLineageSevice Fails with TP3  (was: Fix EntityLineageSevice 
Tests to run against TP3)

> EntityLineageSevice Fails with TP3
> --
>
> Key: ATLAS-1579
> URL: https://issues.apache.org/jira/browse/ATLAS-1579
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Neeru Gupta
>
> EntityLineageService is hard-coded to generate Gremlin that is specific to 
> Tinker Pop 2.  It needs to be updated to use GremlinExpressionFactory to 
> generate Gremlin that is appropriate for the version of Gremlin being used.
> See ATLAS-695, ATLAS-1390.  
> As part of this fix, the logic for skipping the following tests when using 
> Tinker Pop 3 should be removed:
> repository:
> * EntityLineageService - all tests
> webapp:
> * DataSetLineageJerseyResourceIT.testInputsGraphForEntity
> * DataSetLineageJerseyResourceIT.testOutputsGraphForEntity
> * EntityLineageJerseyResourceIT - all tests
> The issue is known to affect at least the following endpoints:
> * v2/lineage/\{guid\}
> * lineage/\{guid\}/inputs/graph
> * lineage/\{guid\}/outputs/graph



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1579) Fix EntityLineageSevice Tests to run against TP3


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

Jeffrey Hagelberg updated ATLAS-1579:
-
Description: 
EntityLineageService is hard-coded to generate Gremlin that is specific to 
Tinker Pop 2.  It needs to be updated to use GremlinExpressionFactory to 
generate Gremlin that is appropriate for the version of Gremlin being used.

See ATLAS-695, ATLAS-1390.  

As part of this fix, the logic for skipping the following tests when using 
Tinker Pop 3 should be removed:

repository:
* EntityLineageService - all tests

webapp:
* DataSetLineageJerseyResourceIT.testInputsGraphForEntity
* DataSetLineageJerseyResourceIT.testOutputsGraphForEntity
* EntityLineageJerseyResourceIT - all tests


The issue is known to affect at least the following endpoints:
* v2/lineage/\{guid\}
* lineage/\{guid\}/inputs/graph
* lineage/\{guid\}/outputs/graph endpoints


  was:
EntityLineageService is hard-coded to generate Gremlin that is specific to 
Tinker Pop 2.  It needs to be updated to use GremlinExpressionFactory to 
generate Gremlin that is appropriate for the version of Gremlin being used.

See ATLAS-695, ATLAS-1390.  

As part of this fix, the logic for skipping the following tests when using 
Tinker Pop 3 should be removed:

repository:

EntityLineageService - all tests

webapp:
DataSetLineageJerseyResourceIT.testInputsGraphForEntity
DataSetLineageJerseyResourceIT.testOutputsGraphForEntity
EntityLineageJerseyResourceIT - all tests


The issue is known to affect at least the following endpoints:
v2/lineage/{guid}
lineage/{guid}/inputs/graph
lineage/{guid}/outputs/graph endpoints



> Fix EntityLineageSevice Tests to run against TP3
> 
>
> Key: ATLAS-1579
> URL: https://issues.apache.org/jira/browse/ATLAS-1579
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Neeru Gupta
>
> EntityLineageService is hard-coded to generate Gremlin that is specific to 
> Tinker Pop 2.  It needs to be updated to use GremlinExpressionFactory to 
> generate Gremlin that is appropriate for the version of Gremlin being used.
> See ATLAS-695, ATLAS-1390.  
> As part of this fix, the logic for skipping the following tests when using 
> Tinker Pop 3 should be removed:
> repository:
> * EntityLineageService - all tests
> webapp:
> * DataSetLineageJerseyResourceIT.testInputsGraphForEntity
> * DataSetLineageJerseyResourceIT.testOutputsGraphForEntity
> * EntityLineageJerseyResourceIT - all tests
> The issue is known to affect at least the following endpoints:
> * v2/lineage/\{guid\}
> * lineage/\{guid\}/inputs/graph
> * lineage/\{guid\}/outputs/graph endpoints



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1579) Fix EntityLineageSevice Tests to run against TP3


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

Jeffrey Hagelberg updated ATLAS-1579:
-
Description: 
EntityLineageService is hard-coded to generate Gremlin that is specific to 
Tinker Pop 2.  It needs to be updated to use GremlinExpressionFactory to 
generate Gremlin that is appropriate for the version of Gremlin being used.

See ATLAS-695, ATLAS-1390.  

As part of this fix, the logic for skipping the following tests when using 
Tinker Pop 3 should be removed:

repository:
* EntityLineageService - all tests

webapp:
* DataSetLineageJerseyResourceIT.testInputsGraphForEntity
* DataSetLineageJerseyResourceIT.testOutputsGraphForEntity
* EntityLineageJerseyResourceIT - all tests


The issue is known to affect at least the following endpoints:
* v2/lineage/\{guid\}
* lineage/\{guid\}/inputs/graph
* lineage/\{guid\}/outputs/graph


  was:
EntityLineageService is hard-coded to generate Gremlin that is specific to 
Tinker Pop 2.  It needs to be updated to use GremlinExpressionFactory to 
generate Gremlin that is appropriate for the version of Gremlin being used.

See ATLAS-695, ATLAS-1390.  

As part of this fix, the logic for skipping the following tests when using 
Tinker Pop 3 should be removed:

repository:
* EntityLineageService - all tests

webapp:
* DataSetLineageJerseyResourceIT.testInputsGraphForEntity
* DataSetLineageJerseyResourceIT.testOutputsGraphForEntity
* EntityLineageJerseyResourceIT - all tests


The issue is known to affect at least the following endpoints:
* v2/lineage/\{guid\}
* lineage/\{guid\}/inputs/graph
* lineage/\{guid\}/outputs/graph endpoints



> Fix EntityLineageSevice Tests to run against TP3
> 
>
> Key: ATLAS-1579
> URL: https://issues.apache.org/jira/browse/ATLAS-1579
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Neeru Gupta
>
> EntityLineageService is hard-coded to generate Gremlin that is specific to 
> Tinker Pop 2.  It needs to be updated to use GremlinExpressionFactory to 
> generate Gremlin that is appropriate for the version of Gremlin being used.
> See ATLAS-695, ATLAS-1390.  
> As part of this fix, the logic for skipping the following tests when using 
> Tinker Pop 3 should be removed:
> repository:
> * EntityLineageService - all tests
> webapp:
> * DataSetLineageJerseyResourceIT.testInputsGraphForEntity
> * DataSetLineageJerseyResourceIT.testOutputsGraphForEntity
> * EntityLineageJerseyResourceIT - all tests
> The issue is known to affect at least the following endpoints:
> * v2/lineage/\{guid\}
> * lineage/\{guid\}/inputs/graph
> * lineage/\{guid\}/outputs/graph



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1579) Fix EntityLineageSevice Tests to run against TP3


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

Jeffrey Hagelberg updated ATLAS-1579:
-
Description: 
EntityLineageService is hard-coded to generate Gremlin that is specific to 
Tinker Pop 2.  It needs to be updated to use GremlinExpressionFactory to 
generate Gremlin that is appropriate for the version of Gremlin being used.

See ATLAS-695, ATLAS-1390.  

As part of this fix, the logic for skipping the following tests when using 
Tinker Pop 3 should be removed:

repository:

EntityLineageService - all tests

webapp:
DataSetLineageJerseyResourceIT.testInputsGraphForEntity
DataSetLineageJerseyResourceIT.testOutputsGraphForEntity
EntityLineageJerseyResourceIT - all tests


The issue is known to affect at least the following endpoints:
v2/lineage/{guid}
lineage/{guid}/inputs/graph
lineage/{guid}/outputs/graph endpoints


  was:
EntityLineageService is hard-coded to generate Gremlin that is specific to 
Tinker Pop 2.  It needs to be updated to use GremlinExpressionFactory to 
generate Gremlin that is appropriate for the version of Gremlin being used.

See ATLAS-695, ATLAS-1390.  

As part of this fix, the logic for skipping the following tests when using 
Tinker Pop 3 should be removed:

repository:

EntityLineageService - all tests

webapp:
DataSetLineageJerseyResourceIT.testInputsGraphForEntity
DataSetLineageJerseyResourceIT.testOutputsGraphForEntity
EntityLineageJerseyResourceIT - all tests




> Fix EntityLineageSevice Tests to run against TP3
> 
>
> Key: ATLAS-1579
> URL: https://issues.apache.org/jira/browse/ATLAS-1579
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Neeru Gupta
>
> EntityLineageService is hard-coded to generate Gremlin that is specific to 
> Tinker Pop 2.  It needs to be updated to use GremlinExpressionFactory to 
> generate Gremlin that is appropriate for the version of Gremlin being used.
> See ATLAS-695, ATLAS-1390.  
> As part of this fix, the logic for skipping the following tests when using 
> Tinker Pop 3 should be removed:
> repository:
> EntityLineageService - all tests
> webapp:
> DataSetLineageJerseyResourceIT.testInputsGraphForEntity
> DataSetLineageJerseyResourceIT.testOutputsGraphForEntity
> EntityLineageJerseyResourceIT - all tests
> The issue is known to affect at least the following endpoints:
> v2/lineage/{guid}
> lineage/{guid}/inputs/graph
> lineage/{guid}/outputs/graph endpoints



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1579) Fix EntityLineageSevice Tests to run against TP3


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

Jeffrey Hagelberg updated ATLAS-1579:
-
Description: 
EntityLineageService is hard-coded to generate Gremlin that is specific to 
Tinker Pop 2.  It needs to be updated to use GremlinExpressionFactory to 
generate Gremlin that is appropriate for the version of Gremlin being used.

See ATLAS-695, ATLAS-1390.  

As part of this fix, the logic for skipping the following tests when using 
Tinker Pop 3 should be removed:

repository:

EntityLineageService - all tests

webapp:
DataSetLineageJerseyResourceIT.testInputsGraphForEntity
DataSetLineageJerseyResourceIT.testOutputsGraphForEntity
EntityLineageJerseyResourceIT - all tests



  was:
EntityLineageService is hard-coded to generate Gremlin that is specific to 
Tinker Pop 2.  It needs to be updated to use GremlinExpressionFactory to 
generate Gremlin that is appropriate for the version of Gremlin being used.

See ATLAS-695, ATLAS-1390.  

As part of this fix, the logic for skipping the following tests when using 
Tinker Pop 2 should be removed:

repository:

EntityLineageService - all tests

webapp:
DataSetLineageJerseyResourceIT.testInputsGraphForEntity
DataSetLineageJerseyResourceIT.testOutputsGraphForEntity
EntityLineageJerseyResourceIT - all tests




> Fix EntityLineageSevice Tests to run against TP3
> 
>
> Key: ATLAS-1579
> URL: https://issues.apache.org/jira/browse/ATLAS-1579
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Neeru Gupta
>
> EntityLineageService is hard-coded to generate Gremlin that is specific to 
> Tinker Pop 2.  It needs to be updated to use GremlinExpressionFactory to 
> generate Gremlin that is appropriate for the version of Gremlin being used.
> See ATLAS-695, ATLAS-1390.  
> As part of this fix, the logic for skipping the following tests when using 
> Tinker Pop 3 should be removed:
> repository:
> EntityLineageService - all tests
> webapp:
> DataSetLineageJerseyResourceIT.testInputsGraphForEntity
> DataSetLineageJerseyResourceIT.testOutputsGraphForEntity
> EntityLineageJerseyResourceIT - all tests



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1579) Fix EntityLineageSevice Tests to run against TP3


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

Jeffrey Hagelberg updated ATLAS-1579:
-
Description: 
EntityLineageService is hard-coded to generate Gremlin that is specific to 
Tinker Pop 2.  It needs to be updated to use GremlinExpressionFactory to 
generate Gremlin that is appropriate for the version of Gremlin being used.

See ATLAS-695, ATLAS-1390.  

As part of this fix, the logic for skipping the following tests when using 
Tinker Pop 2 should be removed:

repository:

EntityLineageService - all tests

webapp:
DataSetLineageJerseyResourceIT.testInputsGraphForEntity
DataSetLineageJerseyResourceIT.testOutputsGraphForEntity
EntityLineageJerseyResourceIT - all tests



  was:
EntityLineageService is hard-coded to generate Gremlin that is specific to 
Tinker Pop 2.  It needs to be updated to use GremlinExpressionFactory to 
generate Gremlin that is appropriate for the version of Gremlin being used.

See ATLAS-695, ATLAS-1390.  As part of this fix, the logic for skipping the 
following tests when using Tinker Pop 2 should be removed:

repository:

EntityLineageService - all tests

webapp:
DataSetLineageJerseyResourceIT.testInputsGraphForEntity
DataSetLineageJerseyResourceIT.testOutputsGraphForEntity
EntityLineageJerseyResourceIT - all tests




> Fix EntityLineageSevice Tests to run against TP3
> 
>
> Key: ATLAS-1579
> URL: https://issues.apache.org/jira/browse/ATLAS-1579
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Neeru Gupta
>
> EntityLineageService is hard-coded to generate Gremlin that is specific to 
> Tinker Pop 2.  It needs to be updated to use GremlinExpressionFactory to 
> generate Gremlin that is appropriate for the version of Gremlin being used.
> See ATLAS-695, ATLAS-1390.  
> As part of this fix, the logic for skipping the following tests when using 
> Tinker Pop 2 should be removed:
> repository:
> EntityLineageService - all tests
> webapp:
> DataSetLineageJerseyResourceIT.testInputsGraphForEntity
> DataSetLineageJerseyResourceIT.testOutputsGraphForEntity
> EntityLineageJerseyResourceIT - all tests



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1579) Fix EntityLineageSevice Tests to run against TP3


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

Jeffrey Hagelberg updated ATLAS-1579:
-
Description: 
EntityLineageService is hard-coded to generate Gremlin that is specific to 
Tinker Pop 2.  It needs to be updated to use GremlinExpressionFactory to 
generate Gremlin that is appropriate for the version of Gremlin being used.

See ATLAS-695, ATLAS-1390.  As part of this fix, the logic for skipping the 
following tests when using Tinker Pop 2 should be removed:

repository:

EntityLineageService - all tests

webapp:
DataSetLineageJerseyResourceIT.testInputsGraphForEntity
DataSetLineageJerseyResourceIT.testOutputsGraphForEntity
EntityLineageJerseyResourceIT - all tests



  was:
EntityLineageService is hard-coded to generate Gremlin that is specific to 
Tinker Pop 2.  It needs to be updated to use GremlinExpressionFactory to 
generate Gremlin that is appropriate for the version of Titan being used.

Titan1 tests fail because of this issue. #ATLAS-695


> Fix EntityLineageSevice Tests to run against TP3
> 
>
> Key: ATLAS-1579
> URL: https://issues.apache.org/jira/browse/ATLAS-1579
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Neeru Gupta
>
> EntityLineageService is hard-coded to generate Gremlin that is specific to 
> Tinker Pop 2.  It needs to be updated to use GremlinExpressionFactory to 
> generate Gremlin that is appropriate for the version of Gremlin being used.
> See ATLAS-695, ATLAS-1390.  As part of this fix, the logic for skipping the 
> following tests when using Tinker Pop 2 should be removed:
> repository:
> EntityLineageService - all tests
> webapp:
> DataSetLineageJerseyResourceIT.testInputsGraphForEntity
> DataSetLineageJerseyResourceIT.testOutputsGraphForEntity
> EntityLineageJerseyResourceIT - all tests



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: V2 REST Api documentation (first-cut)

Thank you Ernie and Keval for your review (forgot to mention in prior email)




On 2/22/17, 11:10 AM, "Apoorv Naik"  wrote:

>Thanks for your detailed review David. 
>
>1. I see that there’s some inconsistency in the Javadocs for EntityREST fixing 
>those should fix the docs too.
>2. Will update the javadocs for the *def classes too. Class -> datatype in 
>javadocs
>3. I didn’t add any admin requests as I feel they’re meant for ops rather that 
>devs.
>4. CRUD of enums and ObjectId is not exposed as separate API thus the docs 
>don’t have any specific section for the same. The API doc examples have sample 
>JSON for *def objects. Let me know if anything is missing there.
>5. Will update the javadocs for all the classes in the model package for 
>better description.
>6. v2/entity/uniqueAttribute/type/{typeName} is a GET for entity so it’s under 
>a correct REST resource.
>
>
>
>On 2/21/17, 5:49 AM, "David Radley"  wrote:
>
>>Hi Apoorv,
>> I think documenting the API like this will make calling Atlas much more 
>>intuitive; seeing the API like this for the first time makes it really 
>>easy to see what there is including  omissions and inconsistencies. I 
>>realize you are exposing what is already there. I am not sure if this is 
>>the sort of feedback you are looking for; here are my initial 
>>observations:
>> 
>>-v2/entity/uniqueAttribute/type/{typeName} shouldn't this be in the types 
>>API?
>>- i notice the bulk APIs are in the section called "REST for single 
>>entity". I suggest creating a separate section for bulk or renaming to 
>>"REST for entity"
>>- "AtlasAttributeDef 
>>class that captures details of a struct-attribute.
>>" I suggest class be renamed to data type. Same for other data types
>>- Some of the data types have no descriptions 
>>- Are we missing the admin requests? 
>>- I see we have a section on entities and classifications (Type 
>>categories). It would be good to see the CRUD of enums and object_ids. 
>>maps, arrays and structures somewhere in the API docs. 
>>- AtlasEntityWithExtInfo Data Type is described as "An instance of an 
>>entity along with extended info - like hive_table, hive_database". I think 
>>these are examples not a definition of what the extended type is. 
>>- AtlasEntityExtInfo has the same description as AtlasEntityExtInfo
>>- I notice that the data type attributes are not documented.
>>- I notice the JSON API is sorted alphabetically but the XML one is not.
>>- AtlasConstraintDef does not document the possible values for the 
>>constraints and their usage. 
>>
>>
>>If this is the type of observations you are looking for - I am willing to 
>>spend more time reviewing the API, 
>>  all the best, David. 
>>
>>
>>
>>From:   Keval Bhatt 
>>To: dev@atlas.incubator.apache.org
>>Date:   20/02/2017 06:12
>>Subject:Re: V2 REST Api documentation (first-cut)
>>
>>
>>
>>Hi Apoorv,
>>
>>API Doc is very simplified and UI is also looks good and clear. It will be
>>really helpful to developers.
>>Integration with swagger  in API documentation is
>>awesome.
>>
>>Thanks,
>>Keval
>>
>>On Sat, Feb 18, 2017 at 9:07 AM, Apoorv Naik  
>>wrote:
>>
>>> Hi Atlas community,
>>>
>>> The REST API docs (first-cut) for the new V2 endpoints and data models 
>>are
>>> now available at http://atlas.incubator.apache.org/api/v2/index.html.
>>> It’d be great if we can gather some feedback on the docs, the existing 
>>docs
>>> have been moved under Legacy API section now. Looking forward to the
>>> community feedback.
>>>
>>
>>
>>
>>Unless stated otherwise above:
>>IBM United Kingdom Limited - Registered in England and Wales with number 
>>741598. 
>>Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>>

Re: V2 REST Api documentation (first-cut)

Thanks for your detailed review David. 

1. I see that there’s some inconsistency in the Javadocs for EntityREST fixing 
those should fix the docs too.
2. Will update the javadocs for the *def classes too. Class -> datatype in 
javadocs
3. I didn’t add any admin requests as I feel they’re meant for ops rather that 
devs.
4. CRUD of enums and ObjectId is not exposed as separate API thus the docs 
don’t have any specific section for the same. The API doc examples have sample 
JSON for *def objects. Let me know if anything is missing there.
5. Will update the javadocs for all the classes in the model package for better 
description.
6. v2/entity/uniqueAttribute/type/{typeName} is a GET for entity so it’s under 
a correct REST resource.



On 2/21/17, 5:49 AM, "David Radley"  wrote:

>Hi Apoorv,
> I think documenting the API like this will make calling Atlas much more 
>intuitive; seeing the API like this for the first time makes it really 
>easy to see what there is including  omissions and inconsistencies. I 
>realize you are exposing what is already there. I am not sure if this is 
>the sort of feedback you are looking for; here are my initial 
>observations:
> 
>-v2/entity/uniqueAttribute/type/{typeName} shouldn't this be in the types 
>API?
>- i notice the bulk APIs are in the section called "REST for single 
>entity". I suggest creating a separate section for bulk or renaming to 
>"REST for entity"
>- "AtlasAttributeDef 
>class that captures details of a struct-attribute.
>" I suggest class be renamed to data type. Same for other data types
>- Some of the data types have no descriptions 
>- Are we missing the admin requests? 
>- I see we have a section on entities and classifications (Type 
>categories). It would be good to see the CRUD of enums and object_ids. 
>maps, arrays and structures somewhere in the API docs. 
>- AtlasEntityWithExtInfo Data Type is described as "An instance of an 
>entity along with extended info - like hive_table, hive_database". I think 
>these are examples not a definition of what the extended type is. 
>- AtlasEntityExtInfo has the same description as AtlasEntityExtInfo
>- I notice that the data type attributes are not documented.
>- I notice the JSON API is sorted alphabetically but the XML one is not.
>- AtlasConstraintDef does not document the possible values for the 
>constraints and their usage. 
>
>
>If this is the type of observations you are looking for - I am willing to 
>spend more time reviewing the API, 
>  all the best, David. 
>
>
>
>From:   Keval Bhatt 
>To: dev@atlas.incubator.apache.org
>Date:   20/02/2017 06:12
>Subject:Re: V2 REST Api documentation (first-cut)
>
>
>
>Hi Apoorv,
>
>API Doc is very simplified and UI is also looks good and clear. It will be
>really helpful to developers.
>Integration with swagger  in API documentation is
>awesome.
>
>Thanks,
>Keval
>
>On Sat, Feb 18, 2017 at 9:07 AM, Apoorv Naik  
>wrote:
>
>> Hi Atlas community,
>>
>> The REST API docs (first-cut) for the new V2 endpoints and data models 
>are
>> now available at http://atlas.incubator.apache.org/api/v2/index.html.
>> It’d be great if we can gather some feedback on the docs, the existing 
>docs
>> have been moved under Legacy API section now. Looking forward to the
>> community feedback.
>>
>
>
>
>Unless stated otherwise above:
>IBM United Kingdom Limited - Registered in England and Wales with number 
>741598. 
>Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>

[jira] [Created] (ATLAS-1588) ExportService is not compatible with Tinkerpop 3

Jeffrey Hagelberg created ATLAS-1588:


 Summary: ExportService is not compatible with Tinkerpop 3
 Key: ATLAS-1588
 URL: https://issues.apache.org/jira/browse/ATLAS-1588
 Project: Atlas
  Issue Type: Bug
Reporter: Jeffrey Hagelberg


The ExportService needs to be changed to generate gremlin using 
GremlinExpressionFactory so that it works with backends that require TinkerPop 
3.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1575) Unable to create/edit hive_table entity in UI.


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

Madhan Neethiraj commented on ATLAS-1575:
-

+1 for the patch. Thanks [~kevalbhatt].

> Unable to create/edit hive_table entity in UI.
> ---
>
> Key: ATLAS-1575
> URL: https://issues.apache.org/jira/browse/ATLAS-1575
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1575.patch
>
>
> Set the following value in custom application properties.
> {code}
> atlas.ui.editable.entity.types=*
> {code}  
> Tried to create/edit a hive_table.
> All GET API requests for hive_table succeeded but UI didn't load the 
> attribute list of hive_table to fill values.
> Following exception was thrown in Console Tab. 
> {code}
> Uncaught TypeError: Cannot read property 'queryText' of undefined
> at CreateEntityLayoutView.js:140
> at Function.m.each.m.forEach (underscore-min.js:5)
> at n. (CreateEntityLayoutView.js:138)
> at _ (backbone-min.js:1)
> at m (backbone-min.js:1)
> at f (backbone-min.js:1)
> at n.l.trigger (backbone-min.js:1)
> at n.reset (backbone-min.js:1)
> at Object. (backbone.paginator.min.js:185)
> at _ (backbone-min.js:1)
> at m (backbone-min.js:1)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1567) Regression: AtlasHook for falcon seems to be broken, it is not invoked when a falcon cluster entity is submitted


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

Madhan Neethiraj commented on ATLAS-1567:
-

+1 for the patch. Thanks [~nixonrodrigues].

> Regression: AtlasHook for falcon seems to be broken, it is not invoked when a 
> falcon cluster entity is submitted
> 
>
> Key: ATLAS-1567
> URL: https://issues.apache.org/jira/browse/ATLAS-1567
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: trunk
>Reporter: Ayub Khan
>Assignee: Nixon Rodrigues
>Priority: Blocker
> Fix For: trunk, 0.8-incubating
>
> Attachments: ATLAS-1567.patch
>
>
> Falcon logs showing the cluster submitted successfully, but still the hook is 
> not invoked
> {noformat}
> 2017-02-17 19:23:40,020 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:] ~ HttpServletRequest RemoteUser is 
> hrt_qa (Servlets:47)
> 2017-02-17 19:23:40,020 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Logging in hrt_qa (CurrentUser:65)
> 2017-02-17 19:23:40,021 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Request from authenticated user: hrt_qa, URL=/api/entities/submit/cluster, 
> doAs user: null (FalconAuthenticationFilter:185)
> 2017-02-17 19:23:40,021 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Authorizing user=hrt_qa against request=RequestParts{resource='entities', 
> action='submit', entityType='cluster'} (FalconAuthorizationFilter:78)
> 2017-02-17 19:23:40,021 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Authorization for action=submit will be done in the API 
> (DefaultAuthorizationProvider:315)
> 2017-02-17 19:23:40,021 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Authorization succeeded for user=hrt_qa, proxy=hrt_qa 
> (FalconAuthorizationFilter:88)
> 2017-02-17 19:23:40,034 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Parsed Entity: cl1 (EntityParser:102)
> 2017-02-17 19:23:40,040 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Parsed Entity: cl1 (EntityParser:102)
> 2017-02-17 19:23:40,040 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Lock acquired for submit on (cluster) cl1 by 726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782 (MemoryLocks:54)
> 2017-02-17 19:23:40,040 ERROR - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Entity node (CLUSTER) cl1 not found in entity graph. (EntityGraph:71)
> 2017-02-17 19:23:40,041 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Successfully released lock on (cluster) cl1 by 726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782 (MemoryLocks:70)
> 2017-02-17 19:23:40,041 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> All locks released on cl1 (AbstractEntityManager:489)
> 2017-02-17 19:23:40,050 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> {Action:submit, Dimensions:{colo=NULL, entityType=cluster}, Status: 
> SUCCEEDED, Time-taken:26995845 ns} (METRIC:38)
> 2017-02-17 19:23:40,051 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:] ~ Audit: hrt_qa@172.27.21.202 
> performed 
> http://ctr-e129-1487033772569-4286-01-04.hwx.site:15000/api/entities/submit/cluster
>  (172.27.17.129) at 2017-02-17T19:23Z (AUDIT:48)
> 2017-02-17 19:23:40,051 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:] ~ Audit: hrt_qa@172.27.21.202 
> performed 
> http://ctr-e129-1487033772569-4286-01-04.hwx.site:15000/api/entities/submit/cluster
>  (172.27.17.129) at 2017-02-17T19:23Z (AUDIT:48)
> 2017-02-17 19:23:51,101 WARN  - [HiveClientCache-cleaner-0:] ~ Evicted client 
> has non-zero user count: 1 (metastore:443)
> {noformat}
> Falcon running command - showing hook jars classpath
> {noformat}
> [root@ctr-e129-1487033772569-4286-01-04 conf]# ps axu | grep -i falcon
> falcon 66767  0.2  0.2 9242152 751692 ?  Sl   Feb16

[jira] [Commented] (ATLAS-1585) Search result page should show the entityType for each result


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

Madhan Neethiraj commented on ATLAS-1585:
-

+1 for the patch.

I will commit the patch after reverting the change to 'sortable' flag on 'name' 
and 'description' columns. Sorting in these columns would require support from 
server-side (i.e. UI can only sort within the current-page; user might expect 
the entire paginated result be sorted with the selected column).

Other changes look good! Thanks [~kevalbhatt].


> Search result page should show the entityType for each result
> -
>
> Key: ATLAS-1585
> URL: https://issues.apache.org/jira/browse/ATLAS-1585
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Madhan Neethiraj
>Assignee: Keval Bhatt
> Attachments: ATLAS-1585.patch
>
>
> Currently, the search result page shows the following columns:
> {noformat}
> - Name
> - Description
> - Owner
> - Tags
> {noformat}
> In addition, it will be helpful to include the entityType for each entry in 
> the result - given that the result might include entities of different types, 
> especially in full-text search and tag-search.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Build failed in Jenkins: apache-atlas-nightly #636

2017-02-22 Thread Apache Jenkins Server

See 


Changes:

[kbhatt] ATLAS-1502 - Fix for not getting atlas application properties using

--
[...truncated 488.88 KB...]
127.0.0.1 - - [22/Feb/2017:15:55:41 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:42 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:42 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:42 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:42 +] "POST 
/api/atlas/entities/5fc3ab6b-b584-4ddb-aa9e-afff262941da/traits HTTP/1.1" 201 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:42 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:42 +] "POST 
/api/atlas/entities/5fc3ab6b-b584-4ddb-aa9e-afff262941da/traits HTTP/1.1" 201 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:42 +] "DELETE 
/api/atlas/entities/5fc3ab6b-b584-4ddb-aa9e-afff262941da/traits/TraitlJImJmmTRl 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:42 +] "POST 
/api/atlas/entities/5fc3ab6b-b584-4ddb-aa9e-afff262941da?property=description 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:42 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:42 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:42 +] "DELETE 
/api/atlas/entities?type=hive_table=qualifiedName=table-vTXND1x1Jp
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.635 sec - in 
org.apache.atlas.notification.EntityNotificationIT
Running org.apache.atlas.notification.NotificationHookConsumerIT
127.0.0.1 - - [22/Feb/2017:15:55:46 +] "GET /api/atlas/types/tableType 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:46 +] "GET /api/atlas/types/serdeType 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:46 +] "GET /api/atlas/types/classification 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:46 +] "GET /api/atlas/types/hive_db_v1 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:47 +] "GET 
/api/atlas/discovery/search/dsl?query=hive_db+where+qualifiedName%3D'dbcEGgeV4kOA'=10=0
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:48 +] "GET 
/api/atlas/entities?type=hive_db=qualifiedName=dbcEGgeV4kOA 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:48 +] "GET 
/api/atlas/entities/e59db08f-cd89-4333-ba7a-8dec0f2d0749/audit?count=1 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:48 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:48 +] "GET 
/api/atlas/entities/012fdcf5-818a-4b89-990c-aa7ff52c2618 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:48 +] "GET 
/api/atlas/entities/012fdcf5-818a-4b89-990c-aa7ff52c2618 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:48 +] "GET 
/api/atlas/discovery/search/dsl?query=hive_db+where+name%3D'dbFDObBVup6A'=10=0
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:49 +] "GET 
/api/atlas/discovery/search/dsl?query=hive_db+where+name%3D'dbFDObBVup6A'=10=0
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:50 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:50 +] "GET 
/api/atlas/discovery/search/dsl?query=hive_db+where+qualifiedName%3D'dbP1HuMS13rd'=10=0
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:51 +] "GET 
/api/atlas/entities?type=hive_db=qualifiedName=dbP1HuMS13rd 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:51 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:51 +] "GET 
/api/atlas/entities?type=hive_db=qualifiedName=dbmjekzot5yV 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:51 +] "GET 
/api/atlas/entities?type=hive_db=qualifiedName=dbmjekzot5yV 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:51 +] "GET 
/api/atlas/entities?type=hive_db=qualifiedName=dbmjekzot5yV 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:51 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:51 +] "GET 
/api/atlas/discovery/search/dsl?query=hive_db+where+qualifiedName%3D'dbxU9YieyLe5'=10=0
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [22/Feb/2017:15:55:52 +] "GET

[jira] [Commented] (ATLAS-1567) Regression: AtlasHook for falcon seems to be broken, it is not invoked when a falcon cluster entity is submitted


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

Nixon Rodrigues commented on ATLAS-1567:


The issue was occurring because hadoop-common jar being present in two 
locations.
{noformat}
java.lang.LinkageError: loader constraint violation: when resolving method 
"org.apache.falcon.security.CurrentUser.getAuthenticatedUGI()Lorg/apache/hadoop/security/UserGroupInformation;"
 the class loader (instance of 
org/apache/atlas/plugin/classloader/AtlasPluginClassLoader) of the current 
class, org/apache/atlas/falcon/Util/EventUtil, and the class loader (instance 
of sun/misc/Launcher$AppClassLoader) for the method's defining class, 
org/apache/falcon/security/CurrentUser, have different Class objects for the 
type org/apache/hadoop/security/UserGroupInformation used in the signature
at org.apache.atlas.falcon.Util.EventUtil.getUser(EventUtil.java:55)
at 
org.apache.atlas.falcon.service.AtlasService.addEntity(AtlasService.java:127)
at 
org.apache.atlas.falcon.service.AtlasService.onAdd(AtlasService.java:67)
at 
org.apache.atlas.falcon.service.AtlasService.onAdd(AtlasService.java:120)
{noformat}
This I have removed hadoop-common jar from falcon hook packaging by changing 
the falcon pom.xml.
Verified that hadoop-common jar is not packaged in 
hook/falcon/atlas-falcon-plugin-impl/ distribution.

I have attached patch for it.

> Regression: AtlasHook for falcon seems to be broken, it is not invoked when a 
> falcon cluster entity is submitted
> 
>
> Key: ATLAS-1567
> URL: https://issues.apache.org/jira/browse/ATLAS-1567
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: trunk
>Reporter: Ayub Khan
>Assignee: Nixon Rodrigues
>Priority: Blocker
> Fix For: trunk, 0.8-incubating
>
> Attachments: ATLAS-1567.patch
>
>
> Falcon logs showing the cluster submitted successfully, but still the hook is 
> not invoked
> {noformat}
> 2017-02-17 19:23:40,020 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:] ~ HttpServletRequest RemoteUser is 
> hrt_qa (Servlets:47)
> 2017-02-17 19:23:40,020 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Logging in hrt_qa (CurrentUser:65)
> 2017-02-17 19:23:40,021 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Request from authenticated user: hrt_qa, URL=/api/entities/submit/cluster, 
> doAs user: null (FalconAuthenticationFilter:185)
> 2017-02-17 19:23:40,021 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Authorizing user=hrt_qa against request=RequestParts{resource='entities', 
> action='submit', entityType='cluster'} (FalconAuthorizationFilter:78)
> 2017-02-17 19:23:40,021 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Authorization for action=submit will be done in the API 
> (DefaultAuthorizationProvider:315)
> 2017-02-17 19:23:40,021 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Authorization succeeded for user=hrt_qa, proxy=hrt_qa 
> (FalconAuthorizationFilter:88)
> 2017-02-17 19:23:40,034 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Parsed Entity: cl1 (EntityParser:102)
> 2017-02-17 19:23:40,040 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Parsed Entity: cl1 (EntityParser:102)
> 2017-02-17 19:23:40,040 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Lock acquired for submit on (cluster) cl1 by 726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782 (MemoryLocks:54)
> 2017-02-17 19:23:40,040 ERROR - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Entity node (CLUSTER) cl1 not found in entity graph. (EntityGraph:71)
> 2017-02-17 19:23:40,041 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Successfully released lock on (cluster) cl1 by 726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782 (MemoryLocks:70)
> 2017-02-17 19:23:40,041 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> All locks released on

[jira] [Updated] (ATLAS-1567) Regression: AtlasHook for falcon seems to be broken, it is not invoked when a falcon cluster entity is submitted


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

Nixon Rodrigues updated ATLAS-1567:
---
Attachment: ATLAS-1567.patch

> Regression: AtlasHook for falcon seems to be broken, it is not invoked when a 
> falcon cluster entity is submitted
> 
>
> Key: ATLAS-1567
> URL: https://issues.apache.org/jira/browse/ATLAS-1567
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: trunk
>Reporter: Ayub Khan
>Assignee: Nixon Rodrigues
>Priority: Blocker
> Fix For: trunk, 0.8-incubating
>
> Attachments: ATLAS-1567.patch
>
>
> Falcon logs showing the cluster submitted successfully, but still the hook is 
> not invoked
> {noformat}
> 2017-02-17 19:23:40,020 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:] ~ HttpServletRequest RemoteUser is 
> hrt_qa (Servlets:47)
> 2017-02-17 19:23:40,020 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Logging in hrt_qa (CurrentUser:65)
> 2017-02-17 19:23:40,021 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Request from authenticated user: hrt_qa, URL=/api/entities/submit/cluster, 
> doAs user: null (FalconAuthenticationFilter:185)
> 2017-02-17 19:23:40,021 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Authorizing user=hrt_qa against request=RequestParts{resource='entities', 
> action='submit', entityType='cluster'} (FalconAuthorizationFilter:78)
> 2017-02-17 19:23:40,021 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Authorization for action=submit will be done in the API 
> (DefaultAuthorizationProvider:315)
> 2017-02-17 19:23:40,021 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Authorization succeeded for user=hrt_qa, proxy=hrt_qa 
> (FalconAuthorizationFilter:88)
> 2017-02-17 19:23:40,034 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Parsed Entity: cl1 (EntityParser:102)
> 2017-02-17 19:23:40,040 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Parsed Entity: cl1 (EntityParser:102)
> 2017-02-17 19:23:40,040 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Lock acquired for submit on (cluster) cl1 by 726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782 (MemoryLocks:54)
> 2017-02-17 19:23:40,040 ERROR - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Entity node (CLUSTER) cl1 not found in entity graph. (EntityGraph:71)
> 2017-02-17 19:23:40,041 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Successfully released lock on (cluster) cl1 by 726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782 (MemoryLocks:70)
> 2017-02-17 19:23:40,041 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> All locks released on cl1 (AbstractEntityManager:489)
> 2017-02-17 19:23:40,050 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> {Action:submit, Dimensions:{colo=NULL, entityType=cluster}, Status: 
> SUCCEEDED, Time-taken:26995845 ns} (METRIC:38)
> 2017-02-17 19:23:40,051 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:] ~ Audit: hrt_qa@172.27.21.202 
> performed 
> http://ctr-e129-1487033772569-4286-01-04.hwx.site:15000/api/entities/submit/cluster
>  (172.27.17.129) at 2017-02-17T19:23Z (AUDIT:48)
> 2017-02-17 19:23:40,051 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:] ~ Audit: hrt_qa@172.27.21.202 
> performed 
> http://ctr-e129-1487033772569-4286-01-04.hwx.site:15000/api/entities/submit/cluster
>  (172.27.17.129) at 2017-02-17T19:23Z (AUDIT:48)
> 2017-02-17 19:23:51,101 WARN  - [HiveClientCache-cleaner-0:] ~ Evicted client 
> has non-zero user count: 1 (metastore:443)
> {noformat}
> Falcon running command - showing hook jars classpath
> {noformat}
> [root@ctr-e129-1487033772569-4286-01-04 conf]# ps axu | grep -i falcon
> falcon 66767  0.2  0.2 9242152 751692 ?  Sl   Feb16   4:00 
> /usr/lib/jvm/java-openjdk/bin/java -Xmx1024m

[jira] [Assigned] (ATLAS-1567) Regression: AtlasHook for falcon seems to be broken, it is not invoked when a falcon cluster entity is submitted


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

Nixon Rodrigues reassigned ATLAS-1567:
--

Assignee: Nixon Rodrigues

> Regression: AtlasHook for falcon seems to be broken, it is not invoked when a 
> falcon cluster entity is submitted
> 
>
> Key: ATLAS-1567
> URL: https://issues.apache.org/jira/browse/ATLAS-1567
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: trunk
>Reporter: Ayub Khan
>Assignee: Nixon Rodrigues
>Priority: Blocker
> Fix For: trunk, 0.8-incubating
>
>
> Falcon logs showing the cluster submitted successfully, but still the hook is 
> not invoked
> {noformat}
> 2017-02-17 19:23:40,020 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:] ~ HttpServletRequest RemoteUser is 
> hrt_qa (Servlets:47)
> 2017-02-17 19:23:40,020 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Logging in hrt_qa (CurrentUser:65)
> 2017-02-17 19:23:40,021 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Request from authenticated user: hrt_qa, URL=/api/entities/submit/cluster, 
> doAs user: null (FalconAuthenticationFilter:185)
> 2017-02-17 19:23:40,021 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Authorizing user=hrt_qa against request=RequestParts{resource='entities', 
> action='submit', entityType='cluster'} (FalconAuthorizationFilter:78)
> 2017-02-17 19:23:40,021 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Authorization for action=submit will be done in the API 
> (DefaultAuthorizationProvider:315)
> 2017-02-17 19:23:40,021 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Authorization succeeded for user=hrt_qa, proxy=hrt_qa 
> (FalconAuthorizationFilter:88)
> 2017-02-17 19:23:40,034 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Parsed Entity: cl1 (EntityParser:102)
> 2017-02-17 19:23:40,040 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Parsed Entity: cl1 (EntityParser:102)
> 2017-02-17 19:23:40,040 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Lock acquired for submit on (cluster) cl1 by 726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782 (MemoryLocks:54)
> 2017-02-17 19:23:40,040 ERROR - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Entity node (CLUSTER) cl1 not found in entity graph. (EntityGraph:71)
> 2017-02-17 19:23:40,041 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> Successfully released lock on (cluster) cl1 by 726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782 (MemoryLocks:70)
> 2017-02-17 19:23:40,041 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> All locks released on cl1 (AbstractEntityManager:489)
> 2017-02-17 19:23:40,050 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:hrt_qa:POST//entities/submit/cluster] ~ 
> {Action:submit, Dimensions:{colo=NULL, entityType=cluster}, Status: 
> SUCCEEDED, Time-taken:26995845 ns} (METRIC:38)
> 2017-02-17 19:23:40,051 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:] ~ Audit: hrt_qa@172.27.21.202 
> performed 
> http://ctr-e129-1487033772569-4286-01-04.hwx.site:15000/api/entities/submit/cluster
>  (172.27.17.129) at 2017-02-17T19:23Z (AUDIT:48)
> 2017-02-17 19:23:40,051 INFO  - [726486469@qtp-1828868503-10 - 
> 39424028-a0e3-490f-ba04-1d025619e782:] ~ Audit: hrt_qa@172.27.21.202 
> performed 
> http://ctr-e129-1487033772569-4286-01-04.hwx.site:15000/api/entities/submit/cluster
>  (172.27.17.129) at 2017-02-17T19:23Z (AUDIT:48)
> 2017-02-17 19:23:51,101 WARN  - [HiveClientCache-cleaner-0:] ~ Evicted client 
> has non-zero user count: 1 (metastore:443)
> {noformat}
> Falcon running command - showing hook jars classpath
> {noformat}
> [root@ctr-e129-1487033772569-4286-01-04 conf]# ps axu | grep -i falcon
> falcon 66767  0.2  0.2 9242152 751692 ?  Sl   Feb16   4:00 
> /usr/lib/jvm/java-openjdk/bin/java -Xmx1024m -noverify 
> -Dfalcon.embeddedmq=True

[jira] [Commented] (ATLAS-1502) UI to create/update entities - configuration to restrict entity-types editable via UI


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

Nixon Rodrigues commented on ATLAS-1502:


Thanks Keval for review and commit.
Commit Id http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/dbfca622


> UI to create/update entities - configuration to restrict entity-types 
> editable via UI
> -
>
> Key: ATLAS-1502
> URL: https://issues.apache.org/jira/browse/ATLAS-1502
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Madhan Neethiraj
>Assignee: Kalyani Kashikar
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1502-1.patch, ATLAS-1502.patch
>
>
> ATLAS-1193 introduced UI to create and update entities. Currently the UI 
> allows an user to create entity of any entity-type - including the superTypes 
> like Referenceable, Asset, Process, etc. It may not be useful to support 
> entity creation of many such entity-types via UI. Restricting the UI to 
> support only a subset of entities would make the UI more usable and avoid 
> potential confusion.
> It should be possible to configure the list of entity-types supported via a 
> configuration, to enable deployments to satisfy specific needs. I would 
> suggest to use a configuration like:
> {code}
> atlas.ui.editable.entity.types="type-1,type-2,type3"
> {code}
> - if the configuration is set to an empty value (or not set): UI should not 
> support create/edit of any entity
> - if the configuration is set to is set to "*", then UI should allow 
> create/edit of any type of entity



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (ATLAS-1502) UI to create/update entities - configuration to restrict entity-types editable via UI


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

Nixon Rodrigues edited comment on ATLAS-1502 at 2/22/17 12:56 PM:
--

Sometimes there was issue in loading atlas application properties from 
classpath using PropertiesConfiguration api, so changed this to use 
org.apache.atlas.ApplicationProperties which internally wraps 
PropertiesConfiguration which loads application properties from conf directory.
I have added this fix in ATLAS-1502-1.patch


was (Author: nixonrodrigues):
Sometimes there was issue in loading atlas application properties using 
PropertiesConfiguration api, so changed this to use 
org.apache.atlas.ApplicationProperties which internally wraps 
PropertiesConfiguration which loads application properties from conf directory.
I have added this fix in ATLAS-1502-1.patch

> UI to create/update entities - configuration to restrict entity-types 
> editable via UI
> -
>
> Key: ATLAS-1502
> URL: https://issues.apache.org/jira/browse/ATLAS-1502
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Madhan Neethiraj
>Assignee: Kalyani Kashikar
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1502-1.patch, ATLAS-1502.patch
>
>
> ATLAS-1193 introduced UI to create and update entities. Currently the UI 
> allows an user to create entity of any entity-type - including the superTypes 
> like Referenceable, Asset, Process, etc. It may not be useful to support 
> entity creation of many such entity-types via UI. Restricting the UI to 
> support only a subset of entities would make the UI more usable and avoid 
> potential confusion.
> It should be possible to configure the list of entity-types supported via a 
> configuration, to enable deployments to satisfy specific needs. I would 
> suggest to use a configuration like:
> {code}
> atlas.ui.editable.entity.types="type-1,type-2,type3"
> {code}
> - if the configuration is set to an empty value (or not set): UI should not 
> support create/edit of any entity
> - if the configuration is set to is set to "*", then UI should allow 
> create/edit of any type of entity



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1502) UI to create/update entities - configuration to restrict entity-types editable via UI


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

Keval Bhatt commented on ATLAS-1502:


+1 for the ATLAS-1502.1.patch

> UI to create/update entities - configuration to restrict entity-types 
> editable via UI
> -
>
> Key: ATLAS-1502
> URL: https://issues.apache.org/jira/browse/ATLAS-1502
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Madhan Neethiraj
>Assignee: Kalyani Kashikar
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1502-1.patch, ATLAS-1502.patch
>
>
> ATLAS-1193 introduced UI to create and update entities. Currently the UI 
> allows an user to create entity of any entity-type - including the superTypes 
> like Referenceable, Asset, Process, etc. It may not be useful to support 
> entity creation of many such entity-types via UI. Restricting the UI to 
> support only a subset of entities would make the UI more usable and avoid 
> potential confusion.
> It should be possible to configure the list of entity-types supported via a 
> configuration, to enable deployments to satisfy specific needs. I would 
> suggest to use a configuration like:
> {code}
> atlas.ui.editable.entity.types="type-1,type-2,type3"
> {code}
> - if the configuration is set to an empty value (or not set): UI should not 
> support create/edit of any entity
> - if the configuration is set to is set to "*", then UI should allow 
> create/edit of any type of entity



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1575) Unable to create/edit hive_table entity in UI.


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

Keval Bhatt updated ATLAS-1575:
---
Attachment: ATLAS-1575.patch

> Unable to create/edit hive_table entity in UI.
> ---
>
> Key: ATLAS-1575
> URL: https://issues.apache.org/jira/browse/ATLAS-1575
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1575.patch
>
>
> Set the following value in custom application properties.
> {code}
> atlas.ui.editable.entity.types=*
> {code}  
> Tried to create/edit a hive_table.
> All GET API requests for hive_table succeeded but UI didn't load the 
> attribute list of hive_table to fill values.
> Following exception was thrown in Console Tab. 
> {code}
> Uncaught TypeError: Cannot read property 'queryText' of undefined
> at CreateEntityLayoutView.js:140
> at Function.m.each.m.forEach (underscore-min.js:5)
> at n. (CreateEntityLayoutView.js:138)
> at _ (backbone-min.js:1)
> at m (backbone-min.js:1)
> at f (backbone-min.js:1)
> at n.l.trigger (backbone-min.js:1)
> at n.reset (backbone-min.js:1)
> at Object. (backbone.paginator.min.js:185)
> at _ (backbone-min.js:1)
> at m (backbone-min.js:1)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1502) UI to create/update entities - configuration to restrict entity-types editable via UI


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

Nixon Rodrigues updated ATLAS-1502:
---
Fix Version/s: 0.8-incubating

> UI to create/update entities - configuration to restrict entity-types 
> editable via UI
> -
>
> Key: ATLAS-1502
> URL: https://issues.apache.org/jira/browse/ATLAS-1502
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Madhan Neethiraj
>Assignee: Kalyani Kashikar
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1502-1.patch, ATLAS-1502.patch
>
>
> ATLAS-1193 introduced UI to create and update entities. Currently the UI 
> allows an user to create entity of any entity-type - including the superTypes 
> like Referenceable, Asset, Process, etc. It may not be useful to support 
> entity creation of many such entity-types via UI. Restricting the UI to 
> support only a subset of entities would make the UI more usable and avoid 
> potential confusion.
> It should be possible to configure the list of entity-types supported via a 
> configuration, to enable deployments to satisfy specific needs. I would 
> suggest to use a configuration like:
> {code}
> atlas.ui.editable.entity.types="type-1,type-2,type3"
> {code}
> - if the configuration is set to an empty value (or not set): UI should not 
> support create/edit of any entity
> - if the configuration is set to is set to "*", then UI should allow 
> create/edit of any type of entity



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1502) UI to create/update entities - configuration to restrict entity-types editable via UI