[jira] [Updated] (ATLAS-3911) UI: Type system management

2020-09-18 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3911:
---
Attachment: ATLAS-3911-1.patch

> UI: Type system management
> --
>
> Key: ATLAS-3911
> URL: https://issues.apache.org/jira/browse/ATLAS-3911
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3911-1.patch, ATLAS-3911.patch, 
> Type_System_Tree.png, Type_System_Tree_Details.png
>
>
> !Type_System_Tree.png|width=482,height=237!
>  
> !Type_System_Tree_Details.png|width=509,height=249!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3827) UI: Use moment date format instead of default date format.

2020-09-17 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3827:
---
Attachment: ATLAS-3827-1.patch

> UI: Use moment date format instead of default date format.
> --
>
> Key: ATLAS-3827
> URL: https://issues.apache.org/jira/browse/ATLAS-3827
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3827-1.patch, ATLAS-3827.patch, 
> image-2020-09-16-17-11-33-386.png, image-2020-09-16-17-12-04-512.png, 
> new_date_format.png
>
>
>  
> UI configured to use the following date formats:
> {code:java}
>  /MM/DD
>  /MM/DD HH:mm:ss
>  MM/DD/ h:mm A z
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3945) UI: Entity details page, Show N/A for date if date value is 0 or null

2020-09-17 Thread Keval Bhatt (Jira)


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

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

> UI: Entity details page,  Show N/A for date if date value is 0 or null
> --
>
> Key: ATLAS-3945
> URL: https://issues.apache.org/jira/browse/ATLAS-3945
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3945.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ATLAS-3945) UI: Entity details page, Show N/A for date if date value is 0 or null

2020-09-17 Thread Keval Bhatt (Jira)
Keval Bhatt created ATLAS-3945:
--

 Summary: UI: Entity details page,  Show N/A for date if date value 
is 0 or null
 Key: ATLAS-3945
 URL: https://issues.apache.org/jira/browse/ATLAS-3945
 Project: Atlas
  Issue Type: Bug
Reporter: Keval Bhatt
Assignee: Keval Bhatt
 Fix For: 3.0.0, 2.2.0






--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3911) UI: Type system management

2020-09-16 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3911:
---
Summary: UI: Type system management  (was: UI: Type system managment)

> UI: Type system management
> --
>
> Key: ATLAS-3911
> URL: https://issues.apache.org/jira/browse/ATLAS-3911
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3911.patch, Type_System_Tree.png, 
> Type_System_Tree_Details.png
>
>
> !Type_System_Tree.png|width=482,height=237!
>  
> !Type_System_Tree_Details.png|width=509,height=249!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3943) UI: Show Import/Export operations in administration audit.

2020-09-16 Thread Keval Bhatt (Jira)


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

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

> UI: Show Import/Export operations in administration audit.
> --
>
> Key: ATLAS-3943
> URL: https://issues.apache.org/jira/browse/ATLAS-3943
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3943.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3827) UI: Use moment date format instead of default date format.

2020-09-16 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3827:
---
Description: 
 

UI configured to use the following date formats:
{code:java}

 /MM/DD
 /MM/DD HH:mm:ss
 MM/DD/ h:mm A z

{code}

  was:
Date Format should be

/MM/DD hh:mm:ss


> UI: Use moment date format instead of default date format.
> --
>
> Key: ATLAS-3827
> URL: https://issues.apache.org/jira/browse/ATLAS-3827
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3827.patch, image-2020-09-16-17-11-33-386.png, 
> image-2020-09-16-17-12-04-512.png, new_date_format.png
>
>
>  
> UI configured to use the following date formats:
> {code:java}
>  /MM/DD
>  /MM/DD HH:mm:ss
>  MM/DD/ h:mm A z
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3827) UI: Use moment date format instead of default date format.

2020-09-16 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3827:
---
Attachment: image-2020-09-16-17-12-04-512.png

> UI: Use moment date format instead of default date format.
> --
>
> Key: ATLAS-3827
> URL: https://issues.apache.org/jira/browse/ATLAS-3827
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3827.patch, image-2020-09-16-17-11-33-386.png, 
> image-2020-09-16-17-12-04-512.png, new_date_format.png
>
>
> Date Format should be
> /MM/DD hh:mm:ss



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (ATLAS-3827) UI: Use moment date format instead of default date format.

2020-09-16 Thread Keval Bhatt (Jira)


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

Keval Bhatt commented on ATLAS-3827:


Before Change:

!image-2020-09-16-17-12-04-512.png|width=279,height=325!

After Change:
!image-2020-09-16-17-11-33-386.png|width=274,height=279!

> UI: Use moment date format instead of default date format.
> --
>
> Key: ATLAS-3827
> URL: https://issues.apache.org/jira/browse/ATLAS-3827
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3827.patch, image-2020-09-16-17-11-33-386.png, 
> image-2020-09-16-17-12-04-512.png, new_date_format.png
>
>
> Date Format should be
> /MM/DD hh:mm:ss



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3827) UI: Use moment date format instead of default date format.

2020-09-16 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3827:
---
Attachment: new_date_format.png

> UI: Use moment date format instead of default date format.
> --
>
> Key: ATLAS-3827
> URL: https://issues.apache.org/jira/browse/ATLAS-3827
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3827.patch, image-2020-09-16-17-11-33-386.png, 
> new_date_format.png
>
>
> Date Format should be
> /MM/DD hh:mm:ss



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3827) UI: Use moment date format instead of default date format.

2020-09-16 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3827:
---
Attachment: image-2020-09-16-17-11-33-386.png

> UI: Use moment date format instead of default date format.
> --
>
> Key: ATLAS-3827
> URL: https://issues.apache.org/jira/browse/ATLAS-3827
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3827.patch, image-2020-09-16-17-11-33-386.png, 
> new_date_format.png
>
>
> Date Format should be
> /MM/DD hh:mm:ss



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3827) UI: Use moment date format instead of default date format.

2020-09-16 Thread Keval Bhatt (Jira)


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

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

> UI: Use moment date format instead of default date format.
> --
>
> Key: ATLAS-3827
> URL: https://issues.apache.org/jira/browse/ATLAS-3827
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3827.patch
>
>
> Date Format should be
> /MM/DD hh:mm:ss



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ATLAS-3943) UI: Show Import/Export operations in administration audit.

2020-09-16 Thread Keval Bhatt (Jira)
Keval Bhatt created ATLAS-3943:
--

 Summary: UI: Show Import/Export operations in administration audit.
 Key: ATLAS-3943
 URL: https://issues.apache.org/jira/browse/ATLAS-3943
 Project: Atlas
  Issue Type: Sub-task
Reporter: Keval Bhatt
Assignee: Keval Bhatt
 Fix For: 3.0.0, 2.2.0






--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (ATLAS-3925) UI: Properties with value 0 or false are displayed as N/A for

2020-09-03 Thread Keval Bhatt (Jira)


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

Keval Bhatt resolved ATLAS-3925.

Resolution: Fixed

> UI: Properties with value 0 or false are displayed as N/A for 
> --
>
> Key: ATLAS-3925
> URL: https://issues.apache.org/jira/browse/ATLAS-3925
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3925-1.patch, ATLAS-3925.patch, 
> image-2020-08-25-12-53-09-294.png, image-2020-08-25-12-53-45-935.png
>
>
> Check the screenshot:
> *partitionCount* is displayed as N/A instead of *0*
>  
> +API response:+
>  
> *!image-2020-08-25-12-53-09-294.png|width=440,height=151!*
> +UI:+ 
>  
> *!image-2020-08-25-12-53-45-935.png|width=427,height=214!*
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3925) UI: Properties with value 0 or false are displayed as N/A for

2020-09-03 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3925:
---
Attachment: ATLAS-3925-1.patch

> UI: Properties with value 0 or false are displayed as N/A for 
> --
>
> Key: ATLAS-3925
> URL: https://issues.apache.org/jira/browse/ATLAS-3925
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3925-1.patch, ATLAS-3925.patch, 
> image-2020-08-25-12-53-09-294.png, image-2020-08-25-12-53-45-935.png
>
>
> Check the screenshot:
> *partitionCount* is displayed as N/A instead of *0*
>  
> +API response:+
>  
> *!image-2020-08-25-12-53-09-294.png|width=440,height=151!*
> +UI:+ 
>  
> *!image-2020-08-25-12-53-45-935.png|width=427,height=214!*
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (ATLAS-3911) UI: Type system managment

2020-09-03 Thread Keval Bhatt (Jira)


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

Keval Bhatt commented on ATLAS-3911:


Updated d3 version from  3.5.17 -> 5.14.2

> UI: Type system managment
> -
>
> Key: ATLAS-3911
> URL: https://issues.apache.org/jira/browse/ATLAS-3911
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3911.patch, Type_System_Tree.png, 
> Type_System_Tree_Details.png
>
>
> !Type_System_Tree.png|width=482,height=237!
>  
> !Type_System_Tree_Details.png|width=509,height=249!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3911) UI: Type system managment

2020-09-03 Thread Keval Bhatt (Jira)


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

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

> UI: Type system managment
> -
>
> Key: ATLAS-3911
> URL: https://issues.apache.org/jira/browse/ATLAS-3911
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3911.patch, Type_System_Tree.png, 
> Type_System_Tree_Details.png
>
>
> !Type_System_Tree.png|width=482,height=237!
>  
> !Type_System_Tree_Details.png|width=509,height=249!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (ATLAS-3911) UI: Type system managment

2020-09-03 Thread Keval Bhatt (Jira)


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

Keval Bhatt reassigned ATLAS-3911:
--

Assignee: Keval Bhatt  (was: Sameer Shaikh)

> UI: Type system managment
> -
>
> Key: ATLAS-3911
> URL: https://issues.apache.org/jira/browse/ATLAS-3911
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: Type_System_Tree.png, Type_System_Tree_Details.png
>
>
> !Type_System_Tree.png|width=482,height=237!
>  
> !Type_System_Tree_Details.png|width=509,height=249!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3925) UI: Properties with value 0 or false are displayed as N/A for

2020-08-26 Thread Keval Bhatt (Jira)


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

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

> UI: Properties with value 0 or false are displayed as N/A for 
> --
>
> Key: ATLAS-3925
> URL: https://issues.apache.org/jira/browse/ATLAS-3925
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3925.patch, image-2020-08-25-12-53-09-294.png, 
> image-2020-08-25-12-53-45-935.png
>
>
> Check the screenshot:
> *partitionCount* is displayed as N/A instead of *0*
>  
> +API response:+
>  
> *!image-2020-08-25-12-53-09-294.png|width=440,height=151!*
> +UI:+ 
>  
> *!image-2020-08-25-12-53-45-935.png|width=427,height=214!*
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3583) Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and DELETE

2020-08-26 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3583:
---
Fix Version/s: 2.2.0

> Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and 
> DELETE
> 
>
> Key: ATLAS-3583
> URL: https://issues.apache.org/jira/browse/ATLAS-3583
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Mandar Ambawane
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3583-V3.patch, ATLAS-3583-V8.patch
>
>
> By using Audit Framework, capture audit entries when Type defs are created/ 
> updated/ deleted.
> These audit entries can be seen under the "Audits" tab of Admin section.
> If there are mutiple Typedefs created/ updated/ deleted in a single request, 
> Then only one audit entry will be recorded. 
> This audit entry will consist of entire information about all the included 
> Typedefs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3822) UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE

2020-08-26 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3822:
---
Fix Version/s: 2.2.0

> UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE
> 
>
> Key: ATLAS-3822
> URL: https://issues.apache.org/jira/browse/ATLAS-3822
> Project: Atlas
>  Issue Type: Bug
>Reporter: Mandar Ambawane
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3822-1.patch, ATLAS-3822-2.patch, 
> ATLAS-3822.patch, image-2020-06-16-17-01-29-797.png, 
> image-2020-06-16-17-01-58-179.png
>
>
> !image-2020-06-16-17-01-29-797.png|width=650,height=361!
>  
> !image-2020-06-16-17-01-58-179.png|width=641,height=472!
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3925) UI: Properties with value 0 or false are displayed as N/A for

2020-08-25 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3925:
---
Fix Version/s: 2.2.0
   3.0.0

> UI: Properties with value 0 or false are displayed as N/A for 
> --
>
> Key: ATLAS-3925
> URL: https://issues.apache.org/jira/browse/ATLAS-3925
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: image-2020-08-25-12-53-09-294.png, 
> image-2020-08-25-12-53-45-935.png
>
>
> Check the screenshot:
> *partitionCount* is displayed as N/A instead of *0*
>  
> +API response:+
>  
> *!image-2020-08-25-12-53-09-294.png|width=440,height=151!*
> +UI:+ 
>  
> *!image-2020-08-25-12-53-45-935.png|width=427,height=214!*
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ATLAS-3925) UI: Properties with value 0 or false are displayed as N/A for

2020-08-25 Thread Keval Bhatt (Jira)
Keval Bhatt created ATLAS-3925:
--

 Summary: UI: Properties with value 0 or false are displayed as N/A 
for 
 Key: ATLAS-3925
 URL: https://issues.apache.org/jira/browse/ATLAS-3925
 Project: Atlas
  Issue Type: Bug
Reporter: Keval Bhatt
Assignee: Keval Bhatt
 Attachments: image-2020-08-25-12-53-09-294.png, 
image-2020-08-25-12-53-45-935.png

Check the screenshot:


*partitionCount* is displayed as N/A instead of *0*

 

+API response:+

 

*!image-2020-08-25-12-53-09-294.png|width=440,height=151!*

+UI:+ 

 

*!image-2020-08-25-12-53-45-935.png|width=427,height=214!*

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3892) Basic search enhanced Feature - Search history

2020-08-14 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3892:
---
Fix Version/s: 3.0.0

> Basic search enhanced Feature - Search history 
> ---
>
> Key: ATLAS-3892
> URL: https://issues.apache.org/jira/browse/ATLAS-3892
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Fix For: 3.0.0
>
>
> Feature to provide filters for better searching abilities : 
> Date Range feature with 6 different filters :
> 1.last 7 days.
> 2.Last month.
> 3.Last 30 days.
> 4.Today.
> 5.Yesterday.
> 6.Custom Range.
> 7.This Month.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3892) Basic search enhanced Feature - Search history

2020-08-14 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3892:
---
Fix Version/s: 2.2.0

> Basic search enhanced Feature - Search history 
> ---
>
> Key: ATLAS-3892
> URL: https://issues.apache.org/jira/browse/ATLAS-3892
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> Feature to provide filters for better searching abilities : 
> Date Range feature with 6 different filters :
> 1.last 7 days.
> 2.Last month.
> 3.Last 30 days.
> 4.Today.
> 5.Yesterday.
> 6.Custom Range.
> 7.This Month.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3827) UI: Use moment date format instead of default date format.

2020-08-13 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3827:
---
Fix Version/s: 2.2.0

> UI: Use moment date format instead of default date format.
> --
>
> Key: ATLAS-3827
> URL: https://issues.apache.org/jira/browse/ATLAS-3827
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> Date Format should be
> /MM/DD hh:mm:ss



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3900) UI: Allow user to select the date range for date attribute in basic search

2020-08-12 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3900:
---
Attachment: ATLAS-3900-3.patch

> UI: Allow user to select the date range for date attribute in basic search
> --
>
> Key: ATLAS-3900
> URL: https://issues.apache.org/jira/browse/ATLAS-3900
> Project: Atlas
>  Issue Type: Sub-task
>  Components: atlas-webui
>Affects Versions: 2.1.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
>  Labels: basic-search, datetimepicker
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3900-1.patch, ATLAS-3900-2.patch, 
> ATLAS-3900-3.patch, ATLAS-3900.patch, Screen Shot 2020-07-21 at 10.59.59 
> PM.png, Screen Shot 2020-07-21 at 11.00.08 PM.png, Screen Shot 2020-07-21 at 
> 11.00.15 PM.png
>
>
> In basic search attribute popup if the user selects the date type attribute 
> then UI should show a few quick search operator and custom range selection. 
> example:
> !Screen Shot 2020-07-21 at 10.59.59 PM.png|width=631,height=282!
>  
> !Screen Shot 2020-07-21 at 11.00.08 PM.png|width=630,height=302!
>  
> !Screen Shot 2020-07-21 at 11.00.15 PM.png|width=630,height=304!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3900) UI: Allow user to select the date range for date attribute in basic search

2020-08-07 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3900:
---
Attachment: ATLAS-3900-2.patch

> UI: Allow user to select the date range for date attribute in basic search
> --
>
> Key: ATLAS-3900
> URL: https://issues.apache.org/jira/browse/ATLAS-3900
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3900-1.patch, ATLAS-3900-2.patch, 
> ATLAS-3900.patch, Screen Shot 2020-07-21 at 10.59.59 PM.png, Screen Shot 
> 2020-07-21 at 11.00.08 PM.png, Screen Shot 2020-07-21 at 11.00.15 PM.png
>
>
> In basic search attribute popup if the user selects the date type attribute 
> then UI should show a few quick search operator and custom range selection. 
> example:
> !Screen Shot 2020-07-21 at 10.59.59 PM.png|width=631,height=282!
>  
> !Screen Shot 2020-07-21 at 11.00.08 PM.png|width=630,height=302!
>  
> !Screen Shot 2020-07-21 at 11.00.15 PM.png|width=630,height=304!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3822) UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE

2020-08-07 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3822:
---
Attachment: ATLAS-3822-2.patch

> UI changes: Audit entries for TypeDefs CREATE, UPDATE and DELETE
> 
>
> Key: ATLAS-3822
> URL: https://issues.apache.org/jira/browse/ATLAS-3822
> Project: Atlas
>  Issue Type: Bug
>Reporter: Mandar Ambawane
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-3822-1.patch, ATLAS-3822-2.patch, 
> ATLAS-3822.patch, image-2020-06-16-17-01-29-797.png, 
> image-2020-06-16-17-01-58-179.png
>
>
> !image-2020-06-16-17-01-29-797.png|width=650,height=361!
>  
> !image-2020-06-16-17-01-58-179.png|width=641,height=472!
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (ATLAS-3911) UI: Type system managment

2020-08-05 Thread Keval Bhatt (Jira)


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

Keval Bhatt reassigned ATLAS-3911:
--

Assignee: Sameer Shaikh  (was: Keval Bhatt)

> UI: Type system managment
> -
>
> Key: ATLAS-3911
> URL: https://issues.apache.org/jira/browse/ATLAS-3911
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Sameer Shaikh
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: Type_System_Tree.png, Type_System_Tree_Details.png
>
>
> !Type_System_Tree.png|width=482,height=237!
>  
> !Type_System_Tree_Details.png|width=509,height=249!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3911) UI: Type system managment

2020-08-05 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3911:
---
Description: 
!Type_System_Tree.png|width=482,height=237!

 

!Type_System_Tree_Details.png|width=509,height=249!

> UI: Type system managment
> -
>
> Key: ATLAS-3911
> URL: https://issues.apache.org/jira/browse/ATLAS-3911
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: Type_System_Tree.png, Type_System_Tree_Details.png
>
>
> !Type_System_Tree.png|width=482,height=237!
>  
> !Type_System_Tree_Details.png|width=509,height=249!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ATLAS-3911) UI: Type system managment

2020-08-05 Thread Keval Bhatt (Jira)
Keval Bhatt created ATLAS-3911:
--

 Summary: UI: Type system managment
 Key: ATLAS-3911
 URL: https://issues.apache.org/jira/browse/ATLAS-3911
 Project: Atlas
  Issue Type: Improvement
Reporter: Keval Bhatt
Assignee: Keval Bhatt
 Fix For: 3.0.0, 2.2.0






--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3911) UI: Type system managment

2020-08-05 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3911:
---
Attachment: Type_System_Tree.png
Type_System_Tree_Details.png

> UI: Type system managment
> -
>
> Key: ATLAS-3911
> URL: https://issues.apache.org/jira/browse/ATLAS-3911
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: Type_System_Tree.png, Type_System_Tree_Details.png
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3909) UI: Improve readability for the table view in the entity detail page

2020-08-03 Thread Keval Bhatt (Jira)


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

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

> UI: Improve readability for the table view in the entity detail page 
> -
>
> Key: ATLAS-3909
> URL: https://issues.apache.org/jira/browse/ATLAS-3909
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3909.patch, image-2020-08-03-12-48-10-984.png, 
> image-2020-08-03-12-48-28-192.png
>
>
> Change the key style to bold for table view in the entity details page. 
>  
> !image-2020-08-03-12-48-10-984.png|width=508,height=311!
> *Expected:*
> !image-2020-08-03-12-48-28-192.png|width=541,height=341!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3909) UI: Improve readability for the table view in the entity detail page

2020-08-03 Thread Keval Bhatt (Jira)


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

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

> UI: Improve readability for the table view in the entity detail page 
> -
>
> Key: ATLAS-3909
> URL: https://issues.apache.org/jira/browse/ATLAS-3909
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: image-2020-08-03-12-48-10-984.png, 
> image-2020-08-03-12-48-28-192.png
>
>
> Change the key style to bold for table view in the entity details page. 
>  
> !image-2020-08-03-12-48-10-984.png|width=508,height=311!
> *Expected:*
> !image-2020-08-03-12-48-28-192.png|width=541,height=341!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3909) UI: Improve readability for the table view in the entity detail page

2020-08-03 Thread Keval Bhatt (Jira)


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

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

> UI: Improve readability for the table view in the entity detail page 
> -
>
> Key: ATLAS-3909
> URL: https://issues.apache.org/jira/browse/ATLAS-3909
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3909.patch, image-2020-08-03-12-48-10-984.png, 
> image-2020-08-03-12-48-28-192.png
>
>
> Change the key style to bold for table view in the entity details page. 
>  
> !image-2020-08-03-12-48-10-984.png|width=508,height=311!
> *Expected:*
> !image-2020-08-03-12-48-28-192.png|width=541,height=341!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3909) UI: Improve readability for the table view in the entity detail page

2020-08-03 Thread Keval Bhatt (Jira)


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

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

> UI: Improve readability for the table view in the entity detail page 
> -
>
> Key: ATLAS-3909
> URL: https://issues.apache.org/jira/browse/ATLAS-3909
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3909.patch, image-2020-08-03-12-48-10-984.png, 
> image-2020-08-03-12-48-28-192.png
>
>
> Change the key style to bold for table view in the entity details page. 
>  
> !image-2020-08-03-12-48-10-984.png|width=508,height=311!
> *Expected:*
> !image-2020-08-03-12-48-28-192.png|width=541,height=341!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3909) UI: Improve readability for the table view in the entity detail page

2020-08-03 Thread Keval Bhatt (Jira)


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

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

> UI: Improve readability for the table view in the entity detail page 
> -
>
> Key: ATLAS-3909
> URL: https://issues.apache.org/jira/browse/ATLAS-3909
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3909.patch, image-2020-08-03-12-48-10-984.png, 
> image-2020-08-03-12-48-28-192.png
>
>
> Change the key style to bold for table view in the entity details page. 
>  
> !image-2020-08-03-12-48-10-984.png|width=508,height=311!
> *Expected:*
> !image-2020-08-03-12-48-28-192.png|width=541,height=341!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3904) Regression: Glossary term deatils page not able to render the classfication tab

2020-08-03 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3904:
---
Attachment: ATLAS-3904-1.patch

> Regression: Glossary term deatils page not able to render the classfication 
> tab
> ---
>
> Key: ATLAS-3904
> URL: https://issues.apache.org/jira/browse/ATLAS-3904
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3904-1.patch, ATLAS-3904.patch, Screen Shot 
> 2020-07-28 at 5.09.08 PM.png
>
>
> Click on the term details page and check the console.
>  
> !Screen Shot 2020-07-28 at 5.09.08 PM.png|width=618,height=304!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3909) UI: Improve readability for the table view in the entity detail page

2020-08-03 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3909:
---
Description: 
Change the key style to bold for table view in the entity details page. 

 

!image-2020-08-03-12-48-10-984.png|width=508,height=311!

*Expected:*

!image-2020-08-03-12-48-28-192.png|width=541,height=341!

  was:
Change the key style to bold for table view in the entity details page. 
 
 


> UI: Improve readability for the table view in the entity detail page 
> -
>
> Key: ATLAS-3909
> URL: https://issues.apache.org/jira/browse/ATLAS-3909
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: image-2020-08-03-12-48-10-984.png, 
> image-2020-08-03-12-48-28-192.png
>
>
> Change the key style to bold for table view in the entity details page. 
>  
> !image-2020-08-03-12-48-10-984.png|width=508,height=311!
> *Expected:*
> !image-2020-08-03-12-48-28-192.png|width=541,height=341!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3909) UI: Improve readability for the table view in the entity detail page

2020-08-03 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3909:
---
Attachment: image-2020-08-03-12-48-28-192.png

> UI: Improve readability for the table view in the entity detail page 
> -
>
> Key: ATLAS-3909
> URL: https://issues.apache.org/jira/browse/ATLAS-3909
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: image-2020-08-03-12-48-10-984.png, 
> image-2020-08-03-12-48-28-192.png
>
>
> Change the key style to bold for table view in the entity details page. 
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3909) UI: Improve readability for the table view in the entity detail page

2020-08-03 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3909:
---
Attachment: image-2020-08-03-12-48-10-984.png

> UI: Improve readability for the table view in the entity detail page 
> -
>
> Key: ATLAS-3909
> URL: https://issues.apache.org/jira/browse/ATLAS-3909
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: image-2020-08-03-12-48-10-984.png, 
> image-2020-08-03-12-48-28-192.png
>
>
> Change the key style to bold for table view in the entity details page. 
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ATLAS-3909) UI: Improve readability for the table view in the entity detail page

2020-08-03 Thread Keval Bhatt (Jira)
Keval Bhatt created ATLAS-3909:
--

 Summary: UI: Improve readability for the table view in the entity 
detail page 
 Key: ATLAS-3909
 URL: https://issues.apache.org/jira/browse/ATLAS-3909
 Project: Atlas
  Issue Type: Improvement
Reporter: Keval Bhatt
Assignee: Keval Bhatt
 Fix For: 3.0.0, 2.2.0


Change the key style to bold for table view in the entity details page. 
 
 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3903) New UI: Glossary category not reflected in the tree after creation.

2020-07-31 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3903:
---
Fix Version/s: 2.2.0

> New UI: Glossary category not reflected in the tree after creation.
> ---
>
> Key: ATLAS-3903
> URL: https://issues.apache.org/jira/browse/ATLAS-3903
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: Category_does_not_reflect_in_dropdown.mkv
>
>
> Steps reproduce the issue:
>  * Create the glossary
>  * Click on "..." to create the category
>  * After adding category details click on save
> Due to regression newly created category is not rendered in the tree view. if 
> a user clicks on the refresh button then it is visible.
> Please check the attached video for a better understanding.
> [^Category_does_not_reflect_in_dropdown.mkv]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3904) Regression: Glossary term deatils page not able to render the classfication tab

2020-07-29 Thread Keval Bhatt (Jira)


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

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

> Regression: Glossary term deatils page not able to render the classfication 
> tab
> ---
>
> Key: ATLAS-3904
> URL: https://issues.apache.org/jira/browse/ATLAS-3904
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3904.patch, Screen Shot 2020-07-28 at 5.09.08 
> PM.png
>
>
> Click on the term details page and check the console.
>  
> !Screen Shot 2020-07-28 at 5.09.08 PM.png|width=618,height=304!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3904) Regression: Glossary term deatils page not able to render the classfication tab

2020-07-28 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3904:
---
Description: 
Click on the term details page and check the console.

 

!Screen Shot 2020-07-28 at 5.09.08 PM.png|width=618,height=304!

> Regression: Glossary term deatils page not able to render the classfication 
> tab
> ---
>
> Key: ATLAS-3904
> URL: https://issues.apache.org/jira/browse/ATLAS-3904
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: Screen Shot 2020-07-28 at 5.09.08 PM.png
>
>
> Click on the term details page and check the console.
>  
> !Screen Shot 2020-07-28 at 5.09.08 PM.png|width=618,height=304!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3904) Regression: Glossary term deatils page not able to render the classfication tab

2020-07-28 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3904:
---
Attachment: Screen Shot 2020-07-28 at 5.09.08 PM.png

> Regression: Glossary term deatils page not able to render the classfication 
> tab
> ---
>
> Key: ATLAS-3904
> URL: https://issues.apache.org/jira/browse/ATLAS-3904
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: Screen Shot 2020-07-28 at 5.09.08 PM.png
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ATLAS-3904) Regression: Glossary term deatils page not able to render the classfication tab

2020-07-28 Thread Keval Bhatt (Jira)
Keval Bhatt created ATLAS-3904:
--

 Summary: Regression: Glossary term deatils page not able to render 
the classfication tab
 Key: ATLAS-3904
 URL: https://issues.apache.org/jira/browse/ATLAS-3904
 Project: Atlas
  Issue Type: Sub-task
Reporter: Keval Bhatt
Assignee: Keval Bhatt
 Fix For: 3.0.0, 2.2.0






--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3903) New UI: Glossary category not reflected in the tree after creation.

2020-07-28 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3903:
---
Description: 
Steps reproduce the issue:
 * Create the glossary
 * Click on "..." to create the category
 * After adding category details click on save

Due to regression newly created category is not rendered in the tree view. if a 
user clicks on the refresh button then it is visible.

Please check the attached video for a better understanding.

[^Category_does_not_reflect_in_dropdown.mkv]

  was:
Steps reproduce the issue:
 * Create the glossary
 * Click on "..." to create the category
 * After adding category details click on save

Due to regression newly created category is not rendered in the tree view. if 
the user clicks on refresh button then it is visible.

Please check the attached video for better understanding.


> New UI: Glossary category not reflected in the tree after creation.
> ---
>
> Key: ATLAS-3903
> URL: https://issues.apache.org/jira/browse/ATLAS-3903
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: Category_does_not_reflect_in_dropdown.mkv
>
>
> Steps reproduce the issue:
>  * Create the glossary
>  * Click on "..." to create the category
>  * After adding category details click on save
> Due to regression newly created category is not rendered in the tree view. if 
> a user clicks on the refresh button then it is visible.
> Please check the attached video for a better understanding.
> [^Category_does_not_reflect_in_dropdown.mkv]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3903) New UI: Glossary category not reflected in the tree after creation.

2020-07-28 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3903:
---
Attachment: Category_does_not_reflect_in_dropdown.mkv

> New UI: Glossary category not reflected in the tree after creation.
> ---
>
> Key: ATLAS-3903
> URL: https://issues.apache.org/jira/browse/ATLAS-3903
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: Category_does_not_reflect_in_dropdown.mkv
>
>
> Steps reproduce the issue:
>  * Create the glossary
>  * Click on "..." to create the category
>  * After adding category details click on save
> Due to regression newly created category is not rendered in the tree view. if 
> the user clicks on refresh button then it is visible.
> Please check the attached video for better understanding.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3903) New UI: Glossary category not reflected in the tree after creation.

2020-07-28 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3903:
---
Description: 
Steps reproduce the issue:
 * Create the glossary
 * Click on "..." to create the category
 * After adding category details click on save

Due to regression newly created category is not rendered in the tree view. if 
the user clicks on refresh button then it is visible.

Please check the attached video for better understanding.

  was:
Steps reproduce the issue:
 * Create the glossary
 * Click on "..." to create the 


> New UI: Glossary category not reflected in the tree after creation.
> ---
>
> Key: ATLAS-3903
> URL: https://issues.apache.org/jira/browse/ATLAS-3903
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0
>
>
> Steps reproduce the issue:
>  * Create the glossary
>  * Click on "..." to create the category
>  * After adding category details click on save
> Due to regression newly created category is not rendered in the tree view. if 
> the user clicks on refresh button then it is visible.
> Please check the attached video for better understanding.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3903) New UI: Glossary category not reflected in the tree after creation.

2020-07-28 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3903:
---
Description: 
Steps reproduce the issue:
 * Create the glossary
 * Click on "..." to create the 

> New UI: Glossary category not reflected in the tree after creation.
> ---
>
> Key: ATLAS-3903
> URL: https://issues.apache.org/jira/browse/ATLAS-3903
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0
>
>
> Steps reproduce the issue:
>  * Create the glossary
>  * Click on "..." to create the 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ATLAS-3903) New UI: Glossary category not reflected in the tree after creation.

2020-07-28 Thread Keval Bhatt (Jira)
Keval Bhatt created ATLAS-3903:
--

 Summary: New UI: Glossary category not reflected in the tree after 
creation.
 Key: ATLAS-3903
 URL: https://issues.apache.org/jira/browse/ATLAS-3903
 Project: Atlas
  Issue Type: Bug
Reporter: Keval Bhatt
Assignee: Keval Bhatt
 Fix For: 3.0.0






--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3900) UI: Allow user to select the date range for date attribute in basic search

2020-07-21 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3900:
---
Description: 
In basic search attribute popup if the user selects the date type attribute 
then UI should show a few quick search operator and custom range selection. 
example:

!Screen Shot 2020-07-21 at 10.59.59 PM.png|width=631,height=282!

 

!Screen Shot 2020-07-21 at 11.00.08 PM.png|width=630,height=302!

 

!Screen Shot 2020-07-21 at 11.00.15 PM.png|width=630,height=304!

  was:
In basic search attribute popup if the user selects the date type attribute 
then UI should show a few quick search operator and custom range selection. 
example:

!Screen Shot 2020-07-08 at 11.49.25 AM.png|width=457,height=230!


> UI: Allow user to select the date range for date attribute in basic search
> --
>
> Key: ATLAS-3900
> URL: https://issues.apache.org/jira/browse/ATLAS-3900
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3900-1.patch, ATLAS-3900.patch, Screen Shot 
> 2020-07-21 at 10.59.59 PM.png, Screen Shot 2020-07-21 at 11.00.08 PM.png, 
> Screen Shot 2020-07-21 at 11.00.15 PM.png
>
>
> In basic search attribute popup if the user selects the date type attribute 
> then UI should show a few quick search operator and custom range selection. 
> example:
> !Screen Shot 2020-07-21 at 10.59.59 PM.png|width=631,height=282!
>  
> !Screen Shot 2020-07-21 at 11.00.08 PM.png|width=630,height=302!
>  
> !Screen Shot 2020-07-21 at 11.00.15 PM.png|width=630,height=304!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3900) UI: Allow user to select the date range for date attribute in basic search

2020-07-21 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3900:
---
Attachment: Screen Shot 2020-07-21 at 11.00.15 PM.png
Screen Shot 2020-07-21 at 11.00.08 PM.png
Screen Shot 2020-07-21 at 10.59.59 PM.png

> UI: Allow user to select the date range for date attribute in basic search
> --
>
> Key: ATLAS-3900
> URL: https://issues.apache.org/jira/browse/ATLAS-3900
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3900-1.patch, ATLAS-3900.patch, Screen Shot 
> 2020-07-21 at 10.59.59 PM.png, Screen Shot 2020-07-21 at 11.00.08 PM.png, 
> Screen Shot 2020-07-21 at 11.00.15 PM.png
>
>
> In basic search attribute popup if the user selects the date type attribute 
> then UI should show a few quick search operator and custom range selection. 
> example:
> !Screen Shot 2020-07-08 at 11.49.25 AM.png|width=457,height=230!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3900) UI: Allow user to select the date range for date attribute in basic search

2020-07-21 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3900:
---
Attachment: (was: Screen Shot 2020-07-08 at 11.49.25 AM.png)

> UI: Allow user to select the date range for date attribute in basic search
> --
>
> Key: ATLAS-3900
> URL: https://issues.apache.org/jira/browse/ATLAS-3900
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3900-1.patch, ATLAS-3900.patch, Screen Shot 
> 2020-07-21 at 10.59.59 PM.png, Screen Shot 2020-07-21 at 11.00.08 PM.png, 
> Screen Shot 2020-07-21 at 11.00.15 PM.png
>
>
> In basic search attribute popup if the user selects the date type attribute 
> then UI should show a few quick search operator and custom range selection. 
> example:
> !Screen Shot 2020-07-08 at 11.49.25 AM.png|width=457,height=230!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3897) UI: Normalize list of propagated classifications

2020-07-21 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3897:
---
Attachment: ATLAS-3897-3.patch

> UI: Normalize list of propagated classifications
> 
>
> Key: ATLAS-3897
> URL: https://issues.apache.org/jira/browse/ATLAS-3897
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3897-1.patch, ATLAS-3897-2.patch, 
> ATLAS-3897-3.patch, ATLAS-3897.patch, Screen Shot 2020-07-17 at 6.13.04 PM.png
>
>
> When an entity has multiple instances of the same propagated classification 
> (e.g. via join of Hive tables), the lineage view will show each of them in 
> the list. The result may be a long list of classifications with identical 
> entries They don't seem to offer any additional information.
> I propose we normalize the list (think _uniq_ command in unix)
>  
> !Screen Shot 2020-07-17 at 6.13.04 PM.png|width=593,height=359!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3900) UI: Allow user to select the date range for date attribute in basic search

2020-07-21 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3900:
---
Attachment: ATLAS-3900-1.patch

> UI: Allow user to select the date range for date attribute in basic search
> --
>
> Key: ATLAS-3900
> URL: https://issues.apache.org/jira/browse/ATLAS-3900
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: ATLAS-3900-1.patch, ATLAS-3900.patch, Screen Shot 
> 2020-07-08 at 11.49.25 AM.png
>
>
> In basic search attribute popup if the user selects the date type attribute 
> then UI should show a few quick search operator and custom range selection. 
> example:
> !Screen Shot 2020-07-08 at 11.49.25 AM.png|width=457,height=230!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3900) UI: Allow user to select the date range for date attribute in basic search

2020-07-21 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3900:
---
Fix Version/s: 2.2.0
   3.0.0

> UI: Allow user to select the date range for date attribute in basic search
> --
>
> Key: ATLAS-3900
> URL: https://issues.apache.org/jira/browse/ATLAS-3900
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3900-1.patch, ATLAS-3900.patch, Screen Shot 
> 2020-07-08 at 11.49.25 AM.png
>
>
> In basic search attribute popup if the user selects the date type attribute 
> then UI should show a few quick search operator and custom range selection. 
> example:
> !Screen Shot 2020-07-08 at 11.49.25 AM.png|width=457,height=230!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3900) UI: Allow user to select the date range for date attribute in basic search

2020-07-21 Thread Keval Bhatt (Jira)


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

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

> UI: Allow user to select the date range for date attribute in basic search
> --
>
> Key: ATLAS-3900
> URL: https://issues.apache.org/jira/browse/ATLAS-3900
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: ATLAS-3900.patch, Screen Shot 2020-07-08 at 11.49.25 
> AM.png
>
>
> In basic search attribute popup if the user selects the date type attribute 
> then UI should show a few quick search operator and custom range selection. 
> example:
> !Screen Shot 2020-07-08 at 11.49.25 AM.png|width=457,height=230!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3900) UI: Allow user to select the date range for date attribute in basic search

2020-07-21 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3900:
---
Description: 
In basic search attribute popup if the user selects the date type attribute 
then UI should show a few quick search operator and custom range selection. 
example:

!Screen Shot 2020-07-08 at 11.49.25 AM.png|width=457,height=230!

  was:
In basic search attribute popup if the user selects the date type attribute 
then UI should show a few quick search operator and custom range selection.

!Screen Shot 2020-07-08 at 11.49.25 AM.png|width=457,height=230!


> UI: Allow user to select the date range for date attribute in basic search
> --
>
> Key: ATLAS-3900
> URL: https://issues.apache.org/jira/browse/ATLAS-3900
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: Screen Shot 2020-07-08 at 11.49.25 AM.png
>
>
> In basic search attribute popup if the user selects the date type attribute 
> then UI should show a few quick search operator and custom range selection. 
> example:
> !Screen Shot 2020-07-08 at 11.49.25 AM.png|width=457,height=230!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3900) UI: Allow user to select the date range for date attribute in basic search

2020-07-21 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3900:
---
Description: 
In basic search attribute popup if the user selects the date type attribute 
then UI should show a few quick search operator and custom range selection.

!Screen Shot 2020-07-08 at 11.49.25 AM.png|width=457,height=230!

> UI: Allow user to select the date range for date attribute in basic search
> --
>
> Key: ATLAS-3900
> URL: https://issues.apache.org/jira/browse/ATLAS-3900
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: Screen Shot 2020-07-08 at 11.49.25 AM.png
>
>
> In basic search attribute popup if the user selects the date type attribute 
> then UI should show a few quick search operator and custom range selection.
> !Screen Shot 2020-07-08 at 11.49.25 AM.png|width=457,height=230!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3900) UI: Allow user to select the date range for date attribute in basic search

2020-07-21 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3900:
---
Attachment: Screen Shot 2020-07-08 at 11.49.25 AM.png

> UI: Allow user to select the date range for date attribute in basic search
> --
>
> Key: ATLAS-3900
> URL: https://issues.apache.org/jira/browse/ATLAS-3900
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: Screen Shot 2020-07-08 at 11.49.25 AM.png
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3900) UI: Allow user to select the date range for date attribute in basic search

2020-07-21 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3900:
---
Summary: UI: Allow user to select the date range for date attribute in 
basic search  (was: UI: Allow user to select the date range or quick selection)

> UI: Allow user to select the date range for date attribute in basic search
> --
>
> Key: ATLAS-3900
> URL: https://issues.apache.org/jira/browse/ATLAS-3900
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ATLAS-3900) UI: Allow user to select the date range or quick selection

2020-07-21 Thread Keval Bhatt (Jira)
Keval Bhatt created ATLAS-3900:
--

 Summary: UI: Allow user to select the date range or quick selection
 Key: ATLAS-3900
 URL: https://issues.apache.org/jira/browse/ATLAS-3900
 Project: Atlas
  Issue Type: Sub-task
Reporter: Keval Bhatt
Assignee: Keval Bhatt






--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3897) UI: Normalize list of propagated classifications

2020-07-21 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3897:
---
Attachment: ATLAS-3897-2.patch

> UI: Normalize list of propagated classifications
> 
>
> Key: ATLAS-3897
> URL: https://issues.apache.org/jira/browse/ATLAS-3897
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3897-1.patch, ATLAS-3897-2.patch, 
> ATLAS-3897.patch, Screen Shot 2020-07-17 at 6.13.04 PM.png
>
>
> When an entity has multiple instances of the same propagated classification 
> (e.g. via join of Hive tables), the lineage view will show each of them in 
> the list. The result may be a long list of classifications with identical 
> entries They don't seem to offer any additional information.
> I propose we normalize the list (think _uniq_ command in unix)
>  
> !Screen Shot 2020-07-17 at 6.13.04 PM.png|width=593,height=359!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3894) UI: User is able to add and remove business metadata from deleted entities

2020-07-17 Thread Keval Bhatt (Jira)


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

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

> UI: User is able to add and remove business metadata from deleted entities
> --
>
> Key: ATLAS-3894
> URL: https://issues.apache.org/jira/browse/ATLAS-3894
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3894.patch
>
>
> User should not allow to add and remove the business metadata from the 
> deleted entity.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3894) UI: User is able to add and remove business metadata from deleted entities

2020-07-17 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3894:
---
Description: User should not allow to add and remove the 

> UI: User is able to add and remove business metadata from deleted entities
> --
>
> Key: ATLAS-3894
> URL: https://issues.apache.org/jira/browse/ATLAS-3894
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> User should not allow to add and remove the 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3894) UI: User is able to add and remove business metadata from deleted entities

2020-07-17 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3894:
---
Description: User should not allow to add and remove the business metadata 
from the deleted entity.  (was: User should not allow to add and remove the 
business metadata from deleted entity.)

> UI: User is able to add and remove business metadata from deleted entities
> --
>
> Key: ATLAS-3894
> URL: https://issues.apache.org/jira/browse/ATLAS-3894
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> User should not allow to add and remove the business metadata from the 
> deleted entity.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3894) UI: User is able to add and remove business metadata from deleted entities

2020-07-17 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3894:
---
Description: User should not allow to add and remove the business metadata 
from deleted entity.  (was: User should not allow to add and remove the )

> UI: User is able to add and remove business metadata from deleted entities
> --
>
> Key: ATLAS-3894
> URL: https://issues.apache.org/jira/browse/ATLAS-3894
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> User should not allow to add and remove the business metadata from deleted 
> entity.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3897) UI: Normalize list of propagated classifications

2020-07-17 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3897:
---
Attachment: ATLAS-3897-1.patch

> UI: Normalize list of propagated classifications
> 
>
> Key: ATLAS-3897
> URL: https://issues.apache.org/jira/browse/ATLAS-3897
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3897-1.patch, ATLAS-3897.patch, Screen Shot 
> 2020-07-17 at 6.13.04 PM.png
>
>
> When an entity has multiple instances of the same propagated classification 
> (e.g. via join of Hive tables), the lineage view will show each of them in 
> the list. The result may be a long list of classifications with identical 
> entries They don't seem to offer any additional information.
> I propose we normalize the list (think _uniq_ command in unix)
>  
> !Screen Shot 2020-07-17 at 6.13.04 PM.png|width=593,height=359!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3897) UI: Normalize list of propagated classifications

2020-07-17 Thread Keval Bhatt (Jira)


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

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

> UI: Normalize list of propagated classifications
> 
>
> Key: ATLAS-3897
> URL: https://issues.apache.org/jira/browse/ATLAS-3897
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3897.patch, Screen Shot 2020-07-17 at 6.13.04 
> PM.png
>
>
> When an entity has multiple instances of the same propagated classification 
> (e.g. via join of Hive tables), the lineage view will show each of them in 
> the list. The result may be a long list of classifications with identical 
> entries They don't seem to offer any additional information.
> I propose we normalize the list (think _uniq_ command in unix)
>  
> !Screen Shot 2020-07-17 at 6.13.04 PM.png|width=593,height=359!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3897) UI: Normalize list of propagated classifications

2020-07-17 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3897:
---
Attachment: Screen Shot 2020-07-17 at 6.13.04 PM.png

> UI: Normalize list of propagated classifications
> 
>
> Key: ATLAS-3897
> URL: https://issues.apache.org/jira/browse/ATLAS-3897
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: Screen Shot 2020-07-17 at 6.13.04 PM.png
>
>
> When an entity has multiple instances of the same propagated classification 
> (e.g. via join of Hive tables), the lineage view will show each of them in 
> the list. The result may be a long list of classifications with identical 
> entries They don't seem to offer any additional information.
> I propose we normalize the list (think _uniq_ command in unix)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3897) UI: Normalize list of propagated classifications

2020-07-17 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3897:
---
Description: 
When an entity has multiple instances of the same propagated classification 
(e.g. via join of Hive tables), the lineage view will show each of them in the 
list. The result may be a long list of classifications with identical entries 
They don't seem to offer any additional information.

I propose we normalize the list (think _uniq_ command in unix)

 

!Screen Shot 2020-07-17 at 6.13.04 PM.png!

  was:
When an entity has multiple instances of the same propagated classification 
(e.g. via join of Hive tables), the lineage view will show each of them in the 
list. The result may be a long list of classifications with identical entries 
They don't seem to offer any additional information.

I propose we normalize the list (think _uniq_ command in unix)


> UI: Normalize list of propagated classifications
> 
>
> Key: ATLAS-3897
> URL: https://issues.apache.org/jira/browse/ATLAS-3897
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: Screen Shot 2020-07-17 at 6.13.04 PM.png
>
>
> When an entity has multiple instances of the same propagated classification 
> (e.g. via join of Hive tables), the lineage view will show each of them in 
> the list. The result may be a long list of classifications with identical 
> entries They don't seem to offer any additional information.
> I propose we normalize the list (think _uniq_ command in unix)
>  
> !Screen Shot 2020-07-17 at 6.13.04 PM.png!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3897) UI: Normalize list of propagated classifications

2020-07-17 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3897:
---
Description: 
When an entity has multiple instances of the same propagated classification 
(e.g. via join of Hive tables), the lineage view will show each of them in the 
list. The result may be a long list of classifications with identical entries 
They don't seem to offer any additional information.

I propose we normalize the list (think _uniq_ command in unix)

 

!Screen Shot 2020-07-17 at 6.13.04 PM.png|width=593,height=359!

  was:
When an entity has multiple instances of the same propagated classification 
(e.g. via join of Hive tables), the lineage view will show each of them in the 
list. The result may be a long list of classifications with identical entries 
They don't seem to offer any additional information.

I propose we normalize the list (think _uniq_ command in unix)

 

!Screen Shot 2020-07-17 at 6.13.04 PM.png!


> UI: Normalize list of propagated classifications
> 
>
> Key: ATLAS-3897
> URL: https://issues.apache.org/jira/browse/ATLAS-3897
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: Screen Shot 2020-07-17 at 6.13.04 PM.png
>
>
> When an entity has multiple instances of the same propagated classification 
> (e.g. via join of Hive tables), the lineage view will show each of them in 
> the list. The result may be a long list of classifications with identical 
> entries They don't seem to offer any additional information.
> I propose we normalize the list (think _uniq_ command in unix)
>  
> !Screen Shot 2020-07-17 at 6.13.04 PM.png|width=593,height=359!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ATLAS-3897) UI: Normalize list of propagated classifications

2020-07-17 Thread Keval Bhatt (Jira)
Keval Bhatt created ATLAS-3897:
--

 Summary: UI: Normalize list of propagated classifications
 Key: ATLAS-3897
 URL: https://issues.apache.org/jira/browse/ATLAS-3897
 Project: Atlas
  Issue Type: Bug
Reporter: Keval Bhatt
Assignee: Keval Bhatt
 Fix For: 3.0.0, 2.2.0


When an entity has multiple instances of the same propagated classification 
(e.g. via join of Hive tables), the lineage view will show each of them in the 
list. The result may be a long list of classifications with identical entries 
They don't seem to offer any additional information.

I propose we normalize the list (think _uniq_ command in unix)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (ATLAS-3743) [Business Metadata] Multiple issues in Audits tab w.r.t. Entity-Business Metadata attributes

2020-07-16 Thread Keval Bhatt (Jira)


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

Keval Bhatt resolved ATLAS-3743.

Resolution: Fixed

> [Business Metadata] Multiple issues in Audits tab w.r.t. Entity-Business 
> Metadata attributes
> 
>
> Key: ATLAS-3743
> URL: https://issues.apache.org/jira/browse/ATLAS-3743
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Critical
> Fix For: 3.0.0, 2.1.0
>
> Attachments: Screenshot 2020-04-20 at 8.53.54 PM.png, Screenshot 
> 2020-04-20 at 8.54.12 PM.png
>
>
>  Following are the issues observed:
>  # All the BM related operations on an entity are listed as 
> BUSINESS_ATTRIBUTE_UPDATE only. Right now, BUSINESS_ATTRIBUTE_UPDATE shows up 
> for all the operations.
>  ## When a BM attribute is added for the first time, ideally 
> BUSINESS_ATTRIBUTE_ADD action should show up.
>  ## On the same lines, when all the BM attributes are removed from entity, 
> BUSINESS_ATTRIBUTE_DELETE should show up.  
>  # Internal name, BUSINESS_ATTRIBUTE_UPDATE, is listed as action, instead of 
> plain text like "Business Attribute(s) Updated"
>  # Date type value is shown as timestamp instead of date, in audit/technical 
> properties. 
> Attached screenshots.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (ATLAS-3743) [Business Metadata] Multiple issues in Audits tab w.r.t. Entity-Business Metadata attributes

2020-07-16 Thread Keval Bhatt (Jira)


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

Keval Bhatt reassigned ATLAS-3743:
--

Assignee: Keval Bhatt

> [Business Metadata] Multiple issues in Audits tab w.r.t. Entity-Business 
> Metadata attributes
> 
>
> Key: ATLAS-3743
> URL: https://issues.apache.org/jira/browse/ATLAS-3743
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: Screenshot 2020-04-20 at 8.53.54 PM.png, Screenshot 
> 2020-04-20 at 8.54.12 PM.png
>
>
>  Following are the issues observed:
>  # All the BM related operations on an entity are listed as 
> BUSINESS_ATTRIBUTE_UPDATE only. Right now, BUSINESS_ATTRIBUTE_UPDATE shows up 
> for all the operations.
>  ## When a BM attribute is added for the first time, ideally 
> BUSINESS_ATTRIBUTE_ADD action should show up.
>  ## On the same lines, when all the BM attributes are removed from entity, 
> BUSINESS_ATTRIBUTE_DELETE should show up.  
>  # Internal name, BUSINESS_ATTRIBUTE_UPDATE, is listed as action, instead of 
> plain text like "Business Attribute(s) Updated"
>  # Date type value is shown as timestamp instead of date, in audit/technical 
> properties. 
> Attached screenshots.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3743) [Business Metadata] Multiple issues in Audits tab w.r.t. Entity-Business Metadata attributes

2020-07-16 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3743:
---
Fix Version/s: 2.1.0
   3.0.0

> [Business Metadata] Multiple issues in Audits tab w.r.t. Entity-Business 
> Metadata attributes
> 
>
> Key: ATLAS-3743
> URL: https://issues.apache.org/jira/browse/ATLAS-3743
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Reporter: Umesh Padashetty
>Assignee: Keval Bhatt
>Priority: Critical
> Fix For: 2.1.0, 3.0.0
>
> Attachments: Screenshot 2020-04-20 at 8.53.54 PM.png, Screenshot 
> 2020-04-20 at 8.54.12 PM.png
>
>
>  Following are the issues observed:
>  # All the BM related operations on an entity are listed as 
> BUSINESS_ATTRIBUTE_UPDATE only. Right now, BUSINESS_ATTRIBUTE_UPDATE shows up 
> for all the operations.
>  ## When a BM attribute is added for the first time, ideally 
> BUSINESS_ATTRIBUTE_ADD action should show up.
>  ## On the same lines, when all the BM attributes are removed from entity, 
> BUSINESS_ATTRIBUTE_DELETE should show up.  
>  # Internal name, BUSINESS_ATTRIBUTE_UPDATE, is listed as action, instead of 
> plain text like "Business Attribute(s) Updated"
>  # Date type value is shown as timestamp instead of date, in audit/technical 
> properties. 
> Attached screenshots.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3896) Doc build not working when we run mvn clean site

2020-07-16 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3896:
---
Fix Version/s: (was: 2.2.0)

> Doc build not working when we run mvn clean site
> 
>
> Key: ATLAS-3896
> URL: https://issues.apache.org/jira/browse/ATLAS-3896
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (ATLAS-3896) Doc build not working when we run mvn clean site

2020-07-16 Thread Keval Bhatt (Jira)


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

Keval Bhatt resolved ATLAS-3896.

Resolution: Duplicate

> Doc build not working when we run mvn clean site
> 
>
> Key: ATLAS-3896
> URL: https://issues.apache.org/jira/browse/ATLAS-3896
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ATLAS-3896) Doc build not working when we run mvn clean site

2020-07-16 Thread Keval Bhatt (Jira)
Keval Bhatt created ATLAS-3896:
--

 Summary: Doc build not working when we run mvn clean site
 Key: ATLAS-3896
 URL: https://issues.apache.org/jira/browse/ATLAS-3896
 Project: Atlas
  Issue Type: Bug
Reporter: Keval Bhatt
Assignee: Keval Bhatt
 Fix For: 3.0.0, 2.2.0






--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3894) UI: User is able to add and remove business metadata from deleted entities

2020-07-16 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3894:
---
Fix Version/s: 2.2.0

> UI: User is able to add and remove business metadata from deleted entities
> --
>
> Key: ATLAS-3894
> URL: https://issues.apache.org/jira/browse/ATLAS-3894
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ATLAS-3894) UI: User is able to add and remove business metadata from deleted entities

2020-07-15 Thread Keval Bhatt (Jira)
Keval Bhatt created ATLAS-3894:
--

 Summary: UI: User is able to add and remove business metadata from 
deleted entities
 Key: ATLAS-3894
 URL: https://issues.apache.org/jira/browse/ATLAS-3894
 Project: Atlas
  Issue Type: Bug
Affects Versions: 3.0.0
Reporter: Keval Bhatt
Assignee: Keval Bhatt
 Fix For: 3.0.0






--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (ATLAS-3887) Consistency and highlighting issues while switching between old and new UI

2020-07-14 Thread Keval Bhatt (Jira)


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

Keval Bhatt reassigned ATLAS-3887:
--

Assignee: Keval Bhatt

> Consistency and highlighting issues while switching between old and new UI
> --
>
> Key: ATLAS-3887
> URL: https://issues.apache.org/jira/browse/ATLAS-3887
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Durga Kadam
>Assignee: Keval Bhatt
>Priority: Minor
> Attachments: classification and glossari does not highlight also 
> glossary does not show title when switched to new UI.mkv
>
>
> Description::
> When switched from old to new UI,
>  # Classification and Glossary does not highlight the content, also
>  # Glossary does not show the title. 
> PFA video



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3891) UI: Quick search cards for ease of search and utilization of white space

2020-07-14 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3891:
---
Attachment: search_dashboard_roun...@2x.png

> UI: Quick search cards for ease of search and utilization of white space
> 
>
> Key: ATLAS-3891
> URL: https://issues.apache.org/jira/browse/ATLAS-3891
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: search_dashboard_roun...@2x.png
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3891) UI: Quick search cards for ease of search and utilization of white space

2020-07-14 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3891:
---
Description: 
Example:

 

!search_dashboard_roun...@2x.png|width=591,height=332!

> UI: Quick search cards for ease of search and utilization of white space
> 
>
> Key: ATLAS-3891
> URL: https://issues.apache.org/jira/browse/ATLAS-3891
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: search_dashboard_roun...@2x.png
>
>
> Example:
>  
> !search_dashboard_roun...@2x.png|width=591,height=332!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3891) UI: Quick search cards for ease of search and utilization of white space

2020-07-14 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3891:
---
Summary: UI: Quick search cards for ease of search and utilization of white 
space  (was: UI: Quick search box for easy of search and utilize of white space)

> UI: Quick search cards for ease of search and utilization of white space
> 
>
> Key: ATLAS-3891
> URL: https://issues.apache.org/jira/browse/ATLAS-3891
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ATLAS-3891) UI: Quick search box for easy of search and utilize of white space

2020-07-14 Thread Keval Bhatt (Jira)
Keval Bhatt created ATLAS-3891:
--

 Summary: UI: Quick search box for easy of search and utilize of 
white space
 Key: ATLAS-3891
 URL: https://issues.apache.org/jira/browse/ATLAS-3891
 Project: Atlas
  Issue Type: Improvement
Affects Versions: 3.0.0
Reporter: Keval Bhatt
Assignee: Keval Bhatt
 Fix For: 3.0.0






--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3882) Classic UI: Loader not disappearing while assigning category to term

2020-07-08 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3882:
---
Affects Version/s: 2.0.0

> Classic UI: Loader not disappearing while assigning category to term 
> -
>
> Key: ATLAS-3882
> URL: https://issues.apache.org/jira/browse/ATLAS-3882
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3882.patch, Screen Shot 2020-07-07 at 3.18.20 
> PM.png
>
>
> Steps to reproduce this issue.
>  
>  # Go to classic UI
>  # Click on Glossary tab
>  # Create term if not exist and click on it
>  # Click on + button of Categories: from the righthand side view of the term 
> detail page.
>  # The popup will be visible with loader.
>  
> !Screen Shot 2020-07-07 at 3.18.20 PM.png|width=579,height=248!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3882) Classic UI: Loader not disappearing while assigning category to term

2020-07-08 Thread Keval Bhatt (Jira)


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

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

> Classic UI: Loader not disappearing while assigning category to term 
> -
>
> Key: ATLAS-3882
> URL: https://issues.apache.org/jira/browse/ATLAS-3882
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.0.0
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3882.patch, Screen Shot 2020-07-07 at 3.18.20 
> PM.png
>
>
> Steps to reproduce this issue.
>  
>  # Go to classic UI
>  # Click on Glossary tab
>  # Create term if not exist and click on it
>  # Click on + button of Categories: from the righthand side view of the term 
> detail page.
>  # The popup will be visible with loader.
>  
> !Screen Shot 2020-07-07 at 3.18.20 PM.png|width=579,height=248!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (ATLAS-3884) Unable to access Apache Atlas UI http://localhost:21000

2020-07-08 Thread Keval Bhatt (Jira)


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

Keval Bhatt commented on ATLAS-3884:


[~Vidyats] 

Can you export these two variables and try to restart atlas.

{code:java}
export MANAGE_LOCAL_HBASE=True
export MANAGE_LOCAL_SOLR=True
{code}


> Unable to access Apache Atlas UI http://localhost:21000
> ---
>
> Key: ATLAS-3884
> URL: https://issues.apache.org/jira/browse/ATLAS-3884
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.0.0
> Environment: RHEL
>Reporter: Vidya
>Priority: Major
>
> Hi,I have installed and ran Apache Atlas with embedded Apache HBase & Apache 
> Solr.After bin/atlas_start.py command I see apache atlas started message and 
> I could grep Atlas,Hbase and Solr process.However,when I do `curl -u 
> admin:admin http://localhost:21000/api/atlas/admin/version`, I am getting 
> below error
> ```
> 
> 
> 
> Error 503 
> 
> 
> HTTP ERROR: 503
> Problem accessing /api/atlas/admin/version. Reason:
>  Service Unavailable
> http://eclipse.org/jetty;>Powered by Jetty:// 
> 9.3.14.v20161028
> 
> 
> ```
> I am getting below error in application logs.
> ```
> Caused by: org.apache.solr.common.SolrException: Cannot connect to cluster at 
> localhost:2181: cluster not found/not ready
>  at 
> org.apache.solr.common.cloud.ZkStateReader.createClusterStateWatchersAndUpdate(ZkStateReader.java:385)
>  at 
> org.apache.solr.client.solrj.impl.ZkClientClusterStateProvider.connect(ZkClientClusterStateProvider.java:141)
>  at 
> org.apache.solr.client.solrj.impl.CloudSolrClient.connect(CloudSolrClient.java:383)
>  at org.janusgraph.diskstorage.solr.Solr6Index.(Solr6Index.java:218)
>  ... 101 more 
> ```



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Comment Edited] (ATLAS-3884) Unable to access Apache Atlas UI http://localhost:21000

2020-07-08 Thread Keval Bhatt (Jira)


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

Keval Bhatt edited comment on ATLAS-3884 at 7/8/20, 11:06 AM:
--

[~Vidyats]

Can you export these two variables and restart atlas.
{code:java}
export MANAGE_LOCAL_HBASE=True
export MANAGE_LOCAL_SOLR=True
{code}


was (Author: kevalbhatt18):
[~Vidyats] 

Can you export these two variables and try to restart atlas.

{code:java}
export MANAGE_LOCAL_HBASE=True
export MANAGE_LOCAL_SOLR=True
{code}


> Unable to access Apache Atlas UI http://localhost:21000
> ---
>
> Key: ATLAS-3884
> URL: https://issues.apache.org/jira/browse/ATLAS-3884
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.0.0
> Environment: RHEL
>Reporter: Vidya
>Priority: Major
>
> Hi,I have installed and ran Apache Atlas with embedded Apache HBase & Apache 
> Solr.After bin/atlas_start.py command I see apache atlas started message and 
> I could grep Atlas,Hbase and Solr process.However,when I do `curl -u 
> admin:admin http://localhost:21000/api/atlas/admin/version`, I am getting 
> below error
> ```
> 
> 
> 
> Error 503 
> 
> 
> HTTP ERROR: 503
> Problem accessing /api/atlas/admin/version. Reason:
>  Service Unavailable
> http://eclipse.org/jetty;>Powered by Jetty:// 
> 9.3.14.v20161028
> 
> 
> ```
> I am getting below error in application logs.
> ```
> Caused by: org.apache.solr.common.SolrException: Cannot connect to cluster at 
> localhost:2181: cluster not found/not ready
>  at 
> org.apache.solr.common.cloud.ZkStateReader.createClusterStateWatchersAndUpdate(ZkStateReader.java:385)
>  at 
> org.apache.solr.client.solrj.impl.ZkClientClusterStateProvider.connect(ZkClientClusterStateProvider.java:141)
>  at 
> org.apache.solr.client.solrj.impl.CloudSolrClient.connect(CloudSolrClient.java:383)
>  at org.janusgraph.diskstorage.solr.Solr6Index.(Solr6Index.java:218)
>  ... 101 more 
> ```



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3882) Classic UI: Loader not disappearing while assigning category to term

2020-07-08 Thread Keval Bhatt (Jira)


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

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

> Classic UI: Loader not disappearing while assigning category to term 
> -
>
> Key: ATLAS-3882
> URL: https://issues.apache.org/jira/browse/ATLAS-3882
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3882.patch, Screen Shot 2020-07-07 at 3.18.20 
> PM.png
>
>
> Steps to reproduce this issue.
>  
>  # Go to classic UI
>  # Click on Glossary tab
>  # Create term if not exist and click on it
>  # Click on + button of Categories: from the righthand side view of the term 
> detail page.
>  # The popup will be visible with loader.
>  
> !Screen Shot 2020-07-07 at 3.18.20 PM.png|width=579,height=248!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (ATLAS-3882) Classic UI: Loader not disappearing while assigning category to term

2020-07-08 Thread Keval Bhatt (Jira)


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

Keval Bhatt updated ATLAS-3882:
---
Summary: Classic UI: Loader not disappearing while assigning category to 
term   (was: Classic UI: Loader not disappearing whie assigning category to 
term )

> Classic UI: Loader not disappearing while assigning category to term 
> -
>
> Key: ATLAS-3882
> URL: https://issues.apache.org/jira/browse/ATLAS-3882
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: Screen Shot 2020-07-07 at 3.18.20 PM.png
>
>
> Steps to reproduce this issue.
>  
>  # Go to classic UI
>  # Click on Glossary tab
>  # Create term if not exist and click on it
>  # Click on + button of Categories: from the righthand side view of the term 
> detail page.
>  # The popup will be visible with loader.
>  
> !Screen Shot 2020-07-07 at 3.18.20 PM.png|width=579,height=248!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (ATLAS-3882) Classic UI: Loader not disappearing whie assigning category to term

2020-07-08 Thread Keval Bhatt (Jira)
Keval Bhatt created ATLAS-3882:
--

 Summary: Classic UI: Loader not disappearing whie assigning 
category to term 
 Key: ATLAS-3882
 URL: https://issues.apache.org/jira/browse/ATLAS-3882
 Project: Atlas
  Issue Type: Bug
Reporter: Keval Bhatt
Assignee: Keval Bhatt
 Fix For: 2.1.0, 3.0.0
 Attachments: Screen Shot 2020-07-07 at 3.18.20 PM.png

Steps to reproduce this issue.

 
 # Go to classic UI
 # Click on Glossary tab
 # Create term if not exist and click on it
 # Click on + button of Categories: from the righthand side view of the term 
detail page.
 # The popup will be visible with loader.

 

!Screen Shot 2020-07-07 at 3.18.20 PM.png|width=579,height=248!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Comment Edited] (ATLAS-3819) Modernize client side technology stack

2020-07-07 Thread Keval Bhatt (Jira)


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

Keval Bhatt edited comment on ATLAS-3819 at 7/8/20, 5:47 AM:
-

[~Koncz] I think one more improvement you can add for proxy. which is the use 
of webpack-dev-server proxy instead of express node server.

[https://webpack.js.org/configuration/dev-server/#devserverproxy]


was (Author: kevalbhatt18):
[~Koncz] I think one more improvement you can do for proxy.

Instead of creating express node server why do you use the proxy which is 
already handled by webpack-dev-server.

[https://webpack.js.org/configuration/dev-server/#devserverproxy]

> Modernize client side technology stack
> --
>
> Key: ATLAS-3819
> URL: https://issues.apache.org/jira/browse/ATLAS-3819
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Affects Versions: 3.0.0
>Reporter: Csaba Koncz
>Priority: Major
> Attachments: image-2020-07-04-16-42-10-643.png
>
>
> While RequireJS has its merits and advantages, it might be worth considering 
> replacing it with another technology.
> A bundle loader like Webpack would open up a number of possibilities:
> - use of ES6 modules, which immediately improves tooling support
> - use TypeScript, which improves tooling support even more
> - a manageable code base would enable refactoring of the JavaScript code so 
> that no logic happens in the module initialization code,
> which in turn would make it possible to write tests for the JavaScript logic.
> As a POC I created a NodeJS project that transforms the current dashboardv2 
> code into Webpack bundles and demonstrates
> that the UI is able to work without RequireJS.
> Right now the JavaScript sources and index.html are used unchanged,
> but the next step would be to start converting the source to ES6 modules.
> Here is the code: https://github.com/csabakoncz/atlas-newui
> The most important file there is `webpack.config.js` that takes over the role 
> of RequireJS.config.
> The other file of interest might be `src/index.ts` which demonstrates the 
> ability to use TypeScript code even now.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (ATLAS-3819) Modernize client side technology stack

2020-07-07 Thread Keval Bhatt (Jira)


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

Keval Bhatt commented on ATLAS-3819:


[~Koncz] I think one more improvement you can do for proxy.

Instead of creating express node server why do you use the proxy which is 
already handled by webpack-dev-server.

[https://webpack.js.org/configuration/dev-server/#devserverproxy]

> Modernize client side technology stack
> --
>
> Key: ATLAS-3819
> URL: https://issues.apache.org/jira/browse/ATLAS-3819
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Affects Versions: 3.0.0
>Reporter: Csaba Koncz
>Priority: Major
> Attachments: image-2020-07-04-16-42-10-643.png
>
>
> While RequireJS has its merits and advantages, it might be worth considering 
> replacing it with another technology.
> A bundle loader like Webpack would open up a number of possibilities:
> - use of ES6 modules, which immediately improves tooling support
> - use TypeScript, which improves tooling support even more
> - a manageable code base would enable refactoring of the JavaScript code so 
> that no logic happens in the module initialization code,
> which in turn would make it possible to write tests for the JavaScript logic.
> As a POC I created a NodeJS project that transforms the current dashboardv2 
> code into Webpack bundles and demonstrates
> that the UI is able to work without RequireJS.
> Right now the JavaScript sources and index.html are used unchanged,
> but the next step would be to start converting the source to ES6 modules.
> Here is the code: https://github.com/csabakoncz/atlas-newui
> The most important file there is `webpack.config.js` that takes over the role 
> of RequireJS.config.
> The other file of interest might be `src/index.ts` which demonstrates the 
> ability to use TypeScript code even now.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (ATLAS-3819) Modernize client side technology stack

2020-07-06 Thread Keval Bhatt (Jira)


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

Keval Bhatt commented on ATLAS-3819:


[~Koncz] I found that you are using webpack-dev-server and node server as well, 
is there any specific reason?

> Modernize client side technology stack
> --
>
> Key: ATLAS-3819
> URL: https://issues.apache.org/jira/browse/ATLAS-3819
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Affects Versions: 3.0.0
>Reporter: Csaba Koncz
>Priority: Major
> Attachments: image-2020-07-04-16-42-10-643.png
>
>
> While RequireJS has its merits and advantages, it might be worth considering 
> replacing it with another technology.
> A bundle loader like Webpack would open up a number of possibilities:
> - use of ES6 modules, which immediately improves tooling support
> - use TypeScript, which improves tooling support even more
> - a manageable code base would enable refactoring of the JavaScript code so 
> that no logic happens in the module initialization code,
> which in turn would make it possible to write tests for the JavaScript logic.
> As a POC I created a NodeJS project that transforms the current dashboardv2 
> code into Webpack bundles and demonstrates
> that the UI is able to work without RequireJS.
> Right now the JavaScript sources and index.html are used unchanged,
> but the next step would be to start converting the source to ES6 modules.
> Here is the code: https://github.com/csabakoncz/atlas-newui
> The most important file there is `webpack.config.js` that takes over the role 
> of RequireJS.config.
> The other file of interest might be `src/index.ts` which demonstrates the 
> ability to use TypeScript code even now.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Comment Edited] (ATLAS-3819) Modernize client side technology stack

2020-07-06 Thread Keval Bhatt (Jira)


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

Keval Bhatt edited comment on ATLAS-3819 at 7/6/20, 6:02 AM:
-

[~Koncz] thanks for coming up with the improvement.

I have checked the repo -> [https://github.com/csabakoncz/atlas-newui 
|https://github.com/csabakoncz/atlas-newui] and have few questions:

can we use webpack-dev-server instead of creating an express node server 
because we need a server only for development.

Do we need typescript loader for atlas code? 
We can use babel-loader for es6 which can easily be used in the current atlas 
code.


was (Author: kevalbhatt18):
[~Koncz] thanks for coming up with the improvement.

I have checked the repo -> [https://github.com/csabakoncz/atlas-newui 
|https://github.com/csabakoncz/atlas-newui] and have few questions:

can we use webpack-dev-server instead of creating an express node server 
because we need a server only for development.

Do we need typescript loader for atlas code? for backbone, we are using plain 
javascript. we can use babel-loader for es6.

> Modernize client side technology stack
> --
>
> Key: ATLAS-3819
> URL: https://issues.apache.org/jira/browse/ATLAS-3819
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Affects Versions: 3.0.0
>Reporter: Csaba Koncz
>Priority: Major
> Attachments: image-2020-07-04-16-42-10-643.png
>
>
> While RequireJS has its merits and advantages, it might be worth considering 
> replacing it with another technology.
> A bundle loader like Webpack would open up a number of possibilities:
> - use of ES6 modules, which immediately improves tooling support
> - use TypeScript, which improves tooling support even more
> - a manageable code base would enable refactoring of the JavaScript code so 
> that no logic happens in the module initialization code,
> which in turn would make it possible to write tests for the JavaScript logic.
> As a POC I created a NodeJS project that transforms the current dashboardv2 
> code into Webpack bundles and demonstrates
> that the UI is able to work without RequireJS.
> Right now the JavaScript sources and index.html are used unchanged,
> but the next step would be to start converting the source to ES6 modules.
> Here is the code: https://github.com/csabakoncz/atlas-newui
> The most important file there is `webpack.config.js` that takes over the role 
> of RequireJS.config.
> The other file of interest might be `src/index.ts` which demonstrates the 
> ability to use TypeScript code even now.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


  1   2   3   4   5   6   7   8   9   10   >