[jira] [Resolved] (ATLAS-1440) Inconsistency in DSL search of tag

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-1440.
-
Resolution: Cannot Reproduce

[~ssainath] - this issue could not be reproduced with the most recent build in 
master/0.8-incubating branches. I tried the following DSL queries:
- Asset where isa parent_tag
- Asset where isa child_tag

In both cases, UI returned a single entity where both tags were attached to. 
Can you please try again? This issue might have existed in pre-release 0.8 
builds; and might have been fixed with the updates for basic-search 
implementation.

> Inconsistency in DSL search of tag
> --
>
> Key: ATLAS-1440
> URL: https://issues.apache.org/jira/browse/ATLAS-1440
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Reporter: Sharmadha Sainath
>Priority: Critical
> Attachments: parent_tag_response.txt, parent_tag_UI.png
>
>
> Created tags :
> 1. parent_tag
> 2. child_tag which has parent_tag has Parent tag
> 1.Associated child_tag to the hive_table . DSL query of both child_tag and 
> parent tag listed entity but GET response of hive_table had only child_tag
> This is reported in https://issues.apache.org/jira/browse/ATLAS-1439.
> 2. Associated parent_tag also to hive_table. DSL query response of parent_tag 
> returns hive_table twice. But UI response is empty.
> Attached the DSL query response of parent_tag and UI screenshot.



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

[jira] [Updated] (ATLAS-1819) V2 APIs : Entity Resource GET query with classification returns 500.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1819:

Affects Version/s: 0.8-incubating

> V2 APIs : Entity Resource GET query with classification returns 500.
> 
>
> Key: ATLAS-1819
> URL: https://issues.apache.org/jira/browse/ATLAS-1819
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Ruchi Solani
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ArrayOutOfBoundsException.txt, ATLAS-1819.patch
>
>
> 1. Created a tag tag1.
> 2. Created a table table1.
> 3. tag1 is *not associated* to table1
> The following query returns 500 Internal server error. 
> {code}
> /api/atlas/v2/entity/guid//classification/tag1
> {code}
> Exception thrown :
> java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
> Attached the complete exception trace thrown in application logs.
> 4. Now created another tag tag2 and associated table1 to tag2.
> 5. Now the same query /api/atlas/v2/entity/guid//tag1 returns 
> expected error code 404.
> That is , when any tag is already associated to the entity, search for the 
> unassociated tag throws 404 , else 500.



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

[jira] [Resolved] (ATLAS-1819) V2 APIs : Entity Resource GET query with classification returns 500.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-1819.
-
   Resolution: Fixed
Fix Version/s: 0.8.1-incubating
   0.9-incubating

Committed to the following branches:
 - master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/35c77644
 - 0.8-incubating: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/a3a59183

> V2 APIs : Entity Resource GET query with classification returns 500.
> 
>
> Key: ATLAS-1819
> URL: https://issues.apache.org/jira/browse/ATLAS-1819
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Ruchi Solani
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ArrayOutOfBoundsException.txt, ATLAS-1819.patch
>
>
> 1. Created a tag tag1.
> 2. Created a table table1.
> 3. tag1 is *not associated* to table1
> The following query returns 500 Internal server error. 
> {code}
> /api/atlas/v2/entity/guid//classification/tag1
> {code}
> Exception thrown :
> java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
> Attached the complete exception trace thrown in application logs.
> 4. Now created another tag tag2 and associated table1 to tag2.
> 5. Now the same query /api/atlas/v2/entity/guid//tag1 returns 
> expected error code 404.
> That is , when any tag is already associated to the entity, search for the 
> unassociated tag throws 404 , else 500.



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

[jira] [Updated] (ATLAS-1804) Allow PAM for authentication

[Shi Wang (JIRA)]

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

Shi Wang updated ATLAS-1804:

Affects Version/s: trunk

> Allow PAM for authentication
> 
>
> Key: ATLAS-1804
> URL: https://issues.apache.org/jira/browse/ATLAS-1804
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Shi Wang
>Assignee: Shi Wang
> Fix For: trunk
>
>
> Atlas currently support File, Kerberos and Ldap authentication. An 
> improvement feature will be adding PAM as another authentication type. 



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

[jira] [Commented] (ATLAS-1804) Allow PAM for authentication

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ATLAS-1804:
---

GitHub user Wancy opened a pull request:

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

ATLAS-1804:Allow PAM for authentication

This patch added a new param atlas.authentication.method.pam to configure 
atlas login using pam authentication. 
The pam module name could be configured by setting the value of 
atlas.authentication.method.pam.service, without explicitly setting the name, 
it will call it "atlas-login" by default.
User can custom the pam module content under /etc/pam.d/atlas-login.

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

$ git pull https://github.com/Wancy/incubator-atlas master

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

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

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

This closes #28


commit 8ae01c91fa42b56a261a2ba19ea521fd253c1c4b
Author: shiwang 
Date:   2017-05-22T23:19:46Z

ATLAS-1804:Allow PAM for authentication




> Allow PAM for authentication
> 
>
> Key: ATLAS-1804
> URL: https://issues.apache.org/jira/browse/ATLAS-1804
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Shi Wang
>Assignee: Shi Wang
>
> Atlas currently support File, Kerberos and Ldap authentication. An 
> improvement feature will be adding PAM as another authentication type. 



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

[GitHub] incubator-atlas pull request #28: ATLAS-1804:Allow PAM for authentication

[Wancy]

GitHub user Wancy opened a pull request:

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

ATLAS-1804:Allow PAM for authentication

This patch added a new param atlas.authentication.method.pam to configure 
atlas login using pam authentication. 
The pam module name could be configured by setting the value of 
atlas.authentication.method.pam.service, without explicitly setting the name, 
it will call it "atlas-login" by default.
User can custom the pam module content under /etc/pam.d/atlas-login.

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

$ git pull https://github.com/Wancy/incubator-atlas master

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

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

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

This closes #28


commit 8ae01c91fa42b56a261a2ba19ea521fd253c1c4b
Author: shiwang 
Date:   2017-05-22T23:19:46Z

ATLAS-1804:Allow PAM for authentication




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

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

[Apache Jenkins Server]

See 


Changes:

[madhan] ATLAS-1819: V2 API to get entity with classification returns 500

--
[...truncated 272.01 KB...]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-repository ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 56 source files to 

[WARNING] 
:
 Some input files use or override a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ atlas-repository 
---
[INFO] Surefire report directory: 

[INFO] Using configured provider org.apache.maven.surefire.testng.TestNGProvider
[WARNING] file.encoding cannot be set as system property, use 
-Dfile.encoding=... instead

---
 T E S T S
---
Running org.apache.atlas.repository.impexp.ImportServiceTest
Running org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1Test
Running org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest
Running 
org.apache.atlas.repository.typestore.StoreBackedTypeCacheConfigurationTest
Running org.apache.atlas.repository.impexp.ZipSourceTest
Running org.apache.atlas.repository.BaseTest
Running org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryHATest
Running org.apache.atlas.repository.graph.AbstractGremlinQueryOptimizerTest
Running org.apache.atlas.repository.graph.GraphBackedRepositoryHardDeleteTest
Running org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStoreTest
Running org.apache.atlas.repository.audit.InMemoryAuditRepositoryTest
Running org.apache.atlas.repository.graph.GraphHelperTest
Running org.apache.atlas.repository.graph.GraphBackedMetadataRepositoryTest
Running org.apache.atlas.repository.impexp.ZipSinkTest
Running org.apache.atlas.repository.typestore.GraphBackedTypeStoreTest
Running org.apache.atlas.repository.impexp.ImportServiceReportingTest
Running org.apache.atlas.repository.graph.Gremlin2QueryOptimizerTest
Running 
org.apache.atlas.repository.store.graph.v1.InverseReferenceUpdateHardDeleteV1Test
Running 
org.apache.atlas.repository.store.graph.v1.InverseReferenceUpdateSoftDeleteV1Test
Running org.apache.atlas.repository.graph.GraphBackedRepositorySoftDeleteTest
Running org.apache.atlas.repository.graph.ReverseReferenceUpdateHardDeleteTest
Running org.apache.atlas.repository.store.graph.v1.SoftDeleteHandlerV1Test
Running org.apache.atlas.repository.store.graph.AtlasEntityDefStoreV1Test
Running org.apache.atlas.repository.impexp.ExportServiceTest
Running org.apache.atlas.repository.typestore.StoreBackedTypeCacheTest
Running org.apache.atlas.repository.store.graph.v1.HardDeleteHandlerV1Test
Running org.apache.atlas.repository.store.graph.v1.AtlasDeleteHandlerV1Test
Running org.apache.atlas.repository.graph.TestIntSequence
Running org.apache.atlas.repository.graph.GraphBackedSearchIndexerTest
Running org.apache.atlas.repository.graph.GraphRepoMapperScaleTest
Running org.apache.atlas.repository.store.graph.v1.InverseReferenceUpdateV1Test
Running org.apache.atlas.repository.graph.Gremlin3QueryOptimizerTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 26.805 sec - in 
org.apache.atlas.repository.BaseTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 27.106 sec - in 
org.apache.atlas.repository.audit.InMemoryAuditRepositoryTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 27.34 sec - in 
org.apache.atlas.repository.impexp.ImportServiceReportingTest
Running org.apache.atlas.repository.graph.GraphHelperMockTest
Running org.apache.atlas.repository.graph.ReverseReferenceUpdateSoftDeleteTest
Running org.apache.atlas.repository.graph.GraphBackedSearchIndexerMockTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 29.713 sec - in 
org.apache.atlas.repository.impexp.ZipSinkTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 29.946 sec - in 

[jira] [Commented] (ATLAS-1819) V2 APIs : Entity Resource GET query with classification returns 500.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-1819:
-

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

> V2 APIs : Entity Resource GET query with classification returns 500.
> 
>
> Key: ATLAS-1819
> URL: https://issues.apache.org/jira/browse/ATLAS-1819
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
> Attachments: ArrayOutOfBoundsException.txt, ATLAS-1819.patch
>
>
> 1. Created a tag tag1.
> 2. Created a table table1.
> 3. tag1 is *not associated* to table1
> The following query returns 500 Internal server error. 
> {code}
> /api/atlas/v2/entity/guid//classification/tag1
> {code}
> Exception thrown :
> java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
> Attached the complete exception trace thrown in application logs.
> 4. Now created another tag tag2 and associated table1 to tag2.
> 5. Now the same query /api/atlas/v2/entity/guid//tag1 returns 
> expected error code 404.
> That is , when any tag is already associated to the entity, search for the 
> unassociated tag throws 404 , else 500.



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

[jira] [Commented] (ATLAS-1690) Introduce top level relationships

[Sarath Subramanian (JIRA)]

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

Sarath Subramanian commented on ATLAS-1690:
---

[~davidrad], I think only committers have access to write to this new branch, 
could you include your patch here so that we all could review and get it 
committed to the feature branch.

> Introduce top level relationships
> -
>
> Key: ATLAS-1690
> URL: https://issues.apache.org/jira/browse/ATLAS-1690
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Radley
>Assignee: David Radley
>  Labels: VirtualDataConnector
> Attachments: Atlas_RelationDef_Json_Structure_v1.pdf, Atlas 
> Relationships proposal v1.0.pdf, Atlas Relationships proposal v1.1.pdf, Atlas 
> Relationships proposal v1.2.pdf, Atlas Relationships proposal v1.3.pdf, Atlas 
> Relationships proposal v1.4.pdf, Atlas Relationships proposal v1.5.pdf, Atlas 
> Relationships proposal v1.6.pdf, Atlas Relationships proposal v1.7.pdf, Atlas 
> Relationships proposal v1.8.pdf, Atlas Relationships proposal v1.9.pdf
>
>
> Introduce top level relationships including support for 
> -many to many relationships
> - relationship names including the name for both ends and the relationship.



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

[jira] [Updated] (ATLAS-1819) V2 APIs : Entity Resource GET query with classification returns 500.

[Ruchi Solani (JIRA)]

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

Ruchi Solani updated ATLAS-1819:

Attachment: ATLAS-1819.patch

Hi All,
I have fix the indexOutofBoundsException and attached the patch , please review 
the code.
Also assign me this jira my jira id ruchi_solani

> V2 APIs : Entity Resource GET query with classification returns 500.
> 
>
> Key: ATLAS-1819
> URL: https://issues.apache.org/jira/browse/ATLAS-1819
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
> Attachments: ArrayOutOfBoundsException.txt, ATLAS-1819.patch
>
>
> 1. Created a tag tag1.
> 2. Created a table table1.
> 3. tag1 is *not associated* to table1
> The following query returns 500 Internal server error. 
> {code}
> /api/atlas/v2/entity/guid//classification/tag1
> {code}
> Exception thrown :
> java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
> Attached the complete exception trace thrown in application logs.
> 4. Now created another tag tag2 and associated table1 to tag2.
> 5. Now the same query /api/atlas/v2/entity/guid//tag1 returns 
> expected error code 404.
> That is , when any tag is already associated to the entity, search for the 
> unassociated tag throws 404 , else 500.



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

Re: Review Request 59439: KNOX-789 :- Apache Atlas REST API support

[Nixon Rodrigues]

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

(Updated May 22, 2017, 10:59 a.m.)


Review request for atlas, Knox, Larry McCay, and Madhan Neethiraj.


Bugs: KNOX-789
https://issues.apache.org/jira/browse/KNOX-789


Repository: knox


Description
---

This patch includes service definition and rewrite rules for Atlas API to 
support proxy through Knox.


Diffs
-

  
gateway-service-definitions/src/main/resources/services/atlas-api/0.8.0/rewrite.xml
 PRE-CREATION 
  
gateway-service-definitions/src/main/resources/services/atlas-api/0.8.0/service.xml
 PRE-CREATION 


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


Testing
---

Tested the api from curl and also from Atlas admin UI


[root@rd-atl-080517-2 bin]# curl -i -k -L -u admin:admin -X GET  
'https://knox-host:8443/gateway/ui/atlas/api/atlas/v2/types/typedefs?type=classification&_=1495442879421'
HTTP/1.1 200 OK
Date: Mon, 22 May 2017 08:50:03 GMT
Date: Mon, 22 May 2017 08:50:03 GMT
Set-Cookie: ATLASSESSIONID=oscz5x1nocfn14y4bj0yv52vs;Path=/;HttpOnly
Expires: Thu, 01 Jan 1970 00:00:00 GMT
X-Frame-Options: DENY
Content-Type: application/json; charset=UTF-8
Server: Jetty(9.2.12.v20150709)
Content-Length: 2070

{"enumDefs":[],"structDefs":[],"classificationDefs":[{"category":"CLASSIFICATION","guid":"abce22ee-a6ed-40f3-816a-555049997b71","createTime":1495108634535,"updateTime":1495108634535,"version":1,"name":"KnoxProxy","description":"KnoxProxy","typeVersion":"1.0","attributeDefs":[],"superTypes":[]},{"category":"CLASSIFICATION","guid":"2410969e-f592-4db8-82d7-47bf6996d090","createTime":1495011488803,"updateTime":1495011488803,"version":1,"name":"PII","description":"PII
 
Classification","typeVersion":"1.0","attributeDefs":[],"superTypes":[]},{"category":"CLASSIFICATION","guid":"ac122a83-37e1-4c60-a260-2a262c98b2f8","createTime":1495011490270,"updateTime":1495011490270,"version":1,"name":"JdbcAccess","description":"JdbcAccess
 
Classification","typeVersion":"1.0","attributeDefs":[],"superTypes":[]},{"category":"CLASSIFICATION","guid":"7bff86b0-a77e-43a0-9577-c125196bb497","createTime":1495011490296,"updateTime":1495011490296,"version":1,"name":"Log
 Data","description":"LogData Classification","
 
typeVersion":"1.0","attributeDefs":[],"superTypes":[]},{"category":"CLASSIFICATION","guid":"1099a2a2-932a-4f1d-9f6c-4ed04021f88e","createTime":1495011488817,"updateTime":1495011488817,"version":1,"name":"Metric","description":"Metric
 
Classification","typeVersion":"1.0","attributeDefs":[],"superTypes":[]},{"category":"CLASSIFICATION","guid":"228842fe-7035-4fd2-9c6c-48b1d74a0995","createTime":1495011487356,"updateTime":1495011487356,"version":1,"name":"Dimension","description":"Dimension
 
Classification","typeVersion":"1.0","attributeDefs":[],"superTypes":[]},{"category":"CLASSIFICATION","guid":"900d0441-393e-4b2f-b6f5-161d5b057d36","createTime":1495011489541,"updateTime":1495011489541,"version":1,"name":"ETL","description":"ETL
 
Classification","typeVersion":"1.0","attributeDefs":[],"superTypes":[]},{"category":"CLASSIFICATION","guid":"42d1752d-58de-4816-8bcb-7157eda14d7f","createTime":1495011488088,"updateTime":1495011488088,"version":1,"name":"Fact","description":"Fact
 Classification
 ","typeVersion":"1.0","attributeDefs":[],"superTypes":[]}],"entityDefs":[]}


Thanks,

Nixon Rodrigues

Re: Please add me to the contributors list

[Jan Hentschel]

It works. Thanks a lot!

 

From: Hemanth Yamijala 
Reply-To: 
Date: Monday, May 22, 2017 at 5:00 AM
To: "dev@atlas.incubator.apache.org" 
Subject: Re: Please add me to the contributors list

 

Done. Can you please check?



From: Jan Hentschel 

Sent: Friday, May 19, 2017 11:53 PM

To: dev@atlas.incubator.apache.org

Subject: Please add me to the contributors list

 

Hi,

 

 

 

I currently have some tickets in JIRA, which I would like to assign to myself. 
Could you please add me to the appropriate group in JIRA? My JIRA ID is “Jan 
Hentschel”.

 

 

 

Best, Jan

 

 

 

[jira] [Updated] (ATLAS-1819) V2 APIs : Entity Resource GET query with classification returns 500.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1819:
---
Description: 
1. Created a tag tag1.
2. Created a table table1.
3. tag1 is *not associated* to table1
The following query returns 500 Internal server error. 
{code}
/api/atlas/v2/entity/guid//classification/tag1
{code}

Exception thrown :
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
Attached the complete exception trace thrown in application logs.

4. Now created another tag tag2 and associated table1 to tag2.
5. Now the same query /api/atlas/v2/entity/guid//tag1 returns 
expected error code 404.

That is , when any tag is already associated to the entity, search for the 
unassociated tag throws 404 , else 500.

  was:
1. Created a tag tag1.
2. Created a table table1.
3. tag1 is *not associated* to table1
The following query returns 500 Internal server error. 
{code}
/api/atlas/v2/entity/guid//tag1
{code}

Exception thrown :
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
Attached the complete exception trace thrown in application logs.

4. Now created another tag tag2 and associated table1 to tag2.
5. Now the same query /api/atlas/v2/entity/guid//tag1 returns 
expected error code 404.

That is , when any tag is already associated to the entity, search for the 
unassociated tag throws 404 , else 500.


> V2 APIs : Entity Resource GET query with classification returns 500.
> 
>
> Key: ATLAS-1819
> URL: https://issues.apache.org/jira/browse/ATLAS-1819
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
> Attachments: ArrayOutOfBoundsException.txt
>
>
> 1. Created a tag tag1.
> 2. Created a table table1.
> 3. tag1 is *not associated* to table1
> The following query returns 500 Internal server error. 
> {code}
> /api/atlas/v2/entity/guid//classification/tag1
> {code}
> Exception thrown :
> java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
> Attached the complete exception trace thrown in application logs.
> 4. Now created another tag tag2 and associated table1 to tag2.
> 5. Now the same query /api/atlas/v2/entity/guid//tag1 returns 
> expected error code 404.
> That is , when any tag is already associated to the entity, search for the 
> unassociated tag throws 404 , else 500.



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

[jira] [Assigned] (ATLAS-1787) Replace explicit type with diamond operator

[Jan Hentschel (JIRA)]

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

Jan Hentschel reassigned ATLAS-1787:


Assignee: Jan Hentschel

> Replace explicit type with diamond operator
> ---
>
> Key: ATLAS-1787
> URL: https://issues.apache.org/jira/browse/ATLAS-1787
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Trivial
> Attachments: ATLAS-1787.001.patch
>
>
> Because Atlas uses Java 7 explicit types can be replaced with the diamond 
> operator. Most of the code already uses the diamond operator, but there are 
> still some places left throughout the codebase.



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

[jira] [Assigned] (ATLAS-1784) Use explicit imports instead of wildcards

[Jan Hentschel (JIRA)]

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

Jan Hentschel reassigned ATLAS-1784:


Assignee: Jan Hentschel

> Use explicit imports instead of wildcards
> -
>
> Key: ATLAS-1784
> URL: https://issues.apache.org/jira/browse/ATLAS-1784
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: ATLAS-1784.001.patch
>
>
> Currently there are a lot of wildcard imports, especially with *java.util.**. 
> To follow best practices, for better readability and to prevent future 
> collisions they should be changed to explicit class imports.



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

[jira] [Assigned] (ATLAS-1786) Remove duplicate dependencies and plugins in pom files

[Jan Hentschel (JIRA)]

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

Jan Hentschel reassigned ATLAS-1786:


Assignee: Jan Hentschel

> Remove duplicate dependencies and plugins in pom files
> --
>
> Key: ATLAS-1786
> URL: https://issues.apache.org/jira/browse/ATLAS-1786
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: ATLAS-1786.001.patch, ATLAS-1786.002.patch
>
>
> Currently the main pom file defines the dependency for *atlas-graphdb-impls* 
> twice. One of it should be removed. Also SLF4J is defined in the main pom 
> file and in several sub-modules. With that the dependencies in the 
> sub-modules are not necessary. Clean up the pom files to remove duplicate 
> entries in the dependencies and the plugins.



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

[jira] [Assigned] (ATLAS-1785) Fix Findbugs problems in falcon-bridge module

[Jan Hentschel (JIRA)]

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

Jan Hentschel reassigned ATLAS-1785:


Assignee: Jan Hentschel

> Fix Findbugs problems in falcon-bridge module
> -
>
> Key: ATLAS-1785
> URL: https://issues.apache.org/jira/browse/ATLAS-1785
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: ATLAS-1785.001.patch
>
>
> Currently Findbugs complains about the following two problems in the 
> *falcon-bridge*
> {code}
> [INFO] Repeated conditional test in 
> org.apache.atlas.falcon.bridge.FalconBridge.createFeedCreationEntity(Feed, 
> ConfigurationStore) [org.apache.atlas.falcon.bridge.FalconBridge, 
> org.apache.atlas.falcon.bridge.FalconBridge] At FalconBridge.java:[line 
> 184]At FalconBridge.java:[line 184]
> [INFO] Switch statement found in 
> org.apache.atlas.falcon.hook.FalconHook.fireAndForget(FalconEvent) where 
> default case is missing [org.apache.atlas.falcon.hook.FalconHook] At 
> FalconHook.java:[lines 161-163]
> {code}
> They should be fixed to get the code more reliable.



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

[jira] [Assigned] (ATLAS-969) Removed unused images in ./docs/src/site/resources/images

[Jan Hentschel (JIRA)]

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

Jan Hentschel reassigned ATLAS-969:
---

Assignee: Jan Hentschel

> Removed unused images in ./docs/src/site/resources/images
> -
>
> Key: ATLAS-969
> URL: https://issues.apache.org/jira/browse/ATLAS-969
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Jan Hentschel
> Attachments: ATLAS-969.001.patch
>
>




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

[jira] [Assigned] (ATLAS-1789) Fix Findbugs problems

[Jan Hentschel (JIRA)]

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

Jan Hentschel reassigned ATLAS-1789:


Assignee: Jan Hentschel

> Fix Findbugs problems
> -
>
> Key: ATLAS-1789
> URL: https://issues.apache.org/jira/browse/ATLAS-1789
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
>
> This is an umbrella ticket for fixing the Findbugs errors throughout the 
> different modules.



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

[jira] [Assigned] (ATLAS-1783) Remove unused imports

[Jan Hentschel (JIRA)]

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

Jan Hentschel reassigned ATLAS-1783:


Assignee: Jan Hentschel

> Remove unused imports
> -
>
> Key: ATLAS-1783
> URL: https://issues.apache.org/jira/browse/ATLAS-1783
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Trivial
> Attachments: ATLAS-1783.001.patch
>
>
> Currently there are some unused imports throughout the codebase. They should 
> be removed.



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

[jira] [Updated] (ATLAS-1823) UI - Change in base path URL for few api/images to make it relative from path it is accessed.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1823:
---
Fix Version/s: 0.9-incubating

> UI - Change in base path URL for few api/images to make it relative from path 
> it is accessed.
> -
>
> Key: ATLAS-1823
> URL: https://issues.apache.org/jira/browse/ATLAS-1823
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1823.patch
>
>
> The currently in Atlas the base path for api and few image are relative to 
> root of the application, ie it always resolves to http://.
> Which causing issue when Atlas UI is accessed for Knox Proxy.
> Proposing following changes in path to make it relative from path it is 
> accessed.
> {code}
> -
> +
> {code}
> {code}
> -baseUrl: '/api/atlas',
> -baseUrlV2: '/api/atlas/v2',
> +baseUrl: 'api/atlas',
> +baseUrlV2: 'api/atlas/v2',
> {code}



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

[jira] [Updated] (ATLAS-1823) UI - Change in base path URL for few api/images to make it relative from path it is accessed.

[Nixon Rodrigues (JIRA)]

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

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

> UI - Change in base path URL for few api/images to make it relative from path 
> it is accessed.
> -
>
> Key: ATLAS-1823
> URL: https://issues.apache.org/jira/browse/ATLAS-1823
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
> Attachments: ATLAS-1823.patch
>
>
> The currently in Atlas the base path for api and few image are relative to 
> root of the application, ie it always resolves to http://.
> Which causing issue when Atlas UI is accessed for Knox Proxy.
> Proposing following changes in path to make it relative from path it is 
> accessed.
> {code}
> -
> +
> {code}
> {code}
> -baseUrl: '/api/atlas',
> -baseUrlV2: '/api/atlas/v2',
> +baseUrl: 'api/atlas',
> +baseUrlV2: 'api/atlas/v2',
> {code}



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

[jira] [Assigned] (ATLAS-1823) UI - Change in base path URL for few api/images to make it relative from path it is accessed.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues reassigned ATLAS-1823:
--

Assignee: Nixon Rodrigues

> UI - Change in base path URL for few api/images to make it relative from path 
> it is accessed.
> -
>
> Key: ATLAS-1823
> URL: https://issues.apache.org/jira/browse/ATLAS-1823
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Attachments: ATLAS-1823.patch
>
>
> The currently in Atlas the base path for api and few image are relative to 
> root of the application, ie it always resolves to http://.
> Which causing issue when Atlas UI is accessed for Knox Proxy.
> Proposing following changes in path to make it relative from path it is 
> accessed.
> {code}
> -
> +
> {code}
> {code}
> -baseUrl: '/api/atlas',
> -baseUrlV2: '/api/atlas/v2',
> +baseUrl: 'api/atlas',
> +baseUrlV2: 'api/atlas/v2',
> {code}



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

[jira] [Created] (ATLAS-1823) UI - Change in base path URL for few api/images to make it relative from path it is accessed.

[Nixon Rodrigues (JIRA)]

Nixon Rodrigues created ATLAS-1823:
--

 Summary: UI - Change in base path URL for few api/images to make 
it relative from path it is accessed.
 Key: ATLAS-1823
 URL: https://issues.apache.org/jira/browse/ATLAS-1823
 Project: Atlas
  Issue Type: Bug
Reporter: Nixon Rodrigues


The currently in Atlas the base path for api and few image are relative to root 
of the application, ie it always resolves to http://.
Which causing issue when Atlas UI is accessed for Knox Proxy.

Proposing following changes in path to make it relative from path it is 
accessed.

{code}
-
+
{code}

{code}
-baseUrl: '/api/atlas',
-baseUrlV2: '/api/atlas/v2',
+baseUrl: 'api/atlas',
+baseUrlV2: 'api/atlas/v2',
{code}



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