Re: Review Request 72638: ATLAS-3875: Enhancing AtlasClient by adding missing API endpoints
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72638/ --- (Updated July 16, 2020, 3:17 a.m.) Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Sarath Subramanian, and Sidharth Mishra. Changes --- Addressing review comments related change Bugs: ATLAS-3875 https://issues.apache.org/jira/browse/ATLAS-3875 Repository: atlas Description --- There are many missing API endpoints in AtlasClientV2. This solution is adding functions corresponding to those missing APIs for the following Rest endpoints. 1. TypeRest 2. EntityRest 3. LineageRest 4. DiscoveryRest 5. GlossaryRest 6. RelationshipRest This will enable users to test and integrate with APIs more effectively via AtlasCient. Diffs (updated) - client/client-v2/src/main/java/org/apache/atlas/AtlasClientV2.java 7b6d1d0f3 client/common/src/main/java/org/apache/atlas/AtlasBaseClient.java e3d2ebc34 webapp/pom.xml 3c55b4dd4 webapp/src/test/java/org/apache/atlas/web/TestUtils.java e22a1c10d webapp/src/test/java/org/apache/atlas/web/integration/BaseResourceIT.java 680028892 webapp/src/test/java/org/apache/atlas/web/integration/BasicSearchIT.java 808f62354 webapp/src/test/java/org/apache/atlas/web/integration/EntityV2JerseyResourceIT.java cc883d615 webapp/src/test/java/org/apache/atlas/web/integration/GlossaryClientV2IT.java PRE-CREATION webapp/src/test/java/org/apache/atlas/web/integration/LineageClientV2IT.java PRE-CREATION webapp/src/test/java/org/apache/atlas/web/integration/TypedefsJerseyResourceIT.java 331ea2c47 webapp/src/test/resources/json/search-parameters/attribute-filters.json PRE-CREATION Diff: https://reviews.apache.org/r/72638/diff/5/ Changes: https://reviews.apache.org/r/72638/diff/4-5/ Testing --- IT has been added for newly created functions in AtlasClientV2. Validated by running IT on local system. Thanks, Jyoti Singh
[jira] [Commented] (ATLAS-3811) Update version in branch-2.0 to 2.2.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/ATLAS-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17158830#comment-17158830 ] ASF subversion and git services commented on ATLAS-3811: Commit 5cf4b6d0e672b192954f8bb2d8591b9efdbbd17f in atlas's branch refs/heads/branch-2.0 from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=5cf4b6d ] ATLAS-3811: updated version in pom.xml from 2.1.0 to 2.2.0-SNAPSHOT > Update version in branch-2.0 to 2.2.0-SNAPSHOT > -- > > Key: ATLAS-3811 > URL: https://issues.apache.org/jira/browse/ATLAS-3811 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 2.1.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Attachments: ATLAS-3811.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3359) Relationships : Unique attribute in a relationship is not honored
[ https://issues.apache.org/jira/browse/ATLAS-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3359: Fix Version/s: (was: 2.1.0) 2.2.0 > Relationships : Unique attribute in a relationship is not honored > - > > Key: ATLAS-3359 > URL: https://issues.apache.org/jira/browse/ATLAS-3359 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Nixon Rodrigues >Assignee: Mayank Jain >Priority: Major > Fix For: 2.2.0 > > > 1.Created a relationship typedef between type1 & type2 with attribute "attr1" > which is unique (set "IsUnique" to true). > 2. Created entity1 (type1) and entity2(type2) and created a relationship > instance between them with "attr1" value , say "value1". > 3. Created entity3 (type1) and entity4(type2) and created a relationship > instance between them with "attr1" value with the same value "value1". > Expected the relationship creation between entity3 and entity4 would fail > because a relationship with "attr1 " with "value1" is already created between > entity1 and entity2. But request passed and the relationship is created > successfully. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3839) import-hive.sh build target directory error
[ https://issues.apache.org/jira/browse/ATLAS-3839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3839: Fix Version/s: (was: 2.1.0) 2.2.0 > import-hive.sh build target directory error > --- > > Key: ATLAS-3839 > URL: https://issues.apache.org/jira/browse/ATLAS-3839 > Project: Atlas > Issue Type: Bug > Components: hive-integration >Affects Versions: 1.1.0, 2.0.0 >Reporter: limbo >Priority: Minor > Labels: patch-available > Fix For: 2.2.0 > > Attachments: ATLAS-3839.patch > > > import-hive.sh build to bin directory rather than in hook-bin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3468) Exclude JTS topology suite library from being packaged
[ https://issues.apache.org/jira/browse/ATLAS-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3468: Fix Version/s: (was: 2.1.0) 2.2.0 > Exclude JTS topology suite library from being packaged > -- > > Key: ATLAS-3468 > URL: https://issues.apache.org/jira/browse/ATLAS-3468 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 2.2.0 > > Attachments: ATLAS-3468.002.patch > > > Exclude JTS topology suite library from being packaged -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3646) Create new 'spark_ml_model_dataset' and 'spark_ml_pipeline_dataset' relationship definitions
[ https://issues.apache.org/jira/browse/ATLAS-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3646: Fix Version/s: (was: 2.1.0) 2.2.0 > Create new 'spark_ml_model_dataset' and 'spark_ml_pipeline_dataset' > relationship definitions > > > Key: ATLAS-3646 > URL: https://issues.apache.org/jira/browse/ATLAS-3646 > Project: Atlas > Issue Type: Task >Reporter: Vladislav Glinskiy >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > Create new 'spark_ml_model_dataset' and 'spark_ml_pipeline_dataset' > relationship definitions. This is required in order to integrate Spark Atlas > Connector's ML event processor. > Previously, Spark Atlas Connector used the 'spark_ml_directory' model for the > ML model directory and 'spark_ml_model_ml_directory', > 'spark_ml_pipeline_ml_directory' relationship definitions. Usage of the > 'spark_ml_directory' was reverted in the scope of > [https://github.com/hortonworks-spark/spark-atlas-connector/issues/61], > [https://github.com/hortonworks-spark/spark-atlas-connector/pull/62] so ML > model directory is 'DataSet' entity(i.e. 'hdfs_path', 'fs_path'). > Thus, new relationship definitions must be created, since there is no > straightforward way to update existing ones to use 'DataSet' type instead of > it's child type 'spark_ml_directory'. > See: > * ATLAS-3640 > * [https://github.com/apache/atlas/pull/88#issuecomment-592699723] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3665) Add 'queryText' attribute to the 'spark_process' type
[ https://issues.apache.org/jira/browse/ATLAS-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3665: Fix Version/s: (was: 2.1.0) 2.2.0 > Add 'queryText' attribute to the 'spark_process' type > - > > Key: ATLAS-3665 > URL: https://issues.apache.org/jira/browse/ATLAS-3665 > Project: Atlas > Issue Type: Task >Reporter: Vladislav Glinskiy >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Time Spent: 2h > Remaining Estimate: 0h > > Add 'queryText' attribute to the 'spark_process' type in order to make > `spark_process` more readable by the user. The `queryText` attribute stores > exact SQL query that are executed within the Spark session as a Spark process. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3353) HMS Hook does not capture the deleted column with alter table replace columns command.
[
https://issues.apache.org/jira/browse/ATLAS-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-3353:
Fix Version/s: (was: 2.1.0)
2.2.0
> HMS Hook does not capture the deleted column with alter table replace columns
> command.
> --
>
> Key: ATLAS-3353
> URL: https://issues.apache.org/jira/browse/ATLAS-3353
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.2.0
>
>
> For the below commands, HMS Hook does not capture the replaced column as
> deleted entity.
> {noformat}
> create table table_with_dropped_cols_1 (id int,name string,dob date)
> alter table table_with_dropped_cols_1 replace columns (id int,name
> string,address string)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3501) Update guava version to 28.0-jre
[ https://issues.apache.org/jira/browse/ATLAS-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3501: Fix Version/s: (was: 2.1.0) 2.2.0 > Update guava version to 28.0-jre > > > Key: ATLAS-3501 > URL: https://issues.apache.org/jira/browse/ATLAS-3501 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Aadarsh Jajodia >Assignee: Aadarsh Jajodia >Priority: Major > Fix For: 2.2.0 > > Attachments: 0001-ATLAS-3501-Update-guava-version-to-28.0-jre.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3724) Qualified name pattern for Column cause ambiguity in Quickstart data.
[ https://issues.apache.org/jira/browse/ATLAS-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3724: Fix Version/s: (was: 2.1.0) 2.2.0 > Qualified name pattern for Column cause ambiguity in Quickstart data. > - > > Key: ATLAS-3724 > URL: https://issues.apache.org/jira/browse/ATLAS-3724 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.0.0, 2.1.0, 3.0.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > Fix For: 2.0.0, 2.2.0 > > Attachments: ATLAS-3724.patch > > > 1) Create Entity of type Column name = app_id, qualified name = app_id@cl1 > assign Table - logging_fact_monthly_mv > 2) Again Create same entity with same qualified name > assign different Table - log_fact_daily_mv > 3) Check Column Relationship, Only one Table relationship is seen > 4) Check Table (logging_fact_monthly_mv,log_fact_daily_mv) In Both > Relationship, Column app_id is seen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3341) Atlas knox SSO doesnt work when using external load balancer for Atlas UI.
[ https://issues.apache.org/jira/browse/ATLAS-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3341: Fix Version/s: (was: 2.1.0) 2.2.0 > Atlas knox SSO doesnt work when using external load balancer for Atlas UI. > -- > > Key: ATLAS-3341 > URL: https://issues.apache.org/jira/browse/ATLAS-3341 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.1.0, 2.0.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 3.0.0, 2.2.0 > > > If Atlas ports are not open to access, so leveraging SSL offloading and using > External loabalancer enabled with SSL to access Atlas UI. > However with the above setup Knox SSO redirection is not working as expected. > As the redirectUrl/Forwarded url created is not set for proper redirection. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3410) Term assigned to historical entity is not visible in Details page.
[ https://issues.apache.org/jira/browse/ATLAS-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3410: Fix Version/s: (was: 2.1.0) 2.2.0 > Term assigned to historical entity is not visible in Details page. > -- > > Key: ATLAS-3410 > URL: https://issues.apache.org/jira/browse/ATLAS-3410 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: chaitali borole >Priority: Minor > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3410-Server.patch, ATLAS-3410-dashboardv3.patch, > ATLAS-3410.patch > > > This issue is related to an earlier one (ATLAS-3403). When a entity with a > term associated to it is deleted, and if you navigate to the Details page for > that entity, the classification is displayed but not the term. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3837) execute import-hive.sh raise exception: Failed to load application properties
[
https://issues.apache.org/jira/browse/ATLAS-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-3837:
Fix Version/s: (was: 2.1.0)
2.2.0
> execute import-hive.sh raise exception: Failed to load application properties
> -
>
> Key: ATLAS-3837
> URL: https://issues.apache.org/jira/browse/ATLAS-3837
> Project: Atlas
> Issue Type: Bug
> Components: hive-integration
>Affects Versions: 1.2.0, 2.0.0
>Reporter: limbo
>Priority: Major
> Fix For: 2.2.0
>
> Attachments: ATLAS-3837.patch
>
>
> when run import-hive.sh, the script raise as follow:
> {code:java}
> 2020-06-11 10:49:01,177 INFO - [main:] ~ Looking for
> atlas-application.properties in classpath (ApplicationProperties:97)
> 2020-06-11 10:49:01,181 INFO - [main:] ~ Looking for
> /atlas-application.properties in classpath (ApplicationProperties:102)
> 2020-06-11 10:49:01,182 INFO - [main:] ~ Loading atlas-application.properties
> from null (ApplicationProperties:110)
> 2020-06-11 10:49:01,199 ERROR - [main:] ~ Import failed
> (HiveMetaStoreBridge:176)
> org.apache.atlas.AtlasException: Failed to load application properties
> at org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:121)
> at org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:73)
> at
> org.apache.atlas.hive.bridge.HiveMetaStoreBridge.main(HiveMetaStoreBridge.java:120)
> Caused by: org.apache.commons.configuration.ConfigurationException: Cannot
> locate configuration source null
> at
> org.apache.commons.configuration.AbstractFileConfiguration.load(AbstractFileConfiguration.java:259)
> at
> org.apache.commons.configuration.AbstractFileConfiguration.load(AbstractFileConfiguration.java:238)
> at
> org.apache.commons.configuration.AbstractFileConfiguration.(AbstractFileConfiguration.java:197)
> at
> org.apache.commons.configuration.PropertiesConfiguration.(PropertiesConfiguration.java:284)
> at
> org.apache.atlas.ApplicationProperties.(ApplicationProperties.java:56)
> at org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:112)
> ... 2 more
> {code}
> the script can not find the config file of atlas-application.properties
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3498) Update basic-search to enable search using labels
[ https://issues.apache.org/jira/browse/ATLAS-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3498: Fix Version/s: (was: 2.1.0) 2.2.0 > Update basic-search to enable search using labels > - > > Key: ATLAS-3498 > URL: https://issues.apache.org/jira/browse/ATLAS-3498 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 2.2.0 > > > Update basic-search to enable search using labels -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3255) UI: IE 10 - Page Limit button gets displaced after clicking it.
[ https://issues.apache.org/jira/browse/ATLAS-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3255: Fix Version/s: (was: 2.1.0) 2.2.0 > UI: IE 10 - Page Limit button gets displaced after clicking it. > --- > > Key: ATLAS-3255 > URL: https://issues.apache.org/jira/browse/ATLAS-3255 > Project: Atlas > Issue Type: Sub-task >Reporter: Rahul Kurup >Assignee: Keval Bhatt >Priority: Minor > Fix For: 3.0.0, 1.3.0, 2.2.0 > > > In IE 10, the Page Limit button position gets displaced and moves to the > middle of the search results page after clicking it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3852) Entity Bulk Create with unique reference
[ https://issues.apache.org/jira/browse/ATLAS-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3852: Fix Version/s: (was: 2.1.0) 2.2.0 > Entity Bulk Create with unique reference > > > Key: ATLAS-3852 > URL: https://issues.apache.org/jira/browse/ATLAS-3852 > Project: Atlas > Issue Type: Improvement >Reporter: Vasanth kumar RJ >Priority: Major > Fix For: 2.2.0 > > Attachments: ATLAS-3852.patch, BulkPostCreate.json > > > Entities created in bulk and unique referenced in same request. Bulk create > DB, Table and Column referenced in a request itself. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3683) Entity details > Business Metadata, multi-valued attribute spacing issue
[ https://issues.apache.org/jira/browse/ATLAS-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3683: Fix Version/s: (was: 2.1.0) 2.2.0 > Entity details > Business Metadata, multi-valued attribute spacing issue > > > Key: ATLAS-3683 > URL: https://issues.apache.org/jira/browse/ATLAS-3683 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty >Priority: Minor > Fix For: 3.0.0, 2.2.0 > > Attachments: Screenshot 2020-03-25 at 1.14.15 AM.png > > > While applying Business metadata attribute to an entity, once the > multi-valued attribute is applied, the multi values are displayed without any > spacing. This is a bit unreadable. It would be good if we can add a space > between comma-separated values. > CC: [~kevalbhatt] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3824) update README.txt to replace earlier version references to 2.1.0
[ https://issues.apache.org/jira/browse/ATLAS-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3824: Fix Version/s: (was: 2.1.0) 2.2.0 > update README.txt to replace earlier version references to 2.1.0 > > > Key: ATLAS-3824 > URL: https://issues.apache.org/jira/browse/ATLAS-3824 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.1.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 2.2.0 > > Attachments: ATLAS-3824.patch > > > Update references to earlier version in README.txt with 2.1.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3407) Regression, Impala and Spark Hook : Rename table doesn't rename existing table , but creates new table with updated name.
[ https://issues.apache.org/jira/browse/ATLAS-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3407: Fix Version/s: (was: 2.1.0) 2.2.0 > Regression, Impala and Spark Hook : Rename table doesn't rename existing > table , but creates new table with updated name. > - > > Key: ATLAS-3407 > URL: https://issues.apache.org/jira/browse/ATLAS-3407 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 2.2.0 > > > with hive hook , rename table works as expected. > With spark and impala hook (hms hook), rename table creates new table with > updated name and doesn't update the existing table entity. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3610) Enable logging to multiple targets (logdir, stdout)
[ https://issues.apache.org/jira/browse/ATLAS-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3610: Fix Version/s: (was: 2.1.0) 2.2.0 > Enable logging to multiple targets (logdir, stdout) > --- > > Key: ATLAS-3610 > URL: https://issues.apache.org/jira/browse/ATLAS-3610 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 3.0.0 >Reporter: Mariusz Górski >Priority: Minor > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3610-1.patch, ATLAS-3610-2.patch, > ATLAS-3610-3.patch, ATLAS-3610.patch > > Time Spent: 50m > Remaining Estimate: 0h > > *Problem description* > When starting Atlas, Python scripts are invoked to spawn all necessary > processes. This is achieved with the use of _subprocess.Popen()_ in > _runProcess()_ function of _atlas_config.py_ script. While doing that, stdout > is being redirected to log files, which (for java processes) can override > log4j configuration (if configured with stdout handler). This creates > situation when log4j configuration cannot be relied upon and prevents logging > to stdout. > *Proposed solution* > * Add possibility to log to stdout by using multiple stdout/stderr handlers > * Adjust _runProcess()_ function from _atlas_config.py_ script (and all > functions relying on it) to provide _logconsole_ kwarg which will add > additional handler to Popen stdout/stderr redirection > * Add _ENABLE_LOGGING_TO_CONSOLE_ env variable (defaulting to _False_) for > backwards compatibility. > * Adjust _atlas_start.py_ script to make use of _ENABLE_LOGGING_TO_CONSOLE_ > and provide it in functions invoking atlas/solr/elasticsearch/zookeeper > *Predicted Benefits* > This improvement would bring the benefit of enabling logging to stdout (which > is supressed for now even if configured in spawned components), which could > be very useful when running Atlas in docker container or in Kubernetes/OC, > where some logging scraping is present. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3890) Enhancement for all BulkAPIs.
[
https://issues.apache.org/jira/browse/ATLAS-3890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-3890:
Fix Version/s: (was: 2.1.0)
2.2.0
> Enhancement for all BulkAPIs.
> -
>
> Key: ATLAS-3890
> URL: https://issues.apache.org/jira/browse/ATLAS-3890
> Project: Atlas
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Labels: api-change
> Fix For: 2.2.0
>
>
> According to below linked Atlas Jira two Bulk Apis are enhanced to return
> authorised entities or modify them when some of then entity types are blocked
> by policies in Ranger for access to user.Hence we are improving the other
> bulk Apis too.
> Previously user only used to get 403 error if he tries to access or modify
> entities which comprised of both authorised as well as unauthorised typenames.
> DELETE /bulk - EntityREST.deleteByGuids()
> GET /bulk/uniqueAttribute/type/\{typeName} -
> EntityREST.getEntitiesByUniqueAttributes()
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3855) Bulk entity tag association and bulk api enhancement
[
https://issues.apache.org/jira/browse/ATLAS-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-3855:
Fix Version/s: (was: 2.1.0)
2.2.0
> Bulk entity tag association and bulk api enhancement
>
>
> Key: ATLAS-3855
> URL: https://issues.apache.org/jira/browse/ATLAS-3855
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Affects Versions: 2.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Labels: api-change
> Fix For: 2.2.0
>
>
> API : /api/atlas/v2/entity/bulk/classification
> Body :
> {code:java}
> {"classification":{"typeName":"PII","attributes":{},"propagate":true,"removePropagationsOnEntityDelete":false,"validityPeriods":[]},"entityGuids":["guid1","guid2"]}
> {code}
> when user doesn't have authorisation on either of guid1 or guid2 , the bulk
> entity call fails with 403.
> bulk api _v2/entity/bulk_ to retrieve a list of entities identified by its
> guids.
> This bulk api fails with 403 if some guids belong to entities on which user
> is *unauthorized* and other guids belong to entities on which user is
> *authorized*.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-3810) Update Atlas website for 2.1.0 release
[ https://issues.apache.org/jira/browse/ATLAS-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17158778#comment-17158778 ] ASF subversion and git services commented on ATLAS-3810: Commit a42f0c1cba87623a9553718a75a844cfadb24218 in atlas's branch refs/heads/master from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=a42f0c1 ] ATLAS-3810: updated documentation for 2.1.0 release (cherry picked from commit 5c613f5ff33d9d6675f2d088f70b47377062417f) > Update Atlas website for 2.1.0 release > -- > > Key: ATLAS-3810 > URL: https://issues.apache.org/jira/browse/ATLAS-3810 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 2.1.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Attachments: ATLAS-3810.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3810) Update Atlas website for 2.1.0 release
[ https://issues.apache.org/jira/browse/ATLAS-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17158777#comment-17158777 ] ASF subversion and git services commented on ATLAS-3810: Commit 5c613f5ff33d9d6675f2d088f70b47377062417f in atlas's branch refs/heads/branch-2.0 from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=5c613f5 ] ATLAS-3810: updated documentation for 2.1.0 release > Update Atlas website for 2.1.0 release > -- > > Key: ATLAS-3810 > URL: https://issues.apache.org/jira/browse/ATLAS-3810 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 2.1.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Attachments: ATLAS-3810.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3809) Publish release artifacts
[ https://issues.apache.org/jira/browse/ATLAS-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved ATLAS-3809. - Fix Version/s: 2.1.0 Assignee: Madhan Neethiraj Resolution: Done > Publish release artifacts > - > > Key: ATLAS-3809 > URL: https://issues.apache.org/jira/browse/ATLAS-3809 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 2.1.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 2.1.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3895) how can I upgrade Atlas
Spongebob created ATLAS-3895: Summary: how can I upgrade Atlas Key: ATLAS-3895 URL: https://issues.apache.org/jira/browse/ATLAS-3895 Project: Atlas Issue Type: Wish Components: atlas-core Affects Versions: 2.0.0 Reporter: Spongebob Fix For: 2.0.0 I had built Apache Atlas with the source package as version 2.0.0. How can I upgrade it to the version 2.1.0 ? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3894) UI: User is able to add and remove business metadata from deleted entities
Keval Bhatt created ATLAS-3894: -- Summary: UI: User is able to add and remove business metadata from deleted entities Key: ATLAS-3894 URL: https://issues.apache.org/jira/browse/ATLAS-3894 Project: Atlas Issue Type: Bug Affects Versions: 3.0.0 Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 3.0.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
