Re: Review Request 72474: ATLAS-3783 : DSL query search should return results for both the relationship edge directions

[Sarath Subramanian]

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


Fix it, then Ship it!





repository/src/main/java/org/apache/atlas/query/RegistryBasedLookup.java
Lines 127 (patched)


consider renaming the variable:

et => entityType
ret => attribute
direction => ret (return value should be ret to avoid confusion)


- Sarath Subramanian


On May 12, 2020, 6:11 a.m., chaitali wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72474/
> ---
> 
> (Updated May 12, 2020, 6:11 a.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Nikhil Bonte, Nixon Rodrigues, and 
> Sarath Subramanian.
> 
> 
> Bugs: ATLAS-3783
> https://issues.apache.org/jira/browse/ATLAS-3783
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Unable to get results for Dsl query eg;hive_column where 
> table.name="employee".
> Due to regression only one edge direction was giving results.
> This patch gives a fix for results for both relationship edge direction 
> queries.
> 
> 
> Diffs
> -
> 
>   repository/src/main/java/org/apache/atlas/query/GremlinQueryComposer.java 
> 04b177533 
>   repository/src/main/java/org/apache/atlas/query/IdentifierHelper.java 
> 6ab61e16b 
>   repository/src/main/java/org/apache/atlas/query/Lookup.java 3c192d824 
>   repository/src/main/java/org/apache/atlas/query/RegistryBasedLookup.java 
> 2b34abff8 
>   repository/src/test/java/org/apache/atlas/query/DSLQueriesTest.java 
> 0bbff2f46 
>   
> repository/src/test/java/org/apache/atlas/query/GremlinQueryComposerTest.java 
> 6f4df88f0 
> 
> 
> Diff: https://reviews.apache.org/r/72474/diff/9/
> 
> 
> Testing
> ---
> 
> TestCases added.
> 
> 
> Thanks,
> 
> chaitali
> 
>

Re: Review Request 72474: ATLAS-3783 : DSL query search should return results for both the relationship edge directions

[chaitali]

> On May 11, 2020, 6:02 p.m., Sarath Subramanian wrote:
> > repository/src/main/java/org/apache/atlas/query/GremlinQueryComposer.java
> > Lines 591 (patched)
> > 
> >
> > same here. remove if/else condition
> 
> chaitali wrote:
> Here in Gremlin composer if we are receiving relationshipedgedirection 
> for the First edge when it comes to this IF condition where the logic is if 
> (direction is "IN" then set GremlinClause as "IN".
> and if direction is "OUT" then set GremlinClause as "OUT".)Hence am 
> executing it twice.

Removed repetitive if/else


- chaitali


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


On May 12, 2020, 1:11 p.m., chaitali wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72474/
> ---
> 
> (Updated May 12, 2020, 1:11 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Nikhil Bonte, Nixon Rodrigues, and 
> Sarath Subramanian.
> 
> 
> Bugs: ATLAS-3783
> https://issues.apache.org/jira/browse/ATLAS-3783
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Unable to get results for Dsl query eg;hive_column where 
> table.name="employee".
> Due to regression only one edge direction was giving results.
> This patch gives a fix for results for both relationship edge direction 
> queries.
> 
> 
> Diffs
> -
> 
>   repository/src/main/java/org/apache/atlas/query/GremlinQueryComposer.java 
> 04b177533 
>   repository/src/main/java/org/apache/atlas/query/IdentifierHelper.java 
> 6ab61e16b 
>   repository/src/main/java/org/apache/atlas/query/Lookup.java 3c192d824 
>   repository/src/main/java/org/apache/atlas/query/RegistryBasedLookup.java 
> 2b34abff8 
>   repository/src/test/java/org/apache/atlas/query/DSLQueriesTest.java 
> 0bbff2f46 
>   
> repository/src/test/java/org/apache/atlas/query/GremlinQueryComposerTest.java 
> 6f4df88f0 
> 
> 
> Diff: https://reviews.apache.org/r/72474/diff/9/
> 
> 
> Testing
> ---
> 
> TestCases added.
> 
> 
> Thanks,
> 
> chaitali
> 
>

Re: Review Request 72474: ATLAS-3783 : DSL query search should return results for both the relationship edge directions

[chaitali]

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

(Updated May 12, 2020, 1:11 p.m.)


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


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


Repository: atlas


Description
---

Unable to get results for Dsl query eg;hive_column where table.name="employee".
Due to regression only one edge direction was giving results.
This patch gives a fix for results for both relationship edge direction queries.


Diffs (updated)
-

  repository/src/main/java/org/apache/atlas/query/GremlinQueryComposer.java 
04b177533 
  repository/src/main/java/org/apache/atlas/query/IdentifierHelper.java 
6ab61e16b 
  repository/src/main/java/org/apache/atlas/query/Lookup.java 3c192d824 
  repository/src/main/java/org/apache/atlas/query/RegistryBasedLookup.java 
2b34abff8 
  repository/src/test/java/org/apache/atlas/query/DSLQueriesTest.java 0bbff2f46 
  repository/src/test/java/org/apache/atlas/query/GremlinQueryComposerTest.java 
6f4df88f0 


Diff: https://reviews.apache.org/r/72474/diff/9/

Changes: https://reviews.apache.org/r/72474/diff/8-9/


Testing
---

TestCases added.


Thanks,

chaitali

Re: Review Request 72474: ATLAS-3783 : DSL query search should return results for both the relationship edge directions

[chaitali]

> On May 11, 2020, 6:02 p.m., Sarath Subramanian wrote:
> > repository/src/main/java/org/apache/atlas/query/GremlinQueryComposer.java
> > Lines 220 (patched)
> > 
> >
> > both if and else condition executes the same statement. please review.

Here in Gremlin composer if we are receiving relationshipedgedirection for the 
second edge when it comes to this IF condition then the logic is if (direction 
is "IN" then set GremlinClause as "OUT".
and if direction is "OUT" then set GremlinClause as "IN".)Hence am executing it 
twice.


> On May 11, 2020, 6:02 p.m., Sarath Subramanian wrote:
> > repository/src/main/java/org/apache/atlas/query/GremlinQueryComposer.java
> > Lines 591 (patched)
> > 
> >
> > same here. remove if/else condition

Here in Gremlin composer if we are receiving relationshipedgedirection for the 
First edge when it comes to this IF condition where the logic is if (direction 
is "IN" then set GremlinClause as "IN".
and if direction is "OUT" then set GremlinClause as "OUT".)Hence am executing 
it twice.


- chaitali


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


On May 11, 2020, 5:56 p.m., chaitali wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72474/
> ---
> 
> (Updated May 11, 2020, 5:56 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Nikhil Bonte, Nixon Rodrigues, and 
> Sarath Subramanian.
> 
> 
> Bugs: ATLAS-3783
> https://issues.apache.org/jira/browse/ATLAS-3783
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Unable to get results for Dsl query eg;hive_column where 
> table.name="employee".
> Due to regression only one edge direction was giving results.
> This patch gives a fix for results for both relationship edge direction 
> queries.
> 
> 
> Diffs
> -
> 
>   repository/src/main/java/org/apache/atlas/query/GremlinQueryComposer.java 
> 04b177533 
>   repository/src/main/java/org/apache/atlas/query/IdentifierHelper.java 
> 6ab61e16b 
>   repository/src/main/java/org/apache/atlas/query/Lookup.java 3c192d824 
>   repository/src/main/java/org/apache/atlas/query/RegistryBasedLookup.java 
> 2b34abff8 
>   repository/src/test/java/org/apache/atlas/query/DSLQueriesTest.java 
> 0bbff2f46 
>   
> repository/src/test/java/org/apache/atlas/query/GremlinQueryComposerTest.java 
> 6f4df88f0 
> 
> 
> Diff: https://reviews.apache.org/r/72474/diff/8/
> 
> 
> Testing
> ---
> 
> TestCases added.
> 
> 
> Thanks,
> 
> chaitali
> 
>

Re: Review Request 72474: ATLAS-3783 : DSL query search should return results for both the relationship edge directions

[chaitali]

> On May 11, 2020, 5:48 p.m., Ashutosh Mestry wrote:
> > repository/src/main/java/org/apache/atlas/query/GremlinQueryComposer.java
> > Line 578 (original), 584 (patched)
> > 
> >
> > Duplicate code.

Kindly refer to last two replies for Sarath's comments :both if and else 
condition executes the same statement. please review & same here. remove 
if/else condition


- chaitali


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


On May 11, 2020, 5:56 p.m., chaitali wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72474/
> ---
> 
> (Updated May 11, 2020, 5:56 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Nikhil Bonte, Nixon Rodrigues, and 
> Sarath Subramanian.
> 
> 
> Bugs: ATLAS-3783
> https://issues.apache.org/jira/browse/ATLAS-3783
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Unable to get results for Dsl query eg;hive_column where 
> table.name="employee".
> Due to regression only one edge direction was giving results.
> This patch gives a fix for results for both relationship edge direction 
> queries.
> 
> 
> Diffs
> -
> 
>   repository/src/main/java/org/apache/atlas/query/GremlinQueryComposer.java 
> 04b177533 
>   repository/src/main/java/org/apache/atlas/query/IdentifierHelper.java 
> 6ab61e16b 
>   repository/src/main/java/org/apache/atlas/query/Lookup.java 3c192d824 
>   repository/src/main/java/org/apache/atlas/query/RegistryBasedLookup.java 
> 2b34abff8 
>   repository/src/test/java/org/apache/atlas/query/DSLQueriesTest.java 
> 0bbff2f46 
>   
> repository/src/test/java/org/apache/atlas/query/GremlinQueryComposerTest.java 
> 6f4df88f0 
> 
> 
> Diff: https://reviews.apache.org/r/72474/diff/8/
> 
> 
> Testing
> ---
> 
> TestCases added.
> 
> 
> Thanks,
> 
> chaitali
> 
>

[jira] [Updated] (ATLAS-3795) UI: statistics Memory Section should have suffix like Bytes /KB /MB

[Keval Bhatt (Jira)]

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

Keval Bhatt updated ATLAS-3795:
---
Attachment: Screen Shot 2020-05-12 at 12.14.38 PM.png

> UI: statistics Memory Section should have suffix like Bytes /KB /MB
> ---
>
> Key: ATLAS-3795
> URL: https://issues.apache.org/jira/browse/ATLAS-3795
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: image-2020-05-12-13-20-36-236.png
>
>




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

[jira] [Updated] (ATLAS-3795) UI: statistics Memory Section should have suffix like Bytes /KB /MB

[Keval Bhatt (Jira)]

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

Keval Bhatt updated ATLAS-3795:
---
Attachment: (was: Screen Shot 2020-05-12 at 12.14.38 PM.png)

> UI: statistics Memory Section should have suffix like Bytes /KB /MB
> ---
>
> Key: ATLAS-3795
> URL: https://issues.apache.org/jira/browse/ATLAS-3795
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: image-2020-05-12-13-20-36-236.png
>
>




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

[jira] [Created] (ATLAS-3795) UI: statistics Memory Section should have suffix like Bytes /KB /MB

[Keval Bhatt (Jira)]

Keval Bhatt created ATLAS-3795:
--

 Summary: UI: statistics Memory Section should have suffix like 
Bytes /KB /MB
 Key: ATLAS-3795
 URL: https://issues.apache.org/jira/browse/ATLAS-3795
 Project: Atlas
  Issue Type: Improvement
Reporter: Keval Bhatt
Assignee: Keval Bhatt
 Fix For: 2.1.0, 3.0.0
 Attachments: image-2020-05-12-13-20-36-236.png





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

[jira] [Updated] (ATLAS-3795) UI: statistics Memory Section should have suffix like Bytes /KB /MB

[Keval Bhatt (Jira)]

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

Keval Bhatt updated ATLAS-3795:
---
Description: !image-2020-05-12-13-20-36-236.png|width=611,height=391!

> UI: statistics Memory Section should have suffix like Bytes /KB /MB
> ---
>
> Key: ATLAS-3795
> URL: https://issues.apache.org/jira/browse/ATLAS-3795
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: image-2020-05-12-13-20-36-236.png
>
>
> !image-2020-05-12-13-20-36-236.png|width=611,height=391!



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

[jira] [Updated] (ATLAS-3795) UI: statistics Memory Section should have suffix like Bytes /KB /MB

[Keval Bhatt (Jira)]

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

Keval Bhatt updated ATLAS-3795:
---
Attachment: image-2020-05-12-13-20-36-236.png

> UI: statistics Memory Section should have suffix like Bytes /KB /MB
> ---
>
> Key: ATLAS-3795
> URL: https://issues.apache.org/jira/browse/ATLAS-3795
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: image-2020-05-12-13-20-36-236.png
>
>




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

[jira] [Created] (ATLAS-3794) New UI: Advance search usablity improvment

[Keval Bhatt (Jira)]

Keval Bhatt created ATLAS-3794:
--

 Summary: New UI: Advance search usablity improvment
 Key: ATLAS-3794
 URL: https://issues.apache.org/jira/browse/ATLAS-3794
 Project: Atlas
  Issue Type: Improvement
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-3793) UI: Entity detail page improvement for label, user-define properties, BM panel

[Keval Bhatt (Jira)]

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

Keval Bhatt updated ATLAS-3793:
---
Summary: UI: Entity detail page improvement for label, user-define 
properties, BM panel  (was: UI: Entity detail page)

> UI: Entity detail page improvement for label, user-define properties, BM panel
> --
>
> Key: ATLAS-3793
> URL: https://issues.apache.org/jira/browse/ATLAS-3793
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
>




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

[jira] [Created] (ATLAS-3793) UI: Entity detail page

[Keval Bhatt (Jira)]

Keval Bhatt created ATLAS-3793:
--

 Summary: UI: Entity detail page
 Key: ATLAS-3793
 URL: https://issues.apache.org/jira/browse/ATLAS-3793
 Project: Atlas
  Issue Type: Improvement
Reporter: Keval Bhatt
Assignee: Keval Bhatt
 Fix For: 2.1.0, 3.0.0






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

[jira] [Created] (ATLAS-3792) New UI: makes it mandate to apply an attribute filter when "Filters" is selected even if the user just wants to select "Show Deleted Entities"

[Keval Bhatt (Jira)]

Keval Bhatt created ATLAS-3792:
--

 Summary: New UI:  makes it mandate to apply an attribute filter 
when "Filters" is selected even if the user just wants to select "Show Deleted 
Entities"
 Key: ATLAS-3792
 URL: https://issues.apache.org/jira/browse/ATLAS-3792
 Project: Atlas
  Issue Type: Bug
Reporter: Keval Bhatt
Assignee: Keval Bhatt
 Fix For: 2.1.0, 3.0.0


New UI: makes it mandate to apply an attribute filter when "Filters" is 
selected even if the user just wants to select "Show Deleted Entities"



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

[jira] [Created] (ATLAS-3791) New UI: In valid option are visible For _CLASSIFIED , _NOT_CLASSIFIED, _ALL_CLASSIFICATION_TYPES

[Keval Bhatt (Jira)]

Keval Bhatt created ATLAS-3791:
--

 Summary: New UI: In valid option are visible For _CLASSIFIED , 
_NOT_CLASSIFIED, _ALL_CLASSIFICATION_TYPES
 Key: ATLAS-3791
 URL: https://issues.apache.org/jira/browse/ATLAS-3791
 Project: Atlas
  Issue Type: Bug
Reporter: Keval Bhatt
Assignee: Keval Bhatt
 Fix For: 2.1.0, 3.0.0


New UI shows the option to delete, edit, create sub-classification for 
_CLASSIFIED , _NOT_CLASSIFIED, _ALL_CLASSIFICATION_TYPES



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

[jira] [Updated] (ATLAS-3789) UI: Date format is not correct for classfication validity periods.

[Keval Bhatt (Jira)]

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

Keval Bhatt updated ATLAS-3789:
---
Description: 
While assigning a classification to the entity

1. selected Add validity Periods.
 2. Start time-> from datePicker : 2020/04/15 10:11:57 -> after Apply -> 
2020/04/15 10:11:57
 3. End Time -> from datePicker : *2020/04/15 20:11:57* -> after Apply -> 
*2020/04/15 08:11:57*
 4. Click Add -> invalid parameters: Invalid dateRange: startTime 2020/04/15 
10:11:57 must be before endTime 2020/04/15 08:11:57

  was:
While assigning classification to the entity

1. selected Add validity Periods.
 2. Start time-> from datePicker : 2020/04/15 10:11:57 -> after Apply -> 
2020/04/15 10:11:57
 3. End Time -> from datePicker : 2020/04/15 20:11:57 -> after Apply -> 
2020/04/15 08:11:57
 4. Click Add -> invalid parameters: Invalid dateRange: startTime 2020/04/15 
10:11:57 must be before endTime 2020/04/15 08:11:57


> UI: Date format is not correct for classfication validity periods.
> --
>
> Key: ATLAS-3789
> URL: https://issues.apache.org/jira/browse/ATLAS-3789
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
>
> While assigning a classification to the entity
> 1. selected Add validity Periods.
>  2. Start time-> from datePicker : 2020/04/15 10:11:57 -> after Apply -> 
> 2020/04/15 10:11:57
>  3. End Time -> from datePicker : *2020/04/15 20:11:57* -> after Apply -> 
> *2020/04/15 08:11:57*
>  4. Click Add -> invalid parameters: Invalid dateRange: startTime 2020/04/15 
> 10:11:57 must be before endTime 2020/04/15 08:11:57



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

[jira] [Updated] (ATLAS-3789) UI: Date format is not correct for classfication validity periods.

[Keval Bhatt (Jira)]

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

Keval Bhatt updated ATLAS-3789:
---
Summary: UI: Date format is not correct for classfication validity periods. 
 (was: UI: Date formating is not correct for classfication validity periods.)

> UI: Date format is not correct for classfication validity periods.
> --
>
> Key: ATLAS-3789
> URL: https://issues.apache.org/jira/browse/ATLAS-3789
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
>
> While attaching classification to the entity
> 1. selected Add validity Periods.
> 2. Start time-> from datePicker : 2020/04/15 10:11:57 -> after Apply -> 
> 2020/04/15 10:11:57
> 3. End Time -> from datePicker : 2020/04/15 20:11:57 -> after Apply -> 
> 2020/04/15 08:11:57
> 4. Click Add -> invalid parameters: Invalid dateRange: startTime 2020/04/15 
> 10:11:57 must be before endTime 2020/04/15 08:11:57



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

[jira] [Updated] (ATLAS-3789) UI: Date format is not correct for classfication validity periods.

[Keval Bhatt (Jira)]

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

Keval Bhatt updated ATLAS-3789:
---
Description: 
While assigning classification to the entity

1. selected Add validity Periods.
 2. Start time-> from datePicker : 2020/04/15 10:11:57 -> after Apply -> 
2020/04/15 10:11:57
 3. End Time -> from datePicker : 2020/04/15 20:11:57 -> after Apply -> 
2020/04/15 08:11:57
 4. Click Add -> invalid parameters: Invalid dateRange: startTime 2020/04/15 
10:11:57 must be before endTime 2020/04/15 08:11:57

  was:
While attaching classification to the entity


1. selected Add validity Periods.
2. Start time-> from datePicker : 2020/04/15 10:11:57 -> after Apply -> 
2020/04/15 10:11:57
3. End Time -> from datePicker : 2020/04/15 20:11:57 -> after Apply -> 
2020/04/15 08:11:57
4. Click Add -> invalid parameters: Invalid dateRange: startTime 2020/04/15 
10:11:57 must be before endTime 2020/04/15 08:11:57


> UI: Date format is not correct for classfication validity periods.
> --
>
> Key: ATLAS-3789
> URL: https://issues.apache.org/jira/browse/ATLAS-3789
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
>
> While assigning classification to the entity
> 1. selected Add validity Periods.
>  2. Start time-> from datePicker : 2020/04/15 10:11:57 -> after Apply -> 
> 2020/04/15 10:11:57
>  3. End Time -> from datePicker : 2020/04/15 20:11:57 -> after Apply -> 
> 2020/04/15 08:11:57
>  4. Click Add -> invalid parameters: Invalid dateRange: startTime 2020/04/15 
> 10:11:57 must be before endTime 2020/04/15 08:11:57



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

[jira] [Updated] (ATLAS-3790) UI: Add Tooltip for Business metadata seachweight

[Keval Bhatt (Jira)]

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

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

> UI: Add Tooltip for Business metadata seachweight
> -
>
> Key: ATLAS-3790
> URL: https://issues.apache.org/jira/browse/ATLAS-3790
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
>




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