[jira] [Created] (ATLAS-4652) Missing null check leading to NPE in isSoftReferenced method in AtlasStructDef
Srikanth Venkat created ATLAS-4652:
--
Summary: Missing null check leading to NPE in isSoftReferenced
method in AtlasStructDef
Key: ATLAS-4652
URL: https://issues.apache.org/jira/browse/ATLAS-4652
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 2.2.0
Reporter: Srikanth Venkat
The code inside isSoftReferenced method in AtlasStructDef class below:
*{{}}* {{@JsonIgnore}}
{{ public boolean isSoftReferenced() {}}
{{ return this.options != null && }}{{
getOptions().containsKey(AtlasAttributeDef.ATTRDEF_OPTION_SOFT_REFERENCE) &&}}
{{
getOptions().get(AtlasAttributeDef.ATTRDEF_OPTION_SOFT_REFERENCE){color:#de350b}.equals(STRING_TRUE){color};}}
{{ }}}
Since the null check is not performed, it can lead to NPE in typedef resolution.
A sample typedef payload like the following can potentially trigger the NPE
error in attribute resolution, i.e. EntityGraphRetriever.mapVertexToAttribute,
where attribute.getAttributeDef().isSoftReferenced() is called
{
"businessMetadataDefs": [
{
"category": "BUSINESS_METADATA",
"name": "bizType1",
"description": "test",
"attributeDefs": [
{
"name": "bizAttr1",
"typeName": "string",
"isOptional": true,
"cardinality": "SINGLE",
"options": {
*"isSoftReference": null,*
"maxStrLength": "50",
"applicableEntityTypes": "[\"Asset\"]"
}
}
]
}
]
}
It would be furthermore helpful to run SonarCube or FindBugs to determine any
other incidences where this pattern of missing null check exists in Atlas
codebase and address them.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [VOTE] Release Apache Atlas version 1.2.0 - rc3
+1 for Atlas 1.2 rc3 Thanks to Atlas community for the timely much needed fixes in this release! Cheers Srikanth Srikanth Venkat Senior Director - Product Management Cloudera On Tue, Jun 4, 2019 at 8:53 PM Le Ma wrote: > + 1 for Apache Atlas 1.2.0 # 3 > > - built successfully from the source tar file > - ran quick_start_v1, data successfully shows up > - validate basic search functionality > - add/delete classification, results are expected. > > thanks, > Le > > Ramesh Mani 于2019年6月4日周二 上午8:44写道： > > > +1 for Apache Atlas 1.2.0 rc3 > > > > - Built successfully from the source tar file > > > > > https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz > > - Verified the PGP and SHA > > > > Thanks, > > Ramesh > > > > On Mon, Jun 3, 2019 at 5:10 AM Binit Gutka < > > binit.gu...@freestoneinfotech.com> wrote: > > > > > +1 Release Apache Atlas 1.2.0 release candidate #3 > > > > > > - Verified PGP signature. > > > - Built successfully from the source tar file > > > - Ran quick start and validated basic functionality. > > > - Tested Atlas UI packaging in embedded-hbase mode. > > > - Performed few basic search. > > > - Lineage Export functionality tested. > > > - Lineage Pan, Zoom, Filter, Search and settings functionality tested. > > > > > > Thanks. > > > > > > On Mon, Jun 3, 2019 at 1:41 PM Nixon Rodrigues < > > > nixon.rodrig...@freestoneinfotech.com> wrote: > > > > > > > Atlas team, > > > > > > > > Apache Atlas 1.2.0 release candidate #3 is now available for a vote > > > within > > > > dev community. > > > > > > > > Following commits went into branch-1.0 since the last release > candidate > > > > (rc2): > > > > > > > > ATLAS-3180:- New Bulk retrieval API with servicetype parameter. > > > > ATLAS-3227:- Bulk delete does not delete the indexes properly. > > > > > > > > Links to the release artifacts are given below. Please review and > vote. > > > > > > > > The vote will be open for at least 72 hours or until necessary votes > > are > > > > reached. > > > > [ ] +1 approve > > > > [ ] +0 no opinion > > > > [ ] -1 disapprove (and reason why) > > > > > > > > > > > > Thanks, > > > > Nixon Rodrigues > > > > > > > > > > > > List of issues addressed in this release: > > > > > > > > > > > > > > https://issues.apache.org/jira/browse/ATLAS-3201?jql=project%20%3D%20ATLAS%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%201.2.0%20ORDER%20BY%20key%20DESC > > > > > > > > Git tag for the release: > > > > https://github.com/apache/atlas/releases/tag/release-1.2.0-rc3 > > > > > > > > Sources for the release: > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz > > > > > > > > Source release verification: > > > > PGP Signature: > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz.asc > > > > MD5 Hash: > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz.md5 > > > > SHA512 Hash: > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/atlas/1.2.0-rc3/apache-atlas-1.2.0-sources.tar.gz.sha512 > > > > > > > > Keys to verify the signature of the release artifacts are available > at: > > > > https://dist.apache.org/repos/dist/dev/atlas/KEYS > > > > > > > > > > > > > -- > > > *Thanks,* > > > *Binit.* > > > > > >
[jira] [Commented] (ATLAS-3153) Support OpenID Connect directly rather than through Knox
[ https://issues.apache.org/jira/browse/ATLAS-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846433#comment-16846433 ] Srikanth Venkat commented on ATLAS-3153: [~bolke] This is a good addition. Can you help the community by providing a design doc for the use case and the arch. and configs needed for Atlas to consume OpenID asserted credentials? Perhaps an interaction diagram to explain how this feature will work, the actual flow, and configs needed (for example how the user/group mappings are fetched) will be useful to review the patch and understand the feature. Also quick question will a similar mechanism work for Azure AD via OAuth2 (especially from an authN/authZ perspective) > Support OpenID Connect directly rather than through Knox > > > Key: ATLAS-3153 > URL: https://issues.apache.org/jira/browse/ATLAS-3153 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Bolke de Bruin >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > The current SSO implementation with Apache Knox is limiting SSO > interoperability to Apache Knox. Knox uses JWT verification which could > easily be extended to allow for direct OpenID Connect support and doesn't > require organizations to deploy Knox. > Required changes: > * Pickup bearer token from headers > * Improve and standardize redirecting > * Optionally: obtain certificates from well_known uri > * Optionally: obtain user groups from userinfo endpoint rather than UGI -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3133) Capture metadata for different executions of the same process in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Venkat updated ATLAS-3133: --- Description: Background: The current process metadata model within Atlas does not track multiple instances of execution of the same process. For example if we run same DDL (e.g. insert into table A select * from table B, C) multiple times Atlas does not capture the multiple instances of execution of the same logical process. User story: As a compliance admin or data steward, I need to be able to track multiple executions of the same process or pipeline that were done at different times and relate them to the logical process so that I can understand traceability and how different instances of my data pipelining operations performed over time. Acceptance Criteria: 1) Every new instance of process execution is captured with the appropriate metadata for the process along with context (who, what, when) 2) One can navigate between process and process execution in Atlas UI and explore relevant metadata of each entity 3) Process nodes in lineage view display high level information about number of process executions associated with a particular process node. was: Background: The current Atlas process metadata model within Atlas does not track multiple instances of execution of the same process. For example if we run same DDL (e.g. insert into table A select * from table B, C) multiple times Atlas does not capture the multiple instances of execution of the same logical process. User story: As a compliance admin or data steward, I need to be able to track multiple executions of the same process or pipeline that were done at different times and relate them to the logical process so that I can provide traceability and understand how different instances of my data pipelining operations performed over time. Acceptance Criteria: 1) Every new instance of process execution is captured with the appropriate metadata for the process along with context (who, what, when) 2) One can navigate between process and process execution in Atlas UI and explore relevant metadata 3) Process nodes in lineage display high level information about number of process executions associated with a particular process node. > Capture metadata for different executions of the same process in Atlas > -- > > Key: ATLAS-3133 > URL: https://issues.apache.org/jira/browse/ATLAS-3133 > Project: Atlas > Issue Type: New Feature > Components: atlas-core, atlas-webui > Reporter: Srikanth Venkat >Assignee: Aadarsh Jajodia >Priority: Critical > Attachments: > 0001-ATLAS-3133-Adding-support-for-Process-Executions-in-.patch, Adding > Process Executions In Atlas(Community).pdf > > > Background: The current process metadata model within Atlas does not track > multiple instances of execution of the same process. For example if we run > same DDL (e.g. insert into table A select * from table B, C) multiple times > Atlas does not capture the multiple instances of execution of the same > logical process. > User story: As a compliance admin or data steward, I need to be able to track > multiple executions of the same process or pipeline that were done at > different times and relate them to the logical process so that I can > understand traceability and how different instances of my data pipelining > operations performed over time. > Acceptance Criteria: > 1) Every new instance of process execution is captured with the appropriate > metadata for the process along with context (who, what, when) > 2) One can navigate between process and process execution in Atlas UI and > explore relevant metadata of each entity > 3) Process nodes in lineage view display high level information about number > of process executions associated with a particular process node. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-3131) UI : Stats Popup Improvements
[ https://issues.apache.org/jira/browse/ATLAS-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16816462#comment-16816462 ] Srikanth Venkat edited comment on ATLAS-3131 at 4/12/19 4:57 PM: - Please add before and after screenshots so we can understand what the improvements are especially since there isn't a lot of description was (Author: srikvenk): Please add before and after screenshots so we can understand what the improvements are. > UI : Stats Popup Improvements > - > > Key: ATLAS-3131 > URL: https://issues.apache.org/jira/browse/ATLAS-3131 > Project: Atlas > Issue Type: Improvement >Reporter: Binit Gutka >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3131-3.patch, ATLAS-3131.patch, > ATLAS-3131_1.patch, ATLAS-3131_2.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3131) UI : Stats Popup Improvements
[ https://issues.apache.org/jira/browse/ATLAS-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16816462#comment-16816462 ] Srikanth Venkat commented on ATLAS-3131: Please add before and after screenshots so we can understand what the improvements are. > UI : Stats Popup Improvements > - > > Key: ATLAS-3131 > URL: https://issues.apache.org/jira/browse/ATLAS-3131 > Project: Atlas > Issue Type: Improvement >Reporter: Binit Gutka >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3131-3.patch, ATLAS-3131.patch, > ATLAS-3131_1.patch, ATLAS-3131_2.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3133) Capture metadata for different executions of the same process in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Venkat updated ATLAS-3133: --- Description: Background: The current Atlas process metadata model within Atlas does not track multiple instances of execution of the same process. For example if we run same DDL (e.g. insert into table A select * from table B, C) multiple times Atlas does not capture the multiple instances of execution of the same logical process. User story: As a compliance admin or data steward, I need to be able to track multiple executions of the same process or pipeline that were done at different times and relate them to the logical process so that I can provide traceability and understand how different instances of my data pipelining operations performed over time. Acceptance Criteria: 1) Every new instance of process execution is captured with the appropriate metadata for the process along with context (who, what, when) 2) One can navigate between process and process execution in Atlas UI and explore relevant metadata 3) Process nodes in lineage display high level information about number of process executions associated with a particular process node. was: Background: The current Atlas process metadata model within Atlas does not track multiple instances of execution of the same process. For example if we run a CTAS command (e.g. insert into table A select * from table B, C) multiple times Atlas does not capture the multiple instances of execution of the same logical process. User story: As a compliance admin or data steward, I need to be able to track multiple executions of the same process or pipeline that were done at different times and relate them to the logical process so that I can provide traceability and understand how different instances of my data pipelining operations performed over time. Acceptance Criteria: 1) Every new instance of process execution is captured with the appropriate metadata for the process along with context (who, what, when) 2) One can navigate between process and process execution in Atlas UI and explore relevant metadata 3) Process nodes in lineage display high level information about number of process executions associated with a particular process node. > Capture metadata for different executions of the same process in Atlas > -- > > Key: ATLAS-3133 > URL: https://issues.apache.org/jira/browse/ATLAS-3133 > Project: Atlas > Issue Type: New Feature > Components: atlas-core, atlas-webui > Reporter: Srikanth Venkat >Assignee: Aadarsh Jajodia >Priority: Critical > > Background: The current Atlas process metadata model within Atlas does not > track multiple instances of execution of the same process. For example if we > run same DDL (e.g. insert into table A select * from table B, C) multiple > times Atlas does not capture the multiple instances of execution of the same > logical process. > User story: As a compliance admin or data steward, I need to be able to track > multiple executions of the same process or pipeline that were done at > different times and relate them to the logical process so that I can provide > traceability and understand how different instances of my data pipelining > operations performed over time. > Acceptance Criteria: > 1) Every new instance of process execution is captured with the appropriate > metadata for the process along with context (who, what, when) > 2) One can navigate between process and process execution in Atlas UI and > explore relevant metadata > 3) Process nodes in lineage display high level information about number of > process executions associated with a particular process node. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3133) Capture metadata for different execution of the same process in Atlas
Srikanth Venkat created ATLAS-3133: -- Summary: Capture metadata for different execution of the same process in Atlas Key: ATLAS-3133 URL: https://issues.apache.org/jira/browse/ATLAS-3133 Project: Atlas Issue Type: New Feature Components: atlas-core, atlas-webui Reporter: Srikanth Venkat Background: The current Atlas process metadata model within Atlas does not track multiple instances of execution of the same process. For example if we run a CTAS command (e.g. insert into table A select * from table B, C) multiple times Atlas does not capture the multiple instances of execution of the same logical process. User story: As a compliance admin or data steward, I need to be able to track multiple executions of the same process or pipeline that were done at different times and relate them to the logical process so that I can provide traceability and understand how different instances of my data pipelining operations performed over time. Acceptance Criteria: 1) Every new instance of process execution is captured with the appropriate metadata for the process along with context (who, what, when) 2) One can navigate between process and process execution in Atlas UI and explore relevant metadata 3) Process nodes in lineage display high level information about number of process executions associated with a particular process node. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3133) Capture metadata for different executions of the same process in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Venkat updated ATLAS-3133: --- Summary: Capture metadata for different executions of the same process in Atlas (was: Capture metadata for different execution of the same process in Atlas) > Capture metadata for different executions of the same process in Atlas > -- > > Key: ATLAS-3133 > URL: https://issues.apache.org/jira/browse/ATLAS-3133 > Project: Atlas > Issue Type: New Feature > Components: atlas-core, atlas-webui > Reporter: Srikanth Venkat >Priority: Critical > > Background: The current Atlas process metadata model within Atlas does not > track multiple instances of execution of the same process. For example if we > run a CTAS command (e.g. insert into table A select * from table B, C) > multiple times Atlas does not capture the multiple instances of execution of > the same logical process. > User story: As a compliance admin or data steward, I need to be able to track > multiple executions of the same process or pipeline that were done at > different times and relate them to the logical process so that I can provide > traceability and understand how different instances of my data pipelining > operations performed over time. > Acceptance Criteria: > 1) Every new instance of process execution is captured with the appropriate > metadata for the process along with context (who, what, when) > 2) One can navigate between process and process execution in Atlas UI and > explore relevant metadata > 3) Process nodes in lineage display high level information about number of > process executions associated with a particular process node. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2951) Lineage Improvments
[ https://issues.apache.org/jira/browse/ATLAS-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16705071#comment-16705071 ] Srikanth Venkat commented on ATLAS-2951: [~kevalbhatt] [~abhib4] Can we please add screenshots for the "before" and "after" experience for each subtask so we can understand how the new behavior will get shown in the UI? > Lineage Improvments > --- > > Key: ATLAS-2951 > URL: https://issues.apache.org/jira/browse/ATLAS-2951 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 0.8.4, 1.2.0, 2.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2976) UI : Show entity specific icon for the lineage node
[ https://issues.apache.org/jira/browse/ATLAS-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16705070#comment-16705070 ] Srikanth Venkat commented on ATLAS-2976: [~kevalbhatt] Can we please add screenshot for what this would look like in UI after this behavior change? > UI : Show entity specific icon for the lineage node > --- > > Key: ATLAS-2976 > URL: https://issues.apache.org/jira/browse/ATLAS-2976 > Project: Atlas > Issue Type: Sub-task >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-2976-1.patch, ATLAS-2976-2.patch, > ATLAS-2976-3.patch, ATLAS-2976.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2983) Fixes and clean up for Atlas Kafka bridge utility
[ https://issues.apache.org/jira/browse/ATLAS-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16705068#comment-16705068 ] Srikanth Venkat commented on ATLAS-2983: I don't think we should remove the capability to add entities from the UI as a convenience for customers that want to track metadata for entities from Kafka but do not have the ability run Atlas bridge/hook in those Kafka environments. > Fixes and clean up for Atlas Kafka bridge utility > - > > Key: ATLAS-2983 > URL: https://issues.apache.org/jira/browse/ATLAS-2983 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Affects Versions: 1.0.0, 1.1.0 >Reporter: Umesh Padashetty >Priority: Major > Attachments: ATLAS-2983.patch > > > # Currently, import-kafka.sh script allows selective kafka topic import by > providing -t or --topic option, but the script only checks for the topics > which start with the topic name provided and does not support regular > expression based selective import. With the fix provided, regex patterns can > be used along with -t as well as -f (file based import) option > # When a bad import-kafka command is being fired, following usage is being > printed on the console. Here, option should be -t instead of -n. Have fixed > this minor issue, along with some more text changes > ** import-kafka.sh [*-n* OR --topic ] > # Since we now have support for kakfa bridge and hbase hook/bridge, option > for creating entities for the following in Atlas UI could be removed > ## hbase_table > ## hbase_column > ## hbase_column_family > ## kafka_topic > ## hbase_namespace -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [VOTE] Release Apache Atlas v 0.8.3 - RC1
+1 (non-binding) Thanks to the Atlas community for the key fixes and stabilization improvements. Thanks Ashutosh for putting this release together! Cheers Srikanth Srikanth Venkat Hortonworks On 10/29/18, 1:34 AM, "Nixon Rodrigues" wrote: Verified the rc1 bits provided. +1 for release of 0.8.3 RC #1 Thanks, Nixon Rodrigues On Sat, Oct 27, 2018 at 12:47 PM Sarath Subramanian wrote: > Thanks Ashutosh for Apache Atlas 0.8.3 RC #1. > > * Verified source checksum and validated signature > * Build source using embedded-hbase-solr profile (build successful) > * Ran quickstart and validated entities in atlas UI. > * Validated basic search, advanced search and saved search feature. > * Validated lineage filtering to hide process entities. > > +1 > > Thanks, > Sarath Subramanian > > > On Fri, Oct 26, 2018 at 3:48 PM Ashutosh Mestry > wrote: > > > Apache Atlas 0.8.3 Release Candidate #1 is now available for a vote > within > > dev community. > > > > Following commits went into branch-0.8 since the last release candidate: > > - ATLAS-2900: Exported connected bug fix. > > - ATLAS-2934: Utility to detect and repair incorrect entity state. > > - ATLAS-2935: Updated NPM package version and added package-lock.json. > > - ATLAS-2927: Update lineage query for Process entities. > > - ATLAS-2930: UI changes to handle softReference attribute elegantly. > > - ATLAS-2931: Set isSoftReferenced method to JsonIgnore. > > - ATLAS-2926: ZipSink out of memory error for very large entities. > > - ATLAS-2917: Filter added for lineage to hide Process entity. > > - ATLAS-2921: Updated import scripts exist status in case of Java error. > > - ATLAS-2924: Used encoded property name in getEncodedProperty. > > > > Links to the release artifacts are given below. Please review and vote. > > > > The vote will be open for at least 72 hours or until necessary votes are > > reached. > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > Ashutosh Mestry > > > > List of issues addressed in this release: > > > https://issues.apache.org/jira/browse/ATLAS-2924?jql=project%20%3D%20ATLAS%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%200.8.3%20ORDER%20BY%20key%20DESC > > > > Git tag for the release: > > https://github.com/apache/atlas/tree/release-0.8.3-rc1 > > > > Sources for the release: > > > https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc1/apache-atlas-0.8.3-sources.tar.gz > > > > Source release verification: > > PGP Signature: > > > https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc1/apache-atlas-0.8.3-sources.tar.gz.asc > > SHA512 > > < > https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc1/apache-atlas-0.8.3-sources.tar.gz.ascSHA512 > > > > Hash: > > > https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc1/apache-atlas-0.8.3-sources.tar.gz.sha512 > > > > Keys to verify the signature of the release artifacts are available at: > > https://dist.apache.org/repos/dist/dev/atlas/KEYS > > > > > > >
[jira] [Assigned] (ATLAS-2694) Avro schema typedef and support for Avro schema evolution in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Venkat reassigned ATLAS-2694: -- Assignee: Barbara Eckman > Avro schema typedef and support for Avro schema evolution in Atlas > --- > > Key: ATLAS-2694 > URL: https://issues.apache.org/jira/browse/ATLAS-2694 > Project: Atlas > Issue Type: New Feature > Components: atlas-core > Reporter: Srikanth Venkat >Assignee: Barbara Eckman >Priority: Critical > > Currently the base types in Atlas do not include Avro schemas. It would be > nice to add typedef for Avro schema and any associated metadata to support > schema evolution. > * For example, Avro_schema type supports: > ** All avro types, both primitive and complex, including union types, as > fields of schema > ** All types have doc strings and defaults > ** A field of a schema can be another schema > ** Indefinite nesting of records, arrays. > ** Associated entities array attribute contains pointers to all datasets > that reflect the avro schema > ** Fully expanded avroNotation for use in serDe > ** Schema evolution features such as isLatest (Boolean) and version number > * Schema evolution Process > ** Input: avro schema > ** Output: new version of avro schema > ** Compatibility: FULL, BACKWARD, FORWARD, NONE > ** IsBreakingChange (Boolean): does the change produce an incompatible > schema? (ie its compatibility is not “FULL”) > * Atlas UI enhancement for JSON-valued attributes to support avro schema and > avro schema evolution > ** Currently JSON-valued attributes are fully displayed in-line with other > attributes, not pretty-printed, cluttering the display. To support a better > display, we can display JSON-valued attributes in a one-line box that can be > scrolled down, or fully expanded with a mouse click that pretty-prints the > JSON. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2696) Typedef extensions for Kafka in Atlas
Srikanth Venkat created ATLAS-2696: -- Summary: Typedef extensions for Kafka in Atlas Key: ATLAS-2696 URL: https://issues.apache.org/jira/browse/ATLAS-2696 Project: Atlas Issue Type: Improvement Reporter: Srikanth Venkat Kafka topic typedef in Atlas can be improved to include many useful operational (config related) and contextual metadata properties: * config inputs such as max throughput per sec, average message size, messages per day, retention time * Sizing outputs such as number and size of partitions, replication factor * Contact information on the data producer * Array of avro schemas that are associated with the topic (based on Avro schema extensions outlined in ATLAS-2694) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2694) Avro schema typedef and support for Avro schema evolution in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Venkat updated ATLAS-2694: --- Issue Type: New Feature (was: Improvement) > Avro schema typedef and support for Avro schema evolution in Atlas > --- > > Key: ATLAS-2694 > URL: https://issues.apache.org/jira/browse/ATLAS-2694 > Project: Atlas > Issue Type: New Feature > Components: atlas-core > Reporter: Srikanth Venkat >Priority: Critical > > Currently the base types in Atlas do not include Avro schemas. It would be > nice to add typedef for Avro schema and any associated metadata to support > schema evolution. > * For example, Avro_schema type supports: > ** All avro types, both primitive and complex, including union types, as > fields of schema > ** All types have doc strings and defaults > ** A field of a schema can be another schema > ** Indefinite nesting of records, arrays. > ** Associated entities array attribute contains pointers to all datasets > that reflect the avro schema > ** Fully expanded avroNotation for use in serDe > ** Schema evolution features such as isLatest (Boolean) and version number > * Schema evolution Process > ** Input: avro schema > ** Output: new version of avro schema > ** Compatibility: FULL, BACKWARD, FORWARD, NONE > ** IsBreakingChange (Boolean): does the change produce an incompatible > schema? (ie its compatibility is not “FULL”) > * Atlas UI enhancement for JSON-valued attributes to support avro schema and > avro schema evolution > ** Currently JSON-valued attributes are fully displayed in-line with other > attributes, not pretty-printed, cluttering the display. To support a better > display, we can display JSON-valued attributes in a one-line box that can be > scrolled down, or fully expanded with a mouse click that pretty-prints the > JSON. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2694) Avro schema typedef and support for Avro schema evolution in Atlas
Srikanth Venkat created ATLAS-2694: -- Summary: Avro schema typedef and support for Avro schema evolution in Atlas Key: ATLAS-2694 URL: https://issues.apache.org/jira/browse/ATLAS-2694 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Srikanth Venkat Currently the base types in Atlas do not include Avro schemas. It would be nice to add typedef for Avro schema and any associated metadata to support schema evolution. * For example, Avro_schema type supports: ** All avro types, both primitive and complex, including union types, as fields of schema ** All types have doc strings and defaults ** A field of a schema can be another schema ** Indefinite nesting of records, arrays. ** Associated entities array attribute contains pointers to all datasets that reflect the avro schema ** Fully expanded avroNotation for use in serDe ** Schema evolution features such as isLatest (Boolean) and version number * Schema evolution Process ** Input: avro schema ** Output: new version of avro schema ** Compatibility: FULL, BACKWARD, FORWARD, NONE ** IsBreakingChange (Boolean): does the change produce an incompatible schema? (ie its compatibility is not “FULL”) * Atlas UI enhancement for JSON-valued attributes to support avro schema and avro schema evolution ** Currently JSON-valued attributes are fully displayed in-line with other attributes, not pretty-printed, cluttering the display. To support a better display, we can display JSON-valued attributes in a one-line box that can be scrolled down, or fully expanded with a mouse click that pretty-prints the JSON. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2607) Classification lifecycle through metadata properties and relationships
[ https://issues.apache.org/jira/browse/ATLAS-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Venkat reassigned ATLAS-2607: -- Assignee: Madhan Neethiraj > Classification lifecycle through metadata properties and relationships > -- > > Key: ATLAS-2607 > URL: https://issues.apache.org/jira/browse/ATLAS-2607 > Project: Atlas > Issue Type: Improvement > Components: atlas-core > Reporter: Srikanth Venkat >Assignee: Madhan Neethiraj >Priority: Critical > > Currently tags or classifications in Atlas are considered active once they > are defined. For governance and stewardship purposes, it would be important > to attach the notion of what state in its lifecycle a particular > classification is. This would help with workflows to manage the lifecycle > aspects and provide any filtering needed to take appropriate actions. For > example only active classifications should be considered for classification > based policy enforcement. Additionally lifecycle status would help with > filtering and search as well as reporting and compliance/audit scenarios. > Implementation Proposal: > * All tags or classifications have a "Lifecycle Status" property > * They can go through the following list of states during their lifecycle: > DRAFT -> ACTIVE -> RETIRED > * Lifecycle Status can be set as an enum property that is mandatory or > required for all classifications. > * All existing classifications already present in Atlas before this change > will default to an ACTIVE status so that all pre-existing classifications > will continue to work as before. > * All new classifications after this change will start out with DRAFT status > and a steward or an admin with appropriate permissions can move them into an > ACTIVE state (controlled via Metadata security policies) > * Policy enforcement for authorization on classifications can ignore any > that are not in ACTIVE state. > * Asset can only be attached to classifications with the status of ACTIVE > * For a classification in RETIRED state, we might have an optional > relationship with another classification called "Replaced By" which is the > new classification that the current one was remapped or replaced with. The > inverse relationship could be labeled "Replaces" which is on the new > classification and points to the removed classification that it replaces. > * The state RETIRED implies this classification is no longer used and policy > enforcement will ignore any classifications in such states. > * Additionally UI can filter and show by default only classifications that > are not RETIRED and a checkbox to "Show Retired" > * Deletion of classifications should work as it currently does with no > behavioral changes. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2607) Classification lifecycle through metadata properties and relationships
Srikanth Venkat created ATLAS-2607: -- Summary: Classification lifecycle through metadata properties and relationships Key: ATLAS-2607 URL: https://issues.apache.org/jira/browse/ATLAS-2607 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Srikanth Venkat Currently tags or classifications in Atlas are considered active once they are defined. For governance and stewardship purposes, it would be important to attach the notion of what state in its lifecycle a particular classification is. This would help with workflows to manage the lifecycle aspects and provide any filtering needed to take appropriate actions. For example only active classifications should be considered for classification based policy enforcement. Additionally lifecycle status would help with filtering and search as well as reporting and compliance/audit scenarios. Implementation Proposal: * All tags or classifications have a "Lifecycle Status" property * They can go through the following list of states during their lifecycle: DRAFT -> ACTIVE -> RETIRED * Lifecycle Status can be set as an enum property that is mandatory or required for all classifications. * All existing classifications already present in Atlas before this change will default to an ACTIVE status so that all pre-existing classifications will continue to work as before. * All new classifications after this change will start out with DRAFT status and a steward or an admin with appropriate permissions can move them into an ACTIVE state (controlled via Metadata security policies) * Policy enforcement for authorization on classifications can ignore any that are not in ACTIVE state. * Asset can only be attached to classifications with the status of ACTIVE * For a classification in RETIRED state, we might have an optional relationship with another classification called "Replaced By" which is the new classification that the current one was remapped or replaced with. The inverse relationship could be labeled "Replaces" which is on the new classification and points to the removed classification that it replaces. * The state RETIRED implies this classification is no longer used and policy enforcement will ignore any classifications in such states. * Additionally UI can filter and show by default only classifications that are not RETIRED and a checkbox to "Show Retired" * Deletion of classifications should work as it currently does with no behavioral changes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [VOTE] Release Apache Atlas version 0.8.2
+1 - Release content looks good, thanks to the community for putting this together. Srikanth Venkat | Hortonworks On 2/2/18, 6:44 PM, "Don Bosco Durai" <bo...@apache.org> wrote: Madhan, thanks. The build went through. +1 - Verified signature - Build Successful Bosco On 2/2/18, 4:59 PM, "Madhan Neethiraj" <mad...@apache.org> wrote: Bosco, Thanks for validating the release. As noted in README.txt, there are intermittent UT/IT failures in branch-0.8. Such test failures have been addressed in master branch, but branch-0.8 needs further investigation and updates. Please build Atlas by skipping the tests, with the following commands: mvn clean -DskipTests install mvn clean -DskipTests package -Pdist Thanks, Madhan On 2/2/18, 4:40 PM, "Don Bosco Durai" <bo...@apache.org> wrote: - Verified signature - OK - Build failed with the following error. Do I need to do anything else? Mine is a clean environment. Failed tests: ActiveServerFilterTest.testRedirectedRequestShouldContainQueryParameters:140 Argument(s) are different! Wanted: servletResponse.sendRedirect( "http://localhost:21000/types?query%3DTRAIT; ); -> at org.apache.atlas.web.filters.ActiveServerFilterTest.testRedirectedRequestShouldContainQueryParameters(ActiveServerFilterTest.java:140) Actual invocation has different arguments: servletResponse.sendRedirect( "http://localhost:21000/types?query=TRAIT; ); -> at org.apache.atlas.web.filters.ActiveServerFilter.handleRedirect(ActiveServerFilter.java:150) On 2/2/18, 6:07 AM, "Keval Bhatt" <kevalbhat...@gmail.com> wrote: +1 for the release. . Verified signature and validated release source. . Build the source successfully with unit tests. . Ran QuickStart successfully and tested UI On 01-Feb-2018 7:58 AM, "Madhan Neethiraj" <mad...@apache.org> wrote: > Atlas team, > > Apache Atlas 0.8.2 release candidate #0 is now available for vote within > dev community. Links to the release artifacts are given below. Please > review and vote. > > The vote will be open for at least 72 hours or until necessary votes are > reached. > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Thanks, > Madhan > > > List of issues addressed in this release: https://issues.apache.org/ > jira/issues/?jql=project%20%3D%20Atlas%20AND%20fixVersion% > 20%3D%200.8.2%20ORDER%20BY%20key > > Git tag for the release: https://github.com/apache/ > atlas/tree/release-0.8.2-rc0 > > Sources for the release: https://dist.apache.org/repos/ > dist/dev/atlas/0.8.2-rc0/apache-atlas-0.8.2-sources.tar.gz > > Source release verification: > PGP Signature: https://dist.apache.org/repos/dist/dev/atlas/0.8.2-rc0/ > apache-atlas-0.8.2-sources.tar.gz.asc > MD5 Hash: https://dist.apache.org/repos/dist/dev/atlas/0.8.2-rc0/ > apache-atlas-0.8.2-sources.tar.gz.md5 > > Keys to verify the signature of the release artifacts are available at: > https://dist.apache.org/repos/dist/dev/atlas/KEYS > > > > >
[jira] [Commented] (ATLAS-2216) Remove Catalog/Taxonomy feature from Atlas
[ https://issues.apache.org/jira/browse/ATLAS-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16208870#comment-16208870 ] Srikanth Venkat commented on ATLAS-2216: [~sarath.ku...@gmail.com] This will be a good approach to helping Atlas users migrate to newer and more scalable graph technology while mitigating risk with the current inefficient implementations that might have undesirable side effects for Atlas users. +1 for this approach! > Remove Catalog/Taxonomy feature from Atlas > -- > > Key: ATLAS-2216 > URL: https://issues.apache.org/jira/browse/ATLAS-2216 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian > Fix For: 1.0.0 > > > Taxonomy was introduced as a tech preview feature earlier, but the following > challenges in design/implementation make it necessary to replace the current > implementation with newer features being introduced: > > 1. Current implementation uses tags to model taxonomy terms, which limits a > term to be associated to one entity only. Associating with multiple entities > would require copying of a term, making it difficult to manage. > 2. Current implementation uses dot separated naming convention to model > taxonomy hierarchy. This makes it inefficient to rebuild taxonomy hierarchy. > 3. Current implementation uses tinkerpop blueprints API and makes it > difficult for migration to newer tinkerpop version. > 4. Current implementation is tied to tinkerpop2/titan0 version and since this > is not abstracted; it blocks the introduction of JanusGraph into Atlas > > ATLAS-1410 introduces a new Glossary API, which uses entities to model > taxonomy terms and uses relationships feature to associate terms with > entities. Also, the new model includes categories, which makes Glossary to be > used for wider use-cases. Use of relationships to associate terms with > entities would also allow tag-propagation more naturally. > > Given above, I propose to remove current tech-preview implementation of > taxonomy feature from both server-side and UI in master branch. Once this is > removed, existing taxonomy terms will be seen as tags along with rest of the > tags. > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2108) Atlas UI Improvements: Advanced Search info popup has placeholder content
Srikanth Venkat created ATLAS-2108: -- Summary: Atlas UI Improvements: Advanced Search info popup has placeholder content Key: ATLAS-2108 URL: https://issues.apache.org/jira/browse/ATLAS-2108 Project: Atlas Issue Type: Improvement Components: atlas-webui Affects Versions: 0.8.1-incubating Reporter: Srikanth Venkat Assignee: Keval Bhatt Currently there is placeholder content in the help popup dialog for Advanced search. Placeholder need to be removed to make the help more useful and the placeholders need to be replaced with relevant content such as from Apache Atlas wiki for DSL search http://atlas.apache.org/Search.html *DSL Examples* For the model, Asset - attributes name, owner, description DB - supertype Asset - attributes clusterName, parameters, comment Column - extends Asset - attributes type, comment Table - supertype Asset - db, columns, parameters, comment Classifications - PII, Log Data DSL queries: * from DB * DB where name="Reporting" select name, owner * DB where name="Reporting" select name, owner orderby name * DB where name="Reporting" select name limit 10 * DB where name="Reporting" select name, owner limit 10 offset 0 * DB where name="Reporting" select name, owner orderby name limit 10 offset 5 * DB where name="Reporting" select name, owner orderby name desc limit 10 offset 5 * DB has name * DB is JdbcAccess * Column where Column isa PII * Table where name="sales_fact", columns * Table where name="sales_fact", columns as column select column.name, column.dataType, column.comment * DB groupby(owner) select owner, count() * DB groupby(owner) select owner, max(name) * DB groupby(owner) select owner, min(name) from Person select count() as 'count', max(Person.age) as 'max', min(Person.age) as 'Log Data' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2107) Atlas UI Improvements: Create Entity Modal Dialog
Srikanth Venkat created ATLAS-2107: -- Summary: Atlas UI Improvements: Create Entity Modal Dialog Key: ATLAS-2107 URL: https://issues.apache.org/jira/browse/ATLAS-2107 Project: Atlas Issue Type: Improvement Components: atlas-webui Affects Versions: 0.8.1-incubating Reporter: Srikanth Venkat Assignee: Keval Bhatt Priority: Critical Attachments: Create_Entity modal.png The current design of the create entity modal dialog can be improved with small changes such as removing dividing lines, justifying the labels and making the dialog box to be have a more consistent look and feel. See attached mockup for the suggested improvements (Create_Entity modal.png) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2105) Atlas UI Improvements: Tag/Entity Attribute search model dialog look & feel
[ https://issues.apache.org/jira/browse/ATLAS-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Venkat updated ATLAS-2105: --- Affects Version/s: 0.8.1-incubating > Atlas UI Improvements: Tag/Entity Attribute search model dialog look & feel > --- > > Key: ATLAS-2105 > URL: https://issues.apache.org/jira/browse/ATLAS-2105 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 0.8.1-incubating > Reporter: Srikanth Venkat > Attachments: AttributeFilterModalDialogMockup.png > > > The attribute filter modal dialog's design is not very clean and can be > improved by: > 1) Removing search and apply feature: Since the current dialog presents > multiple actions for the user as it can add to the cognitive load for the > users. With too many decisions, the experience becomes confusing for the user. > 2) The Add/Remove icons can be made more intuitive. By removing from a > hierarchical presentation on attribute filter list and making the icons > simpler visually, the user experience for this dialog can be made more > pleasing. > See attached AttributeFilterModalDialogMockup.png for the main improvement > suggestions noted above -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2105) Atlas UI Improvements: Tag/Entity Attribute search model dialog look & feel
[ https://issues.apache.org/jira/browse/ATLAS-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Venkat updated ATLAS-2105: --- Component/s: atlas-webui > Atlas UI Improvements: Tag/Entity Attribute search model dialog look & feel > --- > > Key: ATLAS-2105 > URL: https://issues.apache.org/jira/browse/ATLAS-2105 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 0.8.1-incubating > Reporter: Srikanth Venkat > Attachments: AttributeFilterModalDialogMockup.png > > > The attribute filter modal dialog's design is not very clean and can be > improved by: > 1) Removing search and apply feature: Since the current dialog presents > multiple actions for the user as it can add to the cognitive load for the > users. With too many decisions, the experience becomes confusing for the user. > 2) The Add/Remove icons can be made more intuitive. By removing from a > hierarchical presentation on attribute filter list and making the icons > simpler visually, the user experience for this dialog can be made more > pleasing. > See attached AttributeFilterModalDialogMockup.png for the main improvement > suggestions noted above -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2105) Atlas UI Improvements: Tag/Entity Attribute search model dialog look & feel
Srikanth Venkat created ATLAS-2105: -- Summary: Atlas UI Improvements: Tag/Entity Attribute search model dialog look & feel Key: ATLAS-2105 URL: https://issues.apache.org/jira/browse/ATLAS-2105 Project: Atlas Issue Type: Improvement Reporter: Srikanth Venkat Attachments: AttributeFilterModalDialogMockup.png The attribute filter modal dialog's design is not very clean and can be improved by: 1) Removing search and apply feature: Since the current dialog presents multiple actions for the user as it can add to the cognitive load for the users. With too many decisions, the experience becomes confusing for the user. 2) The Add/Remove icons can be made more intuitive. By removing from a hierarchical presentation on attribute filter list and making the icons simpler visually, the user experience for this dialog can be made more pleasing. See attached AttributeFilterModalDialogMockup.png for the main improvement suggestions noted above -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ATLAS-2104) Atlas UI Improvements: Tag CRUD operations UI
[ https://issues.apache.org/jira/browse/ATLAS-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Venkat reassigned ATLAS-2104: -- Assignee: Keval Bhatt > Atlas UI Improvements: Tag CRUD operations UI > - > > Key: ATLAS-2104 > URL: https://issues.apache.org/jira/browse/ATLAS-2104 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 0.8.1-incubating > Reporter: Srikanth Venkat >Assignee: Keval Bhatt >Priority: Critical > Attachments: TagDetailsAddedAttr.png > > > 1. Missing labels in Edit tag popup: A Tag could have the same Name and > Description attribute values. In this case, when editing a tag, the Edit > Description modal does not communicate that only "Description" attribute > value is editable and "Name" is not editable. Also since the field does not > have any label it is confusing as to what attribute is allowed to be modified > on edit. It would be nice to prefix the attribute name to the edit dialogs > for updating the value (i.e. show "Name :" and "Description :" as prefixes to > the field values being edited so it is very clear which field is being edited. > 2. Background color of Tag Delete popup confirmation can be improved to be a > more neutral and lighter color. > 3. On Tag details page, a previously added attribute and the button for > adding a new attribute could be made visually different so the call to action > for the user is more clearer. See attached mockup (TagDetailsAddedAttr.png) > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2104) Atlas UI Improvements: Tag CRUD operations UI
[ https://issues.apache.org/jira/browse/ATLAS-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Venkat updated ATLAS-2104: --- Component/s: atlas-webui > Atlas UI Improvements: Tag CRUD operations UI > - > > Key: ATLAS-2104 > URL: https://issues.apache.org/jira/browse/ATLAS-2104 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 0.8.1-incubating > Reporter: Srikanth Venkat >Assignee: Keval Bhatt >Priority: Critical > Attachments: TagDetailsAddedAttr.png > > > 1. Missing labels in Edit tag popup: A Tag could have the same Name and > Description attribute values. In this case, when editing a tag, the Edit > Description modal does not communicate that only "Description" attribute > value is editable and "Name" is not editable. Also since the field does not > have any label it is confusing as to what attribute is allowed to be modified > on edit. It would be nice to prefix the attribute name to the edit dialogs > for updating the value (i.e. show "Name :" and "Description :" as prefixes to > the field values being edited so it is very clear which field is being edited. > 2. Background color of Tag Delete popup confirmation can be improved to be a > more neutral and lighter color. > 3. On Tag details page, a previously added attribute and the button for > adding a new attribute could be made visually different so the call to action > for the user is more clearer. See attached mockup (TagDetailsAddedAttr.png) > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2104) Atlas UI Improvements: Tag CRUD operations UI
[ https://issues.apache.org/jira/browse/ATLAS-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Venkat updated ATLAS-2104: --- Description: 1. Missing labels in Edit tag popup: A Tag could have the same Name and Description attribute values. In this case, when editing a tag, the Edit Description modal does not communicate that only "Description" attribute value is editable and "Name" is not editable. Also since the field does not have any label it is confusing as to what attribute is allowed to be modified on edit. It would be nice to prefix the attribute name to the edit dialogs for updating the value (i.e. show "Name :" and "Description :" as prefixes to the field values being edited so it is very clear which field is being edited. 2. Background color of Tag Delete popup confirmation can be improved to be a more neutral and lighter color. 3. On Tag details page, a previously added attribute and the button for adding a new attribute could be made visually different so the call to action for the user is more clearer. See attached mockup (TagDetailsAddedAttr.png) was: 1. Missing labels in Edit tag popup: A Tag could have the same Name and Description attribute values. In this case, when editing a tag, the Edit Description modal does not communicate that only "Description" attribute value is editable and "Name" is not editable. Also since the field does not have any label it is confusing as to what attribute is allowed to be modified on edit. It would be nice to prefix the attribute name to the edit dialogs for updating the value (i.e. show "Name :" and "Description :" as prefixes to the field values being edited so it is very clear which field is being edited. 2. Background color of Tag Delete popup confirmation can be improved to be a more neutral and lighter color. 3. On Tag details page, Ta previously added attribute and the button for adding attribute could be made visually different so the call to action for the user is clearer. See attached mockup (TagDetailsAddedAttr.png) > Atlas UI Improvements: Tag CRUD operations UI > - > > Key: ATLAS-2104 > URL: https://issues.apache.org/jira/browse/ATLAS-2104 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 0.8.1-incubating >Reporter: Srikanth Venkat >Priority: Critical > Attachments: TagDetailsAddedAttr.png > > > 1. Missing labels in Edit tag popup: A Tag could have the same Name and > Description attribute values. In this case, when editing a tag, the Edit > Description modal does not communicate that only "Description" attribute > value is editable and "Name" is not editable. Also since the field does not > have any label it is confusing as to what attribute is allowed to be modified > on edit. It would be nice to prefix the attribute name to the edit dialogs > for updating the value (i.e. show "Name :" and "Description :" as prefixes to > the field values being edited so it is very clear which field is being edited. > 2. Background color of Tag Delete popup confirmation can be improved to be a > more neutral and lighter color. > 3. On Tag details page, a previously added attribute and the button for > adding a new attribute could be made visually different so the call to action > for the user is more clearer. See attached mockup (TagDetailsAddedAttr.png) > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2104) Atlas UI Improvements: Tag CRUD operations UI
Srikanth Venkat created ATLAS-2104: -- Summary: Atlas UI Improvements: Tag CRUD operations UI Key: ATLAS-2104 URL: https://issues.apache.org/jira/browse/ATLAS-2104 Project: Atlas Issue Type: Improvement Reporter: Srikanth Venkat Priority: Critical Attachments: TagDetailsAddedAttr.png 1. Missing labels in Edit tag popup: A Tag could have the same Name and Description attribute values. In this case, when editing a tag, the Edit Description modal does not communicate that only "Description" attribute value is editable and "Name" is not editable. Also since the field does not have any label it is confusing as to what attribute is allowed to be modified on edit. It would be nice to prefix the attribute name to the edit dialogs for updating the value (i.e. show "Name :" and "Description :" as prefixes to the field values being edited so it is very clear which field is being edited. 2. Background color of Tag Delete popup confirmation can be improved to be a more neutral and lighter color. 3. On Tag details page, Ta previously added attribute and the button for adding attribute could be made visually different so the call to action for the user is clearer. See attached mockup (TagDetailsAddedAttr.png) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2103) Atlas UI Improvements: Confirmation modal dialog for entity/tag CRUD operations needs to be improved
Srikanth Venkat created ATLAS-2103: -- Summary: Atlas UI Improvements: Confirmation modal dialog for entity/tag CRUD operations needs to be improved Key: ATLAS-2103 URL: https://issues.apache.org/jira/browse/ATLAS-2103 Project: Atlas Issue Type: Improvement Components: atlas-webui Affects Versions: 0.8.1-incubating Reporter: Srikanth Venkat Assignee: Keval Bhatt Priority: Critical Attachments: ConfDialogBoxIssues.png The confirmation dialog when CRUD operations are performed on entities or tags has text that is wrapped with incorrect line breaks and the background color needs to be made lighter to offer a better user experience - see attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2102) Atlas UI Improvements: Search results page
Srikanth Venkat created ATLAS-2102: -- Summary: Atlas UI Improvements: Search results page Key: ATLAS-2102 URL: https://issues.apache.org/jira/browse/ATLAS-2102 Project: Atlas Issue Type: Improvement Components: atlas-webui Affects Versions: 0.8.1-incubating Reporter: Srikanth Venkat Assignee: Keval Bhatt Priority: Critical Attachments: SearchResultsInfoHierarchyUpdates.png 1. Information hierarchy for the text on Search results page needs to be improved. Please see the attached mockup (SearchResultsInfoHierarchyUpdates.png) 2. Previous and Next button should not be present is the number of search results is less than the current page size. 3. Search results table shifts visually if the show historical properties is selected (moves right and down by ~20px) needs to have consistent position in the layout. 4. Edit entity action on Search results table should appear on hover and should not be shown next to the column next to the resulting set fof entity names in as it create unnecessary visual clutter in the table. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Re: [VOTE] Release Apache Atlas 0.8.1 - release candidate 1
+1 (non-binding) I’ve tested on a local VM with a few test scenarios and improvements looks great. The new entity and tag attribute search and column results filter work well and will be great addition for Atlas users. Thanks to the Atlas community for thoughtfully designing and implementing this within such a short period! Cheers Srikanth Srikanth Venkat | Senior Director, Product Management | sven...@hortonworks.com | On 8/25/17, 2:13 PM, "Ramesh Mani" <rm...@hortonworks.com> wrote: +1 for the rc1 of Apache Atlas 0.8.1 release Verified the build with the source https://dist.apache.org/repos/dist/dev/atlas/0.8.1-rc1/apache-atlas-0.8.1- sources.tar.gz Thanks, Ramesh On 8/23/17, 4:48 PM, "Sarath Subramanian" <sar...@apache.org> wrote: >Atlas team, > >I have created a build for Apache Atlas 0.8.1 - release candidate #1. >Thanks to everyone who have contributed to this release and tested >this. > > >Changes since last release-candidate: > > - ATLAS-2038: Minor refactoring to use >org.apache.commons.codec.binary.Base64. > - ATLAS-2073: UI - removing tag or type from drop-down will not >exclude respective filters > - ATLAS-2074: AtlasType.resolveReferences() method made package-private > - ATLAS-2078: Type update using v1 API doesn't route to >createUpdateTypesDef in v2 API > - ATLAS-2079: Fix coverity scan issue and IT failures introduced by >ATLAS-2062 > - ATLAS-2080: fix - tag filters should not be added in the results >attributes list > - ATLAS-2082: basic-search fails when in-memory filters all results >from index-query > >Git tag for the release: > >https://github.com/apache/atlas/tree/release-0.8.1-rc1 > > >Sources for the release: > >https://dist.apache.org/repos/dist/dev/atlas/0.8.1-rc1/apache-atlas-0.8.1- >sources.tar.gz > >Source release verification: > PGP Signature : >https://dist.apache.org/repos/dist/dev/atlas/0.8.1-rc1/apache-atlas-0.8.1- >sources.tar.gz.asc > MD5 Checksum : >https://dist.apache.org/repos/dist/dev/atlas/0.8.1-rc1/apache-atlas-0.8.1- >sources.tar.gz.md5 > > SHA512 Checksum : >https://dist.apache.org/repos/dist/dev/atlas/0.8.1-rc1/apache-atlas-0.8.1- >sources.tar.gz.sha512 > >Keys to verify the signature of the release artifacts are available at: > >https://dist.apache.org/repos/dist/dev/atlas/KEYS > > >List of improvements and issues addressed in this release: > >https://issues.apache.org/jira/browse/ATLAS-2066?jql=project%20%3D%20ATLAS >%20AND%20status%20%3D%20Resolved%20AND%20resolution%20%3D%20Fixed%20AND%20 >fixVersion%20%3D%200.8.1-incubating%20ORDER%20BY%20key%20DESC > > >Note that this is a source only release and we are voting on the >source *release-0.8.1-rc1*. Please download, test, and try it out. > >Voting will be open for at least *72 hours* (until the required number >of votes are obtained) till 26th August, 2017 04:45 PM PT. > >[ ] +1 approve >[ ] +0 no opinion >[ ] -1 disapprove (and reason why) > >+1 from my side for the release. > > >Thanks, > >Sarath Subramanian
