[jira] [Comment Edited] (ATLAS-4860) UI : If deleted entity has long name, propertytab in UI is misaligned
[ https://issues.apache.org/jira/browse/ATLAS-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843737#comment-17843737 ] Rahul Kurup edited comment on ATLAS-4860 at 5/6/24 12:56 PM: - +1 was (Author: rahul_fi): https://issues.apache.org/jira/browse/ATLAS-4860 > UI : If deleted entity has long name, propertytab in UI is misaligned > - > > Key: ATLAS-4860 > URL: https://issues.apache.org/jira/browse/ATLAS-4860 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4860-UI-If-deleted-entity-has-long-name-proper.patch, > 0002-ATLAS-4860-UI-If-deleted-entity-has-long-name-proper.patch, > misaligned_UI.png > > > Please check the screenshot where the entity is deleted and the property tab > of the entity looks misaligned. > This doesn't happen if entity is ACTIVE -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4860) UI : If deleted entity has long name, propertytab in UI is misaligned
[ https://issues.apache.org/jira/browse/ATLAS-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843737#comment-17843737 ] Rahul Kurup commented on ATLAS-4860: https://issues.apache.org/jira/browse/ATLAS-4860 > UI : If deleted entity has long name, propertytab in UI is misaligned > - > > Key: ATLAS-4860 > URL: https://issues.apache.org/jira/browse/ATLAS-4860 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-ATLAS-4860-UI-If-deleted-entity-has-long-name-proper.patch, > 0002-ATLAS-4860-UI-If-deleted-entity-has-long-name-proper.patch, > misaligned_UI.png > > > Please check the screenshot where the entity is deleted and the property tab > of the entity looks misaligned. > This doesn't happen if entity is ACTIVE -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4824) UI: Enable/Disable Propagation window usability needs improvement
[ https://issues.apache.org/jira/browse/ATLAS-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823212#comment-17823212 ] Rahul Kurup commented on ATLAS-4824: +1 > UI: Enable/Disable Propagation window usability needs improvement > -- > > Key: ATLAS-4824 > URL: https://issues.apache.org/jira/browse/ATLAS-4824 > Project: Atlas > Issue Type: Improvement >Reporter: Rahul Kurup >Assignee: Brijesh Bhalala >Priority: Minor > Fix For: 3.0.0 > > Attachments: 0001-ATLAS-4824.patch, 0002-ATLAS-4824.patch, > blocking_propagation2.png, image-2024-02-15-10-37-14-512.png > > > In Atlas UI, the user has the ability to access a window that enables or > disables propagation of a classification in a lineage. It looks like the > attached screenshot. > !image-2024-02-15-10-37-14-512.png! > The UI in the window could use improvement as it uses outdated UI. > Edit: The alignment is improper in the "Selection Classification" pane as > seen in this screenshot below. Also as a suggestion, keep the title of the > modal box consistent. > !blocking_propagation2.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4824) UI: Enable/Disable Propagation window usability needs improvement
[ https://issues.apache.org/jira/browse/ATLAS-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4824: --- Description: In Atlas UI, the user has the ability to access a window that enables or disables propagation of a classification in a lineage. It looks like the attached screenshot. Also as a suggestion, keep the title of the modal box consistent. !image-2024-02-15-10-37-14-512.png! The UI in the window could use improvement as it uses outdated UI. Edit: The alignment is improper in the "Selection Classification" pane as seen in this screenshot below. !blocking_propagation2.png! was: In Atlas UI, the user has the ability to access a window that enables or disables propagation of a classification in a lineage. It looks like the attached screenshot. !image-2024-02-15-10-37-14-512.png! The UI in the window could use improvement as it uses outdated UI. Edit: The alignment is improper in the "Selection Classification" pane as seen in this screenshot below. !blocking_propagation2.png! > UI: Enable/Disable Propagation window usability needs improvement > -- > > Key: ATLAS-4824 > URL: https://issues.apache.org/jira/browse/ATLAS-4824 > Project: Atlas > Issue Type: Improvement >Reporter: Rahul Kurup >Assignee: Brijesh Bhalala >Priority: Minor > Fix For: 3.0.0 > > Attachments: 0001-ATLAS-4824.patch, 0002-ATLAS-4824.patch, > blocking_propagation2.png, image-2024-02-15-10-37-14-512.png > > > In Atlas UI, the user has the ability to access a window that enables or > disables propagation of a classification in a lineage. It looks like the > attached screenshot. Also as a suggestion, keep the title of the modal box > consistent. > !image-2024-02-15-10-37-14-512.png! > The UI in the window could use improvement as it uses outdated UI. > Edit: The alignment is improper in the "Selection Classification" pane as > seen in this screenshot below. > !blocking_propagation2.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4824) UI: Enable/Disable Propagation window usability needs improvement
[ https://issues.apache.org/jira/browse/ATLAS-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4824: --- Description: In Atlas UI, the user has the ability to access a window that enables or disables propagation of a classification in a lineage. It looks like the attached screenshot. !image-2024-02-15-10-37-14-512.png! The UI in the window could use improvement as it uses outdated UI. Edit: The alignment is improper in the "Selection Classification" pane as seen in this screenshot below. Also as a suggestion, keep the title of the modal box consistent. !blocking_propagation2.png! was: In Atlas UI, the user has the ability to access a window that enables or disables propagation of a classification in a lineage. It looks like the attached screenshot. Also as a suggestion, keep the title of the modal box consistent. !image-2024-02-15-10-37-14-512.png! The UI in the window could use improvement as it uses outdated UI. Edit: The alignment is improper in the "Selection Classification" pane as seen in this screenshot below. !blocking_propagation2.png! > UI: Enable/Disable Propagation window usability needs improvement > -- > > Key: ATLAS-4824 > URL: https://issues.apache.org/jira/browse/ATLAS-4824 > Project: Atlas > Issue Type: Improvement >Reporter: Rahul Kurup >Assignee: Brijesh Bhalala >Priority: Minor > Fix For: 3.0.0 > > Attachments: 0001-ATLAS-4824.patch, 0002-ATLAS-4824.patch, > blocking_propagation2.png, image-2024-02-15-10-37-14-512.png > > > In Atlas UI, the user has the ability to access a window that enables or > disables propagation of a classification in a lineage. It looks like the > attached screenshot. > !image-2024-02-15-10-37-14-512.png! > The UI in the window could use improvement as it uses outdated UI. > Edit: The alignment is improper in the "Selection Classification" pane as > seen in this screenshot below. Also as a suggestion, keep the title of the > modal box consistent. > !blocking_propagation2.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4824) UI: Enable/Disable Propagation window usability needs improvement
[ https://issues.apache.org/jira/browse/ATLAS-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4824: --- Attachment: blocking_propagation2.png Description: In Atlas UI, the user has the ability to access a window that enables or disables propagation of a classification in a lineage. It looks like the attached screenshot. !image-2024-02-15-10-37-14-512.png! The UI in the window could use improvement as it uses outdated UI. Edit: The alignment is improper in the "Selection Classification" pane as seen in this screenshot below. !blocking_propagation2.png! was: In Atlas UI, the user has the ability to access a window that enables or disables propagation of a classification in a lineage. It looks like the attached screenshot. !image-2024-02-15-10-37-14-512.png! The UI in the window could use improvement as it uses outdated UI. > UI: Enable/Disable Propagation window usability needs improvement > -- > > Key: ATLAS-4824 > URL: https://issues.apache.org/jira/browse/ATLAS-4824 > Project: Atlas > Issue Type: Improvement >Reporter: Rahul Kurup >Assignee: Brijesh Bhalala >Priority: Minor > Fix For: 3.0.0 > > Attachments: 0001-ATLAS-4824.patch, 0002-ATLAS-4824.patch, > blocking_propagation2.png, image-2024-02-15-10-37-14-512.png > > > In Atlas UI, the user has the ability to access a window that enables or > disables propagation of a classification in a lineage. It looks like the > attached screenshot. > !image-2024-02-15-10-37-14-512.png! > The UI in the window could use improvement as it uses outdated UI. > Edit: The alignment is improper in the "Selection Classification" pane as > seen in this screenshot below. > !blocking_propagation2.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4825) Some DSL/advanced queries using business metadata attribute don't work as expected
[
https://issues.apache.org/jira/browse/ATLAS-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Kurup updated ATLAS-4825:
---
Description:
If we fire these queries(assuming data exists for valid results):
{code:java}
hive_table where qualifiedName like 'dataset_3' and bm1.attr1 like '*' select
bm1.attr1
hive_table where qualifiedName like 'dataset_' and bm1.attr1 like '*' select
bm1.attr1
hive_table where qualifiedName like 'dataset' and bm1.attr1 like '*' select
bm1.attr1{code}
And if we compare the results of each query above, each query fetches more
results than the previous query, which is expected behaviour.
However if we consider these queries:
{code:java}
hive_table where qualifiedName like 'dataset_3' select bm1.attr1
hive_table where qualifiedName like 'dataset_' select bm1.attr1
hive_table where qualifiedName like 'dataset' select bm1.attr1{code}
The results are unexpected. The last two queries should have fetched results,
but only shows blank. Screenshots for the same have been attached below..
The difference noted between the first three and the last three queries was
that the Business metadata attribute is not used in the last 3 queries in the
where clause.
was:
If we fire these queries(assuming data exists for valid results):
hive_table where qualifiedName like 'dataset_3' and bm1.attr1 like '*' select
bm1.attr1
hive_table where qualifiedName like 'dataset_' and bm1.attr1 like '*' select
bm1.attr1
hive_table where qualifiedName like 'dataset' and bm1.attr1 like '*' select
bm1.attr1
And if we compare the results of each query above, each query fetches more
results than the previous query, which is expected behaviour.
However if we consider these queries:
hive_table where qualifiedName like 'dataset_3' select bm1.attr1
hive_table where qualifiedName like 'dataset_' select bm1.attr1
hive_table where qualifiedName like 'dataset' select bm1.attr1
The results are unexpected. The last two queries should have fetched results,
but only shows blank. Screenshots for the same have been attached below..
The difference noted between the first three and the last three queries was
that the Business metadata attribute is not used in the last 3 queries in the
where clause.
> Some DSL/advanced queries using business metadata attribute don't work as
> expected
> --
>
> Key: ATLAS-4825
> URL: https://issues.apache.org/jira/browse/ATLAS-4825
> Project: Atlas
> Issue Type: Bug
>Reporter: Rahul Kurup
>Priority: Major
> Attachments: dataset_3_dsl_screenshot.png,
> dataset_no_underscore_screenshot.png, dataset_underscore_dsl_screenshot.png
>
>
> If we fire these queries(assuming data exists for valid results):
> {code:java}
> hive_table where qualifiedName like 'dataset_3' and bm1.attr1 like '*' select
> bm1.attr1
> hive_table where qualifiedName like 'dataset_' and bm1.attr1 like '*' select
> bm1.attr1
> hive_table where qualifiedName like 'dataset' and bm1.attr1 like '*' select
> bm1.attr1{code}
> And if we compare the results of each query above, each query fetches more
> results than the previous query, which is expected behaviour.
> However if we consider these queries:
> {code:java}
> hive_table where qualifiedName like 'dataset_3' select bm1.attr1
> hive_table where qualifiedName like 'dataset_' select bm1.attr1
> hive_table where qualifiedName like 'dataset' select bm1.attr1{code}
> The results are unexpected. The last two queries should have fetched results,
> but only shows blank. Screenshots for the same have been attached below..
> The difference noted between the first three and the last three queries was
> that the Business metadata attribute is not used in the last 3 queries in the
> where clause.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4825) Some DSL/advanced queries using business metadata attribute don't work as expected
[
https://issues.apache.org/jira/browse/ATLAS-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Kurup updated ATLAS-4825:
---
Description:
If we fire these queries(assuming data exists for valid results):
hive_table where qualifiedName like 'dataset_3' and bm1.attr1 like '*' select
bm1.attr1
hive_table where qualifiedName like 'dataset_' and bm1.attr1 like '*' select
bm1.attr1
hive_table where qualifiedName like 'dataset' and bm1.attr1 like '*' select
bm1.attr1
And if we compare the results of each query above, each query fetches more
results than the previous query, which is expected behaviour.
However if we consider these queries:
hive_table where qualifiedName like 'dataset_3' select bm1.attr1
hive_table where qualifiedName like 'dataset_' select bm1.attr1
hive_table where qualifiedName like 'dataset' select bm1.attr1
The results are unexpected. The last two queries should have fetched results,
but only shows blank. Screenshots for the same have been attached below..
The difference noted between the first three and the last three queries was
that the Business metadata attribute is not used in the last 3 queries in the
where clause.
was:
If we fire these queries(assuming data exists for valid results):
hive_table where qualifiedName like '*{*}dataset_3{*}*' and bm1.attr1 like '*'
select bm1.attr1
hive_table where qualifiedName like '*{*}dataset_{*}*' and bm1.attr1 like '*'
select bm1.attr1
hive_table where qualifiedName like '*{*}dataset{*}*' and bm1.attr1 like '*'
select bm1.attr1
And if we compare the results of each query above, each query fetches more
results than the previous query, which is expected behaviour.
However if we consider these queries:
hive_table where qualifiedName like '*{*}dataset_3{*}*' select bm1.attr1
hive_table where qualifiedName like '*{*}dataset_{*}*' select bm1.attr1
hive_table where qualifiedName like '*{*}dataset{*}*' select bm1.attr1
The results are unexpected. The last two queries should have fetched results,
but only shows blank. Screenshots for the same have been attached below..
The difference noted between the first three and the last three queries was
that the Business metadata attribute is not used in the last 3 queries in the
where clause.
> Some DSL/advanced queries using business metadata attribute don't work as
> expected
> --
>
> Key: ATLAS-4825
> URL: https://issues.apache.org/jira/browse/ATLAS-4825
> Project: Atlas
> Issue Type: Bug
>Reporter: Rahul Kurup
>Priority: Major
> Attachments: dataset_3_dsl_screenshot.png,
> dataset_no_underscore_screenshot.png, dataset_underscore_dsl_screenshot.png
>
>
> If we fire these queries(assuming data exists for valid results):
> hive_table where qualifiedName like 'dataset_3' and bm1.attr1 like '*' select
> bm1.attr1
> hive_table where qualifiedName like 'dataset_' and bm1.attr1 like '*' select
> bm1.attr1
> hive_table where qualifiedName like 'dataset' and bm1.attr1 like '*' select
> bm1.attr1
> And if we compare the results of each query above, each query fetches more
> results than the previous query, which is expected behaviour.
> However if we consider these queries:
> hive_table where qualifiedName like 'dataset_3' select bm1.attr1
> hive_table where qualifiedName like 'dataset_' select bm1.attr1
> hive_table where qualifiedName like 'dataset' select bm1.attr1
> The results are unexpected. The last two queries should have fetched results,
> but only shows blank. Screenshots for the same have been attached below..
> The difference noted between the first three and the last three queries was
> that the Business metadata attribute is not used in the last 3 queries in the
> where clause.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4825) Some DSL/advanced queries using business metadata attribute don't work as expected
Rahul Kurup created ATLAS-4825:
--
Summary: Some DSL/advanced queries using business metadata
attribute don't work as expected
Key: ATLAS-4825
URL: https://issues.apache.org/jira/browse/ATLAS-4825
Project: Atlas
Issue Type: Bug
Reporter: Rahul Kurup
Attachments: dataset_3_dsl_screenshot.png,
dataset_no_underscore_screenshot.png, dataset_underscore_dsl_screenshot.png
If we fire these queries(assuming data exists for valid results):
hive_table where qualifiedName like '*{*}dataset_3{*}*' and bm1.attr1 like '*'
select bm1.attr1
hive_table where qualifiedName like '*{*}dataset_{*}*' and bm1.attr1 like '*'
select bm1.attr1
hive_table where qualifiedName like '*{*}dataset{*}*' and bm1.attr1 like '*'
select bm1.attr1
And if we compare the results of each query above, each query fetches more
results than the previous query, which is expected behaviour.
However if we consider these queries:
hive_table where qualifiedName like '*{*}dataset_3{*}*' select bm1.attr1
hive_table where qualifiedName like '*{*}dataset_{*}*' select bm1.attr1
hive_table where qualifiedName like '*{*}dataset{*}*' select bm1.attr1
The results are unexpected. The last two queries should have fetched results,
but only shows blank. Screenshots for the same have been attached below..
The difference noted between the first three and the last three queries was
that the Business metadata attribute is not used in the last 3 queries in the
where clause.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (ATLAS-4824) UI: Enable/Disable Propagation window usability needs improvement
[ https://issues.apache.org/jira/browse/ATLAS-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup reassigned ATLAS-4824: -- Assignee: Brijesh Bhalala > UI: Enable/Disable Propagation window usability needs improvement > -- > > Key: ATLAS-4824 > URL: https://issues.apache.org/jira/browse/ATLAS-4824 > Project: Atlas > Issue Type: Improvement >Reporter: Rahul Kurup >Assignee: Brijesh Bhalala >Priority: Minor > Attachments: image-2024-02-15-10-37-14-512.png > > > In Atlas UI, the user has the ability to access a window that enables or > disables propagation of a classification in a lineage. It looks like the > attached screenshot. > !image-2024-02-15-10-37-14-512.png! > The UI in the window could use improvement as it uses outdated UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4824) UI: Enable/Disable Propagation window usability needs improvement
Rahul Kurup created ATLAS-4824: -- Summary: UI: Enable/Disable Propagation window usability needs improvement Key: ATLAS-4824 URL: https://issues.apache.org/jira/browse/ATLAS-4824 Project: Atlas Issue Type: Improvement Reporter: Rahul Kurup Attachments: image-2024-02-15-10-37-14-512.png In Atlas UI, the user has the ability to access a window that enables or disables propagation of a classification in a lineage. It looks like the attached screenshot. !image-2024-02-15-10-37-14-512.png! The UI in the window could use improvement as it uses outdated UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4810) Atlas UI Basic Searching result sorting option not available on all Columns
[ https://issues.apache.org/jira/browse/ATLAS-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788405#comment-17788405 ] Rahul Kurup commented on ATLAS-4810: +1 > Atlas UI Basic Searching result sorting option not available on all Columns > --- > > Key: ATLAS-4810 > URL: https://issues.apache.org/jira/browse/ATLAS-4810 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4810-Atlas-UI-Basic-Searching-result-sorting-o.patch, Atlas > Advanced Searching result sorting.png, Atlas Basic Searching result > sorting.png, advanced-search.PNG, basic-search.PNG > > > Basically in Basic search (hive_column as an example), we can add the Columns > from the right side for the results, but those added Columns don't have the > sorting option (Ascending/Descending) on the UI , only 4 default Columns > (Name, Owner, Description and Type) has sorting option. > However if using Advanced reaching, we query the same Column name "from > hive_column select position", that "position" has the sort errors next to it. > Same Column "position" in Basic Searching doesn't have the sort function. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4813) UI: Specific steps cause error when searching for ALL_ENTITY_TYPES in basic search
Rahul Kurup created ATLAS-4813: -- Summary: UI: Specific steps cause error when searching for ALL_ENTITY_TYPES in basic search Key: ATLAS-4813 URL: https://issues.apache.org/jira/browse/ATLAS-4813 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Steps: 1. Select _ALL_ENTITY_TYPES in "Search by Entity" dropdown 2. Select either CLASSIFIED/NON_CLASSIFIED/ALL_CLASSIFICATION_TYPES in "Search by Classification" dropdown 3. In the results page, add the column "Entity Status" by selecting it from the Columns button in the right side of the page. You will see an error "Attribute __entityStatus not found for type __ENTITY_ROOT". At this point if any time a search is triggered for ALL_ENTITY_TYPES, then it causes this error to reappear. Clearing the search results page also doesn't fix this issue. Logging out and logging in stops the error from reoccurring. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4812) UI: Unable to find matching entities for particular relationship attribute in custom typedef
[ https://issues.apache.org/jira/browse/ATLAS-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4812: --- Description: Steps: 1. Create the Atlas entity typedef as per the attached json. 2. (Assuming all typedefs are available for UI entity creation)In UI, click on create entity. 3. Navigate to the section shown in the attached screenshot. 4. Select 'quick_table_e_storagedesc' in the first dropdown and try to provide a qualifiedName for the Table matching the entity type supported for this parameter. Expected Behaviour: Matching qualifiedNames should populate. Actual Behaviour: No qualified names appear. Only the qualified names valid to 'hive_table_storagedesc_dum' appear, which is incorrect behaviour. was: Steps: 1. Create the Atlas entity typedef as per the attached json. 2. (Assuming all typedefs are available for UI entity creation)In UI, click on create entity. 3. Navigate to this section in the dialog box: !image-2023-11-08-14-50-40-062.png|thumbnail! 4. Select 'quick_table_e_storagedesc' in the first dropdown and try to provide a qualifiedName for the Table matching the entity type supported for this parameter. Expected Behaviour: Matching qualifiedNames should populate. Actual Behaviour: No qualified names appear. Only the qualified names valid to 'hive_table_storagedesc_dum' appear, which is incorrect behaviour. > UI: Unable to find matching entities for particular relationship attribute in > custom typedef > > > Key: ATLAS-4812 > URL: https://issues.apache.org/jira/browse/ATLAS-4812 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Priority: Minor > Attachments: custom_entity_storage.json, > image-2023-11-08-14-52-26-074.png > > > Steps: > 1. Create the Atlas entity typedef as per the attached json. > 2. (Assuming all typedefs are available for UI entity creation)In UI, click > on create entity. > 3. Navigate to the section shown in the attached screenshot. > 4. Select 'quick_table_e_storagedesc' in the first dropdown and try to > provide a qualifiedName for the Table matching the entity type supported for > this parameter. > Expected Behaviour: Matching qualifiedNames should populate. > Actual Behaviour: No qualified names appear. Only the qualified names valid > to 'hive_table_storagedesc_dum' appear, which is incorrect behaviour. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4812) UI: Unable to find matching entities for particular relationship attribute in custom typedef
Rahul Kurup created ATLAS-4812: -- Summary: UI: Unable to find matching entities for particular relationship attribute in custom typedef Key: ATLAS-4812 URL: https://issues.apache.org/jira/browse/ATLAS-4812 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Attachments: custom_entity_storage.json, image-2023-11-08-14-52-26-074.png Steps: 1. Create the Atlas entity typedef as per the attached json. 2. (Assuming all typedefs are available for UI entity creation)In UI, click on create entity. 3. Navigate to this section in the dialog box: !image-2023-11-08-14-50-40-062.png|thumbnail! 4. Select 'quick_table_e_storagedesc' in the first dropdown and try to provide a qualifiedName for the Table matching the entity type supported for this parameter. Expected Behaviour: Matching qualifiedNames should populate. Actual Behaviour: No qualified names appear. Only the qualified names valid to 'hive_table_storagedesc_dum' appear, which is incorrect behaviour. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4805) UI: Text editor improvements and code clean up.
[ https://issues.apache.org/jira/browse/ATLAS-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781335#comment-17781335 ] Rahul Kurup commented on ATLAS-4805: +1 > UI: Text editor improvements and code clean up. > --- > > Key: ATLAS-4805 > URL: https://issues.apache.org/jira/browse/ATLAS-4805 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0, 2.3.0 >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4805-UI-Text-editor-improvements-and-code-clea.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4799) UI: Enum type Business metadata attribute shows incorrect data when specific string is in attribute name.
[ https://issues.apache.org/jira/browse/ATLAS-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769439#comment-17769439 ] Rahul Kurup commented on ATLAS-4799: +1 > UI: Enum type Business metadata attribute shows incorrect data when specific > string is in attribute name. > - > > Key: ATLAS-4799 > URL: https://issues.apache.org/jira/browse/ATLAS-4799 > Project: Atlas > Issue Type: Bug >Affects Versions: 3.0.0, 2.3.0 >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: > 0001-ATLAS-4799-UI-Enum-type-Business-metadata-attribute-.patch > > > 1. Create a enum such that its enum name contains the word 'date' (for > example, 'updatetest') with the following values: > v1,v2 > And then create a business metadata attribute whose type is the enum which we > have just now created. > 2. After assigning a enum value (v1 or v2) to the entity with this attribute, > it is observed that it displays some dates rather than 'v1' or 'v2'. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4799) UI: Enum type Business metadata attribute shows incorrect data when specific string is in attribute name.
[ https://issues.apache.org/jira/browse/ATLAS-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4799: --- Summary: UI: Enum type Business metadata attribute shows incorrect data when specific string is in attribute name. (was: Enum type Business metadata attribute shows incorrect data when specific string is in attribute name.) > UI: Enum type Business metadata attribute shows incorrect data when specific > string is in attribute name. > - > > Key: ATLAS-4799 > URL: https://issues.apache.org/jira/browse/ATLAS-4799 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Priority: Major > > 1. Create a enum such that its enum name contains the word 'date' (for > example, 'updatetest') with the following values: > v1,v2 > And then create a business metadata attribute whose type is the enum which we > have just now created. > 2. After assigning a enum value (v1 or v2) to the entity with this attribute, > it is observed that it displays some dates rather than 'v1' or 'v2'. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4799) Enum type Business metadata attribute shows incorrect data when specific string is in attribute name.
Rahul Kurup created ATLAS-4799: -- Summary: Enum type Business metadata attribute shows incorrect data when specific string is in attribute name. Key: ATLAS-4799 URL: https://issues.apache.org/jira/browse/ATLAS-4799 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup 1. Create a enum such that its enum name contains the word 'date' (for example, 'updatetest') with the following values: v1,v2 And then create a business metadata attribute whose type is the enum which we have just now created. 2. After assigning a enum value (v1 or v2) to the entity with this attribute, it is observed that it displays some dates rather than 'v1' or 'v2'. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4798) UI: Saved search created in API not working in UI
[
https://issues.apache.org/jira/browse/ATLAS-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Kurup reassigned ATLAS-4798:
--
Assignee: Prasad P. Pawar (was: Rahul Kurup)
> UI: Saved search created in API not working in UI
> -
>
> Key: ATLAS-4798
> URL: https://issues.apache.org/jira/browse/ATLAS-4798
> Project: Atlas
> Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Minor
>
> The following saved search created through API request doesn't work in UI.
> When we click on the entry for the saved search, no action occurs.
> {code:java}
> {"name":
> "a2","excludeDeletedEntities":true,"includeSubClassifications":true,"includeSubTypes":true,"includeClassificationAttributes":true,"entityFilters":{"attributeName":"name","operator":"contains","attributeValue":"sales"},"tagFilters":null,"attributes":[],"limit":25,"offset":0,"typeName":"Table","classification":null,"termName":null}
> {code}
> Curl Command:
> {code:java}
> curl -X 'POST' \
> 'http://localhost:21000/api/atlas/v2/search/saved' \
> -H 'accept: application/json' \
> -H 'Content-Type: application/json' \
> -H 'X-XSRF-HEADER: NmdrbipuSHT127wqLOf3' \
> -d '{"name":
> "a2","excludeDeletedEntities":true,"includeSubClassifications":true,"includeSubTypes":true,"includeClassificationAttributes":true,"entityFilters":{"attributeName":"name","operator":"contains","attributeValue":"sales"},"tagFilters":null,"attributes":[],"limit":25,"offset":0,"typeName":"Table","classification":null,"termName":null}'
> {code}
> However if we perform the same search using UI and then save it, it works as
> expected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4798) UI: Saved search created in API not working in UI
Rahul Kurup created ATLAS-4798:
--
Summary: UI: Saved search created in API not working in UI
Key: ATLAS-4798
URL: https://issues.apache.org/jira/browse/ATLAS-4798
Project: Atlas
Issue Type: Bug
Reporter: Rahul Kurup
The following saved search created through API request doesn't work in UI. When
we click on the entry for the saved search, no action occurs.
{code:java}
{"name":
"a2","excludeDeletedEntities":true,"includeSubClassifications":true,"includeSubTypes":true,"includeClassificationAttributes":true,"entityFilters":{"attributeName":"name","operator":"contains","attributeValue":"sales"},"tagFilters":null,"attributes":[],"limit":25,"offset":0,"typeName":"Table","classification":null,"termName":null}
{code}
Curl Command:
{code:java}
curl -X 'POST' \
'http://localhost:21000/api/atlas/v2/search/saved' \
-H 'accept: application/json' \
-H 'Content-Type: application/json' \
-H 'X-XSRF-HEADER: NmdrbipuSHT127wqLOf3' \
-d '{"name":
"a2","excludeDeletedEntities":true,"includeSubClassifications":true,"includeSubTypes":true,"includeClassificationAttributes":true,"entityFilters":{"attributeName":"name","operator":"contains","attributeValue":"sales"},"tagFilters":null,"attributes":[],"limit":25,"offset":0,"typeName":"Table","classification":null,"termName":null}'
{code}
However if we perform the same search using UI and then save it, it works as
expected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (ATLAS-4798) UI: Saved search created in API not working in UI
[
https://issues.apache.org/jira/browse/ATLAS-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Kurup reassigned ATLAS-4798:
--
Assignee: Rahul Kurup
> UI: Saved search created in API not working in UI
> -
>
> Key: ATLAS-4798
> URL: https://issues.apache.org/jira/browse/ATLAS-4798
> Project: Atlas
> Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Rahul Kurup
>Priority: Minor
>
> The following saved search created through API request doesn't work in UI.
> When we click on the entry for the saved search, no action occurs.
> {code:java}
> {"name":
> "a2","excludeDeletedEntities":true,"includeSubClassifications":true,"includeSubTypes":true,"includeClassificationAttributes":true,"entityFilters":{"attributeName":"name","operator":"contains","attributeValue":"sales"},"tagFilters":null,"attributes":[],"limit":25,"offset":0,"typeName":"Table","classification":null,"termName":null}
> {code}
> Curl Command:
> {code:java}
> curl -X 'POST' \
> 'http://localhost:21000/api/atlas/v2/search/saved' \
> -H 'accept: application/json' \
> -H 'Content-Type: application/json' \
> -H 'X-XSRF-HEADER: NmdrbipuSHT127wqLOf3' \
> -d '{"name":
> "a2","excludeDeletedEntities":true,"includeSubClassifications":true,"includeSubTypes":true,"includeClassificationAttributes":true,"entityFilters":{"attributeName":"name","operator":"contains","attributeValue":"sales"},"tagFilters":null,"attributes":[],"limit":25,"offset":0,"typeName":"Table","classification":null,"termName":null}'
> {code}
> However if we perform the same search using UI and then save it, it works as
> expected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4793) UI: Search Issues
[ https://issues.apache.org/jira/browse/ATLAS-4793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764580#comment-17764580 ] Rahul Kurup commented on ATLAS-4793: +1 > UI: Search Issues > - > > Key: ATLAS-4793 > URL: https://issues.apache.org/jira/browse/ATLAS-4793 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Major > Attachments: 0001-ATLAS-4793-UI-Search-Issues.patch > > > 1. Usually when a user enters a string in the quick search bar and presses > Enter, Atlas should trigger the search for the same. But instead user is > taken to a page with nothing displayed. > 2. When user clicks on the suggestions listed in the quick search dropdown, > user is taken to a page with nothing displayed. > 3. When user attempts to select _ALL_ENTITY_TYPES in the basic search > functionality, user is taken to a page with nothing displayed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4793) UI: Search Issues
Rahul Kurup created ATLAS-4793: -- Summary: UI: Search Issues Key: ATLAS-4793 URL: https://issues.apache.org/jira/browse/ATLAS-4793 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup 1. Usually when a user enters a string in the quick search bar and presses Enter, Atlas should trigger the search for the same. But instead user is taken to a page with nothing displayed. 2. When user clicks on the suggestions listed in the quick search dropdown, user is taken to a page with nothing displayed. 3. When user attempts to select _ALL_ENTITY_TYPES in the basic search functionality, user is taken to a page with nothing displayed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4791) UI: Incorrect search filter error messages when user specifies range beyond type
Rahul Kurup created ATLAS-4791: -- Summary: UI: Incorrect search filter error messages when user specifies range beyond type Key: ATLAS-4791 URL: https://issues.apache.org/jira/browse/ATLAS-4791 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Attachments: image_2023_09_07T04_45_54_933Z.png, image_2023_09_07T04_50_34_336Z.png In Basic Search filters, when a user attempts to specify criteria for ranges exceed int, float, and short ranges we get the same incorrect messages. When a user tries the same for long attribute type, they get "Something Went Wrong" backend error message and it closes the search popup. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4778) BusinessMetadata string attribute value persists as prefix and suffix
[ https://issues.apache.org/jira/browse/ATLAS-4778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17756883#comment-17756883 ] Rahul Kurup commented on ATLAS-4778: +1 > BusinessMetadata string attribute value persists as prefix and suffix > -- > > Key: ATLAS-4778 > URL: https://issues.apache.org/jira/browse/ATLAS-4778 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Pinal Shah >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4778-BusinessMetadata-string-attribute-value-p.patch, > string_attr.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4780) UI: Graph is not visible after more than 100 entity types are created
Rahul Kurup created ATLAS-4780: -- Summary: UI: Graph is not visible after more than 100 entity types are created Key: ATLAS-4780 URL: https://issues.apache.org/jira/browse/ATLAS-4780 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup The graph charts are not visible in the Statistics window after creating more than 100 entities belonging to different entity Types. We can see the API to the chart being called in the developer tools in the browser but no chart appears. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4770) [UI] When landing on terms page from entity details page, going back lands on same page
[ https://issues.apache.org/jira/browse/ATLAS-4770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746476#comment-17746476 ] Rahul Kurup commented on ATLAS-4770: +1 > [UI] When landing on terms page from entity details page, going back lands on > same page > --- > > Key: ATLAS-4770 > URL: https://issues.apache.org/jira/browse/ATLAS-4770 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Abhishek Pal >Assignee: Farhan Khan >Priority: Minor > > Steps: > # In classic UI, go to any entity with an associated term, or create one if > required. > # In the entity details page, click on term to land in the term details page > # Try to go back > When going back, i.e. to the previous page, it will keep reloading the term > details page. > This is also seen if we click on the term in the search result page itself. > The behaviour is not seen if we directly go to the terms details page - in > this case it properly goes back to the previous page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4774) [UI] Using navigation on the glossary page does not highlight the corresponding term/glossary
[ https://issues.apache.org/jira/browse/ATLAS-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746477#comment-17746477 ] Rahul Kurup commented on ATLAS-4774: +1 > [UI] Using navigation on the glossary page does not highlight the > corresponding term/glossary > - > > Key: ATLAS-4774 > URL: https://issues.apache.org/jira/browse/ATLAS-4774 > Project: Atlas > Issue Type: Bug >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4770-ATLAS-4774-When-landing-on-terms-page-fro.patch > > > Steps: > # In the classic UI, go to the glossaries tab > # Click on a glossary/term > # Click on another glossary/term > # Navigate back > Upon going back the page changes to the correct glossary/term, however the > highlighted term/glossary reflects the most recently selected term/glossary. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4732) UI: Setting 'atlas.ui.date.format' to certain value creates incorrect date entries
[
https://issues.apache.org/jira/browse/ATLAS-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746475#comment-17746475
]
Rahul Kurup commented on ATLAS-4732:
+1
> UI: Setting 'atlas.ui.date.format' to certain value creates incorrect date
> entries
> --
>
> Key: ATLAS-4732
> URL: https://issues.apache.org/jira/browse/ATLAS-4732
> Project: Atlas
> Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments:
> 0001-ATLAS-4732-UI-Setting-atlas.ui.date.format-to-certai.patch
>
>
> Pre-conditions:
> In atlas-application.properties, set the following:-
> {code:java}
> atlas.ui.date.format=DD/MM/ hh:mm:ss{code}
> Steps:
> 1. Create Business Metadata with a date type and assign to a Type (e.g.
> hdfs_path)
> 2. Create an entity for the assigned Type (hdfs_path).
> 3. Add Business Metadata and select the created date type.
> 4. Populate this value with a date in DD/MM/ format, i.e. (06/03/2023)
> 5. Click Apply.
> 6. Click Save.
> The date changes to 03/06/2023 which is a completely different date.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4751) UI: Search Results download window appears without clicking on the icon
Rahul Kurup created ATLAS-4751: -- Summary: UI: Search Results download window appears without clicking on the icon Key: ATLAS-4751 URL: https://issues.apache.org/jira/browse/ATLAS-4751 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup On higher resolution monitor screens, the Search Results window appears even when user has not clicked on the icon to start the process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4736) Atlas UI: Audit tab reporting a date of 1970 in a few properties.
[
https://issues.apache.org/jira/browse/ATLAS-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17704459#comment-17704459
]
Rahul Kurup commented on ATLAS-4736:
+1
> Atlas UI: Audit tab reporting a date of 1970 in a few properties.
> -
>
> Key: ATLAS-4736
> URL: https://issues.apache.org/jira/browse/ATLAS-4736
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Prasad P. Pawar
>Assignee: Prasad P. Pawar
>Priority: Major
> Labels: Atlas-UI, audit
> Attachments:
> 0001-ATLAS-4736-Audit-tab-reporting-a-date-of-1970-in-a-f.patch,
> audit_expand_showing_date_issue.png, entity_audit_tab.png,
> entity_properties_tab_date.png
>
>
> Create entities using the following data in POST command with the "typeName"
> called "DateTimeCheck".
> typedef for "CreateTimeInText", "syncJobUpdateTimeInText" &
> "syncJobCreateTimeInText" is string.
> {code:java}
> POST :
> --data-raw ' {
> "entity": {
> "typeName": "DateTimeCheck",
> "attributes": {
> "syncJobUpdateTimeInText": "2022-12-21 09:01:36 CDT",
> "UpdateTime": null,
> "syncJobCreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreateTime": "0",
> "CreatedByUserId": "admin",
> "Guid": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "description": "ENTITY_FOR_DATE_TIME_CHECK",
> "syncJobUpdatedByUserId": null,
> "CreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreatedByUserId": null,
> "syncJobType": "fullSync",
> "syncJobUpdateTime": 1671649924455,
> "name": "ENTITY_FOR_DATE_TIME_CHECK",
> "additionalProperties": {
> "authDatabase": null,
> "catalogId": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "database": null,
> "host": null,
> "ownerId": "1000331095",
> "ssl": "false",
> "username": null
> },
> "CreatedBy": "1000331095",
> "CreateTime": 1628085696000
> }
> }
> }' {code}
> After the entity is posted, the Atlas audit tab is reporting
> "CreateTimeInText", "syncJobUpdateTimeInText", and "syncJobCreateTimeInText "
> created on the year of 1970.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4736) Atlas UI: Audit tab reporting a date of 1970 in a few properties.
[
https://issues.apache.org/jira/browse/ATLAS-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703913#comment-17703913
]
Rahul Kurup commented on ATLAS-4736:
Hi, if I add a date value that is before 1970 (negative epoch milliseconds) eg:
-2452140, then the date appears as N/A.
> Atlas UI: Audit tab reporting a date of 1970 in a few properties.
> -
>
> Key: ATLAS-4736
> URL: https://issues.apache.org/jira/browse/ATLAS-4736
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Prasad P. Pawar
>Assignee: Prasad P. Pawar
>Priority: Major
> Labels: Atlas-UI, audit
> Attachments:
> 0001-ATLAS-4736-Audit-tab-reporting-a-date-of-1970-in-a-f.patch,
> audit_expand_showing_date_issue.png, entity_audit_tab.png,
> entity_properties_tab_date.png
>
>
> Create entities using the following data in POST command with the "typeName"
> called "DateTimeCheck".
> typedef for "CreateTimeInText", "syncJobUpdateTimeInText" &
> "syncJobCreateTimeInText" is string.
> {code:java}
> POST :
> --data-raw ' {
> "entity": {
> "typeName": "DateTimeCheck",
> "attributes": {
> "syncJobUpdateTimeInText": "2022-12-21 09:01:36 CDT",
> "UpdateTime": null,
> "syncJobCreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreateTime": "0",
> "CreatedByUserId": "admin",
> "Guid": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "description": "ENTITY_FOR_DATE_TIME_CHECK",
> "syncJobUpdatedByUserId": null,
> "CreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreatedByUserId": null,
> "syncJobType": "fullSync",
> "syncJobUpdateTime": 1671649924455,
> "name": "ENTITY_FOR_DATE_TIME_CHECK",
> "additionalProperties": {
> "authDatabase": null,
> "catalogId": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "database": null,
> "host": null,
> "ownerId": "1000331095",
> "ssl": "false",
> "username": null
> },
> "CreatedBy": "1000331095",
> "CreateTime": 1628085696000
> }
> }
> }' {code}
> After the entity is posted, the Atlas audit tab is reporting
> "CreateTimeInText", "syncJobUpdateTimeInText", and "syncJobCreateTimeInText "
> created on the year of 1970.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4732) UI: Setting 'atlas.ui.date.format' to certain value creates incorrect date entries
Rahul Kurup created ATLAS-4732:
--
Summary: UI: Setting 'atlas.ui.date.format' to certain value
creates incorrect date entries
Key: ATLAS-4732
URL: https://issues.apache.org/jira/browse/ATLAS-4732
Project: Atlas
Issue Type: Bug
Reporter: Rahul Kurup
Pre-conditions:
In atlas-application.properties, set the following:-
{code:java}
atlas.ui.date.format=DD/MM/ hh:mm:ss{code}
Steps:
1. Create Business Metadata with a date type and assign to a Type (e.g.
hdfs_path)
2. Create an entity for the assigned Type (hdfs_path).
3. Add Business Metadata and select the created date type.
4. Populate this value with a date in DD/MM/ format, i.e. (06/03/2023)
5. Click Apply.
6. Click Save.
The date changes to 03/06/2023 which is a completely different date.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4730) Unable to assign term to custom entity with no supertype in its typdef
Rahul Kurup created ATLAS-4730:
--
Summary: Unable to assign term to custom entity with no supertype
in its typdef
Key: ATLAS-4730
URL: https://issues.apache.org/jira/browse/ATLAS-4730
Project: Atlas
Issue Type: Bug
Reporter: Rahul Kurup
When we try to assign a glossary term to an entity whose custom typedef does
not have a supertype of any existing typedef, then the following error is
encountered and the term does not get assigned.
{{invalid relationshipDef: AtlasGlossarySemanticAssignment: end type 1:
Referenceable, end type 2: AtlasGlossaryTerm}}
Sample typedef to reproduce the error is given below:
{color:#dcdcdc}{{color}
{color:#9cdcfe}"enumDefs"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#dcdcdc}[],{color}
{color:#9cdcfe}"structDefs"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#dcdcdc}[],{color}
{color:#9cdcfe}"classificationDefs"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#dcdcdc}[],{color}
{color:#9cdcfe}"entityDefs"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#dcdcdc}[{color}
{color:#d4d4d4} {color}{color:#dcdcdc}{{color}
{color:#9cdcfe}"category"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"ENTITY"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"createdBy"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"admin"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"updatedBy"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"admin"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"createTime"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#b5cea8}1537261952180{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"updateTime"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#b5cea8}1537262097732{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"version"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#b5cea8}3{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"name"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"CustomEntity1"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"description"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"CustomEntity1"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"typeVersion"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"1.4"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"attributeDefs"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#dcdcdc}[{color}
{color:#d4d4d4} {color}{color:#dcdcdc}{{color}
{color:#9cdcfe}"name"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"scores"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"typeName"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"int"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"isOptional"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}true{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"cardinality"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"SINGLE"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"valuesMinCount"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#b5cea8}0{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"valuesMaxCount"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#b5cea8}1{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"isUnique"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}false{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"isIndexable"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}false{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"includeInNotification"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}false{color}
{color:#dcdcdc}},{color}
{color:#d4d4d4} {color}{color:#dcdcdc}{{color}
{color:#9cdcfe}"name"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"place"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"typeName"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"string"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"isOptional"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}true{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"cardinality"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"SINGLE"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"valuesMinCount"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#b5cea8}0{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"valuesMaxCount"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#b5cea8}1{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"isUnique"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}false{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"isIndexable"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}false{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"includeInNotification"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
[jira] [Created] (ATLAS-4725) UI (Swagger): API request not being fired correctly for uniqueAttribute related EntityREST APIs
Rahul Kurup created ATLAS-4725:
--
Summary: UI (Swagger): API request not being fired correctly for
uniqueAttribute related EntityREST APIs
Key: ATLAS-4725
URL: https://issues.apache.org/jira/browse/ATLAS-4725
Project: Atlas
Issue Type: Bug
Reporter: Rahul Kurup
There are two issues in the EntityREST APIs section in the Swagger UI given
under the API Documentation link.
1. The APIs are not sanitized properly when fired from the Swagger API page and
always throws an error. It occurs in the following uniqueAttribute related APIs:
DELETE /v2/entity/uniqueAttribute/type/\{typeName}
GET /v2/entity/uniqueAttribute/type/\{typeName}
PUT /v2/entity/uniqueAttribute/type/\{typeName}
DELETE
/v2/entity/uniqueAttribute/type/\{typeName}/classification/\{classificationName}
POST /v2/entity/uniqueAttribute/type/\{typeName}/classifications
PUT /v2/entity/uniqueAttribute/type/\{typeName}/classifications
GET /v2/entity/uniqueAttribute/type/\{typeName}/header
DELETE /v2/entity/uniqueAttribute/type/\{typeName}/labels
POST /v2/entity/uniqueAttribute/type/\{typeName}/labels
PUT /v2/entity/uniqueAttribute/type/\{typeName}/labels
2. It is not possible to pass a valid request to these APIs in the API page:
/v2/entity/uniqueAttribute/type/\{typeName}/classification/\{classificationName}
/v2/entity/uniqueAttribute/type/\{typeName}/classifications
/v2/entity/uniqueAttribute/type/\{typeName}/classifications
/v2/entity/uniqueAttribute/type/\{typeName}/header
/v2/entity/uniqueAttribute/type/\{typeName}/labels
This is because the property attribute and value is improperly added in the
wrong position in the header for these APIs when the request is fired from the
API page.
The positioning of the key-value pair has to be fixed, and it would be better
to have a dedicated field for specifying the property name and value for the
uniqueAttribute APIs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4719) Atlas - Upgrade Swagger to the latest version.
[ https://issues.apache.org/jira/browse/ATLAS-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17655242#comment-17655242 ] Rahul Kurup commented on ATLAS-4719: +1 > Atlas - Upgrade Swagger to the latest version. > -- > > Key: ATLAS-4719 > URL: https://issues.apache.org/jira/browse/ATLAS-4719 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4719-UI-Upgrade-Swagger-to-the-latest-version.patch > > > Please upgrade this package to the latest version -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4715) UI: Option to delete assigned term from deleted entity is visible.
[ https://issues.apache.org/jira/browse/ATLAS-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17640377#comment-17640377 ] Rahul Kurup commented on ATLAS-4715: +1 > UI: Option to delete assigned term from deleted entity is visible. > -- > > Key: ATLAS-4715 > URL: https://issues.apache.org/jira/browse/ATLAS-4715 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: > 0001-ATLAS-4715-UI-Option-to-delete-assigned-term-from-de.patch > > > If a deleted entity is assigned a term and then deleted, viewing the entity > with 'historical entities' filter enabled not only shows the assigned term > but also the option to remove said term from the entity. This goes against > the condition that assigned terms and classifications should not be removed > from deleted entities. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4715) UI: Option to delete assigned term from deleted entity is visible.
Rahul Kurup created ATLAS-4715: -- Summary: UI: Option to delete assigned term from deleted entity is visible. Key: ATLAS-4715 URL: https://issues.apache.org/jira/browse/ATLAS-4715 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup If a deleted entity is assigned a term and then deleted, viewing the entity with 'historical entities' filter enabled not only shows the assigned term but also the option to remove said term from the entity. This goes against the condition that assigned terms and classifications should not be removed from deleted entities. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4710) [Atlas][UI]Relationship Attribute Filter button keeps loading
[ https://issues.apache.org/jira/browse/ATLAS-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17631048#comment-17631048 ] Rahul Kurup commented on ATLAS-4710: +1 > [Atlas][UI]Relationship Attribute Filter button keeps loading > - > > Key: ATLAS-4710 > URL: https://issues.apache.org/jira/browse/ATLAS-4710 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 3.0.0, 2.3.0 >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4710-UI-Relationship-Attribute-Filter-button-k.patch > > > The Relationship Attribute Filter button is stuck on the loading icon loop > and filters don't appear. > This is working on the Entity Attribute Filter button and via the API call, > but not on the UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4695) UI: Clicking on term assigned to deleted entity in entity details page results in error
[ https://issues.apache.org/jira/browse/ATLAS-4695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628692#comment-17628692 ] Rahul Kurup commented on ATLAS-4695: +1 > UI: Clicking on term assigned to deleted entity in entity details page > results in error > --- > > Key: ATLAS-4695 > URL: https://issues.apache.org/jira/browse/ATLAS-4695 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4695-UI-Clicking-on-term-assigned-to-deleted-e.patch > > > Steps: > # Create an entity > # Assign a term to entity > # Delete that entity > # Go to that entity's entity details page. > # Click on the term box link in the Terms section of entity details page. > You will see that an error message "Given instance guid undefined is > invalid/not found" is displayed and page goes into endless loading. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4661) UI: Switching within Terms page does not land you in the same tab.
[ https://issues.apache.org/jira/browse/ATLAS-4661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17626482#comment-17626482 ] Rahul Kurup commented on ATLAS-4661: +1 > UI: Switching within Terms page does not land you in the same tab. > -- > > Key: ATLAS-4661 > URL: https://issues.apache.org/jira/browse/ATLAS-4661 > Project: Atlas > Issue Type: Sub-task >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > Attachments: > 0001-ATLAS-4693-ATLAS-4661-ATLAS-4613-UI-Switching-within.patch > > > There are 4 tabs in a Terms Page: Entities, Properties, Classifications and > Related Terms. When the user attempts to switch from any of these tabs to the > other UI, the user always lands on the Entities tab. > This is inconsistent with the behaviour in Entities Details page where on UI > switch the user lands in the corresponding tab within the target UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4695) UI: Clicking on term assigned to deleted entity in entity details page results in error
Rahul Kurup created ATLAS-4695: -- Summary: UI: Clicking on term assigned to deleted entity in entity details page results in error Key: ATLAS-4695 URL: https://issues.apache.org/jira/browse/ATLAS-4695 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Steps: # Create an entity # Assign a term to entity # Delete that entity # Go to that entity's entity details page. # Click on the term box link in the Terms section of entity details page. You will see that an error message "Given instance guid undefined is invalid/not found" is displayed and page goes into endless loading. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4693) UI: Redundant basic search filters in Terms page and classification page on both UIs
Rahul Kurup created ATLAS-4693: -- Summary: UI: Redundant basic search filters in Terms page and classification page on both UIs Key: ATLAS-4693 URL: https://issues.apache.org/jira/browse/ATLAS-4693 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup 1. When you view the terms page on either UI, you can see that the 'Exclude Sub-classifications' and 'Exclude sub-types' basic search filters are present, which are redundant as you are searching by term. They should be removed from the Terms page to avoid confusion. 2. Classification page in new UI should have the "Exclude Sub-types" filter removed so as to maintain consistency. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4689) UI: Basic Search: Invalid attributes passed in request
[ https://issues.apache.org/jira/browse/ATLAS-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17624875#comment-17624875 ] Rahul Kurup commented on ATLAS-4689: +1 > UI: Basic Search: Invalid attributes passed in request > --- > > Key: ATLAS-4689 > URL: https://issues.apache.org/jira/browse/ATLAS-4689 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Pinal Shah >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4689-UI-Basic-Search-Invalid-attributes-passed.patch > > > Steps to Reproduce: > Basic Search: > # Search with typeName hive_db, attribute filter clusterName. > # Search with typeName hive_table > The request sent will have the 'clusterName' in 'attributes' field. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4686) UI improvements to support Atlas Relationship Search
[ https://issues.apache.org/jira/browse/ATLAS-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17619460#comment-17619460 ] Rahul Kurup commented on ATLAS-4686: +1 > UI improvements to support Atlas Relationship Search > > > Key: ATLAS-4686 > URL: https://issues.apache.org/jira/browse/ATLAS-4686 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0, 2.3.0 >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4686-UI-improvements-to-support-Atlas-Relation.patch > > > *Current Working :* > Atlas is entirely entity-based – it is not possible to search for > relationships. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4610) ATLAS UI : Classification/ Term: Add parent name for classification & name
[ https://issues.apache.org/jira/browse/ATLAS-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17616175#comment-17616175 ] Rahul Kurup commented on ATLAS-4610: +1 > ATLAS UI : Classification/ Term: Add parent name for classification & name > --- > > Key: ATLAS-4610 > URL: https://issues.apache.org/jira/browse/ATLAS-4610 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: ATLAS-4610_ATLAS-4655.patch > > > The classification and term assignment section should display their parents > if present, on the detail page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4610) ATLAS UI : Classification/ Term: Add parent name for classification & name
[ https://issues.apache.org/jira/browse/ATLAS-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17615725#comment-17615725 ] Rahul Kurup commented on ATLAS-4610: +1 > ATLAS UI : Classification/ Term: Add parent name for classification & name > --- > > Key: ATLAS-4610 > URL: https://issues.apache.org/jira/browse/ATLAS-4610 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: 0001-ATLAS-4610_UI_Patch_Classification-Term.patch > > > The classification and term assignment section should display their parents > if present, on the detail page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4673) Atlas UI- Upgrade jquery-ui to 1.13.2
[ https://issues.apache.org/jira/browse/ATLAS-4673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17603984#comment-17603984 ] Rahul Kurup commented on ATLAS-4673: +1 > Atlas UI- Upgrade jquery-ui to 1.13.2 > - > > Key: ATLAS-4673 > URL: https://issues.apache.org/jira/browse/ATLAS-4673 > Project: Atlas > Issue Type: Improvement >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: 0001-ATLAS-4673-UI-Upgrade-jquery-ui-to-1.13.2.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4672) Python Client: Unable to create an entity with classification assigned to it.
Rahul Kurup created ATLAS-4672: -- Summary: Python Client: Unable to create an entity with classification assigned to it. Key: ATLAS-4672 URL: https://issues.apache.org/jira/browse/ATLAS-4672 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup It is possible to create an entity using 'create_entity' method and it is possible to assign a classification to the entity using 'add_classifications_by_guid' in separate API calls, but it is impossible to do both in the same API call using the method 'create_entity'. It is possible to simultaneously create an entity and assign a classification to it in the CURL version of the REST API call, so the same should be made possible in the Python Client method as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4660) UI: Deleting businesss metadata attribute values with spaces in their key names results in unexpected behaviour
[ https://issues.apache.org/jira/browse/ATLAS-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598166#comment-17598166 ] Rahul Kurup commented on ATLAS-4660: +1 > UI: Deleting businesss metadata attribute values with spaces in their key > names results in unexpected behaviour > --- > > Key: ATLAS-4660 > URL: https://issues.apache.org/jira/browse/ATLAS-4660 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > Attachments: > 0001-ATLAS-4660-UI-Deleting-businesss-metadata-attribute-.patch > > > # Create a business metadata with an attribute such that it has a space in > its name. (eg: 'testBusinessMetadata' with attribute 'test attribute1'). > Create at least two more attributes for the business metadata. > # Go to the entity details page for that entity with these business metadata > attributes and assign values to the above attributes. > # After the page refreshes, pick that attribute with the space with its name > and delete its value. > You will notice that on clicking the delete button for the first time, > nothing happens. When the delete button is clicked again,then all of the > other assigned values are wiped out along with the targeted attribute. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4610) ATLAS UI : Classification/ Term: Add parent name for classification & name
[ https://issues.apache.org/jira/browse/ATLAS-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17585321#comment-17585321 ] Rahul Kurup commented on ATLAS-4610: +1 > ATLAS UI : Classification/ Term: Add parent name for classification & name > --- > > Key: ATLAS-4610 > URL: https://issues.apache.org/jira/browse/ATLAS-4610 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4610-ATLAS-UI-Classification-Term-Add-parent-n.patch > > > The classification and term assignment section should display their parents > if present, on the detail page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4667) Cannot create subclassification using subTypes field.
Rahul Kurup created ATLAS-4667:
--
Summary: Cannot create subclassification using subTypes field.
Key: ATLAS-4667
URL: https://issues.apache.org/jira/browse/ATLAS-4667
Project: Atlas
Issue Type: Bug
Reporter: Rahul Kurup
If I create two classifications and then attempt to create parent-child
relation between them, the following request, where the superType is specified,
works:
{{{}}
{{ "classificationDefs": [}}
{{ {}}
{{ "category": "CLASSIFICATION",}}
{{ "guid": "39a8acf8-0d4c-427d-94f1-e677487a9423",}}
{{ "createdBy": "admin",}}
{{ "updatedBy": "admin",}}
{{ "createTime": 1661496389541,}}
{{ "updateTime": 1661496389541,}}
{{ "version": 1,}}
{{ "name": "TCLASS",}}
{{ "description": "TCLASSS",}}
{{ "typeVersion": "1.0",}}
{{ "attributeDefs": [],}}
{{ "superTypes": ["XCLASS1"],}}
{{ "entityTypes": [],}}
{{ "subTypes": []}}
{{ }}}
{{ ],}}
{{ "entityDefs": [],}}
{{ "enumDefs": [],}}
{{ "structDefs": []}}
{{}}}
But this request to create the sub-classification link,where subType is
specified instead, doesnt work:
{{{}}
{{ "classificationDefs": [}}
{{ {}}
{{ "category": "CLASSIFICATION",}}
{{ "guid": "39a8acf8-0d4c-427d-94f1-e677487a9423",}}
{{ "createdBy": "admin",}}
{{ "updatedBy": "admin",}}
{{ "createTime": 1661496389541,}}
{{ "updateTime": 1661496389541,}}
{{ "version": 1,}}
{{ "name": "XCLASS1",}}
{{ "description": "XCLASSS",}}
{{ "typeVersion": "1.0",}}
{{ "attributeDefs": [],}}
{{ "superTypes": [],}}
{{ "entityTypes": [],}}
{{ "subTypes": ["TCLASS"]}}
{{ }}}
{{ ],}}
{{ "entityDefs": [],}}
{{ "enumDefs": [],}}
{{ "structDefs": []}}
{{}}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4666) Intermittently, the audits for creation of hive_db registered are different than expected.
Rahul Kurup created ATLAS-4666: -- Summary: Intermittently, the audits for creation of hive_db registered are different than expected. Key: ATLAS-4666 URL: https://issues.apache.org/jira/browse/ATLAS-4666 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Sometimes, when I create a hive database and then check for the same in Atlas, the audits tab shows unexpected audit entries: it shows two audit entries both marked as 'Entity Updated' rather than showing a 'Entity Created' audit entry anywhere. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4611) Atlas UI: Add text-editor for string attribute value of Business Metadata and for "description" field while creating Classification and Business Metadata.
[ https://issues.apache.org/jira/browse/ATLAS-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584169#comment-17584169 ] Rahul Kurup commented on ATLAS-4611: +1 > Atlas UI: Add text-editor for string attribute value of Business Metadata and > for "description" field while creating Classification and Business Metadata. > -- > > Key: ATLAS-4611 > URL: https://issues.apache.org/jira/browse/ATLAS-4611 > Project: Atlas > Issue Type: Improvement >Reporter: Prasad P. Pawar >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4611-UI-Add-text-editor-for-string-attribute-v.patch > > > 1) Business Metadata ( Entity Detail Page) > String attribute value should have text editor. > 2) Classification and Business Metadata > The "Description" field should have text editor as it has been implemented > for the Glossary section. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4613) UI: After selecting checkboxes from Term page and then switching UI, page gets stuck in endless loading state.
[ https://issues.apache.org/jira/browse/ATLAS-4613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583488#comment-17583488 ] Rahul Kurup commented on ATLAS-4613: +1 > UI: After selecting checkboxes from Term page and then switching UI, page > gets stuck in endless loading state. > -- > > Key: ATLAS-4613 > URL: https://issues.apache.org/jira/browse/ATLAS-4613 > Project: Atlas > Issue Type: Sub-task >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > Attachments: > 0001-ATLAS-4613-UI-After-selecting-checkboxes-from-Term-p.patch > > > Steps: > # In classic UI, Create a term > # Assign a term to any entity > # Go to the term page > # Mark all the checkboxes > # Perform switch to new UI > You will notice that the page gets stuck in endless loading accompanied by an > error : "expected type AtlasGlossaryCategory; found AtlasGlossaryTerm". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4661) UI: Switching within Terms page does not land you in the same tab.
Rahul Kurup created ATLAS-4661: -- Summary: UI: Switching within Terms page does not land you in the same tab. Key: ATLAS-4661 URL: https://issues.apache.org/jira/browse/ATLAS-4661 Project: Atlas Issue Type: Sub-task Reporter: Rahul Kurup There are 4 tabs in a Terms Page: Entities, Properties, Classifications and Related Terms. When the user attempts to switch from any of these tabs to the other UI, the user always lands on the Entities tab. This is inconsistent with the behaviour in Entities Details page where on UI switch the user lands in the corresponding tab within the target UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4660) UI: Deleting businesss metadata attribute values with spaces in their key names results in unexpected behaviour
[ https://issues.apache.org/jira/browse/ATLAS-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4660: --- Summary: UI: Deleting businesss metadata attribute values with spaces in their key names results in unexpected behaviour (was: UI: Deleting businesss metadata attribute values with spaces in their key namess results in unexpected behaviour) > UI: Deleting businesss metadata attribute values with spaces in their key > names results in unexpected behaviour > --- > > Key: ATLAS-4660 > URL: https://issues.apache.org/jira/browse/ATLAS-4660 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Priority: Minor > > # Create a business metadata with an attribute such that it has a space in > its name. (eg: 'testBusinessMetadata' with attribute 'test attribute1'). > Create at least two more attributes for the business metadata. > # Go to the entity details page for that entity with these business metadata > attributes and assign values to the above attributes. > # After the page refreshes, pick that attribute with the space with its name > and delete its value. > You will notice that on clicking the delete button for the first time, > nothing happens. When the delete button is clicked again,then all of the > other assigned values are wiped out along with the targeted attribute. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4660) UI: Deleting businesss metadata attribute values with spaces in their key namess results in unexpected behaviour
Rahul Kurup created ATLAS-4660: -- Summary: UI: Deleting businesss metadata attribute values with spaces in their key namess results in unexpected behaviour Key: ATLAS-4660 URL: https://issues.apache.org/jira/browse/ATLAS-4660 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup # Create a business metadata with an attribute such that it has a space in its name. (eg: 'testBusinessMetadata' with attribute 'test attribute1'). Create at least two more attributes for the business metadata. # Go to the entity details page for that entity with these business metadata attributes and assign values to the above attributes. # After the page refreshes, pick that attribute with the space with its name and delete its value. You will notice that on clicking the delete button for the first time, nothing happens. When the delete button is clicked again,then all of the other assigned values are wiped out along with the targeted attribute. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4600) UI: Add classification button appears for deleted hive_columns in Schema Tab of hive_table entity details page.
[ https://issues.apache.org/jira/browse/ATLAS-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17569819#comment-17569819 ] Rahul Kurup commented on ATLAS-4600: +1 > UI: Add classification button appears for deleted hive_columns in Schema Tab > of hive_table entity details page. > --- > > Key: ATLAS-4600 > URL: https://issues.apache.org/jira/browse/ATLAS-4600 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: > 0001-ATLAS-4600-UI-Add-classification-button-appears-for-.patch, > image-2022-05-06-11-11-37-012.png > > > As you can see from the screenshot below, if you navigate to a deleted > hive_table entity's Schema tab, it is possible to get an 'add classification' > button. > > !image-2022-05-06-11-11-37-012.png|width=762,height=465! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4611) Atlas UI: Add text-editor for string attribute value of Business Metadata and for "description" field while creating Classification and Business Metadata.
[ https://issues.apache.org/jira/browse/ATLAS-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17569820#comment-17569820 ] Rahul Kurup commented on ATLAS-4611: +1 > Atlas UI: Add text-editor for string attribute value of Business Metadata and > for "description" field while creating Classification and Business Metadata. > -- > > Key: ATLAS-4611 > URL: https://issues.apache.org/jira/browse/ATLAS-4611 > Project: Atlas > Issue Type: Improvement >Reporter: Prasad P. Pawar >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4611-UI-Add-text-editor-for-string-attribute-v.patch > > > 1) Business Metadata ( Entity Detail Page) > String attribute value should have text editor. > 2) Classification and Business Metadata > The "Description" field should have text editor as it has been implemented > for the Glossary section. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ATLAS-4600) UI: Add classification button appears for deleted hive_columns in Schema Tab of hive_table entity details page.
[ https://issues.apache.org/jira/browse/ATLAS-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17540034#comment-17540034 ] Rahul Kurup edited comment on ATLAS-4600 at 7/19/22 9:02 AM: - -A similar issue can be observed in the Tables tab of any hive_db entity where on selecting the check all button the Classification and Terms buttons appear for historical entities.- On review, it has been found that this particular issue does not exist. Please disregard the comment. was (Author: rahul_fi): A similar issue can be observed in the Tables tab of any hive_db entity where on selecting the check all button the Classification and Terms buttons appear for historical entities. > UI: Add classification button appears for deleted hive_columns in Schema Tab > of hive_table entity details page. > --- > > Key: ATLAS-4600 > URL: https://issues.apache.org/jira/browse/ATLAS-4600 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Major > Attachments: image-2022-05-06-11-11-37-012.png > > > As you can see from the screenshot below, if you navigate to a deleted > hive_table entity's Schema tab, it is possible to get an 'add classification' > button. > > !image-2022-05-06-11-11-37-012.png|width=762,height=465! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4613) UI: After selecting checkboxes from Term page and then switching UI, page gets stuck in endless loading state.
[ https://issues.apache.org/jira/browse/ATLAS-4613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup reassigned ATLAS-4613: -- Assignee: Prasad P. Pawar (was: Rahul Kurup) > UI: After selecting checkboxes from Term page and then switching UI, page > gets stuck in endless loading state. > -- > > Key: ATLAS-4613 > URL: https://issues.apache.org/jira/browse/ATLAS-4613 > Project: Atlas > Issue Type: Sub-task >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > > Steps: > # In classic UI, Create a term > # Assign a term to any entity > # Go to the term page > # Mark all the checkboxes > # Perform switch to new UI > You will notice that the page gets stuck in endless loading accompanied by an > error : "expected type AtlasGlossaryCategory; found AtlasGlossaryTerm". -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (ATLAS-4613) UI: After selecting checkboxes from Term page and then switching UI, page gets stuck in endless loading state.
[ https://issues.apache.org/jira/browse/ATLAS-4613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup reassigned ATLAS-4613: -- Assignee: Rahul Kurup > UI: After selecting checkboxes from Term page and then switching UI, page > gets stuck in endless loading state. > -- > > Key: ATLAS-4613 > URL: https://issues.apache.org/jira/browse/ATLAS-4613 > Project: Atlas > Issue Type: Sub-task >Reporter: Rahul Kurup >Assignee: Rahul Kurup >Priority: Minor > > Steps: > # In classic UI, Create a term > # Assign a term to any entity > # Go to the term page > # Mark all the checkboxes > # Perform switch to new UI > You will notice that the page gets stuck in endless loading accompanied by an > error : "expected type AtlasGlossaryCategory; found AtlasGlossaryTerm". -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (ATLAS-4613) UI: After selecting checkboxes from Term page and then switching UI, page gets stuck in endless loading state.
Rahul Kurup created ATLAS-4613: -- Summary: UI: After selecting checkboxes from Term page and then switching UI, page gets stuck in endless loading state. Key: ATLAS-4613 URL: https://issues.apache.org/jira/browse/ATLAS-4613 Project: Atlas Issue Type: Sub-task Reporter: Rahul Kurup Steps: # In classic UI, Create a term # Assign a term to any entity # Go to the term page # Mark all the checkboxes # Perform switch to new UI You will notice that the page gets stuck in endless loading accompanied by an error : "expected type AtlasGlossaryCategory; found AtlasGlossaryTerm". -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (ATLAS-4583) UI: When there is no data, error is encountered on switching UI at a specific page
[ https://issues.apache.org/jira/browse/ATLAS-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541291#comment-17541291 ] Rahul Kurup commented on ATLAS-4583: +1 > UI: When there is no data, error is encountered on switching UI at a specific > page > -- > > Key: ATLAS-4583 > URL: https://issues.apache.org/jira/browse/ATLAS-4583 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 3.0.0, 2.3.0 >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > Attachments: > 0001-ATLAS-4583-UI-When-there-is-no-data-error-is-encount.patch > > > In old UI, when there is no data for classification and glossary, if the user > selects either 'tree' toggle in classification or 'category' toggle in > glossary section, and then attempts to switch UI, they get an endless loading > page with the following error message: > viewType=tree: Unknown/invalid classification > or > Given instance guid viewType=category is invalid/not found > > 23/05/22: Also found an issue where after creating a classification, > switching from Classic UI to new UI and then deleting the classification > results in an endless loading within the deletion dialog box. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (ATLAS-4583) UI: When there is no data, error is encountered on switching UI at a specific page
[ https://issues.apache.org/jira/browse/ATLAS-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4583: --- Description: In old UI, when there is no data for classification and glossary, if the user selects either 'tree' toggle in classification or 'category' toggle in glossary section, and then attempts to switch UI, they get an endless loading page with the following error message: viewType=tree: Unknown/invalid classification or Given instance guid viewType=category is invalid/not found 23/05/22: Also found an issue where after creating a classification, switching from Classic UI to new UI and then deleting the classification results in an endless loading within the deletion dialog box. was: In old UI, when there is no data for classification and glossary, if the user selects either 'tree' toggle in classification or 'category' toggle in glossary section, and then attempts to switch UI, they get an endless loading page with the following error message: viewType=tree: Unknown/invalid classification or Given instance guid viewType=category is invalid/not found > UI: When there is no data, error is encountered on switching UI at a specific > page > -- > > Key: ATLAS-4583 > URL: https://issues.apache.org/jira/browse/ATLAS-4583 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > Attachments: > 0001-ATLAS-4583-UI-When-there-is-no-data-error-is-encount.patch > > > In old UI, when there is no data for classification and glossary, if the user > selects either 'tree' toggle in classification or 'category' toggle in > glossary section, and then attempts to switch UI, they get an endless loading > page with the following error message: > viewType=tree: Unknown/invalid classification > or > Given instance guid viewType=category is invalid/not found > > 23/05/22: Also found an issue where after creating a classification, > switching from Classic UI to new UI and then deleting the classification > results in an endless loading within the deletion dialog box. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (ATLAS-4600) UI: Add classification button appears for deleted hive_columns in Schema Tab of hive_table entity details page.
[ https://issues.apache.org/jira/browse/ATLAS-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17540034#comment-17540034 ] Rahul Kurup commented on ATLAS-4600: A similar issue can be observed in the Tables tab of any hive_db entity where on selecting the check all button the Classification and Terms buttons appear for historical entities. > UI: Add classification button appears for deleted hive_columns in Schema Tab > of hive_table entity details page. > --- > > Key: ATLAS-4600 > URL: https://issues.apache.org/jira/browse/ATLAS-4600 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Major > Attachments: image-2022-05-06-11-11-37-012.png > > > As you can see from the screenshot below, if you navigate to a deleted > hive_table entity's Schema tab, it is possible to get an 'add classification' > button. > > !image-2022-05-06-11-11-37-012.png|width=762,height=465! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (ATLAS-4600) UI: Add classification button appears for deleted hive_columns in Schema Tab of hive_table entity details page.
Rahul Kurup created ATLAS-4600: -- Summary: UI: Add classification button appears for deleted hive_columns in Schema Tab of hive_table entity details page. Key: ATLAS-4600 URL: https://issues.apache.org/jira/browse/ATLAS-4600 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Attachments: image-2022-05-06-11-11-37-012.png As you can see from the screenshot below, if you navigate to a deleted hive_table entity's Schema tab, it is possible to get an 'add classification' button. !image-2022-05-06-11-11-37-012.png|width=762,height=465! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (ATLAS-4588) UI: Lineage Settings window appears unexpectedly and won't close.
Rahul Kurup created ATLAS-4588: -- Summary: UI: Lineage Settings window appears unexpectedly and won't close. Key: ATLAS-4588 URL: https://issues.apache.org/jira/browse/ATLAS-4588 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Attachments: lineage_settings_freeze.mp4 If a user performs the navigations as demonstrated in the attached video within a lineage tab, it results in the lineage Settings window suddenly appearing and this window can't be closed. [^lineage_settings_freeze.mp4] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (ATLAS-4587) UI: When you choose "Hide Process", using lineage search shows unexpected behaviour.
[ https://issues.apache.org/jira/browse/ATLAS-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4587: --- Description: # In a lineage page for an entity, select Hide Process # Click on the magnifying icon in the lineage window (search) and select a process from the list. You will see that the view moves to a location where the process used to be displayed. In this scenario, ideally the processes should be removed from the list of searchable elements after the Hide Process option is selected. EDIT: The same issue occurs when 'Hide Deleted Entity' is selected. was: # In a lineage page for an entity, select Hide Process # Click on the magnifying icon in the lineage window (search) and select a process from the list. You will see that the view moves to a location where the process used to be displayed. In this scenario, ideally the processes should be removed from the list of searchable elements after the Hide Process option is selected. > UI: When you choose "Hide Process", using lineage search shows unexpected > behaviour. > - > > Key: ATLAS-4587 > URL: https://issues.apache.org/jira/browse/ATLAS-4587 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Priority: Minor > > # In a lineage page for an entity, select Hide Process > # Click on the magnifying icon in the lineage window (search) and select a > process from the list. > You will see that the view moves to a location where the process used to be > displayed. In this scenario, ideally the processes should be removed from the > list of searchable elements after the Hide Process option is selected. > > EDIT: The same issue occurs when 'Hide Deleted Entity' is selected. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (ATLAS-4587) UI: When you choose "Hide Process", using lineage search shows unexpected behaviour.
Rahul Kurup created ATLAS-4587: -- Summary: UI: When you choose "Hide Process", using lineage search shows unexpected behaviour. Key: ATLAS-4587 URL: https://issues.apache.org/jira/browse/ATLAS-4587 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup # In a lineage page for an entity, select Hide Process # Click on the magnifying icon in the lineage window (search) and select a process from the list. You will see that the view moves to a location where the process used to be displayed. In this scenario, ideally the processes should be removed from the list of searchable elements after the Hide Process option is selected. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (ATLAS-4585) Incorrect hyphenation of words in property description field
[ https://issues.apache.org/jira/browse/ATLAS-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17525423#comment-17525423 ] Rahul Kurup commented on ATLAS-4585: +1 > Incorrect hyphenation of words in property description field > > > Key: ATLAS-4585 > URL: https://issues.apache.org/jira/browse/ATLAS-4585 > Project: Atlas > Issue Type: Bug >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Minor > Attachments: > 0001-ATLAS-4585-Incorrect-hyphenation-of-words-in-propert.patch, > 0001-ATLAS-4585-UI-Incorrect-hyphenation-of-words-in-prop.patch, > screenshot-1.png > > > Hyphenation of words is incorrect. > Ex (see attached picture) : > "Abonnement et" should be : > "abonnement > et" > but we get > "abonnement e" > "t" > => Hyphenation happens at the middle of the word "et" -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (ATLAS-4584) Possible classification scenarios requiring checks.
Rahul Kurup created ATLAS-4584:
--
Summary: Possible classification scenarios requiring checks.
Key: ATLAS-4584
URL: https://issues.apache.org/jira/browse/ATLAS-4584
Project: Atlas
Issue Type: Bug
Reporter: Rahul Kurup
{*}Scenario 1{*}:
1. User creates Classification 1 with attributes A(string), B(boolean), C(int).
2. User creates Classification 2 with the same attributes as above: A,B and C.
3. User creates Classification 3 with its own unique attribute D, but also
makes Classification 1 and Classification 2 as its super-classifications.
4. The resulting classification has A,B,C and D as its attributes but it is
unknown which parent’s attributes are being used.
*Possible negative consequence:* It is unclear to the user as to what is the
flow of inheritance of attributes being followed.
{*}Expected result{*}: A negative error message indicating that parents possess
similar attribute names, denying the action. Or alternately, show in the
typedef of the classification, which attributes come from which parent
classifications.
{*}Scenario 2{*}:
1. User creates Classification 1 with attribute A of type string.
2. User creates Classification 2 with the same attribute name A but with type
boolean.
3. User creates Classification 3 with Classification 1 and Classification 2 as
its super-classifications.
4. The resulting attribute has Classification 2’s A boolean attribute, but not
Classification 1’s A string attribute
{*}Possible negative consequence{*}:Because there is no check in this scenario,
it may be possible that in a particularly large classification hierarchy, a
parent classification may end up cannibalizing another parent classification's
attributes because of their similar names and despite their different types.
This would be unknown to the user creating the child classification from these
parent classifications.
*Expected result:* A negative error message indicating that parents possess
similar attribute names, denying the action. Or find a way to have both
attributes co-exist.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (ATLAS-4582) UI: Unexpected behaviour on specific navigation from full screen lineage
[ https://issues.apache.org/jira/browse/ATLAS-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4582: --- Parent: ATLAS-4581 Issue Type: Sub-task (was: Bug) > UI: Unexpected behaviour on specific navigation from full screen lineage > > > Key: ATLAS-4582 > URL: https://issues.apache.org/jira/browse/ATLAS-4582 > Project: Atlas > Issue Type: Sub-task >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > > Steps: > 1. Go to an entity details page of an entity that has a lineage > 2. From there, go to Lineage tab > 3. Click on full screen button in lineage window > 4. From there, click on the back button of the browser. > You will notice that no navigation action seems to occur, even though the URL > changes in the browser. But on clicking a second time, user is navigated to > the search results page. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ATLAS-4582) UI: Unexpected behaviour on specific navigation from full screen lineage
[ https://issues.apache.org/jira/browse/ATLAS-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522082#comment-17522082 ] Rahul Kurup commented on ATLAS-4582: Done > UI: Unexpected behaviour on specific navigation from full screen lineage > > > Key: ATLAS-4582 > URL: https://issues.apache.org/jira/browse/ATLAS-4582 > Project: Atlas > Issue Type: Sub-task >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > > Steps: > 1. Go to an entity details page of an entity that has a lineage > 2. From there, go to Lineage tab > 3. Click on full screen button in lineage window > 4. From there, click on the back button of the browser. > You will notice that no navigation action seems to occur, even though the URL > changes in the browser. But on clicking a second time, user is navigated to > the search results page. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4583) UI: When there is no data, error is encountered on switching UI at a specific page
Rahul Kurup created ATLAS-4583: -- Summary: UI: When there is no data, error is encountered on switching UI at a specific page Key: ATLAS-4583 URL: https://issues.apache.org/jira/browse/ATLAS-4583 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup In old UI, when there is no data for classification and glossary, if the user selects either 'tree' toggle in classification or 'category' toggle in glossary section, and then attempts to switch UI, they get an endless loading page with the following error message: viewType=tree: Unknown/invalid classification or Given instance guid viewType=category is invalid/not found -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4582) UI: Unexpected behaviour on specific navigation from full screen lineage
Rahul Kurup created ATLAS-4582: -- Summary: UI: Unexpected behaviour on specific navigation from full screen lineage Key: ATLAS-4582 URL: https://issues.apache.org/jira/browse/ATLAS-4582 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Steps: 1. Go to an entity details page of an entity that has a lineage 2. From there, go to Lineage tab 3. Click on full screen button in lineage window 4. From there, click on the back button of the browser. You will notice that no navigation action seems to occur, even though the URL changes in the browser. But on clicking a second time, user is navigated to the search results page. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4581) UI: Page freezes on specific navigation
Rahul Kurup created ATLAS-4581: -- Summary: UI: Page freezes on specific navigation Key: ATLAS-4581 URL: https://issues.apache.org/jira/browse/ATLAS-4581 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Steps: 1. Go to an entity details page of an entity that has a lineage 2. Go to any details tab (Relationship, Classifications, Audits, or Tasks) 3. From there, go to Lineage tab 4. Click on full screen button in lineage window 5. From there, click on the back button of the browser. You will observe that no element of the page is clickable. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ATLAS-4580) Atlas UI- Upgrade jquery-ui to 1.13.0+
[ https://issues.apache.org/jira/browse/ATLAS-4580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519561#comment-17519561 ] Rahul Kurup commented on ATLAS-4580: +1 > Atlas UI- Upgrade jquery-ui to 1.13.0+ > -- > > Key: ATLAS-4580 > URL: https://issues.apache.org/jira/browse/ATLAS-4580 > Project: Atlas > Issue Type: Improvement >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: 0001-Atlas-UI-Upgrade-jQuery-ui-to-1.13.0.patch > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ATLAS-3985) Not able to assign classification with mandatory attribute of type "array"
[
https://issues.apache.org/jira/browse/ATLAS-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17510223#comment-17510223
]
Rahul Kurup commented on ATLAS-3985:
+1
> Not able to assign classification with mandatory attribute of type
> "array"
> ---
>
> Key: ATLAS-3985
> URL: https://issues.apache.org/jira/browse/ATLAS-3985
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core, atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments:
> 0001-ATLAS-3985-3-Not-able-to-assign-classification-with-.patch,
> 0001-ATLAS-3985-UI-1-Not-able-to-assign-classification-wi.patch,
> 0001-ATLAS-3985-UI-2-Not-able-to-assign-classification-wi.patch, Screenshot
> 2020-10-07 at 1.40.43 PM.png, Screenshot 2020-10-07 at 1.41.17 PM.png
>
>
> Create a classification that has mandatory attribute of type
> "*array*" via REST api
> {code:java|title=Create classification with payload:}
> {
> "enumDefs": [],
> "structDefs": [],
> "classificationDefs": [
> {
> "category": "CLASSIFICATION",
> "guid": "8996315b-b5fe-48c6-b9d0-4668fhkfd21af",
> "createdBy": "hrt_qa",
> "updatedBy": "hrt_qa",
> "createTime": 1602057743077,
> "updateTime": 1602057743077,
> "version": 1,
> "name": "read_auth_test_tag1",
> "description": "read_auth_test_tag1",
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "type_long_min",
> "typeName": "long",
> "isOptional": true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1,
> "isUnique": false,
> "isIndexable": false
> },
> {
> "name":"type_arr_list",
> "typeName":"array",
> "isOptional":false,
> "cardinality":"LIST",
> "valuesMinCount":1,
> "valuesMaxCount":2147483647,
> "isUnique":false,
> "isIndexable":false
> },
> {
> "name":"type_set",
> "typeName":"array",
> "isOptional":false,
> "cardinality":"SET",
> "valuesMinCount":1,
> "valuesMaxCount":2147483647,
> "isUnique":false,
> "isIndexable":false
> }
> ],
> "superTypes": [],
> "entityTypes": [],
> "subTypes": []
> }
> ],
> "entityDefs": [],
> "relationshipDefs": [],
> "businessMetadataDefs": []
> }
> {code}
> Assign the same to an entity.
> The assignment fails as the attributes of type "array" are not
> visible on UI
> {code:java|title=error message}
> {"errorCode":"ATLAS-400-00-01A",
> "errorMessage":"invalid parameters: read_auth_test_tag1.type_arr_list:
> mandatory attribute value missing in type read_auth_test_tag1"}
> {code}
>
> The assignment fails via both UI and rest api.
> In UI creation of attribute of such a type is not allowed but via rest api it
> is possible.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (ATLAS-4553) UI: Columns added in search results page gets reset after clicking refresh button
[ https://issues.apache.org/jira/browse/ATLAS-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506859#comment-17506859 ] Rahul Kurup commented on ATLAS-4553: +1 for updated patch. > UI: Columns added in search results page gets reset after clicking refresh > button > - > > Key: ATLAS-4553 > URL: https://issues.apache.org/jira/browse/ATLAS-4553 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > Attachments: > 0001-ATLAS-4553-Classic-UI-Columns-added-in-search-result.patch, > 0001-ATLAS-4553-Columns-added-in-search-results-page-gets.patch > > > In this scenario, after a successful query made in basic search, the user > decides to add more search result columns. If after this step the user clicks > on the refresh button, then those added columns disappear. This behaviour is > not observed in the new UI. > Edit: There is a related issue where the classification attributes don't > appear after being selected when you do a basic search for the classification > alone (present in both classic and new UI). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ATLAS-4553) UI: Columns added in search results page gets reset after clicking refresh button
[ https://issues.apache.org/jira/browse/ATLAS-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4553: --- Summary: UI: Columns added in search results page gets reset after clicking refresh button (was: UI: (Classic) Columns added in search results page gets reset after clicking refresh button) > UI: Columns added in search results page gets reset after clicking refresh > button > - > > Key: ATLAS-4553 > URL: https://issues.apache.org/jira/browse/ATLAS-4553 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > Attachments: > 0001-ATLAS-4553-Classic-UI-Columns-added-in-search-result.patch, > 0001-ATLAS-4553-Columns-added-in-search-results-page-gets.patch > > > In this scenario, after a successful query made in basic search, the user > decides to add more search result columns. If after this step the user clicks > on the refresh button, then those added columns disappear. This behaviour is > not observed in the new UI. > Edit: There is a related issue where the classification attributes don't > appear after being selected when you do a basic search for the classification > alone (present in both classic and new UI). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ATLAS-4553) UI: (Classic) Columns added in search results page gets reset after clicking refresh button
[ https://issues.apache.org/jira/browse/ATLAS-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4553: --- Description: In this scenario, after a successful query made in basic search, the user decides to add more search result columns. If after this step the user clicks on the refresh button, then those added columns disappear. This behaviour is not observed in the new UI. Edit: There is a related issue where the classification attributes don't appear after being selected when you do a basic search for the classification alone (present in both classic and new UI). was: In this scenario, after a successful query made in basic search, the user decides to add more search result columns. If after this step the user clicks on the refresh button, then those added columns disappear. This behaviour is not observed in the new UI. Edit: There is a related issue where the classification attributes don't appear after being selected when you do a basic search for the classification alone. > UI: (Classic) Columns added in search results page gets reset after clicking > refresh button > --- > > Key: ATLAS-4553 > URL: https://issues.apache.org/jira/browse/ATLAS-4553 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > Attachments: > 0001-ATLAS-4553-Classic-UI-Columns-added-in-search-result.patch, > 0001-ATLAS-4553-Columns-added-in-search-results-page-gets.patch > > > In this scenario, after a successful query made in basic search, the user > decides to add more search result columns. If after this step the user clicks > on the refresh button, then those added columns disappear. This behaviour is > not observed in the new UI. > Edit: There is a related issue where the classification attributes don't > appear after being selected when you do a basic search for the classification > alone (present in both classic and new UI). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ATLAS-4553) UI: (Classic) Columns added in search results page gets reset after clicking refresh button
[ https://issues.apache.org/jira/browse/ATLAS-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4553: --- Description: In this scenario, after a successful query made in basic search, the user decides to add more search result columns. If after this step the user clicks on the refresh button, then those added columns disappear. This behaviour is not observed in the new UI. Edit: There is a related issue where the classification attributes don't appear after being selected when you do a basic search for the classification alone. was:In this scenario, after a successful query made in basic search, the user decides to add more search result columns. If after this step the user clicks on the refresh button, then those added columns disappear. This behaviour is not observed in the new UI. > UI: (Classic) Columns added in search results page gets reset after clicking > refresh button > --- > > Key: ATLAS-4553 > URL: https://issues.apache.org/jira/browse/ATLAS-4553 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > Attachments: > 0001-ATLAS-4553-Classic-UI-Columns-added-in-search-result.patch > > > In this scenario, after a successful query made in basic search, the user > decides to add more search result columns. If after this step the user clicks > on the refresh button, then those added columns disappear. This behaviour is > not observed in the new UI. > Edit: There is a related issue where the classification attributes don't > appear after being selected when you do a basic search for the classification > alone. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ATLAS-4513) UI: (Classic) Delete Term option appears even though there is no term to delete.
[ https://issues.apache.org/jira/browse/ATLAS-4513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17492547#comment-17492547 ] Rahul Kurup commented on ATLAS-4513: +1 > UI: (Classic) Delete Term option appears even though there is no term to > delete. > > > Key: ATLAS-4513 > URL: https://issues.apache.org/jira/browse/ATLAS-4513 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > Attachments: > 0001-ATLAS-4513-Delete-Term-option-appears-even-though-th.patch, > deletetermbug.jpg > > > * Steps: > In old UI, > 1. Create Glossary > 2. Immediately click on that area of the created glossary where the ellipsis > menu normally appears so that the drop-down menu appears. > > You will see that the 'Delete Term' option appears as shown in the attached > screenshot. > !deletetermbug.jpg! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ATLAS-4553) UI: (Classic) Columns added in search results page gets reset after clicking refresh button
[ https://issues.apache.org/jira/browse/ATLAS-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491970#comment-17491970 ] Rahul Kurup commented on ATLAS-4553: +1 > UI: (Classic) Columns added in search results page gets reset after clicking > refresh button > --- > > Key: ATLAS-4553 > URL: https://issues.apache.org/jira/browse/ATLAS-4553 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > Attachments: > 0001-ATLAS-4553-Classic-UI-Columns-added-in-search-result.patch > > > In this scenario, after a successful query made in basic search, the user > decides to add more search result columns. If after this step the user clicks > on the refresh button, then those added columns disappear. This behaviour is > not observed in the new UI. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4553) UI: (Classic) Columns added in search results page gets reset after clicking refresh button
Rahul Kurup created ATLAS-4553: -- Summary: UI: (Classic) Columns added in search results page gets reset after clicking refresh button Key: ATLAS-4553 URL: https://issues.apache.org/jira/browse/ATLAS-4553 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup In this scenario, after a successful query made in basic search, the user decides to add more search result columns. If after this step the user clicks on the refresh button, then those added columns disappear. This behaviour is not observed in the new UI. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ATLAS-4532) UI: Statistics button not working in new UI
[ https://issues.apache.org/jira/browse/ATLAS-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17486223#comment-17486223 ] Rahul Kurup commented on ATLAS-4532: +1 > UI: Statistics button not working in new UI > --- > > Key: ATLAS-4532 > URL: https://issues.apache.org/jira/browse/ATLAS-4532 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Attachments: > 0001-ATLAS-4532-1-UI-Statistics-button-not-working-in-new.patch > > > Clicking the statistics button on the new UI doesn't generate the statistics > window. It works fine in the old UI. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ATLAS-3985) Not able to assign classification with mandatory attribute of type "array"
[
https://issues.apache.org/jira/browse/ATLAS-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485784#comment-17485784
]
Rahul Kurup commented on ATLAS-3985:
+1
> Not able to assign classification with mandatory attribute of type
> "array"
> ---
>
> Key: ATLAS-3985
> URL: https://issues.apache.org/jira/browse/ATLAS-3985
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core, atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments:
> 0001-ATLAS-3985-UI-1-Not-able-to-assign-classification-wi.patch,
> 0001-ATLAS-3985-UI-2-Not-able-to-assign-classification-wi.patch, Screenshot
> 2020-10-07 at 1.40.43 PM.png, Screenshot 2020-10-07 at 1.41.17 PM.png
>
>
> Create a classification that has mandatory attribute of type
> "*array*" via REST api
> {code:java|title=Create classification with payload:}
> {
> "enumDefs": [],
> "structDefs": [],
> "classificationDefs": [
> {
> "category": "CLASSIFICATION",
> "guid": "8996315b-b5fe-48c6-b9d0-4668fhkfd21af",
> "createdBy": "hrt_qa",
> "updatedBy": "hrt_qa",
> "createTime": 1602057743077,
> "updateTime": 1602057743077,
> "version": 1,
> "name": "read_auth_test_tag1",
> "description": "read_auth_test_tag1",
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "type_long_min",
> "typeName": "long",
> "isOptional": true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1,
> "isUnique": false,
> "isIndexable": false
> },
> {
> "name":"type_arr_list",
> "typeName":"array",
> "isOptional":false,
> "cardinality":"LIST",
> "valuesMinCount":1,
> "valuesMaxCount":2147483647,
> "isUnique":false,
> "isIndexable":false
> },
> {
> "name":"type_set",
> "typeName":"array",
> "isOptional":false,
> "cardinality":"SET",
> "valuesMinCount":1,
> "valuesMaxCount":2147483647,
> "isUnique":false,
> "isIndexable":false
> }
> ],
> "superTypes": [],
> "entityTypes": [],
> "subTypes": []
> }
> ],
> "entityDefs": [],
> "relationshipDefs": [],
> "businessMetadataDefs": []
> }
> {code}
> Assign the same to an entity.
> The assignment fails as the attributes of type "array" are not
> visible on UI
> {code:java|title=error message}
> {"errorCode":"ATLAS-400-00-01A",
> "errorMessage":"invalid parameters: read_auth_test_tag1.type_arr_list:
> mandatory attribute value missing in type read_auth_test_tag1"}
> {code}
>
> The assignment fails via both UI and rest api.
> In UI creation of attribute of such a type is not allowed but via rest api it
> is possible.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (ATLAS-4547) Classification behaviour is not working as expected (overwriting attribute values and deleted entities)
Rahul Kurup created ATLAS-4547:
--
Summary: Classification behaviour is not working as expected
(overwriting attribute values and deleted entities)
Key: ATLAS-4547
URL: https://issues.apache.org/jira/browse/ATLAS-4547
Project: Atlas
Issue Type: Bug
Reporter: Rahul Kurup
Scenario 1:
If a classification attribute of either type 'string' or type 'array'
is marked as isOptional : false, then that field is a mandatory field and has
to have some value filled in when assigned to an entity.
Assume that an a classification with such an attribute is already assigned to
an entity. Then it is observed that if a request is fired using the PUT request
to the API {{api/atlas/v2/entity/guid//classifications}} such that the
value of that classification attribute is a blank value, it is accepted and the
attribute value becomes blank even though it is a mandatory attribute.
Scenario 2:
It is possible to assign a classification to an entity deleted by a request to
the bulk delete API {{api/atlas/v2/entity/bulk}} or a DELETE request to the
entity API {{api/atlas/v2/entity/guid/}}, even though this behaviour is not
allowed by the Atlas UI.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (ATLAS-4544) UI:(Classic)Disallow continuous clicking of refresh button for Basic search
[ https://issues.apache.org/jira/browse/ATLAS-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17484727#comment-17484727 ] Rahul Kurup commented on ATLAS-4544: +1 > UI:(Classic)Disallow continuous clicking of refresh button for Basic search > --- > > Key: ATLAS-4544 > URL: https://issues.apache.org/jira/browse/ATLAS-4544 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Farhan Khan >Priority: Minor > Attachments: > 0001-ATLAS-4544-Disallow-continuous-clicking-of-refresh-b.patch > > > It is noticed that user is able to continuously click the refresh button, > which leads to "Invalid expression" error messages occurring. It would be > better to block this scenario by adding a delay between each click. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ATLAS-4541) UI: Improve user error message text when search queries abruptly fail
[
https://issues.apache.org/jira/browse/ATLAS-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17484726#comment-17484726
]
Rahul Kurup commented on ATLAS-4541:
+1
> UI: Improve user error message text when search queries abruptly fail
> -
>
> Key: ATLAS-4541
> URL: https://issues.apache.org/jira/browse/ATLAS-4541
> Project: Atlas
> Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Farhan Khan
>Priority: Minor
> Attachments:
> 0001-ATLAS-4541-Improve-user-error-message-text-when-sear.patch
>
>
> When user performs an action that causes a search to fail unexpectedly and
> sometimes repeatedly in a short interval, the error message currently
> received ("Invalid Expression") does not make it clear as to what went wrong.
> There should be an error message fix that should make it clear to the user as
> to what happened.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (ATLAS-4541) UI: Improve user error message text when search queries abruptly fail
[
https://issues.apache.org/jira/browse/ATLAS-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Kurup updated ATLAS-4541:
---
Summary: UI: Improve user error message text when search queries abruptly
fail (was: Improve user error message text when search queries abruptly fail)
> UI: Improve user error message text when search queries abruptly fail
> -
>
> Key: ATLAS-4541
> URL: https://issues.apache.org/jira/browse/ATLAS-4541
> Project: Atlas
> Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Farhan Khan
>Priority: Minor
> Attachments:
> 0001-ATLAS-4541-Improve-user-error-message-text-when-sear.patch
>
>
> When user performs an action that causes a search to fail unexpectedly and
> sometimes repeatedly in a short interval, the error message currently
> received ("Invalid Expression") does not make it clear as to what went wrong.
> There should be an error message fix that should make it clear to the user as
> to what happened.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (ATLAS-4544) UI:(Classic)Disallow continuous clicking of refresh button for Basic search
Rahul Kurup created ATLAS-4544: -- Summary: UI:(Classic)Disallow continuous clicking of refresh button for Basic search Key: ATLAS-4544 URL: https://issues.apache.org/jira/browse/ATLAS-4544 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup It is noticed that user is able to continuously click the refresh button, which leads to "Invalid expression" error messages occurring. It would be better to block this scenario by adding a delay between each click. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4541) Improve user error message text when search queries abruptly fail
Rahul Kurup created ATLAS-4541:
--
Summary: Improve user error message text when search queries
abruptly fail
Key: ATLAS-4541
URL: https://issues.apache.org/jira/browse/ATLAS-4541
Project: Atlas
Issue Type: Bug
Reporter: Rahul Kurup
When user performs an action that causes a search to fail unexpectedly and
sometimes repeatedly in a short interval, the error message currently received
("Invalid Expression") does not make it clear as to what went wrong.
There should be an error message fix that should make it clear to the user as
to what happened.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (ATLAS-4533) UI: Triggering a third search with basic search filters does not close the filters window
[
https://issues.apache.org/jira/browse/ATLAS-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17477839#comment-17477839
]
Rahul Kurup commented on ATLAS-4533:
+1
> UI: Triggering a third search with basic search filters does not close the
> filters window
> -
>
> Key: ATLAS-4533
> URL: https://issues.apache.org/jira/browse/ATLAS-4533
> Project: Atlas
> Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Farhan Khan
>Priority: Minor
> Attachments:
> 0001-ATLAS-4533-Triggering-a-third-search-with-basic-sear.patch
>
>
> Steps:
> 1. Execute a basic search with at least one filter successfully.
> 2.After step1, add a search filter group with a different parameter and
> execute the search. It should be successful
> 3. Go to search filters and try to repeat the search.
> You will see that nothing happens on clicking the search button. Console
> shows the following error:
> {{Uncaught TypeError: value is undefined
> conditionalURl
> http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:280
> X Underscore
> conditionalURl
> http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:269
> conditionalURl
> http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:270
> X Underscore
> conditionalURl
> http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:269
> generateUrl
> http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:288
> okAttrFilterButton
> http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:292
> openAttrFilter
> http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:279
> Backbone 4
> click .ok http://localhost:21000/js/modules/Modal.js?bust=1641881782114:12
> Underscore 3
> jQuery 8
> Backbone 6
> initialize
> http://localhost:21000/js/views/search/SearchQueryView.js?bust=1641881782114:17
> Backbone 5
> openAttrFilter
> http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:267
> execCb
> http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> check
> http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> enable
> http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> init
> http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> f http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> setTimeout handler*req.nextTick<
> http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> f http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> openAttrFilter
> http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:266
>
> http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:34
> Underscore 3
> jQuery }}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (ATLAS-4533) UI: Triggering a third search with basic search filters does not close the filters window
[
https://issues.apache.org/jira/browse/ATLAS-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Kurup updated ATLAS-4533:
---
Summary: UI: Triggering a third search with basic search filters does not
close the filters window (was: UI: Triggering a second seach with basic search
filters does not close the filters window)
> UI: Triggering a third search with basic search filters does not close the
> filters window
> -
>
> Key: ATLAS-4533
> URL: https://issues.apache.org/jira/browse/ATLAS-4533
> Project: Atlas
> Issue Type: Bug
>Reporter: Rahul Kurup
>Priority: Minor
>
> Steps:
> 1. Execute a basic search with at least one filter successfully.
> 2.After step1, add a search filter group with a different parameter and
> execute the search. It should be successful
> 3. Go to search filters and try to repeat the search.
> You will see that nothing happens on clicking the search button. Console
> shows the following error:
> {{Uncaught TypeError: value is undefined
> conditionalURl
> http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:280
> X Underscore
> conditionalURl
> http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:269
> conditionalURl
> http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:270
> X Underscore
> conditionalURl
> http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:269
> generateUrl
> http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:288
> okAttrFilterButton
> http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:292
> openAttrFilter
> http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:279
> Backbone 4
> click .ok http://localhost:21000/js/modules/Modal.js?bust=1641881782114:12
> Underscore 3
> jQuery 8
> Backbone 6
> initialize
> http://localhost:21000/js/views/search/SearchQueryView.js?bust=1641881782114:17
> Backbone 5
> openAttrFilter
> http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:267
> execCb
> http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> check
> http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> enable
> http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> init
> http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> f http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> setTimeout handler*req.nextTick<
> http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> f http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> openAttrFilter
> http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:266
>
> http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:34
> Underscore 3
> jQuery }}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (ATLAS-4533) UI: Triggering a second seach with basic search filters does not close the filters window
Rahul Kurup created ATLAS-4533:
--
Summary: UI: Triggering a second seach with basic search filters
does not close the filters window
Key: ATLAS-4533
URL: https://issues.apache.org/jira/browse/ATLAS-4533
Project: Atlas
Issue Type: Bug
Reporter: Rahul Kurup
Steps:
1. Execute a basic search with at least one filter successfully.
2.After step1, add a search filter group with a different parameter and execute
the search. It should be successful
3. Go to search filters and try to repeat the search.
You will see that nothing happens on clicking the search button. Console shows
the following error:
{{Uncaught TypeError: value is undefined
conditionalURl
http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:280
X Underscore
conditionalURl
http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:269
conditionalURl
http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:270
X Underscore
conditionalURl
http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:269
generateUrl
http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:288
okAttrFilterButton
http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:292
openAttrFilter
http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:279
Backbone 4
click .ok http://localhost:21000/js/modules/Modal.js?bust=1641881782114:12
Underscore 3
jQuery 8
Backbone 6
initialize
http://localhost:21000/js/views/search/SearchQueryView.js?bust=1641881782114:17
Backbone 5
openAttrFilter
http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:267
execCb
http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
check
http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
enable
http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
init
http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
f http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
setTimeout handler*req.nextTick<
http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
f http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
openAttrFilter
http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:266
http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:34
Underscore 3
jQuery }}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (ATLAS-4532) Statistics button not working in new UI
Rahul Kurup created ATLAS-4532: -- Summary: Statistics button not working in new UI Key: ATLAS-4532 URL: https://issues.apache.org/jira/browse/ATLAS-4532 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Clicking the statistics button on the new UI doesn't generate the statistics window. It works fine in the old UI. -- This message was sent by Atlassian Jira (v8.20.1#820001)
