[jira] [Commented] (ATLAS-3766) Atlas Admin Audit UI pagination is not working
[ https://issues.apache.org/jira/browse/ATLAS-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17097186#comment-17097186 ] Nixon Rodrigues commented on ATLAS-3766: +1 for the patch, [~kevalbhatt] thanks for the patch > Atlas Admin Audit UI pagination is not working > -- > > Key: ATLAS-3766 > URL: https://issues.apache.org/jira/browse/ATLAS-3766 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3766-1.patch, ATLAS-3766.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
Review Request 72458: Shadow Attributes Update Post-Migration from 0.8
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72458/ --- Review request for atlas, Madhan Neethiraj, Nikhil Bonte, Nixon Rodrigues, and Sarath Subramanian. Bugs: ATLAS-3773 https://issues.apache.org/jira/browse/ATLAS-3773 Repository: atlas Description --- **Approach** Please refer to JIRA for details. Diffs - repository/src/main/java/org/apache/atlas/repository/patches/UniqueAttributePatch.java 2b5811919 Diff: https://reviews.apache.org/r/72458/diff/1/ Testing --- **Manual verification** Steps: - Imported dataset from 0.8 using migration import. - Let the patch handlers run. - Verified DSL queries and basic search functionality. **Pre-commit** https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1862/ Thanks, Ashutosh Mestry
[jira] [Updated] (ATLAS-3773) Migration: From 0.8 to latest: Breaks Relationships
[ https://issues.apache.org/jira/browse/ATLAS-3773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3773: --- Description: *Steps to Duplicate* # Migrate data from 0.8 to latest. E.g. data containing hive db and tables. # In the web UI, use a DSL search like: _hive_table db.name="migration_database_8"_ _**Expected results:_ The hive_table with for database _migration_database_8_ should be displayed. **_Actual results_: No results are displayed. There are exceptions logged on the server-side. *Root Cause* As part of implementation of ATLAS-3370, shadow properties were introduced for index type STRING. These need to be set for data that is migrated. *Solution* Use patch handler to add these missing types. Rationale for the approach: The same problem would be observed when upgrading from version of Atlas post 0.8 but before the change was introduced. was: *Steps to Duplicate* # Migrate data from 0.8 to latest. E.g. data containing hive db and tables. # In the web UI, use a DSL search like: _hive_table db.name="migration_database_8"_ _**Expected results:_ The hive_table with for database _migration_database_8_ should be displayed. **_Actual results_: No results are displayed. There are exceptions logged on the server-side. *Root Cause* As part of implementation of ATLAS-3370, shadow properties were introduced for index type STRING. These need to be set for data that is migrated. *Solution* Use patch handler to add these missing types. > Migration: From 0.8 to latest: Breaks Relationships > --- > > Key: ATLAS-3773 > URL: https://issues.apache.org/jira/browse/ATLAS-3773 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: trunk > > Attachments: > ATLAS-3773-Handling-shadow-attributes-for-indexType-.patch > > > *Steps to Duplicate* > # Migrate data from 0.8 to latest. E.g. data containing hive db and tables. > # In the web UI, use a DSL search like: _hive_table > db.name="migration_database_8"_ > _**Expected results:_ The hive_table with for database _migration_database_8_ > should be displayed. > **_Actual results_: No results are displayed. There are exceptions logged on > the server-side. > *Root Cause* > As part of implementation of ATLAS-3370, shadow properties were introduced > for index type STRING. These need to be set for data that is migrated. > *Solution* > Use patch handler to add these missing types. > Rationale for the approach: The same problem would be observed when upgrading > from version of Atlas post 0.8 but before the change was introduced. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3762) Entity Creation: Improve Edges Fetch Between Vertices
[ https://issues.apache.org/jira/browse/ATLAS-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3762: --- Attachment: ATLAS-3762-Edge-fetch-improvement-gremlin.patch > Entity Creation: Improve Edges Fetch Between Vertices > - > > Key: ATLAS-3762 > URL: https://issues.apache.org/jira/browse/ATLAS-3762 > Project: Atlas > Issue Type: Improvement >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Attachments: ATLAS-3762-Edge-fetch-improvement-gremlin.patch, > ATLAS-3762-Improve-Edge-creator-using-Genuine-iterat.patch > > > *Background* > One of the earlier commits replaced vertices and edges fetch with > _StreamSupport.stream_. This uses _Collect(toList),_ which causes all > contents to be fetched. > Using this causes large amount of data to be fetched. > *Solution* > Switch to iterators that will use lazy loading. > *Edge Fetch Refactoring* > Change the _getEdge_ to iterate on smaller dataset. > Here are the scenarios: > - _fromVertex_ is _hive_table_, _toVertex_ is _hive_column_. This means that > outgoing edges from _fromVertex_ will be many more than incoming edges to > _toVertex_. > - _fromVertex_ is _hive_process_execution_, _toVertex_ is _hive_table_. This > means that outgoing edges from _fromVertex_ will be fewer than incoming edges > _hive_table_. > Approach: > * Search it is a linear search, it will be more efficient to iterate over > fewer items than more items. > * Fetch count edge items for _fromVertex_ and _toVertex_. If either of the > count is 0, return NULL, since it will not result in anything being found. > * If either of the counts is not 0, take the one with fewer elements and > perform a search. > [~sidharthkmishra] Thanks for this simple but effective fix. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3773) Migration: From 0.8 to latest: Breaks Relationships
Ashutosh Mestry created ATLAS-3773: -- Summary: Migration: From 0.8 to latest: Breaks Relationships Key: ATLAS-3773 URL: https://issues.apache.org/jira/browse/ATLAS-3773 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: trunk Reporter: Ashutosh Mestry Assignee: Ashutosh Mestry Fix For: trunk *Steps to Duplicate* # Migrate data from 0.8 to latest. E.g. data containing hive db and tables. # In the web UI, use a DSL search like: _hive_table db.name="migration_database_8"_ _**Expected results:_ The hive_table with for database _migration_database_8_ should be displayed. **_Actual results_: No results are displayed. There are exceptions logged on the server-side. *Root Cause* As part of implementation of ATLAS-3370, shadow properties were introduced for index type STRING. These need to be set for data that is migrated. *Solution* Use patch handler to add these missing types. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3772) UI: (Classic) Statistics: Clicking the Active or Deleted entities hyperlinks does not close the window.
Rahul Kurup created ATLAS-3772: -- Summary: UI: (Classic) Statistics: Clicking the Active or Deleted entities hyperlinks does not close the window. Key: ATLAS-3772 URL: https://issues.apache.org/jira/browse/ATLAS-3772 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup In Classic UI Statistics menu, on clicking either the 'Active' or 'Deleted' entry the search is executed in the background but the window does not close. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3771) UI: Cannot apply term to AtlasServer type entity
Rahul Kurup created ATLAS-3771: -- Summary: UI: Cannot apply term to AtlasServer type entity Key: ATLAS-3771 URL: https://issues.apache.org/jira/browse/ATLAS-3771 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Applying term to AtlasServer does not work either from search results page (it throws an error when I click on assign) or from the entity details page (the window for applying terms does not appear). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3770) UI(Classic): Active and Deleted hyperlinks for certain entities throwing error on click
Rahul Kurup created ATLAS-3770: -- Summary: UI(Classic): Active and Deleted hyperlinks for certain entities throwing error on click Key: ATLAS-3770 URL: https://issues.apache.org/jira/browse/ATLAS-3770 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup In the Statistics menu under the Entities section, when I try to click the Active or Deleted link for '__ExportImportAuditEntry' ,'AtlasGlossary' and 'AtlasGlossaryTerm', I get an message "Invalid Expression or Classification/Type has been deleted". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3769) UI: Changing page limit in Admin audits resets any filters applied on that page
Rahul Kurup created ATLAS-3769: -- Summary: UI: Changing page limit in Admin audits resets any filters applied on that page Key: ATLAS-3769 URL: https://issues.apache.org/jira/browse/ATLAS-3769 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup If any filters are set in the Audits Page in the Administration menu, changing the page limit in Admin audits resets the filters applied on that page. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3768) Business Metadata import issue with extra commas csv file
Rahul Kurup created ATLAS-3768:
--
Summary: Business Metadata import issue with extra commas csv file
Key: ATLAS-3768
URL: https://issues.apache.org/jira/browse/ATLAS-3768
Project: Atlas
Issue Type: Bug
Reporter: Rahul Kurup
If a csv file contains an extra comma(which gets inserted automatically at the
end of the file after editing and saving the file in a program like Libreoffice
Calc) and is then imported, it throws the error
{code:java}
"Provided UniqueAttributeValue is not valid.at line #1"{code}
which is an invalid error message and doesn't inform the user as to what the
error actually is.
It should point to the extra comma in the error message, or the extra comma
should be handled.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3766) Atlas Admin Audit UI pagination is not working
[ https://issues.apache.org/jira/browse/ATLAS-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3766: --- Attachment: ATLAS-3766-1.patch > Atlas Admin Audit UI pagination is not working > -- > > Key: ATLAS-3766 > URL: https://issues.apache.org/jira/browse/ATLAS-3766 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3766-1.patch, ATLAS-3766.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3767) [BusinessTerm] Create Hierachy on Business Term
Eric Theroude created ATLAS-3767:
Summary: [BusinessTerm] Create Hierachy on Business Term
Key: ATLAS-3767
URL: https://issues.apache.org/jira/browse/ATLAS-3767
Project: Atlas
Issue Type: Improvement
Components: atlas-core
Affects Versions: 2.0.0
Reporter: Eric Theroude
I would like to create a hierarchy on my business term definition.
For example, for a Person :
* Person is a Business Term
* I would like to have also the properties of the Person as a BusinessTerm :
** Person FirstName is a Business Term
** Person Name is a BusinessTerm
** Person Birthday is a BusinessTerm
* And I want to associate the business term for properties of the Person to
the Person Business Term
I don't want to use Categories because it is not possible to associate category
to an Entity.
I would something like this for the defintion of this relationship :
{code:java}
//
{
"relationshipDefs": [
{
"name": "BusinessTermHierarchyRelation",
"serviceType": "Atlas",
"typeVersion": "1.0",
"relationshipCategory": "ASSOCIATION",
"endDef1": {
"name": "parentTerm",
"type": "AtlasGlossaryTerm",
"cardinality": "SINGLE"
},
"endDef2": {
"name": "childrenTerms",
"type": "AtlasGlossaryTerm",
"cardinality": "SET"
},
"propagateTags": "NONE"
}
]
}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-3755) Allow system attributes to be updated when policy allows
[ https://issues.apache.org/jira/browse/ATLAS-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17096435#comment-17096435 ] Bolke de Bruin commented on ATLAS-3755: --- [~madhan] I have updated the patch to only use `entity-update` and `entity-create` and do the access request in one go. This makes the access request backwards incompatible and it would require an update to the Ranger plugin. I suggest putting the check against the attributes behind a feature flag so it remains backwards compatible and it would not affect anyone who isn't using access controls on attributes or system attributes. let me know what you think. > Allow system attributes to be updated when policy allows > > > Key: ATLAS-3755 > URL: https://issues.apache.org/jira/browse/ATLAS-3755 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 2.0.0, 2.1.0 >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Critical > Attachments: > 0001-ATLAS-3755-Allow-system-attributes-to-be-updated-by-.patch, > 0001-ATLAS-3755-Allow-system-attributes-to-be-updated-by-.patch, > 0001-ATLAS-3755-Allow-system-attributes-to-be-updated-by-.patch, feature.patch > > > Atlas does not operate in a isolated environment, this is one of the reasons > the "homeId" system attribute was introduced. Unfortunately system attributes > can only be updated when importing. This means any integration with other > services is significantly limited (Kafka, Rest API will not work). (See also > ATLAS-3754) > To resolve this I propose to make it possible to update the system attributes > when policy allows it. This introduces new > AtlasPrivilege.ENTITY_UPDATE_SYSTEM_ATTRIBUTE and > AtlasPrivilege.ENTITY_CREATE_SYSTEM_ATTRIBUTE next to > AtlasPrivilege.ENTITY_UPDATE_ATTRIBUTE and > AtlasPrivilege.ENTITY_CREATE_ATTRIBUTE rather than just checking on the > entity level. In certain places we will then drop the requirement for an > import to be active as this can now happen through other channels as well. > This allows operators to specify policies that allow granular controls over > attributes and system attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3755) Allow system attributes to be updated when policy allows
[ https://issues.apache.org/jira/browse/ATLAS-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated ATLAS-3755: -- Attachment: feature.patch > Allow system attributes to be updated when policy allows > > > Key: ATLAS-3755 > URL: https://issues.apache.org/jira/browse/ATLAS-3755 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 2.0.0, 2.1.0 >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Critical > Attachments: > 0001-ATLAS-3755-Allow-system-attributes-to-be-updated-by-.patch, > 0001-ATLAS-3755-Allow-system-attributes-to-be-updated-by-.patch, > 0001-ATLAS-3755-Allow-system-attributes-to-be-updated-by-.patch, feature.patch > > > Atlas does not operate in a isolated environment, this is one of the reasons > the "homeId" system attribute was introduced. Unfortunately system attributes > can only be updated when importing. This means any integration with other > services is significantly limited (Kafka, Rest API will not work). (See also > ATLAS-3754) > To resolve this I propose to make it possible to update the system attributes > when policy allows it. This introduces new > AtlasPrivilege.ENTITY_UPDATE_SYSTEM_ATTRIBUTE and > AtlasPrivilege.ENTITY_CREATE_SYSTEM_ATTRIBUTE next to > AtlasPrivilege.ENTITY_UPDATE_ATTRIBUTE and > AtlasPrivilege.ENTITY_CREATE_ATTRIBUTE rather than just checking on the > entity level. In certain places we will then drop the requirement for an > import to be active as this can now happen through other channels as well. > This allows operators to specify policies that allow granular controls over > attributes and system attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Review Request 72438: Allow system attributes to be updated when policy allows
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72438/ --- (Updated April 30, 2020, 11:17 a.m.) Review request for atlas, Ashutosh Mestry, Bolke de Bruin, Madhan Neethiraj, Nixon Rodrigues, and Sarath Subramanian. Changes --- - Simplified access request model Bugs: ATLAS-3755 https://issues.apache.org/jira/browse/ATLAS-3755 Repository: atlas Description --- Atlas does not operate in a isolated environment, this is one of the reasons the "homeId" system attribute was introduced. Unfortunately system attributes can only be updated when importing. This means any integration with other services is significantly limited (Kafka, Rest API will not work). (See also ATLAS-3754) To resolve this I propose to make it possible to update the system attributes when policy allows it. This introduces new AtlasPrivilege.ENTITY_UPDATE_SYSTEM_ATTRIBUTE and AtlasPrivilege.ENTITY_CREATE_SYSTEM_ATTRIBUTE next to AtlasPrivilege.ENTITY_UPDATE_ATTRIBUTE and AtlasPrivilege.ENTITY_CREATE_ATTRIBUTE rather than just checking on the entity level. In certain places we will then drop the requirement for an import to be active as this can now happen through other channels as well. This allows operators to specify policies that allow granular controls over attributes and system attributes. Diffs (updated) - authorization/src/main/java/org/apache/atlas/authorize/AtlasEntityAccessRequest.java 6d49d54b1 authorization/src/main/java/org/apache/atlas/authorize/simple/AtlasSimpleAuthorizer.java 734991691 authorization/src/main/java/org/apache/atlas/authorize/simple/AtlasSimpleAuthzPolicy.java d19112885 authorization/src/main/resources/atlas-simple-authz-policy.json 6b2001279 intg/src/main/java/org/apache/atlas/type/AtlasEntityType.java 3962c3c42 intg/src/main/java/org/apache/atlas/type/Constants.java 3fc13056e repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityStoreV2.java 379150b7b repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphRetriever.java 36bee301d repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityMutationContext.java deb743eea repository/src/main/java/org/apache/atlas/repository/store/graph/v2/IDBasedEntityResolver.java 3b9694851 repository/src/test/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityStoreV2Test.java 38228a8ec Diff: https://reviews.apache.org/r/72438/diff/4/ Changes: https://reviews.apache.org/r/72438/diff/3-4/ Testing --- - Manually tested - Unit test updated Thanks, Bolke de Bruin
[jira] [Updated] (ATLAS-3765) Classic UI: load Clssfication/Administrator url throws error in console
[ https://issues.apache.org/jira/browse/ATLAS-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3765: --- Issue Type: Bug (was: Improvement) > Classic UI: load Clssfication/Administrator url throws error in console > --- > > Key: ATLAS-3765 > URL: https://issues.apache.org/jira/browse/ATLAS-3765 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: image-2020-04-30-11-45-56-461.png > > > Go To browser and enter the following URL and check the console. > http://:/index.html#!/administrator > http://:/index.html#!/tag/tagAttribute/Dimension > !image-2020-04-30-11-45-56-461.png|width=697,height=274! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3766) Atlas Admin Audit UI pagination is not working
[ https://issues.apache.org/jira/browse/ATLAS-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3766: --- Attachment: ATLAS-3766.patch > Atlas Admin Audit UI pagination is not working > -- > > Key: ATLAS-3766 > URL: https://issues.apache.org/jira/browse/ATLAS-3766 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3766.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3766) Atlas Admin Audit UI pagination is not working
Keval Bhatt created ATLAS-3766: -- Summary: Atlas Admin Audit UI pagination is not working Key: ATLAS-3766 URL: https://issues.apache.org/jira/browse/ATLAS-3766 Project: Atlas Issue Type: Bug Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 2.1.0, 3.0.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3765) Classic UI: load Clssfication/Administrator url throws error in console
[ https://issues.apache.org/jira/browse/ATLAS-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3765: --- Fix Version/s: 3.0.0 2.1.0 > Classic UI: load Clssfication/Administrator url throws error in console > --- > > Key: ATLAS-3765 > URL: https://issues.apache.org/jira/browse/ATLAS-3765 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: image-2020-04-30-11-45-56-461.png > > > Go To browser and enter the following URL and check the console. > http://:/index.html#!/administrator > http://:/index.html#!/tag/tagAttribute/Dimension > !image-2020-04-30-11-45-56-461.png|width=697,height=274! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3764) Set default value for "atlas.graph.index.search.max-result-set-size" in ApplicationProperties
[ https://issues.apache.org/jira/browse/ATLAS-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues resolved ATLAS-3764. Resolution: Fixed Thanks [~mad...@apache.org] for review. > Set default value for "atlas.graph.index.search.max-result-set-size" in > ApplicationProperties > - > > Key: ATLAS-3764 > URL: https://issues.apache.org/jira/browse/ATLAS-3764 > Project: Atlas > Issue Type: Improvement > Components: atlas-intg >Affects Versions: 2.0.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3764.1.patch > > > Set Default value "2147483647" for > "*atlas.graph.index.search.max-result-set-size*" property in Atlas > ApplicationProperties. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3764) Set default value for "atlas.graph.index.search.max-result-set-size" in ApplicationProperties
[ https://issues.apache.org/jira/browse/ATLAS-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17096172#comment-17096172 ] ASF subversion and git services commented on ATLAS-3764: Commit a3bb6a959c15fc7aa72acccec8b9e61d0c882659 in atlas's branch refs/heads/branch-2.0 from Nixon Rodrigues [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=a3bb6a9 ] ATLAS-3764 : Set default value for atlas.graph.index.search.max-result-set-size in Atlas ApplicationProperties (cherry picked from commit 861f8f23bc086fa8be0ebee82848dd2c883acdb0) > Set default value for "atlas.graph.index.search.max-result-set-size" in > ApplicationProperties > - > > Key: ATLAS-3764 > URL: https://issues.apache.org/jira/browse/ATLAS-3764 > Project: Atlas > Issue Type: Improvement > Components: atlas-intg >Affects Versions: 2.0.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3764.1.patch > > > Set Default value "2147483647" for > "*atlas.graph.index.search.max-result-set-size*" property in Atlas > ApplicationProperties. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3765) Classic UI: load Clssfication/Administrator url throws error in console
[ https://issues.apache.org/jira/browse/ATLAS-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3765: --- Description: Go To browser and enter the following URL and check the console. http://:/index.html#!/administrator http://:/index.html#!/tag/tagAttribute/Dimension !image-2020-04-30-11-45-56-461.png|width=697,height=274! > Classic UI: load Clssfication/Administrator url throws error in console > --- > > Key: ATLAS-3765 > URL: https://issues.apache.org/jira/browse/ATLAS-3765 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: image-2020-04-30-11-45-56-461.png > > > Go To browser and enter the following URL and check the console. > http://:/index.html#!/administrator > http://:/index.html#!/tag/tagAttribute/Dimension > !image-2020-04-30-11-45-56-461.png|width=697,height=274! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3764) Set default value for "atlas.graph.index.search.max-result-set-size" in ApplicationProperties
[ https://issues.apache.org/jira/browse/ATLAS-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17096170#comment-17096170 ] ASF subversion and git services commented on ATLAS-3764: Commit 861f8f23bc086fa8be0ebee82848dd2c883acdb0 in atlas's branch refs/heads/master from Nixon Rodrigues [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=861f8f2 ] ATLAS-3764 : Set default value for atlas.graph.index.search.max-result-set-size in Atlas ApplicationProperties > Set default value for "atlas.graph.index.search.max-result-set-size" in > ApplicationProperties > - > > Key: ATLAS-3764 > URL: https://issues.apache.org/jira/browse/ATLAS-3764 > Project: Atlas > Issue Type: Improvement > Components: atlas-intg >Affects Versions: 2.0.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3764.1.patch > > > Set Default value "2147483647" for > "*atlas.graph.index.search.max-result-set-size*" property in Atlas > ApplicationProperties. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3765) Classic UI: load Clssfication/Administrator url throws error in console
[ https://issues.apache.org/jira/browse/ATLAS-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3765: --- Attachment: image-2020-04-30-11-45-56-461.png > Classic UI: load Clssfication/Administrator url throws error in console > --- > > Key: ATLAS-3765 > URL: https://issues.apache.org/jira/browse/ATLAS-3765 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: image-2020-04-30-11-45-56-461.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3764) Set default value for "atlas.graph.index.search.max-result-set-size" in ApplicationProperties
[ https://issues.apache.org/jira/browse/ATLAS-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-3764: --- Fix Version/s: 3.0.0 > Set default value for "atlas.graph.index.search.max-result-set-size" in > ApplicationProperties > - > > Key: ATLAS-3764 > URL: https://issues.apache.org/jira/browse/ATLAS-3764 > Project: Atlas > Issue Type: Improvement > Components: atlas-intg >Affects Versions: 2.0.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3764.1.patch > > > Set Default value "2147483647" for > "*atlas.graph.index.search.max-result-set-size*" property in Atlas > ApplicationProperties. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3764) Set default value for "atlas.graph.index.search.max-result-set-size" in ApplicationProperties
[ https://issues.apache.org/jira/browse/ATLAS-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-3764: --- Attachment: ATLAS-3764.1.patch > Set default value for "atlas.graph.index.search.max-result-set-size" in > ApplicationProperties > - > > Key: ATLAS-3764 > URL: https://issues.apache.org/jira/browse/ATLAS-3764 > Project: Atlas > Issue Type: Improvement > Components: atlas-intg >Affects Versions: 2.0.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 2.1.0 > > Attachments: ATLAS-3764.1.patch > > > Set Default value "2147483647" for > "*atlas.graph.index.search.max-result-set-size*" property in Atlas > ApplicationProperties. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3765) Classic UI: load Clssfication/Administrator url throws error in console
[ https://issues.apache.org/jira/browse/ATLAS-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3765: --- Summary: Classic UI: load Clssfication/Administrator url throws error in console (was: Classic UI: load Clssfication/Administrator url throws ) > Classic UI: load Clssfication/Administrator url throws error in console > --- > > Key: ATLAS-3765 > URL: https://issues.apache.org/jira/browse/ATLAS-3765 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3765) Classic UI: load Clssfication/Administrator url throws
[ https://issues.apache.org/jira/browse/ATLAS-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3765: --- Summary: Classic UI: load Clssfication/Administrator url throws (was: Classic UI: load Clssfication/dministrator) > Classic UI: load Clssfication/Administrator url throws > --- > > Key: ATLAS-3765 > URL: https://issues.apache.org/jira/browse/ATLAS-3765 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Review Request 72453: ATLAS-3764 : Set default value for "atlas.graph.index.search.max-result-set-size" in ApplicationProperties
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72453/ --- (Updated April 30, 2020, 6:11 a.m.) Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Nikhil Bonte, and Sarath Subramanian. Changes --- Address review comment from Madhan. Repository: atlas Description --- Inconsistency in search result is seen when atlas.graph.index.search.max-result-set-size is set lower to max result size when solr replication factor is 2. To overcome this issue set default value "2147483647" for "atlas.graph.index.search.max-result-set-size" property in Atlas ApplicationProperties. Diffs (updated) - intg/src/main/java/org/apache/atlas/ApplicationProperties.java 1f1f3771b Diff: https://reviews.apache.org/r/72453/diff/2/ Changes: https://reviews.apache.org/r/72453/diff/1-2/ Testing --- PC build :- https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/1857/console Scenario - 1 When atlas-application.properties is set with atlas.graph.index.search.max-result-set-size=200 [inconsistency seen in search result ] 2020-04-29 18:10:39,799 INFO - [main:] ~ Loading atlas-application.properties from file:/usr/hdp/current/atlas-server/conf/atlas-application.properties (ApplicationProperties:133) 2020-04-29 18:10:39,809 INFO - [main:] ~ Using graphdb backend 'janus' (ApplicationProperties:285) 2020-04-29 18:10:39,809 INFO - [main:] ~ Using storage backend 'hbase2' (ApplicationProperties:296) 2020-04-29 18:10:39,809 INFO - [main:] ~ Using index backend 'solr' (ApplicationProperties:307) 2020-04-29 18:10:39,809 INFO - [main:] ~ Atlas is running in MODE: PROD. (ApplicationProperties:311) 2020-04-29 18:10:39,810 INFO - [main:] ~ Setting solr-wait-searcher property 'true' (ApplicationProperties:317) 2020-04-29 18:10:39,810 INFO - [main:] ~ Setting index.search.map-name property 'false' (ApplicationProperties:321) 2020-04-29 18:10:39,810 INFO - [main:] ~ Setting atlas.graph.index.search.max-result-set-size = 200 (ApplicationProperties:331)(ApplicationProperties:343) Scenario 2 - When custom property atlas.graph.index.search.max-result-set-size is removed from Ambari [ search results are consistent in size] 2020-04-29 18:17:01,883 INFO - [main:] ~ Loading atlas-application.properties from file:/usr/hdp/current/atlas-server/conf/atlas-application.properties (ApplicationProperties:133) 2020-04-29 18:17:01,892 INFO - [main:] ~ Using graphdb backend 'janus' (ApplicationProperties:285) 2020-04-29 18:17:01,892 INFO - [main:] ~ Using storage backend 'hbase2' (ApplicationProperties:296) 2020-04-29 18:17:01,892 INFO - [main:] ~ Using index backend 'solr' (ApplicationProperties:307) 2020-04-29 18:17:01,893 INFO - [main:] ~ Atlas is running in MODE: PROD. (ApplicationProperties:311) 2020-04-29 18:17:01,893 INFO - [main:] ~ Setting solr-wait-searcher property 'true' (ApplicationProperties:317) 2020-04-29 18:17:01,893 INFO - [main:] ~ Setting index.search.map-name property 'false' (ApplicationProperties:321) 2020-04-29 18:17:01,893 INFO - [main:] ~ Setting atlas.graph.index.search.max-result-set-size = 2147483647 (ApplicationProperties:331)2020-04-29 18:17:01,893 INFO - [main:] ~ Property (set to default) atlas.graph.cache.db-cache = true (ApplicationProperties:343) Thanks, Nixon Rodrigues
[jira] [Created] (ATLAS-3765) Classic UI: load Clssfication/dministrator
Keval Bhatt created ATLAS-3765: -- Summary: Classic UI: load Clssfication/dministrator Key: ATLAS-3765 URL: https://issues.apache.org/jira/browse/ATLAS-3765 Project: Atlas Issue Type: Improvement Reporter: Keval Bhatt Assignee: Keval Bhatt -- This message was sent by Atlassian Jira (v8.3.4#803005)
