[jira] [Updated] (ATLAS-2194) In Basic Search for Tag if any columns are removed then UI throws exception

2017-10-09 Thread Keval Bhatt (JIRA)

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

Keval Bhatt updated ATLAS-2194:
---
Component/s: atlas-webui

> In Basic Search for Tag if any columns are removed then UI throws exception
> ---
>
> Key: ATLAS-2194
> URL: https://issues.apache.org/jira/browse/ATLAS-2194
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Tejas Rawool
>Assignee: Keval Bhatt
> Fix For: 1.0.0, 0.8.2
>
> Attachments: ATLAS-2194.patch
>
>
> Steps to Reproduce:-
> 1.Create a new Tag and click on its Search Tag
> 2.Now remove few columns (e.g:- Tags and Type)
> 3.In Console Error appears on "SearchResultLayoutView"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-2194) In Basic Search for Tag if any columns are removed then UI throws exception

2017-10-09 Thread Keval Bhatt (JIRA)

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

Keval Bhatt updated ATLAS-2194:
---
Fix Version/s: 0.8.2
   1.0.0

> In Basic Search for Tag if any columns are removed then UI throws exception
> ---
>
> Key: ATLAS-2194
> URL: https://issues.apache.org/jira/browse/ATLAS-2194
> Project: Atlas
>  Issue Type: Bug
>Reporter: Tejas Rawool
>Assignee: Keval Bhatt
> Fix For: 1.0.0, 0.8.2
>
> Attachments: ATLAS-2194.patch
>
>
> Steps to Reproduce:-
> 1.Create a new Tag and click on its Search Tag
> 2.Now remove few columns (e.g:- Tags and Type)
> 3.In Console Error appears on "SearchResultLayoutView"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-2171) Error in constructing base path for UI API when accessing Atlas via knox proxy without "/" at the end

2017-10-09 Thread Keval Bhatt (JIRA)

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

Keval Bhatt updated ATLAS-2171:
---
Fix Version/s: 0.8.2
   1.0.0

> Error in constructing base path for UI API when accessing Atlas via knox 
> proxy without "/" at the end
> -
>
> Key: ATLAS-2171
> URL: https://issues.apache.org/jira/browse/ATLAS-2171
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Critical
> Fix For: 1.0.0, 0.8.2
>
> Attachments: ATLAS-2171.patch
>
>
> 1. Enabled knox proxy for atlas.
> 2.Accessed Atlas UI via proxy using https://knox_gateway:8443/gateway/ui/atlas
> 3. Provided admin username and password and logged into Atlas
> 4. Now, opened another tab in browser with URL
> {code}
> https://knox_gateway:8443/gateway/ui/atlas
> {code}
> UI is loaded without data because API path is not formed properly.
> If the URL is accessed with "/" at the end, logs in as admin user and all 
> operations work fine.
> Example :
> {code}
> https://knox_gateway:8443/gateway/ui/atlas/
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (ATLAS-2195) Stale transaction eviction errors observed in atlas application logs

2017-10-09 Thread Ayub Pathan (JIRA)
Ayub Pathan created ATLAS-2195:
--

 Summary: Stale transaction eviction errors observed in atlas 
application logs
 Key: ATLAS-2195
 URL: https://issues.apache.org/jira/browse/ATLAS-2195
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 0.8.2
Reporter: Ayub Pathan
Priority: Critical
 Fix For: 0.8.2


{noformat}
2017-10-09 20:18:20,728 ERROR - [Thread-371:] ~ Evicted 
[258@ac1b1980131887-ctr-e134-1499953498516-209460-01-04-hwx-site1] from 
cache but waiting too long for transactions to close. Stale transaction alert 
on: [standardtitantx[null], standardtitantx[null]] (ManagementLogger:189)
2017-10-09 20:18:20,738 ERROR - [Thread-370:] ~ Evicted 
[257@ac1b1980131887-ctr-e134-1499953498516-209460-01-04-hwx-site1] from 
cache but waiting too long for transactions to close. Stale transaction alert 
on: [standardtitantx[null], standardtitantx[null]] (ManagementLogger:189)
2017-10-09 20:18:20,808 ERROR - [Thread-372:] ~ Evicted 
[259@ac1b1980131887-ctr-e134-1499953498516-209460-01-04-hwx-site1] from 
cache but waiting too long for transactions to close. Stale transaction alert 
on: [standardtitantx[null], standardtitantx[null]] (ManagementLogger:189)
2017-10-09 20:18:25,658 ERROR - [Thread-373:] ~ Evicted 
[260@ac1b1980131887-ctr-e134-1499953498516-209460-01-04-hwx-site1] from 
cache but waiting too long for transactions to close. Stale transaction alert 
on: [standardtitantx[null], standardtitantx[null]] (ManagementLogger:189)
2017-10-09 20:18:25,698 ERROR - [Thread-374:] ~ Evicted 
[261@ac1b1980131887-ctr-e134-1499953498516-209460-01-04-hwx-site1] from 
cache but waiting too long for transactions to close. Stale transaction alert 
on: [standardtitantx[null], standardtitantx[null]] (ManagementLogger:189)
2017-10-09 20:18:25,721 ERROR - [Thread-375:] ~ Evicted 
[262@ac1b1980131887-ctr-e134-1499953498516-209460-01-04-hwx-site1] from 
cache but waiting too long for transactions to close. Stale transaction alert 
on: [standardtitantx[null], standardtitantx[null]] (ManagementLogger:189)
2017-10-09 20:18:25,739 ERROR - [Thread-376:] ~ Evicted 
[263@ac1b1980131887-ctr-e134-1499953498516-209460-01-04-hwx-site1] from 
cache but waiting too long for transactions to close. Stale transaction alert 
on: [standardtitantx[null], standardtitantx[null]] (ManagementLogger:189)
2017-10-09 20:18:25,778 ERROR - [Thread-377:] ~ Evicted 
[264@ac1b1980131887-ctr-e134-1499953498516-209460-01-04-hwx-site1] from 
cache but waiting too long for transactions to close. Stale transaction alert 
on: [standardtitantx[null], standardtitantx[null]] (ManagementLogger:189)
2017-10-09 20:18:30,661 ERROR - [Thread-378:] ~ Evicted 
[265@ac1b1980131887-ctr-e134-1499953498516-209460-01-04-hwx-site1] from 
cache but waiting too long for transactions to close. Stale transaction alert 
on: [standardtitantx[null], standardtitantx[null]] (ManagementLogger:189)
2017-10-09 20:18:30,687 ERROR - [Thread-379:] ~ Evicted 
[266@ac1b1980131887-ctr-e134-1499953498516-209460-01-04-hwx-site1] from 
cache but waiting too long for transactions to close. Stale transaction alert 
on: [standardtitantx[null], standardtitantx[null]] (ManagementLogger:189)
{noformat}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Re: Review Request 59821: ATLAS-1805:Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to Atlas

2017-10-09 Thread Madhan Neethiraj

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


Ship it!




Ship It!

- Madhan Neethiraj


On Oct. 9, 2017, 10:10 p.m., Ramesh Mani wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/59821/
> ---
> 
> (Updated Oct. 9, 2017, 10:10 p.m.)
> 
> 
> Review request for atlas and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-1805
> https://issues.apache.org/jira/browse/ATLAS-1805
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-1805: Provide an Atlas hook to send Hbase Namespace/Table/column family 
> metadata to Atlas
> 
> 
> Diffs
> -
> 
>   addons/hbase-bridge-shim/pom.xml PRE-CREATION 
>   
> addons/hbase-bridge-shim/src/main/java/org/apache/atlas/hbase/hook/HBaseAtlasCoprocessor.java
>  PRE-CREATION 
>   addons/hbase-bridge/pom.xml PRE-CREATION 
>   
> addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java
>  PRE-CREATION 
>   
> addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/hook/HBaseAtlasCoprocessor.java
>  PRE-CREATION 
>   
> addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/hook/HBaseAtlasCoprocessorBase.java
>  PRE-CREATION 
>   
> addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/model/HBaseDataTypes.java
>  PRE-CREATION 
>   
> addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/model/HBaseOperationContext.java
>  PRE-CREATION 
>   addons/hbase-bridge/src/main/resources/atlas-hbase-import-log4j.xml 
> PRE-CREATION 
>   
> addons/hbase-bridge/src/test/java/org/apache/atlas/hbase/HBaseAtlasHookTest.java
>  PRE-CREATION 
>   addons/models/1000-Hadoop/1060-hbase_model.json 3e46e06 
>   addons/models/patches/001-hbase_table_column_family_add_attribute.json 
> PRE-CREATION 
>   distro/src/main/assemblies/standalone-package.xml 215cb23 
>   pom.xml 39ae6e7 
> 
> 
> Diff: https://reviews.apache.org/r/59821/diff/6/
> 
> 
> Testing
> ---
> 
> * Review comments fixed with 2 exceptions whcih I have commented on 
> * Added an IT test
> * Testing done in LOCAL VM
> 
> 
> Thanks,
> 
> Ramesh Mani
> 
>



Re: Review Request 59821: ATLAS-1805:Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to Atlas

2017-10-09 Thread Ramesh Mani

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

(Updated Oct. 9, 2017, 10:10 p.m.)


Review request for atlas and Madhan Neethiraj.


Changes
---

Update after fixing review commands


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


Repository: atlas


Description
---

ATLAS-1805: Provide an Atlas hook to send Hbase Namespace/Table/column family 
metadata to Atlas


Diffs (updated)
-

  addons/hbase-bridge-shim/pom.xml PRE-CREATION 
  
addons/hbase-bridge-shim/src/main/java/org/apache/atlas/hbase/hook/HBaseAtlasCoprocessor.java
 PRE-CREATION 
  addons/hbase-bridge/pom.xml PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java
 PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/hook/HBaseAtlasCoprocessor.java
 PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/hook/HBaseAtlasCoprocessorBase.java
 PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/model/HBaseDataTypes.java
 PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/model/HBaseOperationContext.java
 PRE-CREATION 
  addons/hbase-bridge/src/main/resources/atlas-hbase-import-log4j.xml 
PRE-CREATION 
  
addons/hbase-bridge/src/test/java/org/apache/atlas/hbase/HBaseAtlasHookTest.java
 PRE-CREATION 
  addons/models/1000-Hadoop/1060-hbase_model.json 3e46e06 
  addons/models/patches/001-hbase_table_column_family_add_attribute.json 
PRE-CREATION 
  distro/src/main/assemblies/standalone-package.xml 215cb23 
  pom.xml 39ae6e7 


Diff: https://reviews.apache.org/r/59821/diff/6/

Changes: https://reviews.apache.org/r/59821/diff/5-6/


Testing
---

* Review comments fixed with 2 exceptions whcih I have commented on 
* Added an IT test
* Testing done in LOCAL VM


Thanks,

Ramesh Mani



Build failed in Jenkins: Atlas-master-UnitTests #124

2017-10-09 Thread Apache Jenkins Server
See 


Changes:

[madhan] ATLAS-2194 : In Basic Search for Tag if any columns are removed then UI

[madhan] ATLAS-2171: Atlas UI fix when accessed via Knox proxy without / at the

--
[...truncated 509.12 KB...]
at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:74)
at 
com.sun.jersey.api.client.WebResource$Builder.method(WebResource.java:634)
at 
org.apache.atlas.AtlasBaseClient.callAPIWithResource(AtlasBaseClient.java:334)
at 
org.apache.atlas.AtlasBaseClient.callAPIWithResource(AtlasBaseClient.java:311)
at org.apache.atlas.AtlasBaseClient.callAPI(AtlasBaseClient.java:227)
at 
org.apache.atlas.AtlasClient.callAPIWithQueryParams(AtlasClient.java:962)
at org.apache.atlas.AtlasClient.listTypes(AtlasClient.java:344)
at org.apache.atlas.web.security.SSLTest.testService(SSLTest.java:147)

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.filters.ActiveServerFilterTest
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.987 sec - in 
org.apache.atlas.web.filters.ActiveServerFilterTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.filters.AtlasCSRFPreventionFilterTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.289 sec - in 
org.apache.atlas.web.filters.AtlasCSRFPreventionFilterTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.filters.AtlasAuthenticationKerberosFilterTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.339 sec - in 
org.apache.atlas.web.filters.AtlasAuthenticationKerberosFilterTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.filters.AuditFilterTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.222 sec - in 
org.apache.atlas.web.filters.AuditFilterTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.service.AtlasZookeeperSecurityPropertiesTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.411 sec - in 
org.apache.atlas.web.service.AtlasZookeeperSecurityPropertiesTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.service.ServiceStateTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.859 sec - in 
org.apache.atlas.web.service.ServiceStateTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.service.CuratorFactoryTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.161 sec - in 
org.apache.atlas.web.service.CuratorFactoryTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.service.SecureEmbeddedServerTest
Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 48.591 sec <<< 
FAILURE! - in org.apache.atlas.web.service.SecureEmbeddedServerTest
testServerConfiguredUsingCredentialProvider(org.apache.atlas.web.service.SecureEmbeddedServerTest)
  Time elapsed: 43.818 sec  <<< FAILURE!
java.lang.AssertionError: War deploy failed
at sun.security.ssl.InputRecord.read(InputRecord.java:505)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983)
at 
sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1385)
at 
sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1413)
at 
sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1397)
at 
sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559)
at 
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
at 
sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:153)
at 
org.apache.atlas.web.service.SecureEmbeddedServerTest.testServerConfiguredUsingCredentialProvider(SecureEmbeddedServerTest.java:74)

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.service.ActiveInstanceStateTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.893 sec - in 
org.apache.atlas.web.service.ActiveInstanceStateTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.service.ActiveInstanceElectorServiceTest
Tests run: 14, Failures: 0, Errors: 0, S

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

2017-10-09 Thread Apache Jenkins Server
See 


Changes:

[madhan] ATLAS-2194 : In Basic Search for Tag if any columns are removed then UI

[madhan] ATLAS-2171: Atlas UI fix when accessed via Knox proxy without / at the

--
[...truncated 505.77 KB...]
Expected exception org.apache.atlas.AtlasServiceException but got 
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
Caused by: com.sun.jersey.api.client.ClientHandlerException: 
java.net.ConnectException: Connection refused (Connection refused)
Caused by: java.net.ConnectException: Connection refused (Connection refused)

setUp(org.apache.atlas.web.integration.EntityJerseyResourceIT)  Time elapsed: 
0.173 sec  <<< FAILURE!
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.EntityJerseyResourceIT.setUp(EntityJerseyResourceIT.java:87)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.EntityJerseyResourceIT.setUp(EntityJerseyResourceIT.java:87)

testDuplicateCreate(org.apache.atlas.web.integration.TypedefsJerseyResourceIT)  
Time elapsed: 0.006 sec  <<< FAILURE!
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testDuplicateCreate(TypedefsJerseyResourceIT.java:112)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testDuplicateCreate(TypedefsJerseyResourceIT.java:112)

testInvalidGets(org.apache.atlas.web.integration.TypedefsJerseyResourceIT)  
Time elapsed: 0.001 sec  <<< FAILURE!
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testInvalidGets(TypedefsJerseyResourceIT.java:197)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testInvalidGets(TypedefsJerseyResourceIT.java:197)

testListTypesByFilter(org.apache.atlas.web.integration.TypedefsJerseyResourceIT)
  Time elapsed: 0.006 sec  <<< FAILURE!
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testListTypesByFilter(TypedefsJerseyResourceIT.java:277)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testListTypesByFilter(TypedefsJerseyResourceIT.java:277)

testUpdate(org.apache.atlas.web.integration.TypedefsJerseyResourceIT)  Time 
elapsed: 0 sec  <<< FAILURE!
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testUpdate(TypedefsJerseyResourceIT.java:133)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testUpdate(TypedefsJerseyResourceIT.java:133)

testGetDefinitionForNonexistentType(org.apache.atlas.web.integration.TypesJerseyResourceIT)
  Time elapsed: 0.001 sec  <<< FAILURE!
org.testng.TestException: 

Expected exception org.apache.atlas.AtlasServiceException but got 
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypesJerseyResourceIT.testGetDefinitionForNonexistentType(TypesJerseyResourceIT.java:167)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypesJerseyResourceIT.testGetDefinitionForNonexistentType(TypesJerseyResourceIT.java:167)

testGetTraitNames(org.apache.atlas.web.integration.TypesJerseyResourceIT)  Time 
elapsed: 0.041 sec  <<< FAILURE!
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypesJerseyResourceIT.addTraits(TypesJerseyResourceIT.java:226)
at 
org.apache.atlas.web.integration.TypesJerseyResourceIT.testGetTraitNames(TypesJerseyResourceIT.java:188)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypesJerseyResourceIT.addTraits(TypesJerseyResourceIT.java:226)
at 
org.apache.atlas.web.integration.TypesJerseyResourceIT.testGetTraitNames(TypesJerseyResourceIT.java:188)

testListTypesByFilter(org.apache.atlas.web.integration.TypesJerseyR

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

2017-10-09 Thread Apache Jenkins Server
See 


Changes:

[madhan] ATLAS-2194 : In Basic Search for Tag if any columns are removed then UI

[madhan] ATLAS-2171: Atlas UI fix when accessed via Knox proxy without / at the

--
[...truncated 476.66 KB...]
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testDuplicateCreate(TypedefsJerseyResourceIT.java:112)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testDuplicateCreate(TypedefsJerseyResourceIT.java:112)

testInvalidGets(org.apache.atlas.web.integration.TypedefsJerseyResourceIT)  
Time elapsed: 0.001 sec  <<< FAILURE!
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testInvalidGets(TypedefsJerseyResourceIT.java:197)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testInvalidGets(TypedefsJerseyResourceIT.java:197)

testListTypesByFilter(org.apache.atlas.web.integration.TypedefsJerseyResourceIT)
  Time elapsed: 0.002 sec  <<< FAILURE!
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testListTypesByFilter(TypedefsJerseyResourceIT.java:277)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testListTypesByFilter(TypedefsJerseyResourceIT.java:277)

testUpdate(org.apache.atlas.web.integration.TypedefsJerseyResourceIT)  Time 
elapsed: 0.001 sec  <<< FAILURE!
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testUpdate(TypedefsJerseyResourceIT.java:133)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testUpdate(TypedefsJerseyResourceIT.java:133)

testDuplicateSubmit(org.apache.atlas.web.integration.TypesJerseyResourceIT)  
Time elapsed: 0.003 sec  <<< FAILURE!
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypesJerseyResourceIT.testDuplicateSubmit(TypesJerseyResourceIT.java:102)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypesJerseyResourceIT.testDuplicateSubmit(TypesJerseyResourceIT.java:102)

testGetDefinitionForNonexistentType(org.apache.atlas.web.integration.TypesJerseyResourceIT)
  Time elapsed: 0.001 sec  <<< FAILURE!
org.testng.TestException: 

Expected exception org.apache.atlas.AtlasServiceException but got 
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypesJerseyResourceIT.testGetDefinitionForNonexistentType(TypesJerseyResourceIT.java:167)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypesJerseyResourceIT.testGetDefinitionForNonexistentType(TypesJerseyResourceIT.java:167)

testGetTraitNames(org.apache.atlas.web.integration.TypesJerseyResourceIT)  Time 
elapsed: 0.037 sec  <<< FAILURE!
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypesJerseyResourceIT.addTraits(TypesJerseyResourceIT.java:226)
at 
org.apache.atlas.web.integration.TypesJerseyResourceIT.testGetTraitNames(TypesJerseyResourceIT.java:188)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypesJerseyResourceIT.addTraits(TypesJerseyResourceIT.java:226)
at 
org.apache.atlas.web.integration.TypesJerseyResourceIT.testGetTraitNames(TypesJerseyResourceIT.java:188)

testListTypesByFilter(org.apache.atlas.web.integration.TypesJerseyResourceIT)  
Time elapsed: 0.011 sec  <<< FAILURE!
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypesJerseyResourceIT.testListTypesByFilter(TypesJerseyResourceIT.java:206)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypesJerseyResourceIT.testListTypesByFilter(TypesJerseyResourceIT.java:206)

testUpdate(org.apache.atlas.web.integration.TypesJerseyResourceIT)  Time 
elapsed: 0.002 sec  

[jira] [Commented] (ATLAS-2194) In Basic Search for Tag if any columns are removed then UI throws exception

2017-10-09 Thread Madhan Neethiraj (JIRA)

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

Madhan Neethiraj commented on ATLAS-2194:
-

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

> In Basic Search for Tag if any columns are removed then UI throws exception
> ---
>
> Key: ATLAS-2194
> URL: https://issues.apache.org/jira/browse/ATLAS-2194
> Project: Atlas
>  Issue Type: Bug
>Reporter: Tejas Rawool
>Assignee: Keval Bhatt
> Attachments: ATLAS-2194.patch
>
>
> Steps to Reproduce:-
> 1.Create a new Tag and click on its Search Tag
> 2.Now remove few columns (e.g:- Tags and Type)
> 3.In Console Error appears on "SearchResultLayoutView"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Re: Review Request 62838: ATLAS-2171 : Error in constructing base path for UI API when accessing Atlas via knox proxy without "/" at the end

2017-10-09 Thread Madhan Neethiraj

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


Ship it!




Ship It!

- Madhan Neethiraj


On Oct. 9, 2017, 2:04 p.m., keval bhatt wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62838/
> ---
> 
> (Updated Oct. 9, 2017, 2:04 p.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj, Nixon Rodrigues, and Sharmadha 
> Sainath.
> 
> 
> Bugs: ATLAS-2171
> https://issues.apache.org/jira/browse/ATLAS-2171
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> 1. Enabled knox proxy for atlas.
> 2.Accessed Atlas UI via proxy using https://knox_gateway:8443/gateway/ui/atlas
> 3. Provided admin username and password and logged into Atlas
> 4. Now, opened another tab in browser with URL: 
> https://knox_gateway:8443/gateway/ui/atlas
> 
> UI is loaded without data because API path is not formed properly.
> 
> If the URL is accessed with "/" at the end, logs in as admin user and all 
> operations work fine.
> Example : https://knox_gateway:8443/gateway/ui/atlas/
> 
> 
> Fix detail.
> 
> Added one regex to form correct API base url.
> 
> Regex condition.
> 
> it is checking if url exnds with slash then exclude it or if url ends with 
> file extention i.e (.html or .jsp) then exclude that file extention with 
> slash.
> 
> Example of regex input = output:
> 
> 1. https://knox_gateway:8443/gateway/ui/atlas/ = 
> https://knox_gateway:8443/gateway/ui/atlas
> 2. https://knox_gateway:8443/gateway/ui/atlas/index.html = 
> https://knox_gateway:8443/gateway/ui/atlas
> 3. https://knox_gateway:8443/gateway/ui/atlas/index.jsp = 
> https://knox_gateway:8443/gateway/ui/atlas
> 4. https://knox_gateway:8443/gateway/ui/atlas = 
> https://knox_gateway:8443/gateway/ui/atlas
> 
> 
> Diffs
> -
> 
>   dashboardv2/public/css/scss/loader.scss d323212 
>   dashboardv2/public/index.html.tpl f13f34a 
>   
> dashboardv2/public/js/templates/business_catalog/SideNavLayoutView_tmpl.html 
> 3f4c11a 
>   dashboardv2/public/js/utils/UrlLinks.js 913df24 
>   dashboardv2/public/js/utils/Utils.js 1de2106 
>   dashboardv2/public/js/views/business_catalog/SideNavLayoutView.js 1a2590c 
>   dashboardv2/public/js/views/graph/LineageLayoutView.js 46f7117 
> 
> 
> Diff: https://reviews.apache.org/r/62838/diff/1/
> 
> 
> Testing
> ---
> 
> Tested with normal url and also proxy url its working as expected.
> 
> 
> Thanks,
> 
> keval bhatt
> 
>



[jira] [Updated] (ATLAS-1839) Area 3 of the open metadata model - including the Glossary

2017-10-09 Thread David Radley (JIRA)

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

David Radley updated ATLAS-1839:

Attachment: ATLAS1839.patch

https://reviews.apache.org/r/62846/

> Area 3 of the open metadata model - including the Glossary
> --
>
> Key: ATLAS-1839
> URL: https://issues.apache.org/jira/browse/ATLAS-1839
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: David Radley
>  Labels: OpenMetadata, VirtualDataConnector
> Attachments: ATLAS1839.patch
>
>
> This task delivers the JSON files for the new models that describe types for 
> Area 3 in the open metadata model. This area covers the glossary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Review Request 62846: ATLAS1839 Add area 3 types for glossary

2017-10-09 Thread David Radley

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

Review request for atlas, Nigel Jones, Madhan Neethiraj, and Mandy Chessell.


Repository: atlas


Description
---

ATLAS1839 Add area 3 types for glossary


Diffs
-

  addons/models/0300-Area3-SubjectArea/0310-Glossary.json PRE-CREATION 
  addons/models/0300-Area3-SubjectArea/0320-CategoryHierarchy.json PRE-CREATION 
  addons/models/0300-Area3-SubjectArea/0330-Terms.json PRE-CREATION 
  addons/models/0300-Area3-SubjectArea/0340-Dictionary.json PRE-CREATION 
  addons/models/0300-Area3-SubjectArea/0350-RelatedTerms.json PRE-CREATION 
  addons/models/0300-Area3-SubjectArea/0360-Contexts.json PRE-CREATION 
  addons/models/0300-Area3-SubjectArea/0370-SemanticAssignment.json 
PRE-CREATION 
  addons/models/0300-Area3-SubjectArea/0380-SpineObjects.json PRE-CREATION 


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


Testing
---

started Atlas with the types and retrieved them using postman


Thanks,

David Radley



[jira] [Updated] (ATLAS-1839) Area 3 of the open metadata model - including the Glossary

2017-10-09 Thread David Radley (JIRA)

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

David Radley updated ATLAS-1839:

Attachment: (was: 0210Glossary.json)

> Area 3 of the open metadata model - including the Glossary
> --
>
> Key: ATLAS-1839
> URL: https://issues.apache.org/jira/browse/ATLAS-1839
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: David Radley
>  Labels: OpenMetadata, VirtualDataConnector
>
> This task delivers the JSON files for the new models that describe types for 
> Area 3 in the open metadata model. This area covers the glossary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-1839) Area 3 of the open metadata model - including the Glossary

2017-10-09 Thread David Radley (JIRA)

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

David Radley updated ATLAS-1839:

Attachment: (was: 0260Contexts.json)

> Area 3 of the open metadata model - including the Glossary
> --
>
> Key: ATLAS-1839
> URL: https://issues.apache.org/jira/browse/ATLAS-1839
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: David Radley
>  Labels: OpenMetadata, VirtualDataConnector
>
> This task delivers the JSON files for the new models that describe types for 
> Area 3 in the open metadata model. This area covers the glossary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-1839) Area 3 of the open metadata model - including the Glossary

2017-10-09 Thread David Radley (JIRA)

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

David Radley updated ATLAS-1839:

Attachment: (was: 0230Terms.json)

> Area 3 of the open metadata model - including the Glossary
> --
>
> Key: ATLAS-1839
> URL: https://issues.apache.org/jira/browse/ATLAS-1839
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: David Radley
>  Labels: OpenMetadata, VirtualDataConnector
>
> This task delivers the JSON files for the new models that describe types for 
> Area 3 in the open metadata model. This area covers the glossary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-1839) Area 3 of the open metadata model - including the Glossary

2017-10-09 Thread David Radley (JIRA)

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

David Radley updated ATLAS-1839:

Attachment: (was: 0270SemanticAssignment.json)

> Area 3 of the open metadata model - including the Glossary
> --
>
> Key: ATLAS-1839
> URL: https://issues.apache.org/jira/browse/ATLAS-1839
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: David Radley
>  Labels: OpenMetadata, VirtualDataConnector
>
> This task delivers the JSON files for the new models that describe types for 
> Area 3 in the open metadata model. This area covers the glossary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-1839) Area 3 of the open metadata model - including the Glossary

2017-10-09 Thread David Radley (JIRA)

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

David Radley updated ATLAS-1839:

Attachment: (was: 0250RelatedTerms.json)

> Area 3 of the open metadata model - including the Glossary
> --
>
> Key: ATLAS-1839
> URL: https://issues.apache.org/jira/browse/ATLAS-1839
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: David Radley
>  Labels: OpenMetadata, VirtualDataConnector
>
> This task delivers the JSON files for the new models that describe types for 
> Area 3 in the open metadata model. This area covers the glossary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-1839) Area 3 of the open metadata model - including the Glossary

2017-10-09 Thread David Radley (JIRA)

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

David Radley updated ATLAS-1839:

Attachment: (was: 0280SpineObjects.json)

> Area 3 of the open metadata model - including the Glossary
> --
>
> Key: ATLAS-1839
> URL: https://issues.apache.org/jira/browse/ATLAS-1839
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: David Radley
>  Labels: OpenMetadata, VirtualDataConnector
>
> This task delivers the JSON files for the new models that describe types for 
> Area 3 in the open metadata model. This area covers the glossary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-1839) Area 3 of the open metadata model - including the Glossary

2017-10-09 Thread David Radley (JIRA)

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

David Radley updated ATLAS-1839:

Attachment: (was: 0240Dictionary.json)

> Area 3 of the open metadata model - including the Glossary
> --
>
> Key: ATLAS-1839
> URL: https://issues.apache.org/jira/browse/ATLAS-1839
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: David Radley
>  Labels: OpenMetadata, VirtualDataConnector
>
> This task delivers the JSON files for the new models that describe types for 
> Area 3 in the open metadata model. This area covers the glossary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-1839) Area 3 of the open metadata model - including the Glossary

2017-10-09 Thread David Radley (JIRA)

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

David Radley updated ATLAS-1839:

Attachment: (was: 0220CategoryHierarchy.json)

> Area 3 of the open metadata model - including the Glossary
> --
>
> Key: ATLAS-1839
> URL: https://issues.apache.org/jira/browse/ATLAS-1839
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Mandy Chessell
>Assignee: David Radley
>  Labels: OpenMetadata, VirtualDataConnector
>
> This task delivers the JSON files for the new models that describe types for 
> Area 3 in the open metadata model. This area covers the glossary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Review Request 62838: ATLAS-2171 : Error in constructing base path for UI API when accessing Atlas via knox proxy without "/" at the end

2017-10-09 Thread keval bhatt

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

Review request for atlas, Madhan Neethiraj, Nixon Rodrigues, and Sharmadha 
Sainath.


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


Repository: atlas


Description
---

1. Enabled knox proxy for atlas.
2.Accessed Atlas UI via proxy using https://knox_gateway:8443/gateway/ui/atlas
3. Provided admin username and password and logged into Atlas
4. Now, opened another tab in browser with URL: 
https://knox_gateway:8443/gateway/ui/atlas

UI is loaded without data because API path is not formed properly.

If the URL is accessed with "/" at the end, logs in as admin user and all 
operations work fine.
Example : https://knox_gateway:8443/gateway/ui/atlas/


Fix detail.

Added one regex to form correct API base url.

Regex condition.

it is checking if url exnds with slash then exclude it or if url ends with file 
extention i.e (.html or .jsp) then exclude that file extention with slash.

Example of regex input = output:

1. https://knox_gateway:8443/gateway/ui/atlas/ = 
https://knox_gateway:8443/gateway/ui/atlas
2. https://knox_gateway:8443/gateway/ui/atlas/index.html = 
https://knox_gateway:8443/gateway/ui/atlas
3. https://knox_gateway:8443/gateway/ui/atlas/index.jsp = 
https://knox_gateway:8443/gateway/ui/atlas
4. https://knox_gateway:8443/gateway/ui/atlas = 
https://knox_gateway:8443/gateway/ui/atlas


Diffs
-

  dashboardv2/public/css/scss/loader.scss d323212 
  dashboardv2/public/index.html.tpl f13f34a 
  dashboardv2/public/js/templates/business_catalog/SideNavLayoutView_tmpl.html 
3f4c11a 
  dashboardv2/public/js/utils/UrlLinks.js 913df24 
  dashboardv2/public/js/utils/Utils.js 1de2106 
  dashboardv2/public/js/views/business_catalog/SideNavLayoutView.js 1a2590c 
  dashboardv2/public/js/views/graph/LineageLayoutView.js 46f7117 


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


Testing
---

Tested with normal url and also proxy url its working as expected.


Thanks,

keval bhatt



[jira] [Updated] (ATLAS-2194) In Basic Search for Tag if any columns are removed then UI throws exception

2017-10-09 Thread Keval Bhatt (JIRA)

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

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

> In Basic Search for Tag if any columns are removed then UI throws exception
> ---
>
> Key: ATLAS-2194
> URL: https://issues.apache.org/jira/browse/ATLAS-2194
> Project: Atlas
>  Issue Type: Bug
>Reporter: Tejas Rawool
>Assignee: Keval Bhatt
> Attachments: ATLAS-2194.patch
>
>
> Steps to Reproduce:-
> 1.Create a new Tag and click on its Search Tag
> 2.Now remove few columns (e.g:- Tags and Type)
> 3.In Console Error appears on "SearchResultLayoutView"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-2171) Error in constructing base path for UI API when accessing Atlas via knox proxy without "/" at the end

2017-10-09 Thread Keval Bhatt (JIRA)

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

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

> Error in constructing base path for UI API when accessing Atlas via knox 
> proxy without "/" at the end
> -
>
> Key: ATLAS-2171
> URL: https://issues.apache.org/jira/browse/ATLAS-2171
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: ATLAS-2171.patch
>
>
> 1. Enabled knox proxy for atlas.
> 2.Accessed Atlas UI via proxy using https://knox_gateway:8443/gateway/ui/atlas
> 3. Provided admin username and password and logged into Atlas
> 4. Now, opened another tab in browser with URL
> {code}
> https://knox_gateway:8443/gateway/ui/atlas
> {code}
> UI is loaded without data because API path is not formed properly.
> If the URL is accessed with "/" at the end, logs in as admin user and all 
> operations work fine.
> Example :
> {code}
> https://knox_gateway:8443/gateway/ui/atlas/
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-2194) In Basic Search for Tag if any columns are removed then UI throws exception

2017-10-09 Thread Tejas Rawool (JIRA)

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

Tejas Rawool updated ATLAS-2194:

Description: 
Steps to Reproduce:-
1.Create a new Tag and click on its Search Tag
2.Now remove few columns (e.g:- Tags and Type)
3.In Console Error appears on "SearchResultLayoutView"

> In Basic Search for Tag if any columns are removed then UI throws exception
> ---
>
> Key: ATLAS-2194
> URL: https://issues.apache.org/jira/browse/ATLAS-2194
> Project: Atlas
>  Issue Type: Bug
>Reporter: Tejas Rawool
>Assignee: Keval Bhatt
>
> Steps to Reproduce:-
> 1.Create a new Tag and click on its Search Tag
> 2.Now remove few columns (e.g:- Tags and Type)
> 3.In Console Error appears on "SearchResultLayoutView"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (ATLAS-2194) In Basic Search for Tag if any columns are removed then UI throws exception

2017-10-09 Thread Keval Bhatt (JIRA)

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

Keval Bhatt reassigned ATLAS-2194:
--

Assignee: Keval Bhatt

> In Basic Search for Tag if any columns are removed then UI throws exception
> ---
>
> Key: ATLAS-2194
> URL: https://issues.apache.org/jira/browse/ATLAS-2194
> Project: Atlas
>  Issue Type: Bug
>Reporter: Tejas Rawool
>Assignee: Keval Bhatt
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (ATLAS-2194) In Basic Search for Tag if any columns are removed then UI throws exception

2017-10-09 Thread Tejas Rawool (JIRA)
Tejas Rawool created ATLAS-2194:
---

 Summary: In Basic Search for Tag if any columns are removed then 
UI throws exception
 Key: ATLAS-2194
 URL: https://issues.apache.org/jira/browse/ATLAS-2194
 Project: Atlas
  Issue Type: Bug
Reporter: Tejas Rawool






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-2171) Error in constructing base path for UI API when accessing Atlas via knox proxy without "/" at the end

2017-10-09 Thread Keval Bhatt (JIRA)

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

Keval Bhatt updated ATLAS-2171:
---
Attachment: (was: ATLAS-2171.patch)

> Error in constructing base path for UI API when accessing Atlas via knox 
> proxy without "/" at the end
> -
>
> Key: ATLAS-2171
> URL: https://issues.apache.org/jira/browse/ATLAS-2171
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Critical
>
> 1. Enabled knox proxy for atlas.
> 2.Accessed Atlas UI via proxy using https://knox_gateway:8443/gateway/ui/atlas
> 3. Provided admin username and password and logged into Atlas
> 4. Now, opened another tab in browser with URL
> {code}
> https://knox_gateway:8443/gateway/ui/atlas
> {code}
> UI is loaded without data because API path is not formed properly.
> If the URL is accessed with "/" at the end, logs in as admin user and all 
> operations work fine.
> Example :
> {code}
> https://knox_gateway:8443/gateway/ui/atlas/
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Build failed in Jenkins: Atlas-master-UnitTests #123

2017-10-09 Thread Apache Jenkins Server
See 


Changes:

[david_radley] ATLAS1836 Add Area 0 models

--
[...truncated 509.06 KB...]
at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:74)
at 
com.sun.jersey.api.client.WebResource$Builder.method(WebResource.java:634)
at 
org.apache.atlas.AtlasBaseClient.callAPIWithResource(AtlasBaseClient.java:334)
at 
org.apache.atlas.AtlasBaseClient.callAPIWithResource(AtlasBaseClient.java:311)
at org.apache.atlas.AtlasBaseClient.callAPI(AtlasBaseClient.java:227)
at 
org.apache.atlas.AtlasClient.callAPIWithQueryParams(AtlasClient.java:962)
at org.apache.atlas.AtlasClient.listTypes(AtlasClient.java:344)
at org.apache.atlas.web.security.SSLTest.testService(SSLTest.java:147)

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.security.FileAuthenticationTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.908 sec - in 
org.apache.atlas.web.security.FileAuthenticationTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.security.UserDaoTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.727 sec - in 
org.apache.atlas.web.security.UserDaoTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.resources.AdminExportTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.22 sec - in 
org.apache.atlas.web.resources.AdminExportTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.resources.EntityResourceTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.61 sec - in 
org.apache.atlas.web.resources.EntityResourceTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.resources.TaxonomyServiceTest
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.004 sec - in 
org.apache.atlas.web.resources.TaxonomyServiceTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.resources.AdminResourceTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.097 sec - in 
org.apache.atlas.web.resources.AdminResourceTest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.adapters.TestEntityREST$6
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.338 sec - in 
org.apache.atlas.web.adapters.TestEntityREST$6
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.adapters.TestEntityREST$4
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.228 sec - in 
org.apache.atlas.web.adapters.TestEntityREST$4
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.adapters.TestEntityREST$5
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.24 sec - in 
org.apache.atlas.web.adapters.TestEntityREST$5
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.adapters.TestEntitiesREST
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.624 sec - in 
org.apache.atlas.web.adapters.TestEntitiesREST
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.adapters.TestEntityREST$1
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.215 sec - in 
org.apache.atlas.web.adapters.TestEntityREST$1
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.adapters.TestEntityREST
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.93 sec - in 
org.apache.atlas.web.adapters.TestEntityREST
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.adapters.TestEntityREST$2
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.265 sec - in 
org.apache.atlas.web.adapters.TestEntityREST$2
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Running org.apache.atlas.web.adapters.TestEntityREST$7
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.218 sec - in 
org.apache.atlas.web.adapters.TestEntityREST$7
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
su

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

2017-10-09 Thread Apache Jenkins Server
See 


Changes:

[david_radley] ATLAS1836 Add Area 0 models

--
[...truncated 466.72 KB...]
at 
org.apache.atlas.examples.QuickStartV2IT.runQuickStart(QuickStartV2IT.java:49)

setUp(org.apache.atlas.notification.NotificationHookConsumerIT)  Time elapsed: 
0.175 sec  <<< FAILURE!
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.notification.NotificationHookConsumerIT.setUp(NotificationHookConsumerIT.java:55)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.notification.NotificationHookConsumerIT.setUp(NotificationHookConsumerIT.java:55)

testGetVersion(org.apache.atlas.web.integration.AdminJerseyResourceIT)  Time 
elapsed: 0.001 sec  <<< FAILURE!
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.AdminJerseyResourceIT.testGetVersion(AdminJerseyResourceIT.java:40)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.AdminJerseyResourceIT.testGetVersion(AdminJerseyResourceIT.java:40)

setUp(org.apache.atlas.web.integration.DataSetLineageJerseyResourceIT)  Time 
elapsed: 0.175 sec  <<< FAILURE!
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.DataSetLineageJerseyResourceIT.setUp(DataSetLineageJerseyResourceIT.java:56)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.DataSetLineageJerseyResourceIT.setUp(DataSetLineageJerseyResourceIT.java:56)

setUp(org.apache.atlas.web.integration.EntityJerseyResourceIT)  Time elapsed: 
0.173 sec  <<< FAILURE!
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.EntityJerseyResourceIT.setUp(EntityJerseyResourceIT.java:87)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.EntityJerseyResourceIT.setUp(EntityJerseyResourceIT.java:87)

testDuplicateCreate(org.apache.atlas.web.integration.TypedefsJerseyResourceIT)  
Time elapsed: 0.006 sec  <<< FAILURE!
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testDuplicateCreate(TypedefsJerseyResourceIT.java:112)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testDuplicateCreate(TypedefsJerseyResourceIT.java:112)

testInvalidGets(org.apache.atlas.web.integration.TypedefsJerseyResourceIT)  
Time elapsed: 0.001 sec  <<< FAILURE!
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testInvalidGets(TypedefsJerseyResourceIT.java:197)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testInvalidGets(TypedefsJerseyResourceIT.java:197)

testListTypesByFilter(org.apache.atlas.web.integration.TypedefsJerseyResourceIT)
  Time elapsed: 0.005 sec  <<< FAILURE!
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testListTypesByFilter(TypedefsJerseyResourceIT.java:277)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testListTypesByFilter(TypedefsJerseyResourceIT.java:277)

testUpdate(org.apache.atlas.web.integration.TypedefsJerseyResourceIT)  Time 
elapsed: 0.001 sec  <<< FAILURE!
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testUpdate(TypedefsJerseyResourceIT.java:133)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypedefsJerseyResourceIT.testUpdate(TypedefsJerseyResourceIT.java:133)

testDuplicateSubmit(org.apache.atlas.web.integration.TypesJerseyResourceIT)  
Time elapsed: 0.003 sec  <<< FAILURE!
com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: 
Connection refused (Connection refused)
at 
org.apache.atlas.web.integration.TypesJerseyResourceIT.testDuplicateSubmit(TypesJe

[jira] [Updated] (ATLAS-2171) Error in constructing base path for UI API when accessing Atlas via knox proxy without "/" at the end

2017-10-09 Thread Keval Bhatt (JIRA)

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

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

> Error in constructing base path for UI API when accessing Atlas via knox 
> proxy without "/" at the end
> -
>
> Key: ATLAS-2171
> URL: https://issues.apache.org/jira/browse/ATLAS-2171
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: ATLAS-2171.patch
>
>
> 1. Enabled knox proxy for atlas.
> 2.Accessed Atlas UI via proxy using https://knox_gateway:8443/gateway/ui/atlas
> 3. Provided admin username and password and logged into Atlas
> 4. Now, opened another tab in browser with URL
> {code}
> https://knox_gateway:8443/gateway/ui/atlas
> {code}
> UI is loaded without data because API path is not formed properly.
> If the URL is accessed with "/" at the end, logs in as admin user and all 
> operations work fine.
> Example :
> {code}
> https://knox_gateway:8443/gateway/ui/atlas/
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (ATLAS-2171) Error in constructing base path for UI API when accessing Atlas via knox proxy without "/" at the end

2017-10-09 Thread Keval Bhatt (JIRA)

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

Keval Bhatt commented on ATLAS-2171:


[~ssainath] Since the trailing slash in browser URL is manipulated, the base 
path for API is not correctly formed and causes 404 for API call and data is 
not loaded on UI.

> Error in constructing base path for UI API when accessing Atlas via knox 
> proxy without "/" at the end
> -
>
> Key: ATLAS-2171
> URL: https://issues.apache.org/jira/browse/ATLAS-2171
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Critical
>
> 1. Enabled knox proxy for atlas.
> 2.Accessed Atlas UI via proxy using https://knox_gateway:8443/gateway/ui/atlas
> 3. Provided admin username and password and logged into Atlas
> 4. Now, opened another tab in browser with URL
> {code}
> https://knox_gateway:8443/gateway/ui/atlas
> {code}
> I was not logged in as admin but as an unknown user.No read/write operations 
> were allowed. Found the following application logs :
> {code}
> 2017-09-26 05:39:31,467 ERROR - [pool-2-thread-9:] ~ Unable to find Atlas 
> Resource corresponding to :
> Setting UNKNOWN (AtlasAuthorizationUtils:143)
> {code}
> If the URL is accessed with "/" at the end , logs in as admin user and all 
> operations work fine.
> Example :
> {code}
> https://knox_gateway:8443/gateway/ui/atlas/
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-2171) Error in constructing base path for UI API when accessing Atlas via knox proxy without "/" at the end

2017-10-09 Thread Keval Bhatt (JIRA)

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

Keval Bhatt updated ATLAS-2171:
---
Description: 
1. Enabled knox proxy for atlas.
2.Accessed Atlas UI via proxy using https://knox_gateway:8443/gateway/ui/atlas
3. Provided admin username and password and logged into Atlas
4. Now, opened another tab in browser with URL
{code}
https://knox_gateway:8443/gateway/ui/atlas
{code}

UI is loaded without data because API path is not formed properly.

If the URL is accessed with "/" at the end, logs in as admin user and all 
operations work fine.
Example :
{code}
https://knox_gateway:8443/gateway/ui/atlas/
{code}



  was:
1. Enabled knox proxy for atlas.
2.Accessed Atlas UI via proxy using https://knox_gateway:8443/gateway/ui/atlas
3. Provided admin username and password and logged into Atlas
4. Now, opened another tab in browser with URL
{code}
https://knox_gateway:8443/gateway/ui/atlas
{code}
I was not logged in as admin but as an unknown user.No read/write operations 
were allowed. Found the following application logs :
{code}
2017-09-26 05:39:31,467 ERROR - [pool-2-thread-9:] ~ Unable to find Atlas 
Resource corresponding to :
Setting UNKNOWN (AtlasAuthorizationUtils:143)
{code}

If the URL is accessed with "/" at the end , logs in as admin user and all 
operations work fine.
Example :
{code}
https://knox_gateway:8443/gateway/ui/atlas/
{code}




> Error in constructing base path for UI API when accessing Atlas via knox 
> proxy without "/" at the end
> -
>
> Key: ATLAS-2171
> URL: https://issues.apache.org/jira/browse/ATLAS-2171
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Critical
>
> 1. Enabled knox proxy for atlas.
> 2.Accessed Atlas UI via proxy using https://knox_gateway:8443/gateway/ui/atlas
> 3. Provided admin username and password and logged into Atlas
> 4. Now, opened another tab in browser with URL
> {code}
> https://knox_gateway:8443/gateway/ui/atlas
> {code}
> UI is loaded without data because API path is not formed properly.
> If the URL is accessed with "/" at the end, logs in as admin user and all 
> operations work fine.
> Example :
> {code}
> https://knox_gateway:8443/gateway/ui/atlas/
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-2171) Error in constructing base path for UI API when accessing Atlas via knox proxy without "/" at the end

2017-10-09 Thread Keval Bhatt (JIRA)

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

Keval Bhatt updated ATLAS-2171:
---
Summary: Error in constructing base path for UI API when accessing Atlas 
via knox proxy without "/" at the end  (was: Error in parsing API when 
accessing Atlas via knox proxy without "/" at the end)

> Error in constructing base path for UI API when accessing Atlas via knox 
> proxy without "/" at the end
> -
>
> Key: ATLAS-2171
> URL: https://issues.apache.org/jira/browse/ATLAS-2171
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Critical
>
> 1. Enabled knox proxy for atlas.
> 2.Accessed Atlas UI via proxy using https://knox_gateway:8443/gateway/ui/atlas
> 3. Provided admin username and password and logged into Atlas
> 4. Now, opened another tab in browser with URL
> {code}
> https://knox_gateway:8443/gateway/ui/atlas
> {code}
> I was not logged in as admin but as an unknown user.No read/write operations 
> were allowed. Found the following application logs :
> {code}
> 2017-09-26 05:39:31,467 ERROR - [pool-2-thread-9:] ~ Unable to find Atlas 
> Resource corresponding to :
> Setting UNKNOWN (AtlasAuthorizationUtils:143)
> {code}
> If the URL is accessed with "/" at the end , logs in as admin user and all 
> operations work fine.
> Example :
> {code}
> https://knox_gateway:8443/gateway/ui/atlas/
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-2171) Error in parsing API when accessing Atlas via knox proxy without "/" at the end

2017-10-09 Thread Keval Bhatt (JIRA)

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

Keval Bhatt updated ATLAS-2171:
---
Attachment: (was: ATLAS-2171.patch)

> Error in parsing API when accessing Atlas via knox proxy without "/" at the 
> end
> ---
>
> Key: ATLAS-2171
> URL: https://issues.apache.org/jira/browse/ATLAS-2171
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Critical
>
> 1. Enabled knox proxy for atlas.
> 2.Accessed Atlas UI via proxy using https://knox_gateway:8443/gateway/ui/atlas
> 3. Provided admin username and password and logged into Atlas
> 4. Now, opened another tab in browser with URL
> {code}
> https://knox_gateway:8443/gateway/ui/atlas
> {code}
> I was not logged in as admin but as an unknown user.No read/write operations 
> were allowed. Found the following application logs :
> {code}
> 2017-09-26 05:39:31,467 ERROR - [pool-2-thread-9:] ~ Unable to find Atlas 
> Resource corresponding to :
> Setting UNKNOWN (AtlasAuthorizationUtils:143)
> {code}
> If the URL is accessed with "/" at the end , logs in as admin user and all 
> operations work fine.
> Example :
> {code}
> https://knox_gateway:8443/gateway/ui/atlas/
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-2171) Error in parsing API when accessing Atlas via knox proxy without "/" at the end

2017-10-09 Thread Sharmadha Sainath (JIRA)

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

Sharmadha Sainath updated ATLAS-2171:
-
Summary: Error in parsing API when accessing Atlas via knox proxy without 
"/" at the end  (was: Accessing atlas via knox proxy without "/" at the end 
logs in as UNKNOWN user)

> Error in parsing API when accessing Atlas via knox proxy without "/" at the 
> end
> ---
>
> Key: ATLAS-2171
> URL: https://issues.apache.org/jira/browse/ATLAS-2171
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: ATLAS-2171.patch
>
>
> 1. Enabled knox proxy for atlas.
> 2.Accessed Atlas UI via proxy using https://knox_gateway:8443/gateway/ui/atlas
> 3. Provided admin username and password and logged into Atlas
> 4. Now, opened another tab in browser with URL
> {code}
> https://knox_gateway:8443/gateway/ui/atlas
> {code}
> I was not logged in as admin but as an unknown user.No read/write operations 
> were allowed. Found the following application logs :
> {code}
> 2017-09-26 05:39:31,467 ERROR - [pool-2-thread-9:] ~ Unable to find Atlas 
> Resource corresponding to :
> Setting UNKNOWN (AtlasAuthorizationUtils:143)
> {code}
> If the URL is accessed with "/" at the end , logs in as admin user and all 
> operations work fine.
> Example :
> {code}
> https://knox_gateway:8443/gateway/ui/atlas/
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-2171) Accessing atlas via knox proxy without "/" at the end logs in as UNKNOWN user

2017-10-09 Thread Keval Bhatt (JIRA)

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

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

> Accessing atlas via knox proxy without "/" at the end logs in as UNKNOWN user
> -
>
> Key: ATLAS-2171
> URL: https://issues.apache.org/jira/browse/ATLAS-2171
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: ATLAS-2171.patch
>
>
> 1. Enabled knox proxy for atlas.
> 2.Accessed Atlas UI via proxy using https://knox_gateway:8443/gateway/ui/atlas
> 3. Provided admin username and password and logged into Atlas
> 4. Now, opened another tab in browser with URL
> {code}
> https://knox_gateway:8443/gateway/ui/atlas
> {code}
> I was not logged in as admin but as an unknown user.No read/write operations 
> were allowed. Found the following application logs :
> {code}
> 2017-09-26 05:39:31,467 ERROR - [pool-2-thread-9:] ~ Unable to find Atlas 
> Resource corresponding to :
> Setting UNKNOWN (AtlasAuthorizationUtils:143)
> {code}
> If the URL is accessed with "/" at the end , logs in as admin user and all 
> operations work fine.
> Example :
> {code}
> https://knox_gateway:8443/gateway/ui/atlas/
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (ATLAS-2171) Accessing atlas via knox proxy without "/" at the end logs in as UNKNOWN user

2017-10-09 Thread Keval Bhatt (JIRA)

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

Keval Bhatt reassigned ATLAS-2171:
--

Assignee: Keval Bhatt

> Accessing atlas via knox proxy without "/" at the end logs in as UNKNOWN user
> -
>
> Key: ATLAS-2171
> URL: https://issues.apache.org/jira/browse/ATLAS-2171
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Critical
>
> 1. Enabled knox proxy for atlas.
> 2.Accessed Atlas UI via proxy using https://knox_gateway:8443/gateway/ui/atlas
> 3. Provided admin username and password and logged into Atlas
> 4. Now, opened another tab in browser with URL
> {code}
> https://knox_gateway:8443/gateway/ui/atlas
> {code}
> I was not logged in as admin but as an unknown user.No read/write operations 
> were allowed. Found the following application logs :
> {code}
> 2017-09-26 05:39:31,467 ERROR - [pool-2-thread-9:] ~ Unable to find Atlas 
> Resource corresponding to :
> Setting UNKNOWN (AtlasAuthorizationUtils:143)
> {code}
> If the URL is accessed with "/" at the end , logs in as admin user and all 
> operations work fine.
> Example :
> {code}
> https://knox_gateway:8443/gateway/ui/atlas/
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)