Build failed in Jenkins: Atlas-master-IntegrationTests #787

2018-03-16 Thread Apache Jenkins Server 
See 


--
[...truncated 660.21 KB...]
[INFO] --- maven-failsafe-plugin:2.18.1:integration-test (integration-test) @ 
falcon-bridge ---
[WARNING] useSystemClassloader setting has no effect when not forking
[INFO] Failsafe report directory: 

Running org.apache.atlas.falcon.hook.FalconHookIT
127.0.0.1 - - [17/Mar/2018:00:50:57 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_cluster=qualifiedName=clusterf9EKdCKx44
 HTTP/1.1" 404 106 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:50:57 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_cluster=qualifiedName=clusterf9EKdCKx44
 HTTP/1.1" 404 106 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:50:58 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_cluster=qualifiedName=clusterf9EKdCKx44
 HTTP/1.1" 404 106 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:50:58 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_cluster=qualifiedName=clusterf9EKdCKx44
 HTTP/1.1" 404 106 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:50:59 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_cluster=qualifiedName=clusterf9EKdCKx44
 HTTP/1.1" 404 106 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:50:59 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_cluster=qualifiedName=clusterf9EKdCKx44
 HTTP/1.1" 404 106 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:50:59 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed=qualifiedName=feedGpfcUCzEkq@clusterzroSHXcogP
 HTTP/1.1" 404 118 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:51:00 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed=qualifiedName=feedGpfcUCzEkq@clusterzroSHXcogP
 HTTP/1.1" 404 118 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:51:00 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed=qualifiedName=feedGpfcUCzEkq@clusterzroSHXcogP
 HTTP/1.1" 404 118 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:51:01 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed=qualifiedName=feedGpfcUCzEkq@clusterzroSHXcogP
 HTTP/1.1" 200 923 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:51:01 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed=qualifiedName=feedGpfcUCzEkq@clusterzroSHXcogP
 HTTP/1.1" 200 923 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:51:01 +] "GET 
//localhost:31000/api/atlas/entities/7ec33767-ae93-4ac9-96a7-c909338eb561 
HTTP/1.1" 200 923 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:51:01 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed_creation=qualifiedName=feedGpfcUCzEkq@clusterzroSHXcogP
 HTTP/1.1" 200 1266 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:51:01 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed_creation=qualifiedName=feedGpfcUCzEkq@clusterzroSHXcogP
 HTTP/1.1" 200 1266 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:51:01 +] "GET 
//localhost:31000/api/atlas/entities/ff8e273f-3a5b-4b99-a18e-897fb4e7f250 
HTTP/1.1" 200 1266 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:51:01 +] "GET 
//localhost:31000/api/atlas/entities/1eb3d801-cc65-4c15-9c4a-ca5e66f62d63 
HTTP/1.1" 200 1018 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:51:01 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed=qualifiedName=feed6evqKjQjz4@clusterzroSHXcogP
 HTTP/1.1" 404 118 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:51:01 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed=qualifiedName=feed6evqKjQjz4@clusterzroSHXcogP
 HTTP/1.1" 200 923 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:51:01 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed=qualifiedName=feed6evqKjQjz4@clusterzroSHXcogP
 HTTP/1.1" 200 923 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:51:01 +] "GET 
//localhost:31000/api/atlas/entities/9bdbaef6-0a19-44d4-a4c5-00fa872f9138 
HTTP/1.1" 200 923 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:51:01 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed_creation=qualifiedName=feed6evqKjQjz4@clusterzroSHXcogP
 HTTP/1.1" 200 1267 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:51:01 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed_creation=qualifiedName=feed6evqKjQjz4@clusterzroSHXcogP
 HTTP/1.1" 200 1267 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:51:02 +] "GET 
//localhost:31000/api/atlas/entities/04092ad5-c737-435b-992c-0036b18d9e16 
HTTP/1.1" 200 1267 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:51:02 +] "GET 
//localhost:31000/api/atlas/entities/e777a138-299c-43e3-8759-303220d25b76 
HTTP/1.1" 200 1127 "-" "Java/1.8.0_152"
127.0.0.1 - - [17/Mar/2018:00:51:02 +] "GET

[jira] [Resolved] (ATLAS-2484) UI - Need validation for Start Date and End Date while applying validity period

2018-03-16 Thread Nixon Rodrigues (JIRA) 

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

Nixon Rodrigues resolved ATLAS-2484.

Resolution: Fixed

Thanks [~pratik24mac] for the patch. Committed patch to master

commit id -> http://git-wip-us.apache.org/repos/asf/atlas/commit/242733c0

> UI - Need validation for Start Date and End Date while applying validity 
> period
> ---
>
> Key: ATLAS-2484
> URL: https://issues.apache.org/jira/browse/ATLAS-2484
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0-alpha
>Reporter: Tejas Rawool
>Assignee: pratik pandey
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2484.patch
>
>
> While assigning Tags to Entity, If Apply Validity Period is checked then 
> Start Date should not be greater then End Date and Time Zone should not 
> accept empty values.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas

2018-03-16 Thread Graham Wallis (JIRA) 

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

Graham Wallis updated ATLAS-1773:
-
Attachment: ATLAS-1773-16-03-2018.patch

> Create the OMRS Connector for Atlas
> ---
>
> Key: ATLAS-1773
> URL: https://issues.apache.org/jira/browse/ATLAS-1773
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: Graham Wallis
>Priority: Major
> Attachments: ATLAS-1773-06-03-2018.patch, 
> ATLAS-1773-08-03-2018.patch, ATLAS-1773-09-03-2018.patch, 
> ATLAS-1773-15-03-2018.patch, ATLAS-1773-16-03-2018.patch
>
>
> This JIRA provides the definition of the OMRS Connector API and an 
> implementation of this API for a local Apache Atlas metadata repository and 
> for the OMRS REST API.
> The OMRS Connector has 3 API groups
> * The types API - this is the metadata API for a metadata repository
> * The entity and relationships APIs that provide the type-agnostic interfaces 
> that can access any type - even those added dynamically
> * The fine-grained type-safe APIs that are generated from the addons models 
> in the build.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

re: .8 Apache Atlas Connector for IGC

2018-03-16 Thread Ernie Ostic 


My apologies everyone!   It was good news to share, but accidental to be on
the whole list!   Sorry for filling everyone's inbox with that extra
info.; )



Ernie Ostic

Worldwide Technical Sales
InfoSphere Information Server
IBM Analytics

Cell: (617) 331 8238
---
Apache Atlas Update!
https://dsrealtime.wordpress.com/2017/11/16/apache-atlas-update-have-you-been-watching/

Open IGC is here!
https://dsrealtime.wordpress.com/2015/07/29/open-igc-is-here/

Re: Review Request 66111: AtlasClientV2 should support create of relationship

2018-03-16 Thread Nixon Rodrigues 

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


Ship it!




Ship It!

- Nixon Rodrigues


On March 16, 2018, 8:58 a.m., Nigel Jones wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66111/
> ---
> 
> (Updated March 16, 2018, 8:58 a.m.)
> 
> 
> Review request for atlas, David Radley, Graham Wallis, and Madhan Neethiraj.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Add support to Atlas Client v2 api to allow create of relationships
> 
> 
> Diffs
> -
> 
>   client/client-v2/src/main/java/org/apache/atlas/AtlasClientV2.java 92ad923a 
> 
> 
> Diff: https://reviews.apache.org/r/66111/diff/1/
> 
> 
> Testing
> ---
> 
> See JIRA.
> Still testing, but won't be able to complete for a few weeks so posting for 
> feedback/comments & for others to try :-)
> 
> 
> Thanks,
> 
> Nigel Jones
> 
>

Re: Review Request 66086: ATLAS-2484 : UI - Need validation for Start Date and End Date while applying validity period

2018-03-16 Thread Nixon Rodrigues 

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


Ship it!




Ship It!

- Nixon Rodrigues


On March 15, 2018, 12:31 p.m., pratik pandey wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66086/
> ---
> 
> (Updated March 15, 2018, 12:31 p.m.)
> 
> 
> Review request for atlas, keval bhatt, Madhan Neethiraj, and Nixon Rodrigues.
> 
> 
> Bugs: ATLAS-2484
> https://issues.apache.org/jira/browse/ATLAS-2484
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> While assigning Tags to Entity, If Apply Validity Period is checked then 
> Start Date should not be greater then End Date and Time Zone should not 
> accept empty values.
> 
> 
> Diffs
> -
> 
>   dashboardv2/public/js/templates/tag/AddTagModalView_tmpl.html dbf7d66 
>   dashboardv2/public/js/templates/tag/AddTimezoneView_tmpl.html e7e1289 
>   dashboardv2/public/js/views/tag/AddTagModalView.js 9d60e08 
>   dashboardv2/public/js/views/tag/AddTimezoneItemView.js 015bb51 
> 
> 
> Diff: https://reviews.apache.org/r/66086/diff/1/
> 
> 
> Testing
> ---
> 
> Done one rouond of sanity testing.
> 
> 
> Thanks,
> 
> pratik pandey
> 
>

Re: Review Request 66087: ATLAS-2501 : UI , Tag propagation : On Search results page , entities with propagated tags have "Tag Remove button"

2018-03-16 Thread Nixon Rodrigues 

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


Ship it!




Ship It!

- Nixon Rodrigues


On March 15, 2018, 12:34 p.m., pratik pandey wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66087/
> ---
> 
> (Updated March 15, 2018, 12:34 p.m.)
> 
> 
> Review request for atlas, keval bhatt, Madhan Neethiraj, and Nixon Rodrigues.
> 
> 
> Bugs: ATLAS-2501
> https://issues.apache.org/jira/browse/ATLAS-2501
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> 1. Created 2 Hive tables
> a.test_table
> b.test_table_ctas (CTAS of test_table)
> 2. Created a tag and associated the tag to test_table with propagate set to 
> True. 
> 3. Basic search for the tables listed test_table_ctas with PII tag and remove 
> button. On the detailsPage of test_table_ctas , remove button is not present.
> 
> 
> Diffs
> -
> 
>   dashboardv2/public/css/scss/form.scss 0765dde 
>   dashboardv2/public/js/utils/CommonViewFunction.js 47e50d6 
>   dashboardv2/public/js/views/search/SearchResultLayoutView.js ccc666b 
> 
> 
> Diff: https://reviews.apache.org/r/66087/diff/1/
> 
> 
> Testing
> ---
> 
> Done one round of sanity testing.
> 
> 
> Thanks,
> 
> pratik pandey
> 
>

[jira] [Commented] (ATLAS-2502) UI - Entity page not rendering tags and loader keeps loading when server 403 during deleting classification

2018-03-16 Thread Nixon Rodrigues (JIRA) 

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

Nixon Rodrigues commented on ATLAS-2502:


 +1 for the patch, Thanks [~kevalbhatt]

> UI - Entity page not rendering tags and loader keeps loading when server 403 
> during deleting classification
> ---
>
> Key: ATLAS-2502
> URL: https://issues.apache.org/jira/browse/ATLAS-2502
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: ATLAS-2502.patch, Entitypage.png
>
>
> * Steps to reproduce.
>  * Login with a read-only user.
>  * Go to entity page with classification.
>  * Delete any classification
>  * The keeps on loading indefinitely 
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 66111: AtlasClientV2 should support create of relationship

2018-03-16 Thread David Radley 

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


Ship it!




Ship It!

- David Radley


On March 16, 2018, 8:58 a.m., Nigel Jones wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66111/
> ---
> 
> (Updated March 16, 2018, 8:58 a.m.)
> 
> 
> Review request for atlas, David Radley, Graham Wallis, and Madhan Neethiraj.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Add support to Atlas Client v2 api to allow create of relationships
> 
> 
> Diffs
> -
> 
>   client/client-v2/src/main/java/org/apache/atlas/AtlasClientV2.java 92ad923a 
> 
> 
> Diff: https://reviews.apache.org/r/66111/diff/1/
> 
> 
> Testing
> ---
> 
> See JIRA.
> Still testing, but won't be able to complete for a few weeks so posting for 
> feedback/comments & for others to try :-)
> 
> 
> Thanks,
> 
> Nigel Jones
> 
>

.8 Apache Atlas IGC Connector

2018-03-16 Thread Ernie Ostic 


Hi all...

Been caught in the whirlwind of getting ready for THINK, so forgot to also
mention this other successful side project related to IGC + Atlas.   You
are probably already aware of this "early experiment" project, but just in
case, I wanted to let everyone know that I have a working example of the .8
edition of the Connector that the Information Server team built for one of
our customers that needed/wanted to see an integration with Atlas .8.As
you know, the IMAM/Info Server team are also working hard on the 1.x OMRS
edition, but still, this is an exciting proof point that will also be
useful for some customers that want to do something/anything "right now".
I have it running on my laptop, and can show it to any customers that might
want to see it, or anyone else, and I know the team (Cassio, et. al.) will
also be showing it as needed at one of the PEDs.   Let me know if you have
any questions.

@Mandy/@David --- safe travels to Vegassee you there..@Graham, are
you going?

Thanks.

Ernie







Ernie Ostic

Worldwide Technical Sales
InfoSphere Information Server
IBM Analytics

Cell: (617) 331 8238
---
Apache Atlas Update!
https://dsrealtime.wordpress.com/2017/11/16/apache-atlas-update-have-you-been-watching/

Open IGC is here!
https://dsrealtime.wordpress.com/2015/07/29/open-igc-is-here/

[jira] [Updated] (ATLAS-2503) Fix authorization while creating/updating EnumDef

2018-03-16 Thread Nixon Rodrigues (JIRA) 

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

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

> Fix authorization while creating/updating EnumDef 
> --
>
> Key: ATLAS-2503
> URL: https://issues.apache.org/jira/browse/ATLAS-2503
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-2503.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Review Request 66113: ATLAS-2503 :- Fix authorization while creating/updating EnumDef

2018-03-16 Thread Nixon Rodrigues 

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

Review request for atlas, Apoorv Naik, Ashutosh Mestry, deepak sharma, Madhan 
Neethiraj, and Sharmadha Sainath.


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


Repository: atlas


Description
---

This patch includes changes to add authz verify method call to verify authz 
allowed for that action in AtlasEnumDef and AtlasRelationShipDef store.


Diffs
-

  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEnumDefStoreV1.java
 5bd9c12e 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipDefStoreV1.java
 7163e427 


Diff: https://reviews.apache.org/r/66113/diff/1/


Testing
---

Build and Existing UT's / IT's passing.
Tested with DATA-SCIENTIST and DATA-STEWARD role users.


Thanks,

Nixon Rodrigues

[jira] [Commented] (ATLAS-1990) Regression :Traits Attribute that References Another Entity

2018-03-16 Thread Mark Kiami (JIRA) 

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

Mark Kiami commented on ATLAS-1990:
---

Thank you [~madhan.neethiraj] for kindly providing the links. 

I think in my case, I will need to create a relationship to the entity instead 
of a classification.

It would be good to have this documented in one easily accessible place.

> Regression :Traits Attribute that References Another Entity
> ---
>
> Key: ATLAS-1990
> URL: https://issues.apache.org/jira/browse/ATLAS-1990
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
> Environment: HDP2.6
>Reporter: Benjamin BONNET
>Priority: Major
>
> Hi,
> I defined a trait that includes one attribute. That attribute has type 
> "hive_column", i.e. it references a hive_column entity.
> Using Altas 0.5 on a HDP 2.4, I could attach that trait to an entity so that 
> it refers a column. But using Atlas 0.8 on a HDP 2.6 that does not work 
> anymore (I get a NullPointerException).
> I tried both V1 and V2 REST API and got the same error.
> Here is a full sample to reproduce that issue.
> Trait definition : 
> {noformat}
> {"enumTypes":[],
>  "structTypes":[],
>  "traitTypes":[{
>"superTypes":[],
>"hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.TraitType",
>"typeName":"Reference",
>"typeDescription":"reference test",
>"attributeDefinitions":[{"name":"ref",
>"dataTypeName":"hive_column",
>   "multiplicity":"required",
>   "isComposite":false,
>   "isUnique":false,
>   "isIndexable":true,
>   "reverseAttributeName":null
>  }
> ]}],
>   "classTypes":[]}
> {noformat}
> Then I use curl to create that type (ref file contains the traits definition):
> {noformat}
> curl -v -u admin:admin -X POST -d "`cat ref`" -H 'Content-Type: 
> application/json' 'http://127.0.0.1:21000/api/atlas/types'
> {noformat}
> Using that command, trait type is created OK on both 0.5 and 0.8.
> Now, I can tag an entity on Atlas 0.5 :
> {noformat}
> curl -v -u admin:admin -X POST -d 
> '{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
>  
> "typeName":"Reference","values":{"ref":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"9e2b0059-8e75-42ce-a32c-fe9a6157caed","version":0,"typeName":"hive_column"}}}'
>  -H "Content-Type: application/json" 
> "http://127.0.0.1:21000/api/atlas/entities/23d1c3e7-7ad9-47b6-ac54-1d507119d00d/traits;
> {noformat}
> I get a HTTP201 :
> < HTTP/1.1 201 Created
> < Date: Tue, 25 Jul 2017 09:11:23 GMT
> < Location: 
> http://127.0.0.1:21000/api/atlas/entities/23d1c3e7-7ad9-47b6-ac54-1d507119d00d/traits/23d1c3e7-7ad9-47b6-ac54-1d507119d00d
> < Content-Type: application/json; charset=UTF-8
> < Transfer-Encoding: chunked
> < Server: Jetty(9.2.12.v20150709)
> <
> * Connection #0 to host 127.0.0.1 left intact
> * Closing connection #0
> {"requestId":"qtp999445351-15 - 
> 6d4b21dd-af88-46f3-91f4-5b3b20b6840c","GUID":"23d1c3e7-7ad9-47b6-ac54-1d507119d00d"}
> And if I check my entity traits, I can see that tag.
> {noformat}
> curl -v -u admin:admin -X GET  
> "http://127.0.0.1:21000/api/atlas/entities/23d1c3e7-7ad9-47b6-ac54-1d507119d00d/traits;
>  * About to connect() to 127.0.0.1 port 21000 (#0)
> *   Trying 127.0.0.1... connected
> * Connected to 127.0.0.1 (127.0.0.1) port 21000 (#0)
> * Server auth using Basic with user 'admin'
> > GET /api/atlas/entities/23d1c3e7-7ad9-47b6-ac54-1d507119d00d/traits HTTP/1.1
> > Authorization: Basic YWRtaW46YWRtaW4=
> > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.19.1 
> > Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> > Host: 127.0.0.1:21000
> > Accept: */*
> >
> < HTTP/1.1 200 OK
> < Date: Tue, 25 Jul 2017 09:13:27 GMT
> < Content-Type: application/json; charset=UTF-8
> < Transfer-Encoding: chunked
> < Server: Jetty(9.2.12.v20150709)
> <
> * Connection #0 to host 127.0.0.1 left intact
> * Closing connection #0
> {"requestId":"qtp999445351-13 - 
> 15a0ce26-484a-4181-9f5a-742227be5d09","GUID":"23d1c3e7-7ad9-47b6-ac54-1d507119d00d","results":["tag1","tag2","Reference","tag3"],"count":4}
> {noformat}
> So far, so good, but If I try to do the same thing Atlas 0.8, i.e. tagging an 
> entity with that trait :
> {noformat}
> curl -v -u admin:admin -X POST -d 
> '{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
>  
>

[jira] [Commented] (ATLAS-2122) OMAG Server

2018-03-16 Thread Mark Ottesen (JIRA) 

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

Mark Ottesen commented on ATLAS-2122:
-

Regarding the event adapter provider, should the OMRS framework be calling the 
initialize method on that object when we call the "instance" method in the REST 
API?  Today it calls the 2-argument initialize method in ConnectorBase from 
getConnector, but the 7-argument initialize method in 
OMRSRepositoryEventMapperBase (which extends ConnectorBase) never gets called, 
so the event mapper isn't getting connected properly on our side.  We're 
(trying to) work around that by adding that call ourselves in the 
LocalOMRSRepositoryConnector constructor in OMRS, which is getting us a bit 
further, as we try to set up the 2-IGC system cohort that Cassio mentions above 
- is that the right place to be trying to do that?

> OMAG Server
> ---
>
> Key: ATLAS-2122
> URL: https://issues.apache.org/jira/browse/ATLAS-2122
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: Mandy Chessell
>Priority: Major
> Attachments: 0002-ATLAS-2122-initial-OMAG-Server-implementation.patch
>
>
> This Jira Assembles the Open Metadata and Governance components into a 
> configurable server to support the OMAS Access Layer, Repository or native 
> metadata repository.
> The OMAG server is a Spring Boot Application with a simple REST API. It takes 
> the user Id of the administrator, the server name and cohort name as path 
> variables, other parameters are passed as request parameters. These are 
> examples of the commands to set up the server using defaults. 
> Query configuration 
> GET http://localhost:8080/omag/admin/{userId}/{serverName}/configuration/ 
> Set server type name: 
> POST 
> http://localhost:8080/omag/admin/{userId}/{serverName}/server-type?typeName={name}
>  
> Set organization name: 
> POST 
> http://localhost:8080/omag/admin//{userId}/{serverName}/organization-name?name={organizationName}
>  
> Enable the access services: 
> POST 
> http://localhost:8080/omag/admin//{userId}/{serverName}/access-services/mode?serviceMode=ENABLED
>  
> Enable the Atlas graph repository: 
> POST 
> http://localhost:8080/omag/admin//{userId}/{serverName}/local-repository/mode?repositoryMode=LOCAL_GRAPH_REPOSITORY
>  
> Enable the in-memory repository: 
> POST 
> http://localhost:8080/omag/admin//{userId}/{serverName}/local-repository/mode?repositoryMode=IN_MEMORY_REPOSITORY
>  
> Enable server as a repository proxy: 
> POST 
> http://localhost:8080/omag/admin//{userId}/{serverName}/local-repository/mode?repositoryMode=REPOSITORY_PROXY
>  
> To add the local repository connection for the repository proxy 
> POST 
> http://localhost:8080/omag/admin//{userId}/{serverName}/local-repository/proxy-details?connectorProvider={javaClassName}={nativeServerURL}
>  
> To add the local repository's event mapper: 
> POST 
> http://localhost:8080/omag/admin//{userId}/{serverName}/local-repository/event-mapper-details?connectorProvider={javaClassName}={resourceName}
>  
> To enable access to a cohort 
> POST 
> http://localhost:8080/omag/admin//{userId}/{serverName}/cohort/{cohortName}/mode?serviceMode=ENABLED
>  
> To remove the local repository 
> POST 
> http://localhost:8080/omag/admin//{userId}/{serverName}/local-repository/mode?repositoryMode=NO_LOCAL_REPOSITORY
>  
> To disable the access services 
> POST 
> http://localhost:8080/omag/admin//{userId}/{serverName}/access-services/mode?serviceMode=DISABLED
>  
> To disconnect from a cohort 
> POST 
> http://localhost:8080/omag/admin//{userId}/{serverName}/cohort/{cohortName}/mode?serviceMode=DISABLED
>  
> To start up OMRS/OMAS services 
> POST http://localhost:8080/omag/admin//{userId}/{serverName}/instance 
> To shutdown OMRS/OMAS services 
> DELETE 
> http://localhost:8080/omag/admin//{userId}/{serverName}/instance?permanent=false
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2488) AtlasClientV2 should support create of relationship

2018-03-16 Thread Nigel Jones (JIRA) 

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

Nigel Jones commented on ATLAS-2488:


I've not yet been able to thoroughly test the new functions and won't be able 
to for a few weeks, so I've posted the patch (updated with Madhan's changes) so 
that others can also review/comments/try out.

> AtlasClientV2 should support create of relationship
> ---
>
> Key: ATLAS-2488
> URL: https://issues.apache.org/jira/browse/ATLAS-2488
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2488-1.patch, ATLAS-2488-2.patch
>
>
> RelationshipREST allows one to create, delete & get relationships
> However the AtlasClientV2 API only has support for get & delete, not create
> This is an omission (bug arguably?) , since the client should reflect what is 
> available via the rest API in a more java-usable form
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Review Request 66111: AtlasClientV2 should support create of relationship

2018-03-16 Thread Nigel Jones 

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

Review request for atlas, David Radley, Graham Wallis, and Madhan Neethiraj.


Repository: atlas


Description
---

Add support to Atlas Client v2 api to allow create of relationships


Diffs
-

  client/client-v2/src/main/java/org/apache/atlas/AtlasClientV2.java 92ad923a 


Diff: https://reviews.apache.org/r/66111/diff/1/


Testing
---

See JIRA.
Still testing, but won't be able to complete for a few weeks so posting for 
feedback/comments & for others to try :-)


Thanks,

Nigel Jones

Build failed in Jenkins: Atlas-0.8-IntegrationTests #186

2018-03-16 Thread Apache Jenkins Server 
See 


Changes:

[kbhatt] ATLAS-2483 : UI - Display of faceted query

--
[...truncated 494.97 KB...]
127.0.0.1 - - [16/Mar/2018:07:47:56 +] "GET 
/api/atlas/v2/entity/uniqueAttribute/type/hdfs_path?attr:qualifiedName=test%241test%2B%2B-%2B%26%26%2B%7C%7C%2B%21%2B%28%2B%29%2B%7B%2B%7D%2B%5B%2B%5D%2B%5E%2B%3C%2B%3E%2B%3B%2B%3A%2B%22%2B%25%2B*%2B%60%2B%7E
 HTTP/1.1" 404 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:47:56 +] "POST /api/atlas/v2/entity HTTP/1.1" 
200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "POST /api/atlas/v2/search/basic 
HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "POST /api/atlas/v2/search/basic 
HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "POST /api/atlas/v2/search/basic 
HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "POST /api/atlas/v2/search/basic 
HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "POST /api/atlas/v2/search/basic 
HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "POST /api/atlas/v2/search/basic 
HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "POST /api/atlas/v2/search/basic 
HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "POST /api/atlas/v2/search/basic 
HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "POST /api/atlas/v2/search/basic 
HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "POST /api/atlas/v2/search/basic 
HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "POST /api/atlas/v2/search/basic 
HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "GET 
/api/atlas/v2/search/fulltext?offset=0=dbsIEQyEuyW1=10 HTTP/1.1" 
200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "GET 
/api/atlas/v2/search/fulltext?query=dbsIEQyEuyW1 HTTP/1.1" 200 - "-" 
"Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "GET 
/api/atlas/v2/search/fulltext?offset=0=dbsIEQyEuyW1=10 HTTP/1.1" 
200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "GET 
/api/atlas/v2/search/fulltext?offset=1=dbsIEQyEuyW1=10 HTTP/1.1" 
200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "GET 
/api/atlas/v2/search/fulltext?offset=0=dbsIEQyEuyW1=1 HTTP/1.1" 200 
- "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "GET 
/api/atlas/v2/search/fulltext?offset=2=dbsIEQyEuyW1=1 HTTP/1.1" 200 
- "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "GET 
/api/atlas/v2/types/typedef/name/tableType HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "GET 
/api/atlas/v2/types/typedef/name/serdeType HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "GET 
/api/atlas/v2/types/typedef/name/classification HTTP/1.1" 200 - "-" 
"Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "GET 
/api/atlas/v2/types/typedef/name/pii_Tag HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "GET 
/api/atlas/v2/types/typedef/name/phi_Tag HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "GET 
/api/atlas/v2/types/typedef/name/pci_Tag HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "GET 
/api/atlas/v2/types/typedef/name/sox_Tag HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "GET 
/api/atlas/v2/types/typedef/name/sec_Tag HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:01 +] "GET 
/api/atlas/v2/types/typedef/name/finance_Tag HTTP/1.1" 200 - "-" 
"Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:02 +] "GET 
/api/atlas/v2/types/typedef/name/Factf5znSwa49n HTTP/1.1" 404 - "-" 
"Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:02 +] "GET 
/api/atlas/v2/types/typedef/name/ETLZ82F87J2vz HTTP/1.1" 404 - "-" 
"Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:02 +] "GET 
/api/atlas/v2/types/typedef/name/DimensionzercZSAssI HTTP/1.1" 404 - "-" 
"Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:02 +] "GET 
/api/atlas/v2/types/typedef/name/Metricf8w5uZl59z HTTP/1.1" 404 - "-" 
"Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:02 +] "GET 
/api/atlas/v2/types/typedef/name/hive_db_v1 HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:02 +] "GET 
/api/atlas/v2/types/typedef/name/hive_column_v1 HTTP/1.1" 200 - "-" 
"Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:02 +] "GET 
/api/atlas/v2/types/typedef/name/hive_table_v1 HTTP/1.1" 200 - "-" 
"Java/1.8.0_152"
127.0.0.1 - - [16/Mar/2018:07:48:02 +] "GET 
/api/atlas/v2/types/typedef/name/hive_process_v1 HTTP/1.1" 200 - "-" 
"Java/1.8.0_152"
127.0.0.1 - -

Build failed in Jenkins: Atlas-0.8-UnitTests #186

2018-03-16 Thread Apache Jenkins Server 
See 


Changes:

[kbhatt] ATLAS-2483 : UI - Display of faceted query

--
[...truncated 248.20 KB...]
at 
org.apache.atlas.repository.graph.DeleteHandler.deleteEdgeReference(DeleteHandler.java:264)
at 
org.apache.atlas.repository.graph.DeleteHandler.deleteTypeVertex(DeleteHandler.java:176)
at 
org.apache.atlas.repository.graph.DeleteHandler.deleteEntities(DeleteHandler.java:124)
at 
org.apache.atlas.repository.graph.GraphBackedMetadataRepository.deleteEntities(GraphBackedMetadataRepository.java:485)
at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.atlas.TestUtils$3.invoke(TestUtils.java:686)
at com.sun.proxy.$Proxy40.deleteEntities(Unknown Source)
at 
org.apache.atlas.repository.graph.GraphBackedMetadataRepositoryDeleteTestBase.deleteEntities(GraphBackedMetadataRepositoryDeleteTestBase.java:236)
at 
org.apache.atlas.repository.graph.GraphBackedMetadataRepositoryDeleteTestBase.testLowerBoundsIgnoredOnCompositeDeletedEntities(GraphBackedMetadataRepositoryDeleteTestBase.java:932)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:85)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:659)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:845)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1153)
at 
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
at org.testng.TestRunner.privateRun(TestRunner.java:771)
at org.testng.TestRunner.run(TestRunner.java:621)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:357)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:352)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:310)
at org.testng.SuiteRunner.run(SuiteRunner.java:259)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1199)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1124)
at org.testng.TestNG.run(TestNG.java:1032)
at 
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
at 
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:129)
at 
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:113)
at 
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:111)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)

testLowerBoundsIgnoredWhenDeletingCompositeEntitesOwnedByMap(org.apache.atlas.repository.graph.GraphBackedRepositoryHardDeleteTest)
  Time elapsed: 1.411 sec  <<< FAILURE!
org.apache.atlas.repository.RepositoryException: 
org.apache.atlas.typesystem.exception.NullRequiredAttributeException: Cannot 
unset required attribute MapValueReferencer.refToMapValue on vertex[id=26112 
type=MapValueReferencer guid=e1fbfa9a-e702-4788-be78-3c484dcbb0c5] edge = 
__MapValueReferencer.refToMapValue
at 
org.apache.atlas.repository.graph.GraphBackedMetadataRepository.deleteEntities(GraphBackedMetadataRepository.java:488)
at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.atlas.TestUtils$3.invoke(TestUtils.java:686)
at com.sun.proxy.$Proxy40.deleteEntities(Unknown Source)
at 
org.apache.atlas.repository.graph.GraphBackedMetadataRepositoryDeleteTestBase.testLowerBoundsIgnoredWhenDeletingCompositeEntitesOwnedByMap(GraphBackedMetadataRepositoryDeleteTestBase.java:999)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at

[jira] [Updated] (ATLAS-2502) UI - Entity page not rendering tags and loader keeps loading when server 403 during deleting classification

2018-03-16 Thread Keval Bhatt (JIRA) 

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

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

> UI - Entity page not rendering tags and loader keeps loading when server 403 
> during deleting classification
> ---
>
> Key: ATLAS-2502
> URL: https://issues.apache.org/jira/browse/ATLAS-2502
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: ATLAS-2502.patch, Entitypage.png
>
>
> * Steps to reproduce.
>  * Login with a read-only user.
>  * Go to entity page with classification.
>  * Delete any classification
>  * The keeps on loading indefinitely 
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2483) UI : Display of faceted query

2018-03-16 Thread Keval Bhatt (JIRA) 

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

Keval Bhatt updated ATLAS-2483:
---
Fix Version/s: 0.8.3
   1.0.0

> UI : Display of faceted query
> -
>
> Key: ATLAS-2483
> URL: https://issues.apache.org/jira/browse/ATLAS-2483
> Project: Atlas
>  Issue Type: Bug
>Reporter: pratik pandey
>Assignee: pratik pandey
>Priority: Minor
> Fix For: 1.0.0, 0.8.3
>
> Attachments: ATLAS-2483-branch0.8.patch, ATLAS-2483.patch
>
>
> On searching using basic search :
> {code:java}
> type  = hive_column
> filter = position != 1 
> {code}
> the applied search is displayed as Type: hive_column AND (AND (position != 1))
> In earlier versions , when OR support wasn't there in UI , same query would 
> display Type: hive_table AND retention = 1
> "hive_column AND (AND (position != 1))" is confusing to user.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2483) UI : Display of faceted query

2018-03-16 Thread pratik pandey (JIRA) 

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

pratik pandey commented on ATLAS-2483:
--

[~kevalbhatt] I have attached the patch for branch-0.8 please take a look.

> UI : Display of faceted query
> -
>
> Key: ATLAS-2483
> URL: https://issues.apache.org/jira/browse/ATLAS-2483
> Project: Atlas
>  Issue Type: Bug
>Reporter: pratik pandey
>Assignee: pratik pandey
>Priority: Minor
> Attachments: ATLAS-2483-branch0.8.patch, ATLAS-2483.patch
>
>
> On searching using basic search :
> {code:java}
> type  = hive_column
> filter = position != 1 
> {code}
> the applied search is displayed as Type: hive_column AND (AND (position != 1))
> In earlier versions , when OR support wasn't there in UI , same query would 
> display Type: hive_table AND retention = 1
> "hive_column AND (AND (position != 1))" is confusing to user.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2483) UI : Display of faceted query

2018-03-16 Thread pratik pandey (JIRA) 

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

pratik pandey updated ATLAS-2483:
-
Attachment: ATLAS-2483-branch0.8.patch

> UI : Display of faceted query
> -
>
> Key: ATLAS-2483
> URL: https://issues.apache.org/jira/browse/ATLAS-2483
> Project: Atlas
>  Issue Type: Bug
>Reporter: pratik pandey
>Assignee: pratik pandey
>Priority: Minor
> Attachments: ATLAS-2483-branch0.8.patch, ATLAS-2483.patch
>
>
> On searching using basic search :
> {code:java}
> type  = hive_column
> filter = position != 1 
> {code}
> the applied search is displayed as Type: hive_column AND (AND (position != 1))
> In earlier versions , when OR support wasn't there in UI , same query would 
> display Type: hive_table AND retention = 1
> "hive_column AND (AND (position != 1))" is confusing to user.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)