[jira] [Updated] (ATLAS-3015) Tool: Associate Classifications to Entities based on QualifiedName
[ https://issues.apache.org/jira/browse/ATLAS-3015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3015: --- Attachment: ATLAS-3015-Classification-Updater-tool.patch > Tool: Associate Classifications to Entities based on QualifiedName > -- > > Key: ATLAS-3015 > URL: https://issues.apache.org/jira/browse/ATLAS-3015 > Project: Atlas > Issue Type: Improvement >Reporter: Nikhil Bonte >Assignee: Ashutosh Mestry >Priority: Major > Attachments: ATLAS-3015-Classification-Updater-tool.patch > > > *Background* > Situation: A setup where Atlas classifications associated with entities the > data is subsequently erased and all data is lost. Entities are then > re-created using _import-hive.sh_. With this approach, the entities are > created within Atlas but there is no easy way to associate classifications to > these entities. > *Solution and Approach Guidance* > # Before erasing Atlas database, create file with classifications and > entity-classification mapping. > # Erase the database. > # Create entities using appropriate means, say _import-hive.sh_. > # Read the file from step 1 and update Atlas. > The tool should: > * Use _AtlasClient_ REST APIs. > * External and can be executed against a known Atlas instance. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3029) API: Retrieve Classification Events from Audits
[ https://issues.apache.org/jira/browse/ATLAS-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3029: --- Attachment: ATLAS-3029-Classification-events-retrieval.patch > API: Retrieve Classification Events from Audits > --- > > Key: ATLAS-3029 > URL: https://issues.apache.org/jira/browse/ATLAS-3029 > Project: Atlas > Issue Type: Improvement > Components: atlas-core, atlas-intg >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 2.0.0 > > Attachments: ATLAS-3029-Classification-events-retrieval.patch > > > *Use Cases* > 1. In the case where user looses data within Atlas, they can get it ingested > by using tool like _import-hive_. With this approach, the user does not get > the classifications and the entities associated with them. > 2. In case where classifications were inadvertently removed from entities. > *Solution* > In the scenarios above, currently there isn't a way to know the > classification operations performed. > A REST API that would get this information from Atlas' Audit tables would > benefit the user. > *Approach Guidance* > * REST endpoint: Use Atlas' Audit Repository to fetch the audit events. This > API should accept a timestamp range so that useful audit events can be > fetched. > * REST endpoint: Re-play the audit events to update Atlas. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3029) API: Retrieve Classification Events from Audits
[ https://issues.apache.org/jira/browse/ATLAS-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3029: --- Summary: API: Retrieve Classification Events from Audits (was: API: Retrieve Audits for Classification Operations) > API: Retrieve Classification Events from Audits > --- > > Key: ATLAS-3029 > URL: https://issues.apache.org/jira/browse/ATLAS-3029 > Project: Atlas > Issue Type: Improvement > Components: atlas-core, atlas-intg >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 2.0.0 > > > *Use Cases* > 1. In the case where user looses data within Atlas, they can get it ingested > by using tool like _import-hive_. With this approach, the user does not get > the classifications and the entities associated with them. > 2. In case where classifications were inadvertently removed from entities. > *Solution* > In the scenarios above, currently there isn't a way to know the > classification operations performed. > A REST API that would get this information from Atlas' Audit tables would > benefit the user. > *Approach Guidance* > * REST endpoint: Use Atlas' Audit Repository to fetch the audit events. This > API should accept a timestamp range so that useful audit events can be > fetched. > * REST endpoint: Re-play the audit events to update Atlas. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3029) API: Retrieve Audits for Classification Operations
Ashutosh Mestry created ATLAS-3029: -- Summary: API: Retrieve Audits for Classification Operations Key: ATLAS-3029 URL: https://issues.apache.org/jira/browse/ATLAS-3029 Project: Atlas Issue Type: Improvement Components: atlas-core, atlas-intg Affects Versions: trunk Reporter: Ashutosh Mestry Assignee: Ashutosh Mestry Fix For: 2.0.0 *Use Cases* 1. In the case where user looses data within Atlas, they can get it ingested by using tool like _import-hive_. With this approach, the user does not get the classifications and the entities associated with them. 2. In case where classifications were inadvertently removed from entities. *Solution* In the scenarios above, currently there isn't a way to know the classification operations performed. A REST API that would get this information from Atlas' Audit tables would benefit the user. *Approach Guidance* * REST endpoint: Use Atlas' Audit Repository to fetch the audit events. This API should accept a timestamp range so that useful audit events can be fetched. * REST endpoint: Re-play the audit events to update Atlas. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739608#comment-16739608 ] Graham Wallis commented on ATLAS-1773: -- The RBT review for the patch associated with this JIRA is at [https://reviews.apache.org/r/68412/] (The other patches have their own reviews pending where appropriate) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-21.patch, > ATLAS-2810-2019-01-10.patch, ATLAS-2939-2018-12-21.patch, > ATLAS-2985-2019-01-10.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Review Request 68412: ATLAS-1773: Atlas OMRS Repository Connector
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68412/ --- (Updated Jan. 10, 2019, 4:52 p.m.) Review request for atlas. Changes --- Updated connector and event mapper - please note that this version pre-reqs ATLAS-2810 for compile and ATLAS-2939 and ATLAS-2985 for runtime corrections to base function Repository: atlas Description --- ATLAS-1773: Atlas OMRS Repository Connector Diffs (updated) - open-metadata/README.md PRE-CREATION open-metadata/pom.xml PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/eventmapper/AtlasOMRSRepositoryEventMapper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/eventmapper/AtlasOMRSRepositoryEventMapperProvider.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasAttributeDefMapper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasAttributeMapper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasBaseTypeDefMapper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasClassificationDefMapper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasEntityDefMapper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasEntityMapper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasRelationshipDefMapper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasRelationshipMapper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasStoresProxy.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/AtlasStoresProxyImpl.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/Comparator.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/DSLQueryHelper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/EntityDefMapper.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/FamousFive.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/ISpringBridge.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/LocalAtlasOMRSErrorCode.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/LocalAtlasOMRSMetadataCollection.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/LocalAtlasOMRSRepositoryConnector.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/LocalAtlasOMRSRepositoryConnectorProvider.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/SpringBridge.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/TypeDefsByCategory.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/TypeNameUtils.java PRE-CREATION open-metadata/src/main/java/org/apache/atlas/openmetadata/admin/server/spring/OpenMetadataAdminResource.java PRE-CREATION open-metadata/src/test/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/TestAtlasClassificationDefMapper.java PRE-CREATION open-metadata/src/test/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/TestAtlasEntityDefMapper.java PRE-CREATION open-metadata/src/test/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/TestAtlasEntityMapper.java PRE-CREATION open-metadata/src/test/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/TestAtlasRelationshipDefMapper.java PRE-CREATION open-metadata/src/test/java/org/apache/atlas/openmetadata/adapters/repositoryconnector/TestAtlasRelationshipMapper.java PRE-CREATION pom.xml 49fe7de14bf52f9a1de7153eab0484f42e25e37a webapp/pom.xml e1988c34863053489c3331a994b328adc92347b0 webapp/src/main/webapp/WEB-INF/openMetadataContext.xml PRE-CREATION webapp/src/main/webapp/WEB-INF/web.xml 23dc0637a8b521ab89a16ec8b03895cdaf8bc7d8 Diff: https://reviews.apache.org/r/68412/diff/4/ Changes:
Re: Review Request 69392: ATLAS-2810 - Add notifications from RelationshipStore
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/69392/#review211828
---
Ship it!
Ship It!
- Graham Wallis
On Jan. 4, 2019, 1:21 p.m., Nikhil Bonte wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69392/
> ---
>
> (Updated Jan. 4, 2019, 1:21 p.m.)
>
>
> Review request for atlas, Ashutosh Mestry, Nixon Rodrigues, and Sarath
> Subramanian.
>
>
> Bugs: ATLAS-2810
> https://issues.apache.org/jira/browse/ATLAS-2810
>
>
> Repository: atlas
>
>
> Description
> ---
>
> Notifications for relationship mutations.
>
> To enable notifications, set property
> "atlas.notification.relationships.enabled" to true.
> If property is not specified, notifications will be disabled by default.
>
> If enabled, this will add message to kafka topic when relationship is
> added/updated/deleted.
>
> Sample messages :
>
> ADD
> {"version":{"version":"1.0.0","versionParts":[1]},"msgCompressionKind":"NONE","msgSplitIdx":1,"msgSplitCount":1,"msgSourceIP":"127.0.1.1","msgCreatedBy":"","msgCreationTime":1544787083448,"message":{"type":"ENTITY_NOTIFICATION_V2","relationship":{"typeName":"hive_table_db","guid":"e4949325-562a-43bf-a980-c0c562c8759e","status":"ACTIVE","label":"__hive_table.db","end1":{"guid":"6da63233-d449-42d5-8449-b6ad243f6af2","typeName":"hive_table","uniqueAttributes":{"qualifiedName":"tbl2@qn"}},"end2":{"guid":"cea76431-af27-43ae-ab11-98a2ef989bb8","typeName":"hive_db","uniqueAttributes":{"qualifiedName":"db2@qn"}}},"operationType":"RELATIONSHIP_ADD","eventTime":1544787072298}}
>
> UPDATE
> {"version":{"version":"1.0.0","versionParts":[1]},"msgCompressionKind":"NONE","msgSplitIdx":1,"msgSplitCount":1,"msgSourceIP":"127.0.1.1","msgCreatedBy":"","msgCreationTime":1544787404692,"message":{"type":"ENTITY_NOTIFICATION_V2","relationship":{"typeName":"hive_table_db","guid":"e4949325-562a-43bf-a980-c0c562c8759e","status":"ACTIVE","label":"__hive_table.db","end1":{"guid":"6da63233-d449-42d5-8449-b6ad243f6af2","typeName":"hive_table","uniqueAttributes":{"qualifiedName":"tbl2@qn"}},"end2":{"guid":"cea76431-af27-43ae-ab11-98a2ef989bb8","typeName":"hive_db","uniqueAttributes":{"qualifiedName":"db2@qn"}}},"operationType":"RELATIONSHIP_UPDATE","eventTime":1544787404679}}
>
> DELETE
> {"version":{"version":"1.0.0","versionParts":[1]},"msgCompressionKind":"NONE","msgSplitIdx":1,"msgSplitCount":1,"msgSourceIP":"127.0.1.1","msgCreatedBy":"","msgCreationTime":1544787460081,"message":{"type":"ENTITY_NOTIFICATION_V2","relationship":{"typeName":"hive_table_db","guid":"e4949325-562a-43bf-a980-c0c562c8759e","status":"DELETED","label":"__hive_table.db","end1":{"guid":"6da63233-d449-42d5-8449-b6ad243f6af2","typeName":"hive_table","uniqueAttributes":{"qualifiedName":"tbl2@qn"}},"end2":{"guid":"cea76431-af27-43ae-ab11-98a2ef989bb8","typeName":"hive_db","uniqueAttributes":{"qualifiedName":"db2@qn"}}},"operationType":"RELATIONSHIP_DELETE","eventTime":1544787459708}}
>
>
> Diffs
> -
>
> intg/src/main/java/org/apache/atlas/AtlasConfiguration.java c5357f5
> intg/src/main/java/org/apache/atlas/listener/EntityChangeListenerV2.java
> cccf0d4
>
> intg/src/main/java/org/apache/atlas/model/instance/AtlasRelationshipHeader.java
> PRE-CREATION
>
> intg/src/main/java/org/apache/atlas/model/notification/EntityNotification.java
> 1eae100
>
> repository/src/main/java/org/apache/atlas/repository/audit/EntityAuditListenerV2.java
> 16d8879
>
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityChangeNotifier.java
> ca3179a
>
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasRelationshipStoreV2.java
> 86cc98c
>
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphRetriever.java
> 066abc1
>
> webapp/src/main/java/org/apache/atlas/notification/EntityNotificationListenerV2.java
> ef9ebab
>
>
> Diff: https://reviews.apache.org/r/69392/diff/10/
>
>
> Testing
> ---
>
> Tested from REST client(Postman).
> 1) Added/updated/deleted relationship by hitting REST APIs(see details below)
> 2) Verified message is sent to kafka using kafka-console-consumer
>./kafka-console-consumer.sh --bootstrap-server localhost:9027 --topic
> ATLAS_ENTITIES --from-beginning
>
>
> ## Add relationship - create hive_db then create hive_table. This will create
> new relationship
> API - http://localhost:21000/api/atlas/v2/entity - POST
>
> hive_db
> request body -
>
[jira] [Commented] (ATLAS-3025) UI - If go to page is more/less then the available page limit then an error appears in the console
[ https://issues.apache.org/jira/browse/ATLAS-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739506#comment-16739506 ] ASF subversion and git services commented on ATLAS-3025: Commit f397d1e1df61a27c002c52b247ad22054c31502c in atlas's branch refs/heads/branch-0.8 from Keval Bhatt [ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=f397d1e ] ATLAS-3025 : UI - If go to page is more/less then the available page limit then an error appears in the console (cherry picked from commit b455040d06be2c6330dfb0b11e34c6ea480a0b7c) > UI - If go to page is more/less then the available page limit then an error > appears in the console > -- > > Key: ATLAS-3025 > URL: https://issues.apache.org/jira/browse/ATLAS-3025 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.2.0, 2.0.0 >Reporter: Tejas Rawool >Assignee: Keval Bhatt >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-3025.patch, Screenshot 2019-01-07 at 6.01.28 PM.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3010) UI - Lineage hide process filter is not working
[ https://issues.apache.org/jira/browse/ATLAS-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739504#comment-16739504 ] ASF subversion and git services commented on ATLAS-3010: Commit 697baf4c079f70f4839f1b84731e2280e84c6265 in atlas's branch refs/heads/branch-1.0 from Abhishek Kadam [ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=697baf4 ] ATLAS-3010: UI - Lineage hide process filter is not working Signed-off-by: kevalbhatt (cherry picked from commit 3871be8b1e5496214b6d6adf1ee4c334d54f54b6) > UI - Lineage hide process filter is not working > --- > > Key: ATLAS-3010 > URL: https://issues.apache.org/jira/browse/ATLAS-3010 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 0.8.4, 1.2.0, 2.0.0 >Reporter: Tejas Rawool >Assignee: Abhishek Kadam >Priority: Major > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: ATLAS-3010.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3026) Column level lineage show the invalid icon for the process
[ https://issues.apache.org/jira/browse/ATLAS-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739495#comment-16739495 ] ASF subversion and git services commented on ATLAS-3026: Commit 665f8311e45477ffdf951b7f9d9eb304badfaab8 in atlas's branch refs/heads/master from Keval Bhatt [ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=665f831 ] ATLAS-3026 : Column level lineage show the invalid icon for the process > Column level lineage show the invalid icon for the process > -- > > Key: ATLAS-3026 > URL: https://issues.apache.org/jira/browse/ATLAS-3026 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3026.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739509#comment-16739509 ] David Radley commented on ATLAS-1773: - [~grahamwallis] I wonder if you could add the link to this Jira to the associated RBT(s) for the latest patches. I assume you are looking for the RBTs to be reviewed > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-21.patch, > ATLAS-2810-2019-01-10.patch, ATLAS-2939-2018-12-21.patch, > ATLAS-2985-2019-01-10.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3026) Column level lineage show the invalid icon for the process
[ https://issues.apache.org/jira/browse/ATLAS-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739507#comment-16739507 ] ASF subversion and git services commented on ATLAS-3026: Commit 439cd066880874323f72e9d1ab430e0c25fcb1f4 in atlas's branch refs/heads/branch-0.8 from Keval Bhatt [ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=439cd06 ] ATLAS-3026 : Column level lineage show the invalid icon for the process (cherry picked from commit 665f8311e45477ffdf951b7f9d9eb304badfaab8) > Column level lineage show the invalid icon for the process > -- > > Key: ATLAS-3026 > URL: https://issues.apache.org/jira/browse/ATLAS-3026 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3026.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3010) UI - Lineage hide process filter is not working
[ https://issues.apache.org/jira/browse/ATLAS-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739508#comment-16739508 ] ASF subversion and git services commented on ATLAS-3010: Commit e11172cd8206ba110adc4060cd005ff022e04b6c in atlas's branch refs/heads/branch-0.8 from Abhishek Kadam [ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=e11172c ] ATLAS-3010: UI - Lineage hide process filter is not working Signed-off-by: kevalbhatt (cherry picked from commit 3871be8b1e5496214b6d6adf1ee4c334d54f54b6) > UI - Lineage hide process filter is not working > --- > > Key: ATLAS-3010 > URL: https://issues.apache.org/jira/browse/ATLAS-3010 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 0.8.4, 1.2.0, 2.0.0 >Reporter: Tejas Rawool >Assignee: Abhishek Kadam >Priority: Major > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: ATLAS-3010.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3027) UI : Metric modal Improvements
[ https://issues.apache.org/jira/browse/ATLAS-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739502#comment-16739502 ] ASF subversion and git services commented on ATLAS-3027: Commit 598184c8763c86adc7e75409a9203271f42ce184 in atlas's branch refs/heads/branch-1.0 from Keval Bhatt [ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=598184c ] ATLAS-3027 : UI : Metric modal Improvements (cherry picked from commit e8b32778cad16a61bcb6341b32fee90301028f71) > UI : Metric modal Improvements > -- > > Key: ATLAS-3027 > URL: https://issues.apache.org/jira/browse/ATLAS-3027 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3027.patch > > > Following point need to improve > * Count column should be right-aligned > * Show 'Total Active Entities’ and ‘Total Deleted Entities' > * Increase the modal height -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739499#comment-16739499 ] Graham Wallis commented on ATLAS-1773: -- Have updated two of the above patches. The ATLAS-2810 patch is the same as Nikhil's latest patch from the current review of ATLAS-2810; which will hopefully commit soon. The updated ATLAS-2985 patch contains further updates to cater for the fact that hard/soft delete does not work correctly. Suggest you continue to apply them in the order listed in the previous comment. > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-21.patch, > ATLAS-2810-2019-01-10.patch, ATLAS-2939-2018-12-21.patch, > ATLAS-2985-2019-01-10.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3025) UI - If go to page is more/less then the available page limit then an error appears in the console
[ https://issues.apache.org/jira/browse/ATLAS-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739501#comment-16739501 ] ASF subversion and git services commented on ATLAS-3025: Commit 325f9da92fe21dbace562f15e79702e3e97b66b8 in atlas's branch refs/heads/branch-1.0 from Keval Bhatt [ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=325f9da ] ATLAS-3025 : UI - If go to page is more/less then the available page limit then an error appears in the console (cherry picked from commit b455040d06be2c6330dfb0b11e34c6ea480a0b7c) > UI - If go to page is more/less then the available page limit then an error > appears in the console > -- > > Key: ATLAS-3025 > URL: https://issues.apache.org/jira/browse/ATLAS-3025 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.2.0, 2.0.0 >Reporter: Tejas Rawool >Assignee: Keval Bhatt >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-3025.patch, Screenshot 2019-01-07 at 6.01.28 PM.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3026) Column level lineage show the invalid icon for the process
[ https://issues.apache.org/jira/browse/ATLAS-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739503#comment-16739503 ] ASF subversion and git services commented on ATLAS-3026: Commit c2141f593bc2584b1ce54433e93dd8cf2133dd37 in atlas's branch refs/heads/branch-1.0 from Keval Bhatt [ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=c2141f5 ] ATLAS-3026 : Column level lineage show the invalid icon for the process (cherry picked from commit 665f8311e45477ffdf951b7f9d9eb304badfaab8) > Column level lineage show the invalid icon for the process > -- > > Key: ATLAS-3026 > URL: https://issues.apache.org/jira/browse/ATLAS-3026 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3026.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3025) UI - If go to page is more/less then the available page limit then an error appears in the console
[ https://issues.apache.org/jira/browse/ATLAS-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739497#comment-16739497 ] ASF subversion and git services commented on ATLAS-3025: Commit b455040d06be2c6330dfb0b11e34c6ea480a0b7c in atlas's branch refs/heads/master from Keval Bhatt [ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=b455040 ] ATLAS-3025 : UI - If go to page is more/less then the available page limit then an error appears in the console > UI - If go to page is more/less then the available page limit then an error > appears in the console > -- > > Key: ATLAS-3025 > URL: https://issues.apache.org/jira/browse/ATLAS-3025 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.2.0, 2.0.0 >Reporter: Tejas Rawool >Assignee: Keval Bhatt >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-3025.patch, Screenshot 2019-01-07 at 6.01.28 PM.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3010) UI - Lineage hide process filter is not working
[ https://issues.apache.org/jira/browse/ATLAS-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739494#comment-16739494 ] ASF subversion and git services commented on ATLAS-3010: Commit 3871be8b1e5496214b6d6adf1ee4c334d54f54b6 in atlas's branch refs/heads/master from Abhishek Kadam [ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=3871be8 ] ATLAS-3010: UI - Lineage hide process filter is not working Signed-off-by: kevalbhatt > UI - Lineage hide process filter is not working > --- > > Key: ATLAS-3010 > URL: https://issues.apache.org/jira/browse/ATLAS-3010 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 0.8.4, 1.2.0, 2.0.0 >Reporter: Tejas Rawool >Assignee: Abhishek Kadam >Priority: Major > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: ATLAS-3010.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: ATLAS-2985-2019-01-10.patch ATLAS-2810-2019-01-10.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-21.patch, > ATLAS-2810-2019-01-10.patch, ATLAS-2939-2018-12-21.patch, > ATLAS-2985-2019-01-10.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-2810-2018-12-21.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-21.patch, ATLAS-2939-2018-12-21.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-2985-2018-12-21.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-21.patch, ATLAS-2939-2018-12-21.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3027) UI : Metric modal Improvements
[ https://issues.apache.org/jira/browse/ATLAS-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739490#comment-16739490 ] Tejas Rawool commented on ATLAS-3027: - Hi [~kevalbhatt], Patch looks good +1 for the Patch. > UI : Metric modal Improvements > -- > > Key: ATLAS-3027 > URL: https://issues.apache.org/jira/browse/ATLAS-3027 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3027.patch > > > Following point need to improve > * Count column should be right-aligned > * Show 'Total Active Entities’ and ‘Total Deleted Entities' > * Increase the modal height -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3025) UI - If go to page is more/less then the available page limit then an error appears in the console
[ https://issues.apache.org/jira/browse/ATLAS-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739423#comment-16739423 ] Tejas Rawool commented on ATLAS-3025: - Hi [~kevalbhatt], Patch looks good +1 for the Patch > UI - If go to page is more/less then the available page limit then an error > appears in the console > -- > > Key: ATLAS-3025 > URL: https://issues.apache.org/jira/browse/ATLAS-3025 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.2.0, 2.0.0 >Reporter: Tejas Rawool >Assignee: Keval Bhatt >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-3025.patch, Screenshot 2019-01-07 at 6.01.28 PM.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3010) UI - Lineage hide process filter is not working
[ https://issues.apache.org/jira/browse/ATLAS-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739416#comment-16739416 ] Tejas Rawool commented on ATLAS-3010: - Hi [~abhib4], Patch looks good +1 for the Patch. > UI - Lineage hide process filter is not working > --- > > Key: ATLAS-3010 > URL: https://issues.apache.org/jira/browse/ATLAS-3010 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 0.8.4, 1.2.0, 2.0.0 >Reporter: Tejas Rawool >Assignee: Abhishek Kadam >Priority: Major > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: ATLAS-3010.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3026) Column level lineage show the invalid icon for the process
[ https://issues.apache.org/jira/browse/ATLAS-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739418#comment-16739418 ] Tejas Rawool commented on ATLAS-3026: - Hi [~kevalbhatt], Patch looks good +1 for the Patch. > Column level lineage show the invalid icon for the process > -- > > Key: ATLAS-3026 > URL: https://issues.apache.org/jira/browse/ATLAS-3026 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3026.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3026) Column level lineage show the invalid icon for the process
[ https://issues.apache.org/jira/browse/ATLAS-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3026: --- Attachment: ATLAS-3026.patch > Column level lineage show the invalid icon for the process > -- > > Key: ATLAS-3026 > URL: https://issues.apache.org/jira/browse/ATLAS-3026 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3026.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3027) UI : Metric modal Improvements
[ https://issues.apache.org/jira/browse/ATLAS-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3027: --- Attachment: ATLAS-3027.patch > UI : Metric modal Improvements > -- > > Key: ATLAS-3027 > URL: https://issues.apache.org/jira/browse/ATLAS-3027 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3027.patch > > > Following point need to improve > * Count column should be right-aligned > * Show 'Total Active Entities’ and ‘Total Deleted Entities' > * Increase the modal height -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3027) UI : Metric modal Improvements
[ https://issues.apache.org/jira/browse/ATLAS-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3027: --- Attachment: (was: ATLAS-3027.patch) > UI : Metric modal Improvements > -- > > Key: ATLAS-3027 > URL: https://issues.apache.org/jira/browse/ATLAS-3027 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3027.patch > > > Following point need to improve > * Count column should be right-aligned > * Show 'Total Active Entities’ and ‘Total Deleted Entities' > * Increase the modal height -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3027) UI : Metric modal Improvements
[ https://issues.apache.org/jira/browse/ATLAS-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3027: --- Attachment: ATLAS-3027.patch > UI : Metric modal Improvements > -- > > Key: ATLAS-3027 > URL: https://issues.apache.org/jira/browse/ATLAS-3027 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3027.patch > > > Following point need to improve > * Count column should be right-aligned > * Show 'Total Active Entities’ and ‘Total Deleted Entities' > * Increate the Modal size (height) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3027) UI : Metric modal Improvements
[ https://issues.apache.org/jira/browse/ATLAS-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3027: --- Attachment: ATLAS-3027.patch > UI : Metric modal Improvements > -- > > Key: ATLAS-3027 > URL: https://issues.apache.org/jira/browse/ATLAS-3027 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3027.patch > > > Following point need to improve > * Count column should be right-aligned > * Show 'Total Active Entities’ and ‘Total Deleted Entities' > * Increase the modal height -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3027) UI : Metric modal Improvements
[ https://issues.apache.org/jira/browse/ATLAS-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3027: --- Description: Following point need to improve * Count column should be right-aligned * Show 'Total Active Entities’ and ‘Total Deleted Entities' * Increase the modal height was: Following point need to improve * Count column should be right-aligned * Show 'Total Active Entities’ and ‘Total Deleted Entities' > UI : Metric modal Improvements > -- > > Key: ATLAS-3027 > URL: https://issues.apache.org/jira/browse/ATLAS-3027 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3027.patch > > > Following point need to improve > * Count column should be right-aligned > * Show 'Total Active Entities’ and ‘Total Deleted Entities' > * Increase the modal height -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3025) UI - If go to page is more/less then the available page limit then an error appears in the console
[ https://issues.apache.org/jira/browse/ATLAS-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3025: --- Attachment: ATLAS-3025.patch > UI - If go to page is more/less then the available page limit then an error > appears in the console > -- > > Key: ATLAS-3025 > URL: https://issues.apache.org/jira/browse/ATLAS-3025 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.2.0, 2.0.0 >Reporter: Tejas Rawool >Assignee: Keval Bhatt >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-3025.patch, Screenshot 2019-01-07 at 6.01.28 PM.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3027) UI : Metric modal Improvements
[ https://issues.apache.org/jira/browse/ATLAS-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3027: --- Description: Following point need to improve * Count column should be right-aligned * Show 'Total Active Entities’ and ‘Total Deleted Entities' was: Following point need to improve * Count column should be right-aligned * Show 'Total Active Entities’ and ‘Total Deleted Entities' * Increate the Modal size (height) > UI : Metric modal Improvements > -- > > Key: ATLAS-3027 > URL: https://issues.apache.org/jira/browse/ATLAS-3027 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3027.patch > > > Following point need to improve > * Count column should be right-aligned > * Show 'Total Active Entities’ and ‘Total Deleted Entities' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Consensus for migration of git repositories to gitbox
Hi Madhan, +1 I like the idea of being pro active with this. We are looking to demo master Atlas code at a conference in the following week, so we need to have a working Atlas master build, so it would be good to make this change asap. On a related subject, would it be possible for the community to not make any big changes (types, software level changes or API changes) coming up to the week of the 16th of February - so the Atlas / Egeria demo continues to build. If there are big changes you need in, could I request that the community be informed and given a change to assess the impact during this period and potentially delay pervasive changes, many thanks , David. From: Madhan Neethiraj To: "dev@atlas.apache.org" Date: 10/01/2019 07:37 Subject:Re: Consensus for migration of git repositories to gitbox +1 Thanks Apoorv for volunteering. Please keep the community updated of the progress and actions to be done by each to access the migrated repo. Thanks, Madhan On 1/9/19, 11:01 PM, "Ashutosh Mestry" wrote: +1 for migrating Atlas repositories. Thanks Apoorv! ~ ashutosh On 1/9/19, 10:58 PM, "Nixon Rodrigues" wrote: Thanks Apoorv for volunteering this effort +1 for migrating Atlas repositories to gitbox server. Regards, Nixon On Thu, Jan 10, 2019 at 11:50 AM Apoorv Naik wrote: > Hi Atlas devs, > > There's an ASF initiative to migrate the git-wip-us-apache.org > repositories > to the gitbox server before Feb 7, after which it'll be mass migrated > without a warning. I volunteer to take this migration effort to avoid any > disruption to commit activity. > > PMCs and committers, please share your +1 or -1 vote for this move (this is > the first step in starting the migration) > > *Apoorv Naik* > Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
[jira] [Created] (ATLAS-3028) UI - If a column is deleted then user needs to stop and start the server to see the change in Statistics count
Tejas Rawool created ATLAS-3028: --- Summary: UI - If a column is deleted then user needs to stop and start the server to see the change in Statistics count Key: ATLAS-3028 URL: https://issues.apache.org/jira/browse/ATLAS-3028 Project: Atlas Issue Type: Bug Affects Versions: 1.2.0, 2.0.0 Reporter: Tejas Rawool Fix For: 1.2.0, 2.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3027) UI : Metric modal Improvements
Keval Bhatt created ATLAS-3027: -- Summary: UI : Metric modal Improvements Key: ATLAS-3027 URL: https://issues.apache.org/jira/browse/ATLAS-3027 Project: Atlas Issue Type: Improvement Reporter: Keval Bhatt Assignee: Keval Bhatt -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3027) UI : Metric modal Improvements
[ https://issues.apache.org/jira/browse/ATLAS-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3027: --- Description: Following point need to improve * Count column should be right-aligned * Show 'Total Active Entities’ and ‘Total Deleted Entities' * Increate the Modal size (height) > UI : Metric modal Improvements > -- > > Key: ATLAS-3027 > URL: https://issues.apache.org/jira/browse/ATLAS-3027 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > > Following point need to improve > * Count column should be right-aligned > * Show 'Total Active Entities’ and ‘Total Deleted Entities' > * Increate the Modal size (height) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2994) UI - If Hide deleted entity filter is applied then to UI displays deleted entity in lineage
[ https://issues.apache.org/jira/browse/ATLAS-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kadam reassigned ATLAS-2994: - Assignee: Abhishek Kadam (was: Keval Bhatt) > UI - If Hide deleted entity filter is applied then to UI displays deleted > entity in lineage > --- > > Key: ATLAS-2994 > URL: https://issues.apache.org/jira/browse/ATLAS-2994 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.0.0, trunk >Reporter: Tejas Rawool >Assignee: Abhishek Kadam >Priority: Major > Fix For: 2.0.0 > > Attachments: SS7.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3010) UI - Lineage hide process filter is not working
[ https://issues.apache.org/jira/browse/ATLAS-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kadam updated ATLAS-3010: -- Attachment: ATLAS-3010.patch > UI - Lineage hide process filter is not working > --- > > Key: ATLAS-3010 > URL: https://issues.apache.org/jira/browse/ATLAS-3010 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 0.8.4, 1.2.0, 2.0.0 >Reporter: Tejas Rawool >Assignee: Abhishek Kadam >Priority: Major > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: ATLAS-3010.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Consensus for migration of git repositories to gitbox
Thank you Apoorv :) +1 to be proactive about the migration. All the best Mandy ___ Mandy Chessell CBE FREng CEng FBCS IBM Distinguished Engineer Master Inventor Member of the IBM Academy of Technology Visiting Professor, Department of Computer Science, University of Sheffield Email: mandy_chess...@uk.ibm.com LinkedIn: http://www.linkedin.com/pub/mandy-chessell/22/897/a49 Assistant: Janet Brooks - jsbrook...@uk.ibm.com From: Apoorv Naik To: dev Date: 10/01/2019 07:20 Subject:Consensus for migration of git repositories to gitbox Hi Atlas devs, There's an ASF initiative to migrate the git-wip-us-apache.org repositories to the gitbox server before Feb 7, after which it'll be mass migrated without a warning. I volunteer to take this migration effort to avoid any disruption to commit activity. PMCs and committers, please share your +1 or -1 vote for this move (this is the first step in starting the migration) *Apoorv Naik* Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
