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

2017-11-23 Thread Apache Jenkins Server 
See 


Changes:

[madhan] ATLAS-2275: fix for incorrect serialization of date type trait

--
[...truncated 529.38 KB...]
127.0.0.1 - - [23/Nov/2017:23:04:28 +] "GET 
/api/atlas/v2/entity/guid/765fdde1-3c0a-4f48-a5af-0cee2b21bebb HTTP/1.1" 200 - 
"-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:28 +] "POST /api/atlas/v2/entity HTTP/1.1" 
200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:28 +] "GET 
/api/atlas/v2/entity/guid/7cba743f-fd6d-4d02-8a0f-f4079d511465 HTTP/1.1" 200 - 
"-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:28 +] "POST /api/atlas/v2/entity HTTP/1.1" 
200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:28 +] "GET 
/api/atlas/v2/entity/guid/99f060f1-5c00-4701-9e75-39a47bd6e421 HTTP/1.1" 200 - 
"-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:28 +] "POST /api/atlas/v2/entity HTTP/1.1" 
200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:28 +] "GET 
/api/atlas/v2/entity/guid/9cde25be-5f45-4d93-89ec-303a3479e4d0 HTTP/1.1" 200 - 
"-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:28 +] "POST /api/atlas/v2/entity HTTP/1.1" 
200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:28 +] "GET 
/api/atlas/v2/entity/guid/d2c3ff36-9f67-4490-977a-93c5e10bd449 HTTP/1.1" 200 - 
"-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:28 +] "POST /api/atlas/v2/entity HTTP/1.1" 
200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:28 +] "GET 
/api/atlas/v2/entity/guid/0686111a-52fe-4a51-883e-adcba8df2295 HTTP/1.1" 200 - 
"-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:28 +] "POST /api/atlas/v2/entity HTTP/1.1" 
200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:28 +] "GET 
/api/atlas/v2/entity/guid/7f208b12-186c-4b03-a104-3d930bd6a843 HTTP/1.1" 200 - 
"-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:28 +] "POST /api/atlas/v2/entity HTTP/1.1" 
200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:28 +] "GET 
/api/atlas/v2/entity/guid/51bda540-d1d6-4e6b-bb50-117b49c1ce8c HTTP/1.1" 200 - 
"-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:28 +] "GET 
/api/atlas/v2/search/dsl?offset=0&query=from+DB&limit=10 HTTP/1.1" 200 - "-" 
"Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:29 +] "GET 
/api/atlas/v2/search/dsl?offset=0&query=DB&limit=10 HTTP/1.1" 200 - "-" 
"Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:30 +] "GET 
/api/atlas/v2/search/dsl?offset=0&query=DB+where+name%3D%22Reporting%22&limit=10
 HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:31 +] "GET 
/api/atlas/v2/search/dsl?offset=0&query=DB+where+DB.name%3D%22Reporting%22&limit=10
 HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:31 +] "GET 
/api/atlas/v2/search/dsl?offset=0&query=DB+name+%3D+%22Reporting%22&limit=10 
HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:32 +] "GET 
/api/atlas/v2/search/dsl?offset=0&query=DB+DB.name+%3D+%22Reporting%22&limit=10 
HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:33 +] "GET 
/api/atlas/v2/search/dsl?offset=0&query=DB+where+name%3D%22Reporting%22+select+name,+owner&limit=10
 HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:34 +] "GET 
/api/atlas/v2/search/dsl?offset=0&query=DB+where+DB.name%3D%22Reporting%22+select+name,+owner&limit=10
 HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:35 +] "GET 
/api/atlas/v2/search/dsl?offset=0&query=DB+has+name&limit=10 HTTP/1.1" 200 - 
"-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:36 +] "GET 
/api/atlas/v2/search/dsl?offset=0&query=DB+where+DB+has+name&limit=10 HTTP/1.1" 
200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:37 +] "GET 
/api/atlas/v2/search/dsl?offset=0&query=DB,+Table&limit=10 HTTP/1.1" 200 - "-" 
"Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:38 +] "GET 
/api/atlas/v2/search/dsl?offset=0&query=DB+is+JdbcAccess&limit=10 HTTP/1.1" 200 
- "-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:38 +] "GET 
/api/atlas/v2/search/dsl?offset=0&query=from+Table&limit=10 HTTP/1.1" 200 - "-" 
"Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:39 +] "GET 
/api/atlas/v2/search/dsl?offset=0&query=Table&limit=10 HTTP/1.1" 200 - "-" 
"Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:40 +] "GET 
/api/atlas/v2/search/dsl?offset=0&query=Table+is+Dimension&limit=10 HTTP/1.1" 
200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:40 +] "GET 
/api/atlas/v2/search/dsl?offset=0&query=Column+where+Column+isa+PII&limit=10 
HTTP/1.1" 200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:41 +] "GET 
/api/atlas/v2/search/dsl?offset=0&query=View+is+Dimension&limit=10 HTTP/1.1" 
200 - "-" "Java/1.8.0_152"
127.0.0.1 - - [23/Nov/2017:23:04:41 +] "GET 
/api/atlas/v2/search/dsl?offset=0&query=Colum

Re: Review Request 64048: ATLAS-2275: fix for incorrect serialization of date type trait attributes in entity notification

2017-11-23 Thread Ashutosh Mestry 

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


Ship it!




Ship It!

- Ashutosh Mestry


On Nov. 23, 2017, 10:24 a.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/64048/
> ---
> 
> (Updated Nov. 23, 2017, 10:24 a.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, Abhay Kulkarni, and 
> Sarath Subramanian.
> 
> 
> Bugs: ATLAS-2275
> https://issues.apache.org/jira/browse/ATLAS-2275
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Entity seraialization didn't handle IStruct correctly, casuing this issue. 
> This patch fixes the issue.
> 
> 
> Diffs
> -
> 
>   
> notification/src/main/java/org/apache/atlas/notification/AbstractNotification.java
>  4f56bd8d 
> 
> 
> Diff: https://reviews.apache.org/r/64048/diff/1/
> 
> 
> Testing
> ---
> 
> Verified that date type trait attributes are serialzied in correct format in 
> entity notifications.
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Re: Review Request 63502: ATLAS-2246 - Review request for the OMRS Connector API.

2017-11-23 Thread Yao Li 


> On Nov. 20, 2017, 11:43 a.m., Yao Li wrote:
> > omrs/src/main/java/org/apache/atlas/omrs/metadatacollection/properties/typedefs/EnumDefs.java
> > Lines 33 (patched)
> > 
> >
> > in the 
> > [https://issues.apache.org/jira/projects/ATLAS/issues/ATLAS-2246?filter=allopenissues](https://issues.apache.org/jira/projects/ATLAS/issues/ATLAS-2246?filter=allopenissues)
> >  java doc, EnumDefs also extends java.lang.Object which I think it can be 
> > deleted.

for all the iterator classes code, such as ClassficationDefs, CollectionDefs 
etc. you all extends TypeDefElementHeader, although it has the same function as 
implements Serializable, but I think it is more consistent with other codes ;)


- Yao


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


On Nov. 10, 2017, 1:43 p.m., Mandy Chessell wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63502/
> ---
> 
> (Updated Nov. 10, 2017, 1:43 p.m.)
> 
> 
> Review request for atlas, David Radley and Madhan Neethiraj.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This is a request for review of the OMRS Connector API.  The files of 
> interest are:
> 
> omrs/src/main/java/org/apache/atlas/omrs/metadatacollection/*
> omrs/src/main/java/org/apache/atlas/omrs/connectors/*
> omrs/src/main/java/org/apache/atlas/omrs/ffdc/*
> 
> There is a patch connected to 
> https://issues.apache.org/jira/projects/ATLAS/issues/ATLAS-2246 that has the 
> code plus other code that is not ready for review.  The OMRS Connector API 
> depends on the OCF - see https://issues.apache.org/jira/browse/ATLAS-1095.
> 
> 
> Diffs
> -
> 
>   omrs/README.md PRE-CREATION 
>   omrs/pom.xml PRE-CREATION 
>   omrs/src/main/java/org/apache/atlas/omrs/connectors/OMRSConnection.java 
> PRE-CREATION 
>   omrs/src/main/java/org/apache/atlas/omrs/connectors/OMRSConnector.java 
> PRE-CREATION 
>   omrs/src/main/java/org/apache/atlas/omrs/connectors/OMRSConnectorBase.java 
> PRE-CREATION 
>   
> omrs/src/main/java/org/apache/atlas/omrs/connectors/OMRSConnectorProviderBase.java
>  PRE-CREATION 
>   
> omrs/src/main/java/org/apache/atlas/omrs/connectors/igc/IGCOMRSConnector.java 
> PRE-CREATION 
>   
> omrs/src/main/java/org/apache/atlas/omrs/connectors/igc/IGCOMRSConnectorProvider.java
>  PRE-CREATION 
>   
> omrs/src/main/java/org/apache/atlas/omrs/connectors/igc/IGCOMRSMetadataCollection.java
>  PRE-CREATION 
>   
> omrs/src/main/java/org/apache/atlas/omrs/connectors/rest/OMRSRESTConnector.java
>  PRE-CREATION 
>   
> omrs/src/main/java/org/apache/atlas/omrs/connectors/rest/OMRSRESTConnectorProvider.java
>  PRE-CREATION 
>   
> omrs/src/main/java/org/apache/atlas/omrs/connectors/rest/OMRSRESTMetadataCollection.java
>  PRE-CREATION 
>   
> omrs/src/main/java/org/apache/atlas/omrs/ffdc/ClassificationNotKnownException.java
>  PRE-CREATION 
>   
> omrs/src/main/java/org/apache/atlas/omrs/ffdc/EntityNotDeletedException.java 
> PRE-CREATION 
>   omrs/src/main/java/org/apache/atlas/omrs/ffdc/EntityNotKnownException.java 
> PRE-CREATION 
>   
> omrs/src/main/java/org/apache/atlas/omrs/ffdc/NotImplementedRuntimeException.java
>  PRE-CREATION 
>   omrs/src/main/java/org/apache/atlas/omrs/ffdc/OMRSCheckedExceptionBase.java 
> PRE-CREATION 
>   omrs/src/main/java/org/apache/atlas/omrs/ffdc/OMRSErrorCode.java 
> PRE-CREATION 
>   omrs/src/main/java/org/apache/atlas/omrs/ffdc/OMRSRuntimeException.java 
> PRE-CREATION 
>   omrs/src/main/java/org/apache/atlas/omrs/ffdc/PagingErrorException.java 
> PRE-CREATION 
>   omrs/src/main/java/org/apache/atlas/omrs/ffdc/PropertyErrorException.java 
> PRE-CREATION 
>   omrs/src/main/java/org/apache/atlas/omrs/ffdc/README.md PRE-CREATION 
>   
> omrs/src/main/java/org/apache/atlas/omrs/ffdc/RelationshipNotDeletedException.java
>  PRE-CREATION 
>   
> omrs/src/main/java/org/apache/atlas/omrs/ffdc/RelationshipNotKnownException.java
>  PRE-CREATION 
>   omrs/src/main/java/org/apache/atlas/omrs/ffdc/RepositoryErrorException.java 
> PRE-CREATION 
>   
> omrs/src/main/java/org/apache/atlas/omrs/ffdc/StatusNotSupportedException.java
>  PRE-CREATION 
>   omrs/src/main/java/org/apache/atlas/omrs/ffdc/TypeDefInUseException.java 
> PRE-CREATION 
>   omrs/src/main/java/org/apache/atlas/omrs/ffdc/TypeDefNotKnownException.java 
> PRE-CREATION 
>   omrs/src/main/java/org/apache/atlas/omrs/ffdc/TypeErrorException.java 
> PRE-CREATION 
>   
> omrs/src/main/java/org/apache/atlas/omrs/metadatacollection/MetadataCollection.java
>  PRE-CREATION 
>   
> omrs/src/main/java/org/apache/atlas/omrs/metadatacollection/MetadataCollectionBase.java
>  PRE-CREATION

[jira] [Updated] (ATLAS-2275) Entity notification serialization results in incorrect format for date attributes in traits

2017-11-23 Thread Madhan Neethiraj (JIRA) 

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

Madhan Neethiraj updated ATLAS-2275:

Attachment: ATLAS-2275.patch

Review board URL: https://reviews.apache.org/r/64048/

> Entity notification serialization results in incorrect format for date 
> attributes in traits
> ---
>
> Key: ATLAS-2275
> URL: https://issues.apache.org/jira/browse/ATLAS-2275
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
> Fix For: 1.0.0, 0.8.2
>
> Attachments: ATLAS-2275.patch
>
>
> Entity notification object has 3 fields: entity, operationType, traits. Date 
> type attributes in 'traits' are serialized in a different format than the 
> same attributes in entity.traits field, as shown below:
> notification.entity.traits:
> {noformat}
> "traits": {
>   "TEST_TAG":{
> 
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
> "typeName":"TEST_TAG",
> "values": {
>   "createTime":"2017-11-22T08:00:00.000Z"
> }
>   }
> }
> {noformat}
> notification.traits:
> {noformat}
> "traits": [
>   {
> "typeName":"TEST_TAG",
> "values": {
>   "createTime":"Nov 22, 2017 12:00:00 AM"
> }
>   }
> ]
> {noformat}
> This needs to be fixed so that the notification consumers will be able read 
> the same value in either fields.



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

Review Request 64048: ATLAS-2275: fix for incorrect serialization of date type trait attributes in entity notification

2017-11-23 Thread Madhan Neethiraj 

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

Review request for atlas, Apoorv Naik, Ashutosh Mestry, Abhay Kulkarni, and 
Sarath Subramanian.


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


Repository: atlas


Description
---

Entity seraialization didn't handle IStruct correctly, casuing this issue. This 
patch fixes the issue.


Diffs
-

  
notification/src/main/java/org/apache/atlas/notification/AbstractNotification.java
 4f56bd8d 


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


Testing
---

Verified that date type trait attributes are serialzied in correct format in 
entity notifications.


Thanks,

Madhan Neethiraj

[jira] [Updated] (ATLAS-2276) Path value for hdfs_path type entity is set to lower case from hive-bridge.

2017-11-23 Thread Nixon Rodrigues (JIRA) 

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

Nixon Rodrigues updated ATLAS-2276:
---
Affects Version/s: trunk

> Path value for hdfs_path type entity is set to lower case from hive-bridge.
> ---
>
> Key: ATLAS-2276
> URL: https://issues.apache.org/jira/browse/ATLAS-2276
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk, 0.8-incubating
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Fix For: trunk, 0.8.2
>
> Attachments: upload.png
>
>
> Steps to reproduce:- 
> * Create hive table with external file location
> {code}
> create external table hive_atlas_bug_test1 ( column1 int )
>  LOCATION ‘/store/Hive_Atlas_Bug_Test1'
> {code}
> * Check the hdfs_path type entity created on hive, the path is set with 
> lowercase.
> While hive objects are case insensitive and hdfs paths are case sensitive.  
> When hive table is created, the Atlas-hook's hive-bridge creates hdfs_path 
> entities and sends entity to Atlas server, the path value is stored in 
> lowercase in Metadata store.
> This will cause issues when other subsystems attempt to link lineage to atlas 
> entities using the proper case sensitive hdfs paths



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

[jira] [Updated] (ATLAS-2276) Path value for hdfs_path type entity is set to lower case from hive-bridge.

2017-11-23 Thread Nixon Rodrigues (JIRA) 

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

Nixon Rodrigues updated ATLAS-2276:
---
Description: 
Steps to reproduce:- 
* Create hive table with external file location
{code}
create external table hive_atlas_bug_test1 ( column1 int )
 LOCATION ‘/store/Hive_Atlas_Bug_Test1'
{code}

* Check the hdfs_path type entity created on hive, the path is set with 
lowercase.

While hive objects are case insensitive and hdfs paths are case sensitive.  
When hive table is created, the Atlas-hook's hive-bridge creates hdfs_path 
entities and sends entity to Atlas server, the path value is stored in 
lowercase in Metadata store.

This will cause issues when other subsystems attempt to link lineage to atlas 
entities using the proper case sensitive hdfs paths



  was:
Steps to reproduce:- 
* Create hive table with external file location
{code}
create external table hive_atlas_bug_test1 ( column1 int )
 LOCATION ‘/store/Hive_Atlas_Bug_Test'
{code}

* Check the hdfs_path type entity created on hive, the path is set with 
lowercase.

While hive objects are case insensitive and hdfs paths are case sensitive.  
When hive table is created, the Atlas-hook's hive-bridge creates hdfs_path 
entities and sends entity to Atlas server, the path value is stored in 
lowercase in Metadata store.

This will cause issues when other subsystems attempt to link lineage to atlas 
entities using the proper case sensitive hdfs paths




> Path value for hdfs_path type entity is set to lower case from hive-bridge.
> ---
>
> Key: ATLAS-2276
> URL: https://issues.apache.org/jira/browse/ATLAS-2276
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Fix For: trunk, 0.8.2
>
> Attachments: upload.png
>
>
> Steps to reproduce:- 
> * Create hive table with external file location
> {code}
> create external table hive_atlas_bug_test1 ( column1 int )
>  LOCATION ‘/store/Hive_Atlas_Bug_Test1'
> {code}
> * Check the hdfs_path type entity created on hive, the path is set with 
> lowercase.
> While hive objects are case insensitive and hdfs paths are case sensitive.  
> When hive table is created, the Atlas-hook's hive-bridge creates hdfs_path 
> entities and sends entity to Atlas server, the path value is stored in 
> lowercase in Metadata store.
> This will cause issues when other subsystems attempt to link lineage to atlas 
> entities using the proper case sensitive hdfs paths



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

[jira] [Created] (ATLAS-2277) Search using entity and trait attributes - excludeDeletedEntities parameter doesn't take effect when classification is "*"

2017-11-23 Thread Sharmadha Sainath (JIRA) 
Sharmadha Sainath created ATLAS-2277:


 Summary: Search using entity and trait attributes - 
excludeDeletedEntities parameter doesn't take effect when classification is "*"
 Key: ATLAS-2277
 URL: https://issues.apache.org/jira/browse/ATLAS-2277
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath


POST request body to /api/atlas/v2/search/basic :
{code}
{
"excludeDeletedEntities":true,
"includeClassificationAttributes": true,
"entityFilters":null,
"tagFilters":null,
"attributes":[],
"limit":100,
"offset":0,
"classification":"*"
}
{code}
though excludeDeletedEntities is True , when classification is "*" , the result 
has the DELETED entities too.
When any tag name is provided and excludeDeletedEntities when set to True , 
response doesn't have DELETED entities.
Hence incorrect results only when classification is "*".

CC : [~sarath.ku...@gmail.com] [~nixonrodrigues]



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

[jira] [Created] (ATLAS-2276) Path value for hdfs_path type entity is set to lower case from hive-bridge.

2017-11-23 Thread Nixon Rodrigues (JIRA) 
Nixon Rodrigues created ATLAS-2276:
--

 Summary: Path value for hdfs_path type entity is set to lower case 
from hive-bridge.
 Key: ATLAS-2276
 URL: https://issues.apache.org/jira/browse/ATLAS-2276
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.8-incubating
Reporter: Nixon Rodrigues
Assignee: Nixon Rodrigues
 Fix For: trunk, 0.8.2
 Attachments: upload.png

Steps to reproduce:- 
* Create hive table with external file location
{code}
create external table hive_atlas_bug_test1 ( column1 int )
 LOCATION ‘/store/Hive_Atlas_Bug_Test'
{code}

* Check the hdfs_path type entity created on hive, the path is set with 
lowercase.

While hive objects are case insensitive and hdfs paths are case sensitive.  
When hive table is created, the Atlas-hook's hive-bridge creates hdfs_path 
entities and sends entity to Atlas server, the path value is stored in 
lowercase in Metadata store.

This will cause issues when other subsystems attempt to link lineage to atlas 
entities using the proper case sensitive hdfs paths





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

[jira] [Created] (ATLAS-2275) Entity notification serialization results in incorrect format for date attributes in traits

2017-11-23 Thread Madhan Neethiraj (JIRA) 
Madhan Neethiraj created ATLAS-2275:
---

 Summary: Entity notification serialization results in incorrect 
format for date attributes in traits
 Key: ATLAS-2275
 URL: https://issues.apache.org/jira/browse/ATLAS-2275
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 0.8-incubating
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj


Entity notification object has 3 fields: entity, operationType, traits. Date 
type attributes in 'traits' are serialized in a different format than the same 
attributes in entity.traits field, as shown below:

notification.entity.traits:
{noformat}
"traits": {
  "TEST_TAG":{

"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
"typeName":"TEST_TAG",
"values": {
  "createTime":"2017-11-22T08:00:00.000Z"
}
  }
}
{noformat}

notification.traits:
{noformat}
"traits": [
  {
"typeName":"TEST_TAG",
"values": {
  "createTime":"Nov 22, 2017 12:00:00 AM"
}
  }
]
{noformat}

This needs to be fixed so that the notification consumers will be able read the 
same value in either fields.




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

[jira] [Updated] (ATLAS-2274) Search using entity and trait attributes - typename and "*" in classificationName throws Invalid condition exception

2017-11-23 Thread Sharmadha Sainath (JIRA) 

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

Sharmadha Sainath updated ATLAS-2274:
-
Attachment: Atlas_asterisk_in_classification_and type_name_exception.txt

> Search using entity and trait attributes - typename and "*" in 
> classificationName throws Invalid condition exception
> 
>
> Key: ATLAS-2274
> URL: https://issues.apache.org/jira/browse/ATLAS-2274
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
> Attachments: Atlas_asterisk_in_classification_and 
> type_name_exception.txt
>
>
> Following is the POST request body to /api/atlas/v2/search/basic
> {code}
> {
> "excludeDeletedEntities":true,
> "entityFilters":null,
> "tagFilters":null,
> "attributes":[],
> "limit":25,
> "offset":0,
> "typeName":"hive_table",
> "classification":"*"
> }
> {code}
> When any typeName is provided , Atlas throws 500 Internal server 
> exception.Attached the exception stack trace.
> When typeName parameter is removed ,or is given "null" value , response is 
> 200 OK.
> When a tag name is provided instead of "*" , and typeName is given ,no issues 
> are seen.
> Hence , issue with * in classificationName and typeName provided together.
> CC : [~sarath.ku...@gmail.com]



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

[jira] [Updated] (ATLAS-1116) Performance monitoring of backend methods in API requests

2017-11-23 Thread Sharmadha Sainath (JIRA) 

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

Sharmadha Sainath updated ATLAS-1116:
-
Attachment: (was: Atlas_asterisk_in_classification_and 
type_name_exception.txt)

> Performance monitoring of backend methods in API requests
> -
>
> Key: ATLAS-1116
> URL: https://issues.apache.org/jira/browse/ATLAS-1116
> Project: Atlas
>  Issue Type: Bug
>Reporter: Vimal Sharma
>Assignee: Shwetha G S
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1116-v2.patch, ATLAS-1116-v3.patch, 
> ATLAS-1116.patch
>
>
> Time taken by methods used in API calls for add/update/delete entities and 
> traits need to be monitored for performance



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

[jira] [Created] (ATLAS-2274) Search using entity and trait attributes - typename and "*" in classificationName throws Invalid condition exception

2017-11-23 Thread Sharmadha Sainath (JIRA) 
Sharmadha Sainath created ATLAS-2274:


 Summary: Search using entity and trait attributes - typename and 
"*" in classificationName throws Invalid condition exception
 Key: ATLAS-2274
 URL: https://issues.apache.org/jira/browse/ATLAS-2274
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath


Following is the POST request body to /api/atlas/v2/search/basic
{code}
{
"excludeDeletedEntities":true,
"entityFilters":null,
"tagFilters":null,
"attributes":[],
"limit":25,
"offset":0,
"typeName":"hive_table",
"classification":"*"
}
{code}
When any typeName is provided , Atlas throws 500 Internal server 
exception.Attached the exception stack trace.

When typeName parameter is removed ,or is given "null" value , response is 200 
OK.

When a tag name is provided instead of "*" , and typeName is given ,no issues 
are seen.

Hence , issue with * in classificationName and typeName provided together.

CC : [~sarath.ku...@gmail.com]



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

[jira] [Updated] (ATLAS-1116) Performance monitoring of backend methods in API requests

2017-11-23 Thread Sharmadha Sainath (JIRA) 

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

Sharmadha Sainath updated ATLAS-1116:
-
Attachment: Atlas_asterisk_in_classification_and type_name_exception.txt

> Performance monitoring of backend methods in API requests
> -
>
> Key: ATLAS-1116
> URL: https://issues.apache.org/jira/browse/ATLAS-1116
> Project: Atlas
>  Issue Type: Bug
>Reporter: Vimal Sharma
>Assignee: Shwetha G S
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1116-v2.patch, ATLAS-1116-v3.patch, 
> ATLAS-1116.patch, Atlas_asterisk_in_classification_and type_name_exception.txt
>
>
> Time taken by methods used in API calls for add/update/delete entities and 
> traits need to be monitored for performance



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