Re: Review Request 73917: ATLAS-4572 Improved Soft Delete behavior for relationships edges
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/73917/ --- (Updated April 13, 2022, 5:44 a.m.) Review request for atlas, Ashutosh Mestry, Jayendra Parab, Madhan Neethiraj, Pinal Shah, Radhika Kundam, Sarath Subramanian, and Sidharth Mishra. Bugs: ATLAS-4572 https://issues.apache.org/jira/browse/ATLAS-4572 Repository: atlas Description --- Earlier the process for soft deleting relationships involved unnecessary invocation of delete methods on already deleted Relationship edges. This would consume a lot of time on an entity which has a long list of soft deleted relationships. This changes implements a check on relationship edges, identifying already deleted relationship edges and avoiding invocation of delete method on them. Thus only allowing deletion of active relationship edges. Diffs (updated) - repository/src/main/java/org/apache/atlas/repository/store/graph/v1/DeleteHandlerV1.java f118ae69a Diff: https://reviews.apache.org/r/73917/diff/2/ Changes: https://reviews.apache.org/r/73917/diff/1-2/ Testing --- PreCommit: https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/1065/ Thanks, Mandar Ambawane
[GitHub] [atlas] dependabot[bot] opened a new pull request, #173: Bump hadoop-common from 3.0.3 to 3.2.3 in /addons/hbase-testing-util
dependabot[bot] opened a new pull request, #173: URL: https://github.com/apache/atlas/pull/173 Bumps hadoop-common from 3.0.3 to 3.2.3. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/atlas/network/alerts). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@atlas.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-atlas] dependabot[bot] opened a new pull request, #48: Bump hadoop-common from 2.7.1 to 3.2.3
dependabot[bot] opened a new pull request, #48: URL: https://github.com/apache/incubator-atlas/pull/48 Bumps hadoop-common from 2.7.1 to 3.2.3. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/incubator-atlas/network/alerts). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@atlas.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [atlas] dependabot[bot] opened a new pull request, #172: Bump hadoop-common from 3.0.3 to 3.2.3 in /addons/hbase-bridge
dependabot[bot] opened a new pull request, #172: URL: https://github.com/apache/atlas/pull/172 Bumps hadoop-common from 3.0.3 to 3.2.3. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/atlas/network/alerts). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@atlas.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (ATLAS-4571) Impakla Hook : Indexed string field (solr.StrField) which is too large ERROR
[ https://issues.apache.org/jira/browse/ATLAS-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Snehal Ambavkar resolved ATLAS-4571. Fix Version/s: 3.0.0 Resolution: Fixed > Impakla Hook : Indexed string field (solr.StrField) which is too large ERROR > > > Key: ATLAS-4571 > URL: https://issues.apache.org/jira/browse/ATLAS-4571 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Snehal Ambavkar >Assignee: Snehal Ambavkar >Priority: Major > Fix For: 3.0.0 > > > ERROR : > Exception writing document id test1 to the index; possible analysis error: > Document contains at least one immense term in field="test_s" (whose UTF8 > encoding is longer than the max length 32766), all of which were skipped. > Please correct the analyzer to not produce such terms. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4583) UI: When there is no data, error is encountered on switching UI at a specific page
Rahul Kurup created ATLAS-4583: -- Summary: UI: When there is no data, error is encountered on switching UI at a specific page Key: ATLAS-4583 URL: https://issues.apache.org/jira/browse/ATLAS-4583 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup In old UI, when there is no data for classification and glossary, if the user selects either 'tree' toggle in classification or 'category' toggle in glossary section, and then attempts to switch UI, they get an endless loading page with the following error message: viewType=tree: Unknown/invalid classification or Given instance guid viewType=category is invalid/not found -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4582) UI: Unexpected behaviour on specific navigation from full screen lineage
Rahul Kurup created ATLAS-4582: -- Summary: UI: Unexpected behaviour on specific navigation from full screen lineage Key: ATLAS-4582 URL: https://issues.apache.org/jira/browse/ATLAS-4582 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Steps: 1. Go to an entity details page of an entity that has a lineage 2. From there, go to Lineage tab 3. Click on full screen button in lineage window 4. From there, click on the back button of the browser. You will notice that no navigation action seems to occur, even though the URL changes in the browser. But on clicking a second time, user is navigated to the search results page. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4581) UI: Page freezes on specific navigation
Rahul Kurup created ATLAS-4581: -- Summary: UI: Page freezes on specific navigation Key: ATLAS-4581 URL: https://issues.apache.org/jira/browse/ATLAS-4581 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Steps: 1. Go to an entity details page of an entity that has a lineage 2. Go to any details tab (Relationship, Classifications, Audits, or Tasks) 3. From there, go to Lineage tab 4. Click on full screen button in lineage window 5. From there, click on the back button of the browser. You will observe that no element of the page is clickable. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ATLAS-4571) Impakla Hook : Indexed string field (solr.StrField) which is too large ERROR
[ https://issues.apache.org/jira/browse/ATLAS-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520954#comment-17520954 ] ASF subversion and git services commented on ATLAS-4571: Commit c4bc80b22d397cbeeffdc3f85a837fc7670d6487 in atlas's branch refs/heads/branch-2.0 from snehal.ambavkar [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=c4bc80b22 ] ATLAS-4571 : Impala Hook : query-string is too large to store Asset.name (solr.StrField). Signed-off-by: Pinal Shah (cherry picked from commit 742eeba4021d1f9972e8bf572693474fd8d7b367) > Impakla Hook : Indexed string field (solr.StrField) which is too large ERROR > > > Key: ATLAS-4571 > URL: https://issues.apache.org/jira/browse/ATLAS-4571 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Snehal Ambavkar >Assignee: Snehal Ambavkar >Priority: Major > > ERROR : > Exception writing document id test1 to the index; possible analysis error: > Document contains at least one immense term in field="test_s" (whose UTF8 > encoding is longer than the max length 32766), all of which were skipped. > Please correct the analyzer to not produce such terms. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ATLAS-4571) Impakla Hook : Indexed string field (solr.StrField) which is too large ERROR
[ https://issues.apache.org/jira/browse/ATLAS-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520953#comment-17520953 ] ASF subversion and git services commented on ATLAS-4571: Commit 742eeba4021d1f9972e8bf572693474fd8d7b367 in atlas's branch refs/heads/master from snehal.ambavkar [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=742eeba40 ] ATLAS-4571 : Impala Hook : query-string is too large to store Asset.name (solr.StrField). Signed-off-by: Pinal Shah > Impakla Hook : Indexed string field (solr.StrField) which is too large ERROR > > > Key: ATLAS-4571 > URL: https://issues.apache.org/jira/browse/ATLAS-4571 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Snehal Ambavkar >Assignee: Snehal Ambavkar >Priority: Major > > ERROR : > Exception writing document id test1 to the index; possible analysis error: > Document contains at least one immense term in field="test_s" (whose UTF8 > encoding is longer than the max length 32766), all of which were skipped. > Please correct the analyzer to not produce such terms. -- This message was sent by Atlassian Jira (v8.20.1#820001)
Re: Review Request 73926: ATLAS-4571 : Impala Hook : Indexed string field (solr.StrField) which is too large ERROR
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/73926/ --- (Updated April 12, 2022, 7:03 a.m.) Review request for atlas, Jayendra Parab, Mandar Ambawane, Pinal Shah, Radhika Kundam, and Sidharth Mishra. Bugs: ATLAS-4571 https://issues.apache.org/jira/browse/ATLAS-4571 Repository: atlas Description --- ERROR : Exception writing document id test1 to the index; possible analysis error: Document contains at least one immense term in field="test_s" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped. Please correct the analyzer to not produce such terms. RCA : Imapala process entities created by ImpalaHook saves query-string in name field. Since query-string can be large, we are getting the longer than the max error. Fix : To store qualifiedName in name field instead of query-string Diffs (updated) - addons/impala-bridge/src/main/java/org/apache/atlas/impala/hook/events/BaseImpalaEvent.java 32efb8321 addons/impala-bridge/src/test/java/org/apache/atlas/impala/ImpalaLineageToolIT.java 53e9b1224 addons/impala-bridge/src/test/java/org/apache/atlas/impala/hook/ImpalaLineageHookIT.java 56d74fee3 Diff: https://reviews.apache.org/r/73926/diff/3/ Changes: https://reviews.apache.org/r/73926/diff/2-3/ Testing --- Created tables and inserted data as per jira scenario Created smaller hive tables through impala-shell and verified presence in Atlas through hook Applied and removed classifications on impala-generated entities and hive tables Assigned terms to impala-generated entities and hive tables Created and assigned business meta data to impala-generated entities and hive tables. Deleted and purged impala-generated entities (Checked the above in both old and new UI) Eg : Created two hive tables with 4000 columns. Performed query as follows insert into table_2 select from <4000 column names> from table_1; Also tested with other queries that would intiate creation of impala_process and impala_process_execution entities. Precommit : https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/1068/ Thanks, Snehal Ambavkar
