Re: Review Request 69707: API: Audit Scan for Classification Updates

2019-01-14 Thread Madhan Neethiraj

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




intg/src/main/java/org/apache/atlas/model/instance/ClassificationAssociateResponse.java
Lines 39 (patched)


ClassificationAssociateResponse ==> AtlasEntityHeaders



repository/src/main/java/org/apache/atlas/repository/store/graph/v2/ClassificationAssociator.java
Lines 132 (patched)


classifications that are already associated with the entity, but not in the 
incoming entity should be deleted as well i.e. not just when the incoming 
entity has empty classification list.



webapp/src/main/java/org/apache/atlas/web/rest/EntityREST.java
Lines 95 (patched)


ClassificationAssociator is needed only in getEntityHeaders() method. 
Consider instantiating one in this method, instead of injecting here.



webapp/src/main/java/org/apache/atlas/web/rest/EntityREST.java
Line 264 (original), 277 (patched)


perhaps this comment was updated during code-refactoring?



webapp/src/main/java/org/apache/atlas/web/rest/EntityREST.java
Lines 759 (patched)


Consider adding AtlasEntityStore.setClassifications() method (similar to 
add/update/delete classification methods) and call it directly from here, 
instead of going through classificationAssociator.


- Madhan Neethiraj


On Jan. 15, 2019, 1:26 a.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69707/
> ---
> 
> (Updated Jan. 15, 2019, 1:26 a.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj, Nikhil Bonte, Nixon Rodrigues, 
> and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-3029
> https://issues.apache.org/jira/browse/ATLAS-3029
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Approach**
> - Scan HBase 'ATLAS_ENTITY_AUDIT_EVENTS' table with approprite paramters.
> - Package the output into _AtlasEntityHeader_.
> - Provide _REST APIs_ to _EntityREST_.
> 
> **CURL**
> 
> _Fetch_
> curl -X GET  -u admin:passWord -H 'Content-Type: application/json'
>   
> 'http://localhost:21000/api/atlas/v2/entity/audit/classifications?timeRange=154699200:154715760'
>  \
> 
> _Udpate_
> curl -X POST  -u admin:passWord -H 'Content-Type: application/json'
>   'http://localhost:21000/api/atlas/v2/entity/audit/classifications' 
>   -d @fetched-classifications.json
> 
> 
> **Not supported**
> - Cassandra based Audits.
> - For testing: In-memory audits.
> 
> 
> Diffs
> -
> 
>   client/client-v2/src/main/java/org/apache/atlas/AtlasClientV2.java 
> 7c8caee89 
>   
> intg/src/main/java/org/apache/atlas/model/instance/ClassificationAssociateResponse.java
>  PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/EntityAuditRepository.java
>  aab2d5b6c 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/HBaseBasedAuditRepository.java
>  6f4415fa8 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/InMemoryEntityAuditRepository.java
>  dca3b853e 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/NoopEntityAuditRepository.java
>  e3a607809 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/ClassificationAssociator.java
>  PRE-CREATION 
>   
> repository/src/test/java/org/apache/atlas/repository/store/graph/v2/ClassificationAssociatorTest.java
>  PRE-CREATION 
>   repository/src/test/resources/json/entity-headers.json PRE-CREATION 
>   webapp/src/main/java/org/apache/atlas/web/rest/EntityREST.java 68c132c37 
> 
> 
> Diff: https://reviews.apache.org/r/69707/diff/3/
> 
> 
> Testing
> ---
> 
> **Unit tests**
> New tests added.
> 
> **Functional tests**
> Via CURL calls.
> 
> **Volume tests**
> Loads of over 2000 entities.
> 
> 
> File Attachments
> 
> 
> entity-headers.json
>   
> https://reviews.apache.org/media/uploaded/files/2019/01/14/a23bead7-6990-4d5b-b3b8-f46f990f5d99__entity-headers.json
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>



Re: Review Request 69744: ATLAS-3032 Importing an entity with tag attribute of type float data type fails with an BigDecimal Exception

2019-01-14 Thread Sarath Subramanian

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


Ship it!




Ship It!

- Sarath Subramanian


On Jan. 14, 2019, 6:23 a.m., Kapildeo Nayak wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69744/
> ---
> 
> (Updated Jan. 14, 2019, 6:23 a.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Nixon Rodrigues, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-3032
> https://issues.apache.org/jira/browse/ATLAS-3032
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> 1. In source cluster , created a tag with float attribute.
> 2. Created an hive_db and associated the tag to the hive_db with value 
> "-3.4028235E+38"
> 3. On importing the exported hive_db entity, exception is seen and import 
> fails.
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasGraphUtilsV2.java
>  69d3f63f9 
> 
> 
> Diff: https://reviews.apache.org/r/69744/diff/1/
> 
> 
> Testing
> ---
> 
> Tested in import-export with transformers options.
> 
> 
> Thanks,
> 
> Kapildeo Nayak
> 
>



[jira] [Updated] (ATLAS-3015) Tool: Associate Classifications to Entities based on QualifiedName

2019-01-14 Thread Ashutosh Mestry (JIRA)


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

Ashutosh Mestry updated ATLAS-3015:
---
Attachment: (was: ATLAS-3015-Classification-Updater-tool-master.patch)

> Tool: Associate Classifications to Entities based on QualifiedName
> --
>
> Key: ATLAS-3015
> URL: https://issues.apache.org/jira/browse/ATLAS-3015
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nikhil Bonte
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-3015-Classification-Updater-tool-master.patch
>
>
> *Background*
> Situation: A setup where Atlas classifications associated with entities the 
> data is subsequently erased and all data is lost. Entities are then 
> re-created using _import-hive.sh_. With this approach, the entities are 
> created within Atlas but there is no easy way to associate classifications to 
> these entities.
> *Solution and Approach Guidance*
>  # Before erasing Atlas database, create file with classifications and 
> entity-classification mapping.
>  # Erase the database.
>  # Create entities using appropriate means, say _import-hive.sh_.
>  # Read the file from step 1 and update Atlas.
> The tool should:
>  * Use _AtlasClient_ REST APIs.
>  * External and can be executed against a known Atlas instance.
>  



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


[jira] [Updated] (ATLAS-3015) Tool: Associate Classifications to Entities based on QualifiedName

2019-01-14 Thread Ashutosh Mestry (JIRA)


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

Ashutosh Mestry updated ATLAS-3015:
---
Attachment: ATLAS-3015-Classification-Updater-tool-master.patch

> Tool: Associate Classifications to Entities based on QualifiedName
> --
>
> Key: ATLAS-3015
> URL: https://issues.apache.org/jira/browse/ATLAS-3015
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nikhil Bonte
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-3015-Classification-Updater-tool-master.patch
>
>
> *Background*
> Situation: A setup where Atlas classifications associated with entities the 
> data is subsequently erased and all data is lost. Entities are then 
> re-created using _import-hive.sh_. With this approach, the entities are 
> created within Atlas but there is no easy way to associate classifications to 
> these entities.
> *Solution and Approach Guidance*
>  # Before erasing Atlas database, create file with classifications and 
> entity-classification mapping.
>  # Erase the database.
>  # Create entities using appropriate means, say _import-hive.sh_.
>  # Read the file from step 1 and update Atlas.
> The tool should:
>  * Use _AtlasClient_ REST APIs.
>  * External and can be executed against a known Atlas instance.
>  



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


[jira] [Updated] (ATLAS-3015) Tool: Associate Classifications to Entities based on QualifiedName

2019-01-14 Thread Ashutosh Mestry (JIRA)


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

Ashutosh Mestry updated ATLAS-3015:
---
Attachment: (was: ATLAS-3015-Classification-Updater-tool-master.patch)

> Tool: Associate Classifications to Entities based on QualifiedName
> --
>
> Key: ATLAS-3015
> URL: https://issues.apache.org/jira/browse/ATLAS-3015
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nikhil Bonte
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-3015-Classification-Updater-tool-master.patch
>
>
> *Background*
> Situation: A setup where Atlas classifications associated with entities the 
> data is subsequently erased and all data is lost. Entities are then 
> re-created using _import-hive.sh_. With this approach, the entities are 
> created within Atlas but there is no easy way to associate classifications to 
> these entities.
> *Solution and Approach Guidance*
>  # Before erasing Atlas database, create file with classifications and 
> entity-classification mapping.
>  # Erase the database.
>  # Create entities using appropriate means, say _import-hive.sh_.
>  # Read the file from step 1 and update Atlas.
> The tool should:
>  * Use _AtlasClient_ REST APIs.
>  * External and can be executed against a known Atlas instance.
>  



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


[jira] [Updated] (ATLAS-3015) Tool: Associate Classifications to Entities based on QualifiedName

2019-01-14 Thread Ashutosh Mestry (JIRA)


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

Ashutosh Mestry updated ATLAS-3015:
---
Attachment: ATLAS-3015-Classification-Updater-tool-master.patch

> Tool: Associate Classifications to Entities based on QualifiedName
> --
>
> Key: ATLAS-3015
> URL: https://issues.apache.org/jira/browse/ATLAS-3015
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nikhil Bonte
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-3015-Classification-Updater-tool-master.patch
>
>
> *Background*
> Situation: A setup where Atlas classifications associated with entities the 
> data is subsequently erased and all data is lost. Entities are then 
> re-created using _import-hive.sh_. With this approach, the entities are 
> created within Atlas but there is no easy way to associate classifications to 
> these entities.
> *Solution and Approach Guidance*
>  # Before erasing Atlas database, create file with classifications and 
> entity-classification mapping.
>  # Erase the database.
>  # Create entities using appropriate means, say _import-hive.sh_.
>  # Read the file from step 1 and update Atlas.
> The tool should:
>  * Use _AtlasClient_ REST APIs.
>  * External and can be executed against a known Atlas instance.
>  



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


Re: Review Request 69707: API: Audit Scan for Classification Updates

2019-01-14 Thread Ashutosh Mestry

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

(Updated Jan. 15, 2019, 1:26 a.m.)


Review request for atlas, Madhan Neethiraj, Nikhil Bonte, Nixon Rodrigues, and 
Sarath Subramanian.


Changes
---

Updates include: Addressed review comments.


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


Repository: atlas


Description
---

**Approach**
- Scan HBase 'ATLAS_ENTITY_AUDIT_EVENTS' table with approprite paramters.
- Package the output into _AtlasEntityHeader_.
- Provide _REST APIs_ to _EntityREST_.

**CURL**

_Fetch_
curl -X GET  -u admin:passWord -H 'Content-Type: application/json'
  
'http://localhost:21000/api/atlas/v2/entity/audit/classifications?timeRange=154699200:154715760'
 \

_Udpate_
curl -X POST  -u admin:passWord -H 'Content-Type: application/json'
  'http://localhost:21000/api/atlas/v2/entity/audit/classifications' 
  -d @fetched-classifications.json


**Not supported**
- Cassandra based Audits.
- For testing: In-memory audits.


Diffs (updated)
-

  client/client-v2/src/main/java/org/apache/atlas/AtlasClientV2.java 7c8caee89 
  
intg/src/main/java/org/apache/atlas/model/instance/ClassificationAssociateResponse.java
 PRE-CREATION 
  
repository/src/main/java/org/apache/atlas/repository/audit/EntityAuditRepository.java
 aab2d5b6c 
  
repository/src/main/java/org/apache/atlas/repository/audit/HBaseBasedAuditRepository.java
 6f4415fa8 
  
repository/src/main/java/org/apache/atlas/repository/audit/InMemoryEntityAuditRepository.java
 dca3b853e 
  
repository/src/main/java/org/apache/atlas/repository/audit/NoopEntityAuditRepository.java
 e3a607809 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/ClassificationAssociator.java
 PRE-CREATION 
  
repository/src/test/java/org/apache/atlas/repository/store/graph/v2/ClassificationAssociatorTest.java
 PRE-CREATION 
  repository/src/test/resources/json/entity-headers.json PRE-CREATION 
  webapp/src/main/java/org/apache/atlas/web/rest/EntityREST.java 68c132c37 


Diff: https://reviews.apache.org/r/69707/diff/3/

Changes: https://reviews.apache.org/r/69707/diff/2-3/


Testing
---

**Unit tests**
New tests added.

**Functional tests**
Via CURL calls.

**Volume tests**
Loads of over 2000 entities.


File Attachments


entity-headers.json
  
https://reviews.apache.org/media/uploaded/files/2019/01/14/a23bead7-6990-4d5b-b3b8-f46f990f5d99__entity-headers.json


Thanks,

Ashutosh Mestry



Re: Review Request 69707: API: Audit Scan for Classification Updates

2019-01-14 Thread Ashutosh Mestry


> On Jan. 14, 2019, 6:17 a.m., Madhan Neethiraj wrote:
> > intg/src/main/java/org/apache/atlas/model/instance/BulkHeadersResponse.java
> > Lines 40 (patched)
> > 
> >
> > Please review if BulkHeadersResponse class is necessary; perhaps the 
> > return value can simply be Map?
> > 
> > The interpretation of 'fromTimestamp' and 'toTimestamp' attributes here 
> > is not clear; also, more criterion can be added in the REST API, and we can 
> > avoid having to update BulkHeadersResponse to be in sync.

The Map ends with the serialization problem. We will 
have to use _TypeRefernce_ within _AtlasClient_ methods. Hence I choose this.


> On Jan. 14, 2019, 6:17 a.m., Madhan Neethiraj wrote:
> > repository/src/main/java/org/apache/atlas/repository/audit/EntityAuditRepository.java
> > Lines 87 (patched)
> > 
> >
> > Instead of returning List, returning Set 
> > i.e. guids might be more efficient; contents of EntityAuditEventV2 is not 
> > useful for the current use of this method. Please reveiew.

This is the change in approach I mentioned earlier. Just returnining guids will 
not make us get the state during that time range. We will end up with the 
latest state. Hence the events are returned.


- Ashutosh


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


On Jan. 14, 2019, 5:23 a.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69707/
> ---
> 
> (Updated Jan. 14, 2019, 5:23 a.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj, Nikhil Bonte, Nixon Rodrigues, 
> and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-3029
> https://issues.apache.org/jira/browse/ATLAS-3029
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Approach**
> - Scan HBase 'ATLAS_ENTITY_AUDIT_EVENTS' table with approprite paramters.
> - Package the output into _AtlasEntityHeader_.
> - Provide _REST APIs_ to _EntityREST_.
> 
> **CURL**
> 
> _Fetch_
> curl -X GET  -u admin:passWord -H 'Content-Type: application/json'
>   
> 'http://localhost:21000/api/atlas/v2/entity/audit/classifications?timeRange=154699200:154715760'
>  \
> 
> _Udpate_
> curl -X POST  -u admin:passWord -H 'Content-Type: application/json'
>   'http://localhost:21000/api/atlas/v2/entity/audit/classifications' 
>   -d @fetched-classifications.json
> 
> 
> **Not supported**
> - Cassandra based Audits.
> - For testing: In-memory audits.
> 
> 
> Diffs
> -
> 
>   client/client-v2/src/main/java/org/apache/atlas/AtlasClientV2.java 
> 7c8caee89 
>   intg/src/main/java/org/apache/atlas/model/instance/BulkHeadersResponse.java 
> PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/BulkEntityRetrieveAndUpdate.java
>  PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/CassandraBasedAuditRepository.java
>  eb78f8f70 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/EntityAuditRepository.java
>  aab2d5b6c 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/HBaseBasedAuditRepository.java
>  6f4415fa8 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/InMemoryEntityAuditRepository.java
>  dca3b853e 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/NoopEntityAuditRepository.java
>  e3a607809 
>   
> repository/src/test/java/org/apache/atlas/repository/audit/BulkEntityRetrieveAndUpdateTest.java
>  PRE-CREATION 
>   repository/src/test/resources/json/audit-event-1.json PRE-CREATION 
>   repository/src/test/resources/json/audit-event-2.json PRE-CREATION 
>   repository/src/test/resources/json/entity-headers.json PRE-CREATION 
>   webapp/src/main/java/org/apache/atlas/web/rest/EntityREST.java 68c132c37 
> 
> 
> Diff: https://reviews.apache.org/r/69707/diff/2/
> 
> 
> Testing
> ---
> 
> **Unit tests**
> New tests added.
> 
> **Functional tests**
> Via CURL calls.
> 
> **Volume tests**
> Loads of over 2000 entities.
> 
> 
> File Attachments
> 
> 
> entity-headers.json
>   
> https://reviews.apache.org/media/uploaded/files/2019/01/14/a23bead7-6990-4d5b-b3b8-f46f990f5d99__entity-headers.json
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>



[jira] [Updated] (ATLAS-3032) Importing an entity with tag attribute of type float data type fails with an BigDecimal Exception

2019-01-14 Thread Kapildeo Nayak (JIRA)


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

Kapildeo Nayak updated ATLAS-3032:
--
Attachment: ATLAS-3032.patch

> Importing an entity with tag attribute of type float data type fails with an 
> BigDecimal Exception
> -
>
> Key: ATLAS-3032
> URL: https://issues.apache.org/jira/browse/ATLAS-3032
> Project: Atlas
>  Issue Type: Bug
>Reporter: Kapildeo Nayak
>Priority: Critical
> Attachments: ATLAS-3032.patch
>
>
> 1. In source cluster , created a tag with float attribute.
> 2. Created an hive_db and associated the tag to the hive_db with value 
> "-3.4028235E+38"
> 3. On importing the exported hive_db entity, exception is seen and import 
> fails.



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


Review Request 69744: ATLAS-3032 Importing an entity with tag attribute of type float data type fails with an BigDecimal Exception

2019-01-14 Thread Kapildeo Nayak

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

Review request for atlas, Ashutosh Mestry, Nixon Rodrigues, and Sarath 
Subramanian.


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


Repository: atlas


Description
---

1. In source cluster , created a tag with float attribute.
2. Created an hive_db and associated the tag to the hive_db with value 
"-3.4028235E+38"
3. On importing the exported hive_db entity, exception is seen and import fails.


Diffs
-

  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasGraphUtilsV2.java
 69d3f63f9 


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


Testing
---

Tested in import-export with transformers options.


Thanks,

Kapildeo Nayak



[jira] [Updated] (ATLAS-2988) Replace title with the Bootstrap tooltip

2019-01-14 Thread Keval Bhatt (JIRA)


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

Keval Bhatt updated ATLAS-2988:
---
Attachment: ATLAS-2988-branch-0.8.patch

> Replace title with the Bootstrap tooltip
> 
>
> Key: ATLAS-2988
> URL: https://issues.apache.org/jira/browse/ATLAS-2988
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: ATLAS-2988-branch-0.8.patch
>
>
> Default title HTML attribute is taking few secs to show the tooltip. it will 
> be good to have a bootstrap tooltip (Example: 
> https://getbootstrap.com/docs/3.3/javascript/#tooltips)



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


[jira] [Updated] (ATLAS-2988) Replace title with the Bootstrap tooltip

2019-01-14 Thread Keval Bhatt (JIRA)


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

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

> Replace title with the Bootstrap tooltip
> 
>
> Key: ATLAS-2988
> URL: https://issues.apache.org/jira/browse/ATLAS-2988
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: ATLAS-2988-branch-0.8.patch, ATLAS-2988.patch
>
>
> Default title HTML attribute is taking few secs to show the tooltip. it will 
> be good to have a bootstrap tooltip (Example: 
> https://getbootstrap.com/docs/3.3/javascript/#tooltips)



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


[jira] [Created] (ATLAS-3032) Importing an entity with tag attribute of type float data type fails with an BigDecimal Exception

2019-01-14 Thread Kapildeo Nayak (JIRA)
Kapildeo Nayak created ATLAS-3032:
-

 Summary: Importing an entity with tag attribute of type float data 
type fails with an BigDecimal Exception
 Key: ATLAS-3032
 URL: https://issues.apache.org/jira/browse/ATLAS-3032
 Project: Atlas
  Issue Type: Bug
Reporter: Kapildeo Nayak


1. In source cluster , created a tag with float attribute.
2. Created an hive_db and associated the tag to the hive_db with value 
"-3.4028235E+38"
3. On importing the exported hive_db entity, exception is seen and import fails.



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


[jira] [Commented] (ATLAS-2994) UI - If Hide deleted entity filter is applied then to UI displays deleted entity in lineage

2019-01-14 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on ATLAS-2994:


Commit 8f65a33c9b65204c043c7612b9ba0ade669ab136 in atlas's branch 
refs/heads/branch-1.0 from Abhishek Kadam
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=8f65a33 ]

ATLAS-2994 UI - If Hide deleted entity filter is applied then to UI displays 
deleted entity in lineage

(cherry picked from commit 90b0e20aa310da9398a8a3e978ab97782a811a0a)
Signed-off-by: kevalbhatt 


> UI - If Hide deleted entity filter is applied then to UI displays deleted 
> entity in lineage
> ---
>
> Key: ATLAS-2994
> URL: https://issues.apache.org/jira/browse/ATLAS-2994
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0, trunk
>Reporter: Tejas Rawool
>Assignee: Abhishek Kadam
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: ATLAS-2994.patch, SS7.png
>
>




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


[jira] [Commented] (ATLAS-2994) UI - If Hide deleted entity filter is applied then to UI displays deleted entity in lineage

2019-01-14 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on ATLAS-2994:


Commit 96bdc802cc0b94819f1c02b9ed4b911ce05c947d in atlas's branch 
refs/heads/master from Abhishek Kadam
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=96bdc80 ]

ATLAS-2994 UI - If Hide deleted entity filter is applied then to UI displays 
deleted entity in lineage

(cherry picked from commit 90b0e20aa310da9398a8a3e978ab97782a811a0a)
Signed-off-by: kevalbhatt 


> UI - If Hide deleted entity filter is applied then to UI displays deleted 
> entity in lineage
> ---
>
> Key: ATLAS-2994
> URL: https://issues.apache.org/jira/browse/ATLAS-2994
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0, trunk
>Reporter: Tejas Rawool
>Assignee: Abhishek Kadam
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: ATLAS-2994.patch, SS7.png
>
>




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


[jira] [Commented] (ATLAS-2994) UI - If Hide deleted entity filter is applied then to UI displays deleted entity in lineage

2019-01-14 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on ATLAS-2994:


Commit 90b0e20aa310da9398a8a3e978ab97782a811a0a in atlas's branch 
refs/heads/branch-0.8 from Abhishek Kadam
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=90b0e20 ]

ATLAS-2994 UI - If Hide deleted entity filter is applied then to UI displays 
deleted entity in lineage


> UI - If Hide deleted entity filter is applied then to UI displays deleted 
> entity in lineage
> ---
>
> Key: ATLAS-2994
> URL: https://issues.apache.org/jira/browse/ATLAS-2994
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0, trunk
>Reporter: Tejas Rawool
>Assignee: Abhishek Kadam
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: ATLAS-2994.patch, SS7.png
>
>




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


[jira] [Commented] (ATLAS-2994) UI - If Hide deleted entity filter is applied then to UI displays deleted entity in lineage

2019-01-14 Thread Tejas Rawool (JIRA)


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

Tejas Rawool commented on ATLAS-2994:
-

[~abhib4] - I have verified the patch and it working fine. +1 for the patch.

> UI - If Hide deleted entity filter is applied then to UI displays deleted 
> entity in lineage
> ---
>
> Key: ATLAS-2994
> URL: https://issues.apache.org/jira/browse/ATLAS-2994
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0, trunk
>Reporter: Tejas Rawool
>Assignee: Abhishek Kadam
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: ATLAS-2994.patch, SS7.png
>
>




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