Re: Facing issue while installing apache atlas
could you add more details? like logs what command etc On Thu, Nov 23, 2023 at 2:15 AM Syed Shahid wrote: >
[jira] [Commented] (ATLAS-4488) Readme for Run / build atlas website
[ https://issues.apache.org/jira/browse/ATLAS-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17446853#comment-17446853 ] Keval Bhatt commented on ATLAS-4488: Looks like node start is not working anymore created the Jira for it will fix it 2 - 3 days https://issues.apache.org/jira/browse/ATLAS-4490 > Readme for Run / build atlas website > > > Key: ATLAS-4488 > URL: https://issues.apache.org/jira/browse/ATLAS-4488 > Project: Atlas > Issue Type: Task > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Minor > Attachments: ATLAS-4488.patch > > > Add the details about how to build the atlas website and run it in the dev > environment. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (ATLAS-4488) Readme for Run / build atlas website
[ https://issues.apache.org/jira/browse/ATLAS-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17446851#comment-17446851 ] Keval Bhatt edited comment on ATLAS-4488 at 11/20/21, 6:14 PM: --- I have added the readme to run/build the doc, can someone review it. CC [~mad...@apache.org] [~ayubpathan] [~jayendrap] [~prasadpp13] was (Author: kevalbhatt18): CC [~mad...@apache.org] [~ayubpathan] [~jayendrap] [~prasadpp13] > Readme for Run / build atlas website > > > Key: ATLAS-4488 > URL: https://issues.apache.org/jira/browse/ATLAS-4488 > Project: Atlas > Issue Type: Task > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Minor > Attachments: ATLAS-4488.patch > > > Add the details about how to build the atlas website and run it in the dev > environment. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (ATLAS-4488) Readme for Run / build atlas website
[ https://issues.apache.org/jira/browse/ATLAS-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17446851#comment-17446851 ] Keval Bhatt edited comment on ATLAS-4488 at 11/20/21, 6:13 PM: --- CC [~mad...@apache.org] [~ayubpathan] [~jayendrap] [~prasadpp13] was (Author: kevalbhatt18): CC [~mad...@apache.org] [~ayubpathan] [~jayendrap] > Readme for Run / build atlas website > > > Key: ATLAS-4488 > URL: https://issues.apache.org/jira/browse/ATLAS-4488 > Project: Atlas > Issue Type: Task > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Minor > Attachments: ATLAS-4488.patch > > > Add the details about how to build the atlas website and run it in the dev > environment. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ATLAS-4488) Readme for Run / build atlas website
[ https://issues.apache.org/jira/browse/ATLAS-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-4488: --- Summary: Readme for Run / build atlas website (was: Readme for build atlas website) > Readme for Run / build atlas website > > > Key: ATLAS-4488 > URL: https://issues.apache.org/jira/browse/ATLAS-4488 > Project: Atlas > Issue Type: Task > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Minor > Attachments: ATLAS-4488.patch > > > Add the details about how to build the atlas website and run it in the dev > environment. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ATLAS-4488) Readme for build atlas website
[ https://issues.apache.org/jira/browse/ATLAS-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-4488: --- Attachment: ATLAS-4488.patch > Readme for build atlas website > -- > > Key: ATLAS-4488 > URL: https://issues.apache.org/jira/browse/ATLAS-4488 > Project: Atlas > Issue Type: Task > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Minor > Attachments: ATLAS-4488.patch > > > Add the details about how to build the atlas website and run it in the dev > environment. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4490) docz node dev server is not working
Keval Bhatt created ATLAS-4490: -- Summary: docz node dev server is not working Key: ATLAS-4490 URL: https://issues.apache.org/jira/browse/ATLAS-4490 Project: Atlas Issue Type: Task Reporter: Keval Bhatt Assignee: Keval Bhatt -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4489) Enable search in the Atlas website
Keval Bhatt created ATLAS-4489: -- Summary: Enable search in the Atlas website Key: ATLAS-4489 URL: https://issues.apache.org/jira/browse/ATLAS-4489 Project: Atlas Issue Type: Task Reporter: Keval Bhatt Assignee: Keval Bhatt -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ATLAS-4488) Readme for build atlas website
[ https://issues.apache.org/jira/browse/ATLAS-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-4488: --- Description: Add the details about how to build the atlas website and run it in the dev environment. > Readme for build atlas website > -- > > Key: ATLAS-4488 > URL: https://issues.apache.org/jira/browse/ATLAS-4488 > Project: Atlas > Issue Type: Task > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Minor > > Add the details about how to build the atlas website and run it in the dev > environment. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4488) Readme for build atlas website
Keval Bhatt created ATLAS-4488: -- Summary: Readme for build atlas website Key: ATLAS-4488 URL: https://issues.apache.org/jira/browse/ATLAS-4488 Project: Atlas Issue Type: Task Reporter: Keval Bhatt Assignee: Keval Bhatt -- This message was sent by Atlassian Jira (v8.20.1#820001)
Re: npm error building dashboardv2
What is the maven version?
On Tue, Nov 16, 2021 at 8:34 AM BOOZ 樂 wrote:
> I'm wondering if someone could help me figure out how to finish my Atlas
> compile.
>
> I'm following the build instructions here: https://github.com/apache/atlas
> and using the 2.2.0 source from
>
> https://www.apache.org/dyn/closer.cgi/atlas/2.2.0/apache-atlas-2.2.0-sources.tar.gz
>
> I had to change the buildtools version in pom.xml to 0.8.1 to make it this
> far, as discovered here:
>
> https://ducfilan.wordpress.com/2021/07/29/installing-apache-atlas-and-its-awkward/
>
> Here's the error I'm encountering when it gets to dashboardv2:
>
> [INFO] --- frontend-maven-plugin:1.4:npm (npm install) @ atlas-dashboardv2
> ---
>
>
> [INFO] Running 'npm install' in
> /x/gardem/ATLAS/apache-atlas-sources-2.2.0/dashboardv2/target
>
>
>
> [ERROR] internal/modules/cjs/loader.js:984
>
>
>
> [ERROR] throw err;
>
>
>
> [ERROR] ^
>
>
>
> [ERROR]
>
>
>
> [ERROR] Error: Cannot find module 'semver'
>
>
>
> [ERROR] Require stack:
>
>
>
> [ERROR] -
>
> /x/gardem/ATLAS/apache-atlas-sources-2.2.0/dashboardv2/target/node/node_modules/npm/lib/utils/unsupported.js
>
>
> [ERROR] -
>
> /x/gardem/ATLAS/apache-atlas-sources-2.2.0/dashboardv2/target/node/node_modules/npm/bin/npm-cli.js
>
>
>
> [ERROR] at Function.Module._resolveFilename
> (internal/modules/cjs/loader.js:981:15)
>
>
> [ERROR] at Function.Module._load
> (internal/modules/cjs/loader.js:863:27)
>
>
> [ERROR] at Module.require (internal/modules/cjs/loader.js:1043:19)
>
>
>
> [ERROR] at require (internal/modules/cjs/helpers.js:77:18)
>
>
>
> [ERROR] at Object.
>
> (/x/gardem/ATLAS/apache-atlas-sources-2.2.0/dashboardv2/target/node/node_modules/npm/lib/utils/unsupported.js:2:14)
>
>
> [ERROR] at Module._compile (internal/modules/cjs/loader.js:1157:30)
>
>
>
> [ERROR] at Object.Module._extensions..js
> (internal/modules/cjs/loader.js:1177:10)
>
>
> [ERROR] at Module.load (internal/modules/cjs/loader.js:1001:32)
>
>
>
> [ERROR] at Function.Module._load
> (internal/modules/cjs/loader.js:900:14)
>
>
> [ERROR] at Module.require (internal/modules/cjs/loader.js:1043:19) {
>
>
>
> [ERROR] code: 'MODULE_NOT_FOUND',
>
>
>
> [ERROR] requireStack: [
>
>
>
> [ERROR]
>
> '/x/gardem/ATLAS/apache-atlas-sources-2.2.0/dashboardv2/target/node/node_modules/npm/lib/utils/unsupported.js',
>
>
> [ERROR]
>
> '/x/gardem/ATLAS/apache-atlas-sources-2.2.0/dashboardv2/target/node/node_modules/npm/bin/npm-cli.js'
>
>
> [ERROR] ]
>
>
>
> [ERROR] }
>
>
>
> [INFO]
>
>
>
>
> [INFO] Reactor Summary:
>
>
>
> [INFO]
>
>
>
> [INFO] Apache Atlas Server Build Tools SUCCESS [
> 0.719 s]
>
>
> [INFO] apache-atlas 2.2.0 . SUCCESS [
> 5.147 s]
>
>
> [INFO] Apache Atlas Integration ... SUCCESS [
> 20.095 s]
>
>
> [INFO] Apache Atlas Test Utility Tools SUCCESS [
> 8.901 s]
>
>
> [INFO] Apache Atlas Common SUCCESS [
> 9.003 s]
>
>
> [INFO] Apache Atlas Client SUCCESS [
> 0.358 s]
>
>
> [INFO] atlas-client-common SUCCESS [
> 4.538 s]
>
>
> [INFO] atlas-client-v1 SUCCESS [
> 5.281 s]
>
>
> [INFO] Apache Atlas Server API SUCCESS [
> 6.837 s]
>
>
> [INFO] Apache Atlas Notification .. SUCCESS [
> 11.072 s]
>
>
> [INFO] atlas-client-v2 SUCCESS [
> 4.899 s]
>
>
> [INFO] Apache Atlas Graph Database Projects ... SUCCESS [
> 0.356 s]
>
>
> [INFO] Apache Atlas Graph Database API SUCCESS [
> 4.534 s]
>
>
> [INFO] Graph Database Common Code . SUCCESS [
> 3.700 s]
>
>
> [INFO] Apache Atlas JanusGraph-HBase2 Module .. SUCCESS [
> 5.433 s]
>
>
> [INFO] Apache Atlas JanusGraph DB Impl SUCCESS [
> 14.073 s]
>
>
> [INFO] Apache Atlas Graph DB Dependencies . SUCCESS [
> 1.375 s]
>
>
> [INFO] Apache Atlas Authorization . SUCCESS [
> 7.535 s]
>
>
> [INFO] Apache Atlas Repository SUCCESS [
> 34.258 s]
>
>
> [INFO] Apache Atlas UI FAILURE [
> 13.342 s]
> [INFO] Apache Atlas New UI SKIPPED
>
>
>
> [INFO] Apache Atlas Web Application ... SKIPPED
> [INFO] Apache Atlas Documentation . SKIPPED
> [INFO] Apache Atlas FileSystem Model .. SKIPPED
> [INFO] Apache Atlas Plugin Classloader SKIPPED
> [INFO] Apache Atlas Hive Bridge Shim .. SKIPPED
> [INFO] Apache Atlas Hive Bridge ... SKIPPED
> [INFO] Apache Atlas Falcon Bridge Shim SKIPPED
> [INFO]
Fwd: Modify the port number（21000）, unable to access
-- Forwarded message - From: Lonely <1084689...@qq.com.invalid> Date: Tue, Sep 7, 2021 at 11:00 AM Subject: Modify the port number（21000）, unable to access To: dev Hello！I want to change the default port number (originally 21000) to 8001, but I can't access it after startup. What should I do？My modifications include: 1.vim atlas_config.py DEFAULT_ATLAS_HTTP_PORT="8001" 2.vi atlas-application.properties atlas.server.http.port=8001 atlas.rest.address=http://localhost:8001 atlas.server.address.id1=localhost:8001 How to solve it？
[jira] [Updated] (ATLAS-4116) UI should not allow the user to create a glossary with blank(" ") name
[
https://issues.apache.org/jira/browse/ATLAS-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt updated ATLAS-4116:
---
Fix Version/s: 2.2.0
> UI should not allow the user to create a glossary with blank(" ") name
> --
>
> Key: ATLAS-4116
> URL: https://issues.apache.org/jira/browse/ATLAS-4116
> Project: Atlas
> Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Prasad P. Pawar
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments:
> 0001-ATLAS-4116-UI-UI-should-not-allow-the-user-to-create.patch,
> 0001-ATLAS-4116-UI-V1-UI-should-not-allow-the-user-to-cre.patch,
> 0001-Atlas-4166-UI-V2-UI-should-not-allow-the-user-to-cre.patch,
> Atlas-4116Fix.png
>
>
> When just space is input the "Create" button is not enabled, but when the
> space is selected, then the "Create" button is enabled and User is allowed to
> click on "*Create*".
> This results in un-necessary failures
> *
> {"errorCode":"ATLAS-400-00-079","errorMessage":"Attributes qualifiedName and
> name are missing. Failed to derive a unique name for Glossary"}
> *
> It is better to not allow clicking on "Create" for such an input via UI
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4116) UI should not allow the user to create a glossary with blank(" ") name
[
https://issues.apache.org/jira/browse/ATLAS-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt updated ATLAS-4116:
---
Fix Version/s: 3.0.0
> UI should not allow the user to create a glossary with blank(" ") name
> --
>
> Key: ATLAS-4116
> URL: https://issues.apache.org/jira/browse/ATLAS-4116
> Project: Atlas
> Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Prasad P. Pawar
>Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> 0001-ATLAS-4116-UI-UI-should-not-allow-the-user-to-create.patch,
> 0001-ATLAS-4116-UI-V1-UI-should-not-allow-the-user-to-cre.patch,
> 0001-Atlas-4166-UI-V2-UI-should-not-allow-the-user-to-cre.patch,
> Atlas-4116Fix.png
>
>
> When just space is input the "Create" button is not enabled, but when the
> space is selected, then the "Create" button is enabled and User is allowed to
> click on "*Create*".
> This results in un-necessary failures
> *
> {"errorCode":"ATLAS-400-00-079","errorMessage":"Attributes qualifiedName and
> name are missing. Failed to derive a unique name for Glossary"}
> *
> It is better to not allow clicking on "Create" for such an input via UI
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4116) UI should not allow the user to create a glossary with blank(" ") name
[
https://issues.apache.org/jira/browse/ATLAS-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17277131#comment-17277131
]
Keval Bhatt commented on ATLAS-4116:
Thanks [~prasadpp13] for the updated patch
[^0001-ATLAS-4116-UI-V1-UI-should-not-allow-the-user-to-cre.patch].
Few review comments, do we need filter inside the binding event?
what if we only bind the *keyup* and with *modal-body input* so that "this"
will point to input directly.
and the below call is the global pointer better to avoid it when we are
creating a common listener.
{code:java}
$(".modal-footer").find('button.ok').removeAttr("disabled");
{code}
Example:
{code:java}
$('body').on('keyup', '.modal-body input', function (e) {
var $this = $(this);
if (this.getAttribute('placeholder') &&
this.getAttribute('placeholder').indexOf('require') >= 0) {
return (this.value.trim() == "");
}
var $footerButton = $this.parent(".modal").find('.modal-footer
button.ok');
if (requiredInputField.length > 0) {
$footerButton.attr("disabled", "true");
} else {
$footerButton.removeAttr("disabled");
}
});
{code}
> UI should not allow the user to create a glossary with blank(" ") name
> --
>
> Key: ATLAS-4116
> URL: https://issues.apache.org/jira/browse/ATLAS-4116
> Project: Atlas
> Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments:
> 0001-ATLAS-4116-UI-UI-should-not-allow-the-user-to-create.patch,
> 0001-ATLAS-4116-UI-V1-UI-should-not-allow-the-user-to-cre.patch,
> Atlas-4116Fix.png
>
>
> When just space is input the "Create" button is not enabled, but when the
> space is selected, then the "Create" button is enabled and User is allowed to
> click on "*Create*".
> This results in un-necessary failures
> *
> {"errorCode":"ATLAS-400-00-079","errorMessage":"Attributes qualifiedName and
> name are missing. Failed to derive a unique name for Glossary"}
> *
> It is better to not allow clicking on "Create" for such an input via UI
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4116) UI should not allow the user to create a glossary with blank(" ") name
[
https://issues.apache.org/jira/browse/ATLAS-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17276859#comment-17276859
]
Keval Bhatt commented on ATLAS-4116:
Hi [~prasadpp13], Thanks for the patch.
In the new patch
[^0001-ATLAS-4116-UI-UI-should-not-allow-the-user-to-create.patch] I think the
condition is specific to modal so you should bind to specific modal input
Example:
{code:java}
$('body').on('keyup input', '.modal-body input', function(e) {}){code}
or create the custom JQuery event for a specific element which is not bond to
modal only
Example:
{code:java}
$('body').on('keyup input', 'input.no-empty', function(e) {
(true) ? this.trigger("input:success") : this.trigger("input:failed");
}){code}
> UI should not allow the user to create a glossary with blank(" ") name
> --
>
> Key: ATLAS-4116
> URL: https://issues.apache.org/jira/browse/ATLAS-4116
> Project: Atlas
> Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments:
> 0001-ATLAS-4116-UI-UI-should-not-allow-the-user-to-create.patch,
> Atlas-4116Fix.png
>
>
> When just space is input the "Create" button is not enabled, but when the
> space is selected, then the "Create" button is enabled and User is allowed to
> click on "*Create*".
> This results in un-necessary failures
> *
> {"errorCode":"ATLAS-400-00-079","errorMessage":"Attributes qualifiedName and
> name are missing. Failed to derive a unique name for Glossary"}
> *
> It is better to not allow clicking on "Create" for such an input via UI
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4116) UI should not allow the user to create a glossary with blank(" ") name
[
https://issues.apache.org/jira/browse/ATLAS-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17274449#comment-17274449
]
Keval Bhatt commented on ATLAS-4116:
Example:
https://github.com/apache/atlas/blob/master/dashboardv3/public/js/utils/Helper.js#L121
> UI should not allow the user to create a glossary with blank(" ") name
> --
>
> Key: ATLAS-4116
> URL: https://issues.apache.org/jira/browse/ATLAS-4116
> Project: Atlas
> Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments:
> 0001-ATLAS-4116-UI-UI-should-not-allow-the-user-to-create.patch,
> Atlas-4116Fix.png
>
>
> When just space is input the "Create" button is not enabled, but when the
> space is selected, then the "Create" button is enabled and User is allowed to
> click on "*Create*".
> This results in un-necessary failures
> *
> {"errorCode":"ATLAS-400-00-079","errorMessage":"Attributes qualifiedName and
> name are missing. Failed to derive a unique name for Glossary"}
> *
> It is better to not allow clicking on "Create" for such an input via UI
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4116) UI should not allow the user to create a glossary with blank(" ") name
[
https://issues.apache.org/jira/browse/ATLAS-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17274448#comment-17274448
]
Keval Bhatt commented on ATLAS-4116:
[~prasadpp13] is it possible to keep all the "keyup" event in once place?
> UI should not allow the user to create a glossary with blank(" ") name
> --
>
> Key: ATLAS-4116
> URL: https://issues.apache.org/jira/browse/ATLAS-4116
> Project: Atlas
> Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments:
> 0001-ATLAS-4116-UI-UI-should-not-allow-the-user-to-create.patch,
> Atlas-4116Fix.png
>
>
> When just space is input the "Create" button is not enabled, but when the
> space is selected, then the "Create" button is enabled and User is allowed to
> click on "*Create*".
> This results in un-necessary failures
> *
> {"errorCode":"ATLAS-400-00-079","errorMessage":"Attributes qualifiedName and
> name are missing. Failed to derive a unique name for Glossary"}
> *
> It is better to not allow clicking on "Create" for such an input via UI
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4053) UI: Create the shell entity icon.
Keval Bhatt created ATLAS-4053: -- Summary: UI: Create the shell entity icon. Key: ATLAS-4053 URL: https://issues.apache.org/jira/browse/ATLAS-4053 Project: Atlas Issue Type: Sub-task Reporter: Keval Bhatt Assignee: Sameer Shaikh -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4044) There is no way to differentiate between complete (non-shell) and incomplete (shell) entities in UI
[ https://issues.apache.org/jira/browse/ATLAS-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt resolved ATLAS-4044. Fix Version/s: 2.2.0 3.0.0 Resolution: Fixed > There is no way to differentiate between complete (non-shell) and incomplete > (shell) entities in UI > --- > > Key: ATLAS-4044 > URL: https://issues.apache.org/jira/browse/ATLAS-4044 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Umesh Padashetty >Assignee: Deep Singh >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: non-shell entity.png, shell entity.png, > shell_entity_guid.png > > > Previously, we used to show the hourglass icon for the shell entities. But > this behaviour is now removed and we show the same icons for both shell and > non-shell entities. > One difference between these 2 on UI is we show only minimal information for > shell entities, like qualifiedName and typeName. But this not very obvious, > and sometimes it gets very difficult to differentiate between the two. > Attached screenshots. > It is important to note that api/atlas/v2/entity/guid/ > does return "isIncomplete": true. > So, it would be great if we can show isIncomplete parameter on the UI, which > would help the user in differentiation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Review Request 73036: ATLAS-4044: There is no way to differentiate between complete (non-shell) and incomplete (shell) entities in UI
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/73036/#review31 --- Ship it! Ship It! - keval bhatt On Nov. 24, 2020, 7:52 a.m., Deep Singh wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/73036/ > --- > > (Updated Nov. 24, 2020, 7:52 a.m.) > > > Review request for atlas, keval bhatt, Madhan Neethiraj, and Sarath > Subramanian. > > > Bugs: atlas-4044 > https://issues.apache.org/jira/browse/atlas-4044 > > > Repository: atlas > > > Description > --- > > isIncomplete property at the entity level can be used to distinguish between > shell and non-shell entities. > This fix will add 'isIncomplete' property in the technical properties section > of the UI. > > > Diffs > - > > dashboardv2/public/js/views/entity/EntityDetailTableLayoutView.js 0a7d51a78 > dashboardv3/public/js/views/entity/EntityDetailTableLayoutView.js 0a7d51a78 > > > Diff: https://reviews.apache.org/r/73036/diff/1/ > > > Testing > --- > > manual testing was done. > > > Thanks, > > Deep Singh > >
[jira] [Assigned] (ATLAS-4044) There is no way to differentiate between complete (non-shell) and incomplete (shell) entities in UI
[ https://issues.apache.org/jira/browse/ATLAS-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reassigned ATLAS-4044: -- Assignee: Keval Bhatt > There is no way to differentiate between complete (non-shell) and incomplete > (shell) entities in UI > --- > > Key: ATLAS-4044 > URL: https://issues.apache.org/jira/browse/ATLAS-4044 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0 >Reporter: Umesh Padashetty >Assignee: Keval Bhatt >Priority: Major > Attachments: non-shell entity.png, shell entity.png, > shell_entity_guid.png > > > Previously, we used to show the hourglass icon for the shell entities. But > this behaviour is no removed and we show the same icons for both shell and > non-shell entities. > One difference between these 2 on UI is we show only minimal information for > shell entities, like qualifiedName and typeName. But this not very obvious, > and sometimes it gets very difficult to differentiate between the two. > Attached screenshots. > It is important to note that api/atlas/v2/entity/guid/ > does return "isIncomplete": true. > So, it would be great if we can show isIncomplete parameter on the UI, which > would help the user in differentiation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4042) "Error while authentication" grammatical error
[ https://issues.apache.org/jira/browse/ATLAS-4042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235331#comment-17235331 ] Keval Bhatt commented on ATLAS-4042: +1 for the patch > "Error while authentication" grammatical error > -- > > Key: ATLAS-4042 > URL: https://issues.apache.org/jira/browse/ATLAS-4042 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Alasdair Brown >Assignee: Sarath Subramanian >Priority: Trivial > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-4042.001.patch, image-2020-11-18-17-58-00-819.png > > > Just a grammatical error - An error when authenticating generates this error > on the login screen "Error while authentication" should probably be "Error > while authenticating" > !image-2020-11-18-17-58-00-819.png|width=377,height=355! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4042) "Error while authentication" grammatical error
[ https://issues.apache.org/jira/browse/ATLAS-4042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-4042: --- Fix Version/s: 2.2.0 3.0.0 > "Error while authentication" grammatical error > -- > > Key: ATLAS-4042 > URL: https://issues.apache.org/jira/browse/ATLAS-4042 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Alasdair Brown >Assignee: Sarath Subramanian >Priority: Trivial > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-4042.001.patch, image-2020-11-18-17-58-00-819.png > > > Just a grammatical error - An error when authenticating generates this error > on the login screen "Error while authentication" should probably be "Error > while authenticating" > !image-2020-11-18-17-58-00-819.png|width=377,height=355! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4022) Atlas UI: After d3 verion upgrade profile tab not working
[ https://issues.apache.org/jira/browse/ATLAS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-4022: --- Attachment: build_fix.patch > Atlas UI: After d3 verion upgrade profile tab not working > - > > Key: ATLAS-4022 > URL: https://issues.apache.org/jira/browse/ATLAS-4022 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-4022.patch, build_fix.patch > > > The Profile tab only shows loader. > Removing nvd3 dependency from atlas. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4022) Atlas UI: After d3 verion upgrade profile tab not working
[ https://issues.apache.org/jira/browse/ATLAS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-4022: --- Attachment: ATLAS-4022.patch > Atlas UI: After d3 verion upgrade profile tab not working > - > > Key: ATLAS-4022 > URL: https://issues.apache.org/jira/browse/ATLAS-4022 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-4022.patch > > > The Profile tab only shows loader. > Removing nvd3 dependency from atlas. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4022) Atlas UI: After d3 verion upgrade profile tab not working
[ https://issues.apache.org/jira/browse/ATLAS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-4022: --- Attachment: (was: ATLAS-4022.patch) > Atlas UI: After d3 verion upgrade profile tab not working > - > > Key: ATLAS-4022 > URL: https://issues.apache.org/jira/browse/ATLAS-4022 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > > The Profile tab only shows loader. > Removing nvd3 dependency from atlas. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4022) Atlas UI: After d3 verion upgrade profile tab not working
[ https://issues.apache.org/jira/browse/ATLAS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-4022: --- Attachment: ATLAS-4022.patch > Atlas UI: After d3 verion upgrade profile tab not working > - > > Key: ATLAS-4022 > URL: https://issues.apache.org/jira/browse/ATLAS-4022 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-4022.patch > > > The Profile tab only shows loader. > Removing nvd3 dependency from atlas. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4022) Atlas UI: After d3 verion upgrade profile tab not working
[ https://issues.apache.org/jira/browse/ATLAS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-4022: --- Description: The Profile tab only shows loader. Removing nvd3 dependency from atlas. was:The Profile tab only show loader > Atlas UI: After d3 verion upgrade profile tab not working > - > > Key: ATLAS-4022 > URL: https://issues.apache.org/jira/browse/ATLAS-4022 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt >Priority: Major > > The Profile tab only shows loader. > Removing nvd3 dependency from atlas. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4022) Atlas UI: After d3 verion upgrade profile tab not working
[ https://issues.apache.org/jira/browse/ATLAS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-4022: --- Fix Version/s: 2.2.0 3.0.0 > Atlas UI: After d3 verion upgrade profile tab not working > - > > Key: ATLAS-4022 > URL: https://issues.apache.org/jira/browse/ATLAS-4022 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > > The Profile tab only shows loader. > Removing nvd3 dependency from atlas. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4022) Atlas UI: After d3 verion upgrade profile tab not working
[ https://issues.apache.org/jira/browse/ATLAS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reassigned ATLAS-4022: -- Assignee: Keval Bhatt > Atlas UI: After d3 verion upgrade profile tab not working > - > > Key: ATLAS-4022 > URL: https://issues.apache.org/jira/browse/ATLAS-4022 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > > The Profile tab only shows loader. > Removing nvd3 dependency from atlas. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4022) Atlas UI: After d3 verion upgrade profile tab not working
[ https://issues.apache.org/jira/browse/ATLAS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-4022: --- Summary: Atlas UI: After d3 verion upgrade profile tab not working (was: Atlas UI: Profile tab not working) > Atlas UI: After d3 verion upgrade profile tab not working > - > > Key: ATLAS-4022 > URL: https://issues.apache.org/jira/browse/ATLAS-4022 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt >Priority: Major > > The Profile tab only show loader -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4022) Atlas UI: Profile tab not working
[ https://issues.apache.org/jira/browse/ATLAS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-4022: --- Description: The Profile tab only show loader > Atlas UI: Profile tab not working > - > > Key: ATLAS-4022 > URL: https://issues.apache.org/jira/browse/ATLAS-4022 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt >Priority: Major > > The Profile tab only show loader -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4022) Atlas UI: Profile tab not working
Keval Bhatt created ATLAS-4022: -- Summary: Atlas UI: Profile tab not working Key: ATLAS-4022 URL: https://issues.apache.org/jira/browse/ATLAS-4022 Project: Atlas Issue Type: Bug Reporter: Keval Bhatt -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (ATLAS-4021) 'npm install' failed: System Exit error 1
[ https://issues.apache.org/jira/browse/ATLAS-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17230403#comment-17230403 ] Keval Bhatt edited comment on ATLAS-4021 at 11/12/20, 7:46 AM: --- [~batman135] can you please provide the mvn version? and please provide full error log. was (Author: kevalbhatt18): [~batman135] can you please provide the mvn version? > 'npm install' failed: System Exit error 1 > - > > Key: ATLAS-4021 > URL: https://issues.apache.org/jira/browse/ATLAS-4021 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Ajeet Mohan >Priority: Major > > I am installing Apache Atlas on a Linux VM. I followed all of the > instructions on this link > > [https://atlas.apache.org/2.0.0/InstallationSteps.html] > > I got to the step where it says: > mvn clean -DskipTests install > After which I got this error, > > [INFO] Total time: 08:58 min > [INFO] Finished at: 2020-11-11T13:45:20-05:00 > [INFO] > > [ERROR] Failed to execute goal > com.github.eirslett:frontend-maven-plugin:1.4:npm (npm install) on project > atlas-dashboardv2: Failed to run task: 'npm install' failed. > org.apache.commons.exec.ExecuteException: Process exited with an error: 1 > (Exit value: 1) -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn -rf :atlas-dashboardv2 > > I have tried to look online but could not find any way to resolve it. Can > anyone please help me? Thanks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4021) 'npm install' failed: System Exit error 1
[ https://issues.apache.org/jira/browse/ATLAS-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17230403#comment-17230403 ] Keval Bhatt commented on ATLAS-4021: [~batman135] can you please provide the mvn version? > 'npm install' failed: System Exit error 1 > - > > Key: ATLAS-4021 > URL: https://issues.apache.org/jira/browse/ATLAS-4021 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Ajeet Mohan >Priority: Major > > I am installing Apache Atlas on a Linux VM. I followed all of the > instructions on this link > > [https://atlas.apache.org/2.0.0/InstallationSteps.html] > > I got to the step where it says: > mvn clean -DskipTests install > After which I got this error, > > [INFO] Total time: 08:58 min > [INFO] Finished at: 2020-11-11T13:45:20-05:00 > [INFO] > > [ERROR] Failed to execute goal > com.github.eirslett:frontend-maven-plugin:1.4:npm (npm install) on project > atlas-dashboardv2: Failed to run task: 'npm install' failed. > org.apache.commons.exec.ExecuteException: Process exited with an error: 1 > (Exit value: 1) -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn -rf :atlas-dashboardv2 > > I have tried to look online but could not find any way to resolve it. Can > anyone please help me? Thanks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3794) New UI: Advance search usablity improvment
[ https://issues.apache.org/jira/browse/ATLAS-3794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reassigned ATLAS-3794: -- Assignee: Sameer Shaikh (was: Keval Bhatt) > New UI: Advance search usablity improvment > -- > > Key: ATLAS-3794 > URL: https://issues.apache.org/jira/browse/ATLAS-3794 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt >Assignee: Sameer Shaikh >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3794) New UI: Advance search usablity improvment
[ https://issues.apache.org/jira/browse/ATLAS-3794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3794: --- Fix Version/s: 2.2.0 > New UI: Advance search usablity improvment > -- > > Key: ATLAS-3794 > URL: https://issues.apache.org/jira/browse/ATLAS-3794 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt >Assignee: Sameer Shaikh >Priority: Major > Fix For: 3.0.0, 2.2.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3030) UI : Allow to search the node in the lineage graph
[ https://issues.apache.org/jira/browse/ATLAS-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3030: --- Fix Version/s: (was: 0.8.4) > UI : Allow to search the node in the lineage graph > -- > > Key: ATLAS-3030 > URL: https://issues.apache.org/jira/browse/ATLAS-3030 > Project: Atlas > Issue Type: Sub-task > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-3030-1.patch, ATLAS-3030.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3030) UI : Allow to search the node in the lineage graph
[ https://issues.apache.org/jira/browse/ATLAS-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17225137#comment-17225137 ] Keval Bhatt commented on ATLAS-3030: for branch-0.8 fix has been committed using ATLAS-3259 > UI : Allow to search the node in the lineage graph > -- > > Key: ATLAS-3030 > URL: https://issues.apache.org/jira/browse/ATLAS-3030 > Project: Atlas > Issue Type: Sub-task > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: ATLAS-3030-1.patch, ATLAS-3030.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3743) [Business Metadata] Multiple issues in Audits tab w.r.t. Entity-Business Metadata attributes
[ https://issues.apache.org/jira/browse/ATLAS-3743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3743: --- Attachment: ATLAS-3743.patch > [Business Metadata] Multiple issues in Audits tab w.r.t. Entity-Business > Metadata attributes > > > Key: ATLAS-3743 > URL: https://issues.apache.org/jira/browse/ATLAS-3743 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Reporter: Umesh Padashetty >Assignee: Keval Bhatt >Priority: Critical > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3743.patch, Screenshot 2020-04-20 at 8.53.54 > PM.png, Screenshot 2020-04-20 at 8.54.12 PM.png > > > Following are the issues observed: > # All the BM related operations on an entity are listed as > BUSINESS_ATTRIBUTE_UPDATE only. Right now, BUSINESS_ATTRIBUTE_UPDATE shows up > for all the operations. > ## When a BM attribute is added for the first time, ideally > BUSINESS_ATTRIBUTE_ADD action should show up. > ## On the same lines, when all the BM attributes are removed from entity, > BUSINESS_ATTRIBUTE_DELETE should show up. > # Internal name, BUSINESS_ATTRIBUTE_UPDATE, is listed as action, instead of > plain text like "Business Attribute(s) Updated" > # Date type value is shown as timestamp instead of date, in audit/technical > properties. > Attached screenshots. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3970) When the search button is hit on the atlas entity page, show the match count near "Results for: "
[ https://issues.apache.org/jira/browse/ATLAS-3970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reassigned ATLAS-3970: -- Assignee: Keval Bhatt > When the search button is hit on the atlas entity page, show the match count > near "Results for: " > - > > Key: ATLAS-3970 > URL: https://issues.apache.org/jira/browse/ATLAS-3970 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Dharshana M Krishnamoorthy >Assignee: Keval Bhatt >Priority: Major > Attachments: image-2020-10-05-16-43-15-155.png > > > Eg: When we fire a search with *Type: _ALL_ENTITY_TYPES* and *Classification: > _NOT_CLASSIFIED* all the results are displayed but it is difficult to know > the result count of the search criteria, unless we calculate it manually. It > will be better of the result count is also displayed > !image-2020-10-05-16-43-15-155.png|width=553,height=104! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3992) UI: Upgrade to JQuery 3.5.1
[ https://issues.apache.org/jira/browse/ATLAS-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3992: --- Attachment: ATLAS-3992-1.patch > UI: Upgrade to JQuery 3.5.1 > --- > > Key: ATLAS-3992 > URL: https://issues.apache.org/jira/browse/ATLAS-3992 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.1.0 > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3992-1.patch, ATLAS-3992.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3986) UI Allow user to update the date format from JAVA property file
[ https://issues.apache.org/jira/browse/ATLAS-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3986: --- Attachment: ATLAS-3986-1.patch > UI Allow user to update the date format from JAVA property file > --- > > Key: ATLAS-3986 > URL: https://issues.apache.org/jira/browse/ATLAS-3986 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 2.1.0 > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3986-1.patch, ATLAS-3986.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3943) UI: Show Import/Export operations in administration audit.
[ https://issues.apache.org/jira/browse/ATLAS-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3943: --- Attachment: ATLAS-3943-4.patch > UI: Show Import/Export operations in administration audit. > -- > > Key: ATLAS-3943 > URL: https://issues.apache.org/jira/browse/ATLAS-3943 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3943-1.patch, ATLAS-3943-2.patch, > ATLAS-3943-3.patch, ATLAS-3943-4.patch, ATLAS-3943.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3943) UI: Show Import/Export operations in administration audit.
[ https://issues.apache.org/jira/browse/ATLAS-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3943: --- Parent: (was: ATLAS-3935) Issue Type: Improvement (was: Sub-task) > UI: Show Import/Export operations in administration audit. > -- > > Key: ATLAS-3943 > URL: https://issues.apache.org/jira/browse/ATLAS-3943 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3943-1.patch, ATLAS-3943-2.patch, > ATLAS-3943-3.patch, ATLAS-3943.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3943) UI: Show Import/Export operations in administration audit.
[ https://issues.apache.org/jira/browse/ATLAS-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3943: --- Attachment: ATLAS-3943-3.patch > UI: Show Import/Export operations in administration audit. > -- > > Key: ATLAS-3943 > URL: https://issues.apache.org/jira/browse/ATLAS-3943 > Project: Atlas > Issue Type: Sub-task > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3943-1.patch, ATLAS-3943-2.patch, > ATLAS-3943-3.patch, ATLAS-3943.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3986) UI Allow user to update the date format from JAVA property file
[ https://issues.apache.org/jira/browse/ATLAS-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3986: --- Attachment: ATLAS-3986.patch > UI Allow user to update the date format from JAVA property file > --- > > Key: ATLAS-3986 > URL: https://issues.apache.org/jira/browse/ATLAS-3986 > Project: Atlas > Issue Type: Sub-task > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3986.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3990) UI: When user clicks to view hive-table details, shown some wrong tabs
[ https://issues.apache.org/jira/browse/ATLAS-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3990: --- Affects Version/s: 2.1.0 > UI: When user clicks to view hive-table details, shown some wrong tabs > -- > > Key: ATLAS-3990 > URL: https://issues.apache.org/jira/browse/ATLAS-3990 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.1.0 >Reporter: Durga Kadam > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3990.patch, wrong_tabs_showing_on_clicks.mkv > > > Steps to reproduce:: > # Have a hive_db with at least one table > # Click on 'Tables' tab > # Click on one of the tables listed in the tab > # The page renders the table details, including addition of 'Schema' tab > # However, 'Tables' tab is still visible; this tab needs to be hidden > # Also, on clicking the db link in Properties page of hive_table, 'Schema' > tab is still visible. This should be hidden > PFA evidence file attached - wrong_tabs_showing_on_clicks.mkv -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3990) UI: When user clicks to view hive-table details, shown some wrong tabs
[ https://issues.apache.org/jira/browse/ATLAS-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3990: --- Fix Version/s: 2.2.0 3.0.0 > UI: When user clicks to view hive-table details, shown some wrong tabs > -- > > Key: ATLAS-3990 > URL: https://issues.apache.org/jira/browse/ATLAS-3990 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3990.patch, wrong_tabs_showing_on_clicks.mkv > > > Steps to reproduce:: > # Have a hive_db with at least one table > # Click on 'Tables' tab > # Click on one of the tables listed in the tab > # The page renders the table details, including addition of 'Schema' tab > # However, 'Tables' tab is still visible; this tab needs to be hidden > # Also, on clicking the db link in Properties page of hive_table, 'Schema' > tab is still visible. This should be hidden > PFA evidence file attached - wrong_tabs_showing_on_clicks.mkv -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3990) UI: When user clicks to view hive-table details, shown some wrong tabs
[ https://issues.apache.org/jira/browse/ATLAS-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3990: --- Attachment: ATLAS-3990.patch > UI: When user clicks to view hive-table details, shown some wrong tabs > -- > > Key: ATLAS-3990 > URL: https://issues.apache.org/jira/browse/ATLAS-3990 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam > Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3990.patch, wrong_tabs_showing_on_clicks.mkv > > > Steps to reproduce:: > # Have a hive_db with at least one table > # Click on 'Tables' tab > # Click on one of the tables listed in the tab > # The page renders the table details, including addition of 'Schema' tab > # However, 'Tables' tab is still visible; this tab needs to be hidden > # Also, on clicking the db link in Properties page of hive_table, 'Schema' > tab is still visible. This should be hidden > PFA evidence file attached - wrong_tabs_showing_on_clicks.mkv -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3992) UI: Upgrade to JQuery 3.5.1
[ https://issues.apache.org/jira/browse/ATLAS-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3992: --- Attachment: ATLAS-3992.patch > UI: Upgrade to JQuery 3.5.1 > --- > > Key: ATLAS-3992 > URL: https://issues.apache.org/jira/browse/ATLAS-3992 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.1.0 > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3992.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3992) UI: Upgrade to JQuery 3.5.1
Keval Bhatt created ATLAS-3992: -- Summary: UI: Upgrade to JQuery 3.5.1 Key: ATLAS-3992 URL: https://issues.apache.org/jira/browse/ATLAS-3992 Project: Atlas Issue Type: Improvement Affects Versions: 2.1.0 Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 3.0.0, 2.2.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3991) UI: Handlebar helper number format issue
[ https://issues.apache.org/jira/browse/ATLAS-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3991: --- Attachment: ATLAS-3991.patch > UI: Handlebar helper number format issue > > > Key: ATLAS-3991 > URL: https://issues.apache.org/jira/browse/ATLAS-3991 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.1.0 > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3991.patch, > screenshot-localhost_-2020.10.13-18_21_07.png > > > if a number has coma in it then arithmetic helper not able to calculate the > value. > Example: > if the value is *20,201* then the helper will return the value *20* > > *!screenshot-localhost_-2020.10.13-18_21_07.png!* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3991) UI: Handlebar helper number format issue
[ https://issues.apache.org/jira/browse/ATLAS-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3991: --- Description: if a number has coma in it then arithmetic helper not able to calculate the value. Example: if the value is *20,201* then the helper will return the value *20* *!screenshot-localhost_-2020.10.13-18_21_07.png!* > UI: Handlebar helper number format issue > > > Key: ATLAS-3991 > URL: https://issues.apache.org/jira/browse/ATLAS-3991 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.1.0 > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: screenshot-localhost_-2020.10.13-18_21_07.png > > > if a number has coma in it then arithmetic helper not able to calculate the > value. > Example: > if the value is *20,201* then the helper will return the value *20* > > *!screenshot-localhost_-2020.10.13-18_21_07.png!* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3991) UI: Handlebar helper number format issue
[ https://issues.apache.org/jira/browse/ATLAS-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3991: --- Attachment: screenshot-localhost_-2020.10.13-18_21_07.png > UI: Handlebar helper number format issue > > > Key: ATLAS-3991 > URL: https://issues.apache.org/jira/browse/ATLAS-3991 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.1.0 > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: screenshot-localhost_-2020.10.13-18_21_07.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3991) UI: Handlebar helper number format issue
Keval Bhatt created ATLAS-3991: -- Summary: UI: Handlebar helper number format issue Key: ATLAS-3991 URL: https://issues.apache.org/jira/browse/ATLAS-3991 Project: Atlas Issue Type: Bug Affects Versions: 2.1.0 Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 3.0.0, 2.2.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3990) UI: When user clicks to view hive-table details, shown some wrong tabs
[ https://issues.apache.org/jira/browse/ATLAS-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reassigned ATLAS-3990: -- Assignee: Keval Bhatt > UI: When user clicks to view hive-table details, shown some wrong tabs > -- > > Key: ATLAS-3990 > URL: https://issues.apache.org/jira/browse/ATLAS-3990 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam > Assignee: Keval Bhatt >Priority: Major > Attachments: wrong_tabs_showing_on_clicks.mkv > > > Steps to reproduce:: > # Have a hive_db with at least one table > # Click on 'Tables' tab > # Click on one of the tables listed in the tab > # The page renders the table details, including addition of 'Schema' tab > # However, 'Tables' tab is still visible; this tab needs to be hidden > # Also, on clicking the db link in Properties page of hive_table, 'Schema' > tab is still visible. This should be hidden > PFA evidence file attached - wrong_tabs_showing_on_clicks.mkv -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3954) UI: Type system property table improvement
[ https://issues.apache.org/jira/browse/ATLAS-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3954: --- Attachment: ATLAS-3954-1.patch > UI: Type system property table improvement > -- > > Key: ATLAS-3954 > URL: https://issues.apache.org/jira/browse/ATLAS-3954 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3954-1.patch, ATLAS-3954.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3954) UI: Type system property table improvement
[ https://issues.apache.org/jira/browse/ATLAS-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3954: --- Attachment: ATLAS-3954.patch > UI: Type system property table improvement > -- > > Key: ATLAS-3954 > URL: https://issues.apache.org/jira/browse/ATLAS-3954 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3954.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3978) In Administration, Audits filter for 'OR' condition does not work
[ https://issues.apache.org/jira/browse/ATLAS-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3978: --- Attachment: ATLAS-3978.patch > In Administration, Audits filter for 'OR' condition does not work > - > > Key: ATLAS-3978 > URL: https://issues.apache.org/jira/browse/ATLAS-3978 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3978.patch, OR condition not working.mkv > > > Description:: > When user uses OR condition it does not apply on filter, results are listed > with AND condition. PFA evidence file [OR condition not working.mkv] > Steps to regenerate:: > # Go to Administration- Audits > # Select the OR condition filter > # Check the console for response > # Results are listed with 'AND' operator instead of 'OR' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3986) UI Allow user to update the date format from JAVA property file
[ https://issues.apache.org/jira/browse/ATLAS-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3986: --- Summary: UI Allow user to update the date format from JAVA property file (was: UI Allow user to update the date format from JAVA properties file) > UI Allow user to update the date format from JAVA property file > --- > > Key: ATLAS-3986 > URL: https://issues.apache.org/jira/browse/ATLAS-3986 > Project: Atlas > Issue Type: Sub-task > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3986) UI Allow user to update the date format from JAVA properties file
[ https://issues.apache.org/jira/browse/ATLAS-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3986: --- Fix Version/s: 2.2.0 3.0.0 > UI Allow user to update the date format from JAVA properties file > - > > Key: ATLAS-3986 > URL: https://issues.apache.org/jira/browse/ATLAS-3986 > Project: Atlas > Issue Type: Sub-task > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3986) UI Allow user to update the date format from JAVA properties file
Keval Bhatt created ATLAS-3986: -- Summary: UI Allow user to update the date format from JAVA properties file Key: ATLAS-3986 URL: https://issues.apache.org/jira/browse/ATLAS-3986 Project: Atlas Issue Type: Sub-task Reporter: Keval Bhatt Assignee: Keval Bhatt -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3361) UI: improve Lineage, Relationship graph position changes
[ https://issues.apache.org/jira/browse/ATLAS-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt resolved ATLAS-3361. Resolution: Invalid > UI: improve Lineage, Relationship graph position changes > > > Key: ATLAS-3361 > URL: https://issues.apache.org/jira/browse/ATLAS-3361 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0 > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3692) [Business Metadata] Incorrect values for long data type being stored
[ https://issues.apache.org/jira/browse/ATLAS-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210120#comment-17210120 ] Keval Bhatt commented on ATLAS-3692: The issue is fixed by ATLAS-3964. > [Business Metadata] Incorrect values for long data type being stored > - > > Key: ATLAS-3692 > URL: https://issues.apache.org/jira/browse/ATLAS-3692 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: long issue.mov > > > While assigning very long values to the business metadata attribute, the > values are being stored incorrectly. For instance, the range of long data > type in java is +9223372036854775807 to -9223372036854775808. But the > following issues are being observed > # When you give the value as +9223372036854775807 it is being stored as > +9223372036854776000 > # When you give the value as -9223372036854775808 it is being stored as > -9223372036854776000 > # Once the value gets stored as 9223372036854776000, any further save on the > attribute values keeps throwing out of range exception. This is weird, > because the value is still saved as 9223372036854776000, but UI keeps > complaining > Attached is the video -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3692) [Business Metadata] Incorrect values for long data type being stored
[ https://issues.apache.org/jira/browse/ATLAS-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3692: --- Fix Version/s: 2.2.0 3.0.0 > [Business Metadata] Incorrect values for long data type being stored > - > > Key: ATLAS-3692 > URL: https://issues.apache.org/jira/browse/ATLAS-3692 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Umesh Padashetty > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: long issue.mov > > > While assigning very long values to the business metadata attribute, the > values are being stored incorrectly. For instance, the range of long data > type in java is +9223372036854775807 to -9223372036854775808. But the > following issues are being observed > # When you give the value as +9223372036854775807 it is being stored as > +9223372036854776000 > # When you give the value as -9223372036854775808 it is being stored as > -9223372036854776000 > # Once the value gets stored as 9223372036854776000, any further save on the > attribute values keeps throwing out of range exception. This is weird, > because the value is still saved as 9223372036854776000, but UI keeps > complaining > Attached is the video -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3692) [Business Metadata] Incorrect values for long data type being stored
[ https://issues.apache.org/jira/browse/ATLAS-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt resolved ATLAS-3692. Resolution: Fixed > [Business Metadata] Incorrect values for long data type being stored > - > > Key: ATLAS-3692 > URL: https://issues.apache.org/jira/browse/ATLAS-3692 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Umesh Padashetty > Assignee: Keval Bhatt >Priority: Major > Attachments: long issue.mov > > > While assigning very long values to the business metadata attribute, the > values are being stored incorrectly. For instance, the range of long data > type in java is +9223372036854775807 to -9223372036854775808. But the > following issues are being observed > # When you give the value as +9223372036854775807 it is being stored as > +9223372036854776000 > # When you give the value as -9223372036854775808 it is being stored as > -9223372036854776000 > # Once the value gets stored as 9223372036854776000, any further save on the > attribute values keeps throwing out of range exception. This is weird, > because the value is still saved as 9223372036854776000, but UI keeps > complaining > Attached is the video -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3692) [Business Metadata] Incorrect values for long data type being stored
[ https://issues.apache.org/jira/browse/ATLAS-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3692: --- Parent: (was: ATLAS-3964) Issue Type: Bug (was: Sub-task) > [Business Metadata] Incorrect values for long data type being stored > - > > Key: ATLAS-3692 > URL: https://issues.apache.org/jira/browse/ATLAS-3692 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: long issue.mov > > > While assigning very long values to the business metadata attribute, the > values are being stored incorrectly. For instance, the range of long data > type in java is +9223372036854775807 to -9223372036854775808. But the > following issues are being observed > # When you give the value as +9223372036854775807 it is being stored as > +9223372036854776000 > # When you give the value as -9223372036854775808 it is being stored as > -9223372036854776000 > # Once the value gets stored as 9223372036854776000, any further save on the > attribute values keeps throwing out of range exception. This is weird, > because the value is still saved as 9223372036854776000, but UI keeps > complaining > Attached is the video -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3692) [Business Metadata] Incorrect values for long data type being stored
[ https://issues.apache.org/jira/browse/ATLAS-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3692: --- Parent: ATLAS-3964 Issue Type: Sub-task (was: Bug) > [Business Metadata] Incorrect values for long data type being stored > - > > Key: ATLAS-3692 > URL: https://issues.apache.org/jira/browse/ATLAS-3692 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui >Reporter: Umesh Padashetty > Assignee: Keval Bhatt >Priority: Major > Attachments: long issue.mov > > > While assigning very long values to the business metadata attribute, the > values are being stored incorrectly. For instance, the range of long data > type in java is +9223372036854775807 to -9223372036854775808. But the > following issues are being observed > # When you give the value as +9223372036854775807 it is being stored as > +9223372036854776000 > # When you give the value as -9223372036854775808 it is being stored as > -9223372036854776000 > # Once the value gets stored as 9223372036854776000, any further save on the > attribute values keeps throwing out of range exception. This is weird, > because the value is still saved as 9223372036854776000, but UI keeps > complaining > Attached is the video -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3978) In Administration, Audits filter for 'OR' condition does not work
[ https://issues.apache.org/jira/browse/ATLAS-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3978: --- Fix Version/s: 2.2.0 3.0.0 > In Administration, Audits filter for 'OR' condition does not work > - > > Key: ATLAS-3978 > URL: https://issues.apache.org/jira/browse/ATLAS-3978 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: OR condition not working.mkv > > > Description:: > When user uses OR condition it does not apply on filter, results are listed > with AND condition. PFA evidence file [OR condition not working.mkv] > Steps to regenerate:: > # Go to Administration- Audits > # Select the OR condition filter > # Check the console for response > # Results are listed with 'AND' operator instead of 'OR' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3978) In Administration, Audits filter for 'OR' condition does not work
[ https://issues.apache.org/jira/browse/ATLAS-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reassigned ATLAS-3978: -- Assignee: Keval Bhatt > In Administration, Audits filter for 'OR' condition does not work > - > > Key: ATLAS-3978 > URL: https://issues.apache.org/jira/browse/ATLAS-3978 > Project: Atlas > Issue Type: Bug >Reporter: Durga Kadam > Assignee: Keval Bhatt >Priority: Major > Attachments: OR condition not working.mkv > > > Description:: > When user uses OR condition it does not apply on filter, results are listed > with AND condition. PFA evidence file [OR condition not working.mkv] > Steps to regenerate:: > # Go to Administration- Audits > # Select the OR condition filter > # Check the console for response > # Results are listed with 'AND' operator instead of 'OR' -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Review Request 72932: ATLAS-3964: Fix for regression caused by earlier patch
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72932/#review221997 --- Ship it! Ship It! - keval bhatt On Oct. 6, 2020, 2:05 a.m., Deep Singh wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/72932/ > --- > > (Updated Oct. 6, 2020, 2:05 a.m.) > > > Review request for atlas, keval bhatt, Madhan Neethiraj, and Sarath > Subramanian. > > > Bugs: ATLAS-3964 > https://issues.apache.org/jira/browse/ATLAS-3964 > > > Repository: atlas > > > Description > --- > > Regression was observed in counts of entities. > With earlier patch all sorts of numbers were parsed into string. > Only those numbers where information is being lost must be passed into a > string. > > > Diffs > - > > dashboardv2/public/js/utils/Overrides.js 63770b5c3 > dashboardv3/public/js/utils/Overrides.js 63770b5c3 > > > Diff: https://reviews.apache.org/r/72932/diff/1/ > > > Testing > --- > > Testing was done on Atlas loaded with 3738 entities (2057 active and 1681 > deleted) > > > Thanks, > > Deep Singh > >
[jira] [Updated] (ATLAS-3943) UI: Show Import/Export operations in administration audit.
[ https://issues.apache.org/jira/browse/ATLAS-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3943: --- Attachment: ATLAS-3943-2.patch > UI: Show Import/Export operations in administration audit. > -- > > Key: ATLAS-3943 > URL: https://issues.apache.org/jira/browse/ATLAS-3943 > Project: Atlas > Issue Type: Sub-task > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3943-1.patch, ATLAS-3943-2.patch, ATLAS-3943.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3979) Beta UI : Removing one of the filters with an attribute name removes all of the filters with that attribute name.
[ https://issues.apache.org/jira/browse/ATLAS-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3979: --- Attachment: ATLAS-3979.patch > Beta UI : Removing one of the filters with an attribute name removes all of > the filters with that attribute name. > - > > Key: ATLAS-3979 > URL: https://issues.apache.org/jira/browse/ATLAS-3979 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3979.patch > > > Create a basic search with filters: > typename = _ALL_ENTITY_TYPES > filters: > _classificationNames = tag1 and > _classificationNames = tag2 and > _createdBy = hive > Fire Search. > From UI , remove "_classificationNames = tag1" filter . > This removes "_classificationNames = tag2" filter too since the attribute > name _classificationNames is same. > Other attribute _createdBy is intact. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3980) classic UI: When classification is created, the left pane takes the control to the end of the long list of classifications
[ https://issues.apache.org/jira/browse/ATLAS-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3980: --- Attachment: ATLAS-3980.patch > classic UI: When classification is created, the left pane takes the control > to the end of the long list of classifications > -- > > Key: ATLAS-3980 > URL: https://issues.apache.org/jira/browse/ATLAS-3980 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3980.patch > > > When a new classification is created, the control goes to the end of the list > of classifications created, instead of taking it to the new classification > created. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3981) UI: Create Entity button is shown for a user without create entity permission in ranger
[ https://issues.apache.org/jira/browse/ATLAS-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3981: --- Attachment: ATLAS-3981.patch > UI: Create Entity button is shown for a user without create entity permission > in ranger > --- > > Key: ATLAS-3981 > URL: https://issues.apache.org/jira/browse/ATLAS-3981 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3981.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3980) classic UI: When classification is created, the left pane takes the control to the end of the long list of classifications
[ https://issues.apache.org/jira/browse/ATLAS-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3980: --- Summary: classic UI: When classification is created, the left pane takes the control to the end of the long list of classifications (was: When classification is created, the left pane takes the control to the end of the long list of classifications) > classic UI: When classification is created, the left pane takes the control > to the end of the long list of classifications > -- > > Key: ATLAS-3980 > URL: https://issues.apache.org/jira/browse/ATLAS-3980 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > > When a new classification is created, the control goes to the end of the list > of classifications created, instead of taking it to the new classification > created. > Attaching the recording for reference. > This might be a little annoying to the customers from user experience point > of view when there is a long list of classification -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3980) classic UI: When classification is created, the left pane takes the control to the end of the long list of classifications
[ https://issues.apache.org/jira/browse/ATLAS-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3980: --- Description: When a new classification is created, the control goes to the end of the list of classifications created, instead of taking it to the new classification created. (was: When a new classification is created, the control goes to the end of the list of classifications created, instead of taking it to the new classification created. Attaching the recording for reference. This might be a little annoying to the customers from user experience point of view when there is a long list of classification) > classic UI: When classification is created, the left pane takes the control > to the end of the long list of classifications > -- > > Key: ATLAS-3980 > URL: https://issues.apache.org/jira/browse/ATLAS-3980 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > > When a new classification is created, the control goes to the end of the list > of classifications created, instead of taking it to the new classification > created. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3981) Beta UI: Create Entity button is shown for a user without create entity permission in ranger
[ https://issues.apache.org/jira/browse/ATLAS-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reassigned ATLAS-3981: -- Assignee: Keval Bhatt > Beta UI: Create Entity button is shown for a user without create entity > permission in ranger > > > Key: ATLAS-3981 > URL: https://issues.apache.org/jira/browse/ATLAS-3981 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3981) UI: Create Entity button is shown for a user without create entity permission in ranger
[ https://issues.apache.org/jira/browse/ATLAS-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3981: --- Summary: UI: Create Entity button is shown for a user without create entity permission in ranger (was: Beta UI: Create Entity button is shown for a user without create entity permission in ranger) > UI: Create Entity button is shown for a user without create entity permission > in ranger > --- > > Key: ATLAS-3981 > URL: https://issues.apache.org/jira/browse/ATLAS-3981 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3981) Beta UI: Create Entity button is shown for a user without create entity permission in ranger
Keval Bhatt created ATLAS-3981: -- Summary: Beta UI: Create Entity button is shown for a user without create entity permission in ranger Key: ATLAS-3981 URL: https://issues.apache.org/jira/browse/ATLAS-3981 Project: Atlas Issue Type: Bug Reporter: Keval Bhatt Fix For: 3.0.0, 2.2.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3980) When classification is created, the left pane takes the control to the end of the long list of classifications
Keval Bhatt created ATLAS-3980: -- Summary: When classification is created, the left pane takes the control to the end of the long list of classifications Key: ATLAS-3980 URL: https://issues.apache.org/jira/browse/ATLAS-3980 Project: Atlas Issue Type: Bug Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 3.0.0, 2.2.0 When a new classification is created, the control goes to the end of the list of classifications created, instead of taking it to the new classification created. Attaching the recording for reference. This might be a little annoying to the customers from user experience point of view when there is a long list of classification -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3979) Beta UI : Removing one of the filters with an attribute name removes all of the filters with that attribute name.
[ https://issues.apache.org/jira/browse/ATLAS-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3979: --- Fix Version/s: 2.2.0 3.0.0 > Beta UI : Removing one of the filters with an attribute name removes all of > the filters with that attribute name. > - > > Key: ATLAS-3979 > URL: https://issues.apache.org/jira/browse/ATLAS-3979 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > > Create a basic search with filters: > typename = _ALL_ENTITY_TYPES > filters: > _classificationNames = tag1 and > _classificationNames = tag2 and > _createdBy = hive > Fire Search. > From UI , remove "_classificationNames = tag1" filter . > This removes "_classificationNames = tag2" filter too since the attribute > name _classificationNames is same. > Other attribute _createdBy is intact. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3979) Beta UI : Removing one of the filters with an attribute name removes all of the filters with that attribute name.
Keval Bhatt created ATLAS-3979: -- Summary: Beta UI : Removing one of the filters with an attribute name removes all of the filters with that attribute name. Key: ATLAS-3979 URL: https://issues.apache.org/jira/browse/ATLAS-3979 Project: Atlas Issue Type: Bug Reporter: Keval Bhatt Assignee: Keval Bhatt Create a basic search with filters: typename = _ALL_ENTITY_TYPES filters: _classificationNames = tag1 and _classificationNames = tag2 and _createdBy = hive Fire Search. >From UI , remove "_classificationNames = tag1" filter . This removes "_classificationNames = tag2" filter too since the attribute name _classificationNames is same. Other attribute _createdBy is intact. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3964) Atlas UI displays large numbers incorrectly
[ https://issues.apache.org/jira/browse/ATLAS-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt resolved ATLAS-3964. Resolution: Fixed > Atlas UI displays large numbers incorrectly > --- > > Key: ATLAS-3964 > URL: https://issues.apache.org/jira/browse/ATLAS-3964 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Deep Singh >Assignee: Deep Singh >Priority: Major > Attachments: details.doc > > > In the case of a type that has an attribute of type Long, and it contains a > very large number, the Atlas UI does not show the correct number. > Steps to reproduce: > From the command line: > # create an entity type which has a field of type long > # create an entity of this same type and the value of the field should be > "1085741226505763426" > # Atlas will respond with the created entity, you will see that the field > value is correct > # now open the Atlas website and search for this same entity; you will see > the value displayed is "1085741226505763500" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3964) Atlas UI displays large numbers incorrectly
[ https://issues.apache.org/jira/browse/ATLAS-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17205219#comment-17205219 ] Keval Bhatt commented on ATLAS-3964: [~deepam1982] Thanks for the fix, + 1 from my side > Atlas UI displays large numbers incorrectly > --- > > Key: ATLAS-3964 > URL: https://issues.apache.org/jira/browse/ATLAS-3964 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Deep Singh >Assignee: Deep Singh >Priority: Major > Attachments: details.doc > > > In the case of a type that has an attribute of type Long, and it contains a > very large number, the Atlas UI does not show the correct number. > Steps to reproduce: > From the command line: > # create an entity type which has a field of type long > # create an entity of this same type and the value of the field should be > "1085741226505763426" > # Atlas will respond with the created entity, you will see that the field > value is correct > # now open the Atlas website and search for this same entity; you will see > the value displayed is "1085741226505763500" -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Review Request 72917: ATLAS-3964 Atlas UI displays large numbers incorrectly
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72917/#review221979 --- Ship it! Ship It! - keval bhatt On Sept. 30, 2020, 10:52 p.m., Deep Singh wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/72917/ > --- > > (Updated Sept. 30, 2020, 10:52 p.m.) > > > Review request for atlas, Ashutosh Mestry, keval bhatt, madhan, Madhan > Neethiraj, and Sarath Subramanian. > > > Bugs: ATLAS-3964 > https://issues.apache.org/jira/browse/ATLAS-3964 > > > Repository: atlas > > > Description > --- > > In the case of a type that has an attribute of type Long, and it contains a > very large number, the Atlas UI does not show the correct number. The problem > is with client-side parsing. It's not an issue with our UI code, its a > problem on browser's javascript engine. > Javascript cannot handle values bigger than Number.MAX_SAFE_INTEGER (2^53 == > 9 007 199 254 740 992). long is 2^64, so for any number greater than 2^53, > javascript does internal optimization to maintain sanity. > > > Diffs > - > > dashboardv2/gruntfile.js 747de0bc7 > dashboardv2/package.json c2f7c0fc3 > dashboardv2/public/js/main.js 8caa78122 > dashboardv2/public/js/utils/Overrides.js 33328f07c > dashboardv3/gruntfile.js 378a69a04 > dashboardv3/package.json 895020068 > dashboardv3/public/js/main.js 17e336208 > dashboardv3/public/js/utils/Overrides.js 33328f07c > > > Diff: https://reviews.apache.org/r/72917/diff/1/ > > > Testing > --- > > Testing is done with local setup. > > > Thanks, > > Deep Singh > >
[jira] [Updated] (ATLAS-3955) Read Type Auth, UI : detailsPage doesn't load for user who has read permission for entity but no read auth for entity's type
[
https://issues.apache.org/jira/browse/ATLAS-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt updated ATLAS-3955:
---
Attachment: ATLAS-3955-1.patch
> Read Type Auth, UI : detailsPage doesn't load for user who has read
> permission for entity but no read auth for entity's type
>
>
> Key: ATLAS-3955
> URL: https://issues.apache.org/jira/browse/ATLAS-3955
> Project: Atlas
> Issue Type: Bug
> Reporter: Keval Bhatt
> Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-3955-1.patch, ATLAS-3955.patch
>
>
> -
> Simple scenario
> -
> 1 . hive_table employee is created.
> 2. USER has permissions to read the employee table entity
> 3. USER doesn't have permissions to read type hive_table
> 4. USER logs into Atlas and searches for _ALL___ENTITY_TYPES , which lists
> the hive_table entity "employee"
> 5. Clicking on it, UI throws following error in Console tab and UI keeps
> loading.
> {code:java}
> DetailPageLayoutView.js?bust=1600212682027:109 Uncaught TypeError: Cannot
> read property 'toJSON' of undefined
> at N.d. (DetailPageLayoutView.js?bust=1600212682027:109)
> at s (backbone-min.js?bust=1600212682027:1)
> at r (backbone-min.js?bust=1600212682027:1)
> at m (backbone-min.js?bust=1600212682027:1)
> at N.d.k.trigger (backbone-min.js?bust=1600212682027:1)
> at N.d.reset (backbone-min.js?bust=1600212682027:1)
> at Object. (backbone.paginator.min.js?bust=1600212682027:1)
> at s (backbone-min.js?bust=1600212682027:1)
> at r (backbone-min.js?bust=1600212682027:1)
> at m (backbone-min.js?bust=1600212682027:1) {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3955) Read Type Auth, UI : detailsPage doesn't load for user who has read permission for entity but no read auth for entity's type
[
https://issues.apache.org/jira/browse/ATLAS-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt updated ATLAS-3955:
---
Attachment: ATLAS-3955.patch
> Read Type Auth, UI : detailsPage doesn't load for user who has read
> permission for entity but no read auth for entity's type
>
>
> Key: ATLAS-3955
> URL: https://issues.apache.org/jira/browse/ATLAS-3955
> Project: Atlas
> Issue Type: Bug
> Reporter: Keval Bhatt
> Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-3955.patch
>
>
> -
> Simple scenario
> -
> 1 . hive_table employee is created.
> 2. USER has permissions to read the employee table entity
> 3. USER doesn't have permissions to read type hive_table
> 4. USER logs into Atlas and searches for _ALL___ENTITY_TYPES , which lists
> the hive_table entity "employee"
> 5. Clicking on it, UI throws following error in Console tab and UI keeps
> loading.
> {code:java}
> DetailPageLayoutView.js?bust=1600212682027:109 Uncaught TypeError: Cannot
> read property 'toJSON' of undefined
> at N.d. (DetailPageLayoutView.js?bust=1600212682027:109)
> at s (backbone-min.js?bust=1600212682027:1)
> at r (backbone-min.js?bust=1600212682027:1)
> at m (backbone-min.js?bust=1600212682027:1)
> at N.d.k.trigger (backbone-min.js?bust=1600212682027:1)
> at N.d.reset (backbone-min.js?bust=1600212682027:1)
> at Object. (backbone.paginator.min.js?bust=1600212682027:1)
> at s (backbone-min.js?bust=1600212682027:1)
> at r (backbone-min.js?bust=1600212682027:1)
> at m (backbone-min.js?bust=1600212682027:1) {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3955) Read Type Auth, UI : detailsPage doesn't load for user who has read permission for entity but no read auth for entity's type
[
https://issues.apache.org/jira/browse/ATLAS-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt updated ATLAS-3955:
---
Description:
-
Simple scenario
-
1 . hive_table employee is created.
2. USER has permissions to read the employee table entity
3. USER doesn't have permissions to read type hive_table
4. USER logs into Atlas and searches for _ALL___ENTITY_TYPES , which lists the
hive_table entity "employee"
5. Clicking on it, UI throws following error in Console tab and UI keeps
loading.
{code:java}
DetailPageLayoutView.js?bust=1600212682027:109 Uncaught TypeError: Cannot read
property 'toJSON' of undefined
at N.d. (DetailPageLayoutView.js?bust=1600212682027:109)
at s (backbone-min.js?bust=1600212682027:1)
at r (backbone-min.js?bust=1600212682027:1)
at m (backbone-min.js?bust=1600212682027:1)
at N.d.k.trigger (backbone-min.js?bust=1600212682027:1)
at N.d.reset (backbone-min.js?bust=1600212682027:1)
at Object. (backbone.paginator.min.js?bust=1600212682027:1)
at s (backbone-min.js?bust=1600212682027:1)
at r (backbone-min.js?bust=1600212682027:1)
at m (backbone-min.js?bust=1600212682027:1) {code}
was:
-
Simple scenario
-
1 . hive_table employee is created.
2. USER has permissions to read the employee table entity
3. USER doesn't have permissions to read type hive_table
4. USER user logs into Atlas and searches for _ALL___ENTITY_TYPES , which lists
the hive_table entity "employee"
5. Clicking on it, UI throws following error in Console tab and UI keeps
loading.
{code:java}
DetailPageLayoutView.js?bust=1600212682027:109 Uncaught TypeError: Cannot read
property 'toJSON' of undefined
at N.d. (DetailPageLayoutView.js?bust=1600212682027:109)
at s (backbone-min.js?bust=1600212682027:1)
at r (backbone-min.js?bust=1600212682027:1)
at m (backbone-min.js?bust=1600212682027:1)
at N.d.k.trigger (backbone-min.js?bust=1600212682027:1)
at N.d.reset (backbone-min.js?bust=1600212682027:1)
at Object. (backbone.paginator.min.js?bust=1600212682027:1)
at s (backbone-min.js?bust=1600212682027:1)
at r (backbone-min.js?bust=1600212682027:1)
at m (backbone-min.js?bust=1600212682027:1) {code}
> Read Type Auth, UI : detailsPage doesn't load for user who has read
> permission for entity but no read auth for entity's type
>
>
> Key: ATLAS-3955
> URL: https://issues.apache.org/jira/browse/ATLAS-3955
> Project: Atlas
> Issue Type: Bug
> Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0
>
>
> -
> Simple scenario
> -
> 1 . hive_table employee is created.
> 2. USER has permissions to read the employee table entity
> 3. USER doesn't have permissions to read type hive_table
> 4. USER logs into Atlas and searches for _ALL___ENTITY_TYPES , which lists
> the hive_table entity "employee"
> 5. Clicking on it, UI throws following error in Console tab and UI keeps
> loading.
> {code:java}
> DetailPageLayoutView.js?bust=1600212682027:109 Uncaught TypeError: Cannot
> read property 'toJSON' of undefined
> at N.d. (DetailPageLayoutView.js?bust=1600212682027:109)
> at s (backbone-min.js?bust=1600212682027:1)
> at r (backbone-min.js?bust=1600212682027:1)
> at m (backbone-min.js?bust=1600212682027:1)
> at N.d.k.trigger (backbone-min.js?bust=1600212682027:1)
> at N.d.reset (backbone-min.js?bust=1600212682027:1)
> at Object. (backbone.paginator.min.js?bust=1600212682027:1)
> at s (backbone-min.js?bust=1600212682027:1)
> at r (backbone-min.js?bust=1600212682027:1)
> at m (backbone-min.js?bust=1600212682027:1) {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-3955) Read Type Auth, UI : detailsPage doesn't load for user who has read permission for entity but no read auth for entity's type
Keval Bhatt created ATLAS-3955:
--
Summary: Read Type Auth, UI : detailsPage doesn't load for user
who has read permission for entity but no read auth for entity's type
Key: ATLAS-3955
URL: https://issues.apache.org/jira/browse/ATLAS-3955
Project: Atlas
Issue Type: Bug
Reporter: Keval Bhatt
Assignee: Keval Bhatt
Fix For: 3.0.0
-
Simple scenario
-
1 . hive_table employee is created.
2. USER has permissions to read the employee table entity
3. USER doesn't have permissions to read type hive_table
4. USER user logs into Atlas and searches for _ALL___ENTITY_TYPES , which lists
the hive_table entity "employee"
5. Clicking on it, UI throws following error in Console tab and UI keeps
loading.
{code:java}
DetailPageLayoutView.js?bust=1600212682027:109 Uncaught TypeError: Cannot read
property 'toJSON' of undefined
at N.d. (DetailPageLayoutView.js?bust=1600212682027:109)
at s (backbone-min.js?bust=1600212682027:1)
at r (backbone-min.js?bust=1600212682027:1)
at m (backbone-min.js?bust=1600212682027:1)
at N.d.k.trigger (backbone-min.js?bust=1600212682027:1)
at N.d.reset (backbone-min.js?bust=1600212682027:1)
at Object. (backbone.paginator.min.js?bust=1600212682027:1)
at s (backbone-min.js?bust=1600212682027:1)
at r (backbone-min.js?bust=1600212682027:1)
at m (backbone-min.js?bust=1600212682027:1) {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-3954) UI: Type system property table improvement
Keval Bhatt created ATLAS-3954: -- Summary: UI: Type system property table improvement Key: ATLAS-3954 URL: https://issues.apache.org/jira/browse/ATLAS-3954 Project: Atlas Issue Type: Sub-task Components: atlas-webui Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 3.0.0, 2.2.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3943) UI: Show Import/Export operations in administration audit.
[ https://issues.apache.org/jira/browse/ATLAS-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3943: --- Attachment: ATLAS-3943-1.patch > UI: Show Import/Export operations in administration audit. > -- > > Key: ATLAS-3943 > URL: https://issues.apache.org/jira/browse/ATLAS-3943 > Project: Atlas > Issue Type: Sub-task > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3943-1.patch, ATLAS-3943.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3911) UI: Type system management
[ https://issues.apache.org/jira/browse/ATLAS-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3911: --- Attachment: ATLAS-3911-2.patch > UI: Type system management > -- > > Key: ATLAS-3911 > URL: https://issues.apache.org/jira/browse/ATLAS-3911 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3911-1.patch, ATLAS-3911-2.patch, > ATLAS-3911.patch, Type_System_Tree.png, Type_System_Tree_Details.png > > > !Type_System_Tree.png|width=482,height=237! > > !Type_System_Tree_Details.png|width=509,height=249! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3911) UI: Type system management
[ https://issues.apache.org/jira/browse/ATLAS-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3911: --- Attachment: ATLAS-3911-1.patch > UI: Type system management > -- > > Key: ATLAS-3911 > URL: https://issues.apache.org/jira/browse/ATLAS-3911 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3911-1.patch, ATLAS-3911.patch, > Type_System_Tree.png, Type_System_Tree_Details.png > > > !Type_System_Tree.png|width=482,height=237! > > !Type_System_Tree_Details.png|width=509,height=249! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3827) UI: Use moment date format instead of default date format.
[
https://issues.apache.org/jira/browse/ATLAS-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt updated ATLAS-3827:
---
Attachment: ATLAS-3827-1.patch
> UI: Use moment date format instead of default date format.
> --
>
> Key: ATLAS-3827
> URL: https://issues.apache.org/jira/browse/ATLAS-3827
> Project: Atlas
> Issue Type: Improvement
> Reporter: Keval Bhatt
> Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3827-1.patch, ATLAS-3827.patch,
> image-2020-09-16-17-11-33-386.png, image-2020-09-16-17-12-04-512.png,
> new_date_format.png
>
>
>
> UI configured to use the following date formats:
> {code:java}
> /MM/DD
> /MM/DD HH:mm:ss
> MM/DD/ h:mm A z
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3945) UI: Entity details page, Show N/A for date if date value is 0 or null
[ https://issues.apache.org/jira/browse/ATLAS-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3945: --- Attachment: ATLAS-3945.patch > UI: Entity details page, Show N/A for date if date value is 0 or null > -- > > Key: ATLAS-3945 > URL: https://issues.apache.org/jira/browse/ATLAS-3945 > Project: Atlas > Issue Type: Bug > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3945.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3945) UI: Entity details page, Show N/A for date if date value is 0 or null
Keval Bhatt created ATLAS-3945: -- Summary: UI: Entity details page, Show N/A for date if date value is 0 or null Key: ATLAS-3945 URL: https://issues.apache.org/jira/browse/ATLAS-3945 Project: Atlas Issue Type: Bug Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 3.0.0, 2.2.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3911) UI: Type system management
[ https://issues.apache.org/jira/browse/ATLAS-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3911: --- Summary: UI: Type system management (was: UI: Type system managment) > UI: Type system management > -- > > Key: ATLAS-3911 > URL: https://issues.apache.org/jira/browse/ATLAS-3911 > Project: Atlas > Issue Type: Improvement > Reporter: Keval Bhatt > Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3911.patch, Type_System_Tree.png, > Type_System_Tree_Details.png > > > !Type_System_Tree.png|width=482,height=237! > > !Type_System_Tree_Details.png|width=509,height=249! -- This message was sent by Atlassian Jira (v8.3.4#803005)
