Re: Review Request 72766: ATLAS-3920 : Harmonize joda-time to version 2.10.latest.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72766/#review221569 --- Ship it! Ship It! - Sarath Subramanian On Aug. 12, 2020, 9:53 p.m., mayank jain wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/72766/ > --- > > (Updated Aug. 12, 2020, 9:53 p.m.) > > > Review request for atlas, Madhan Neethiraj and Sarath Subramanian. > > > Bugs: ATLAS-3920 > https://issues.apache.org/jira/browse/ATLAS-3920 > > > Repository: atlas > > > Description > --- > > Atlas currently uses outdated joda-time versions, which can cause issues. To > avoid issue we need to update it to the latest version of joda-time. > > > Diffs > - > > pom.xml 5e0442a > > > Diff: https://reviews.apache.org/r/72766/diff/1/ > > > Testing > --- > > The test cases passed and also tested basic features and they worked. > > > Thanks, > > mayank jain > >
[jira] [Updated] (ATLAS-3921) Need migration path from AWS s3 v1 to v2 entities
[ https://issues.apache.org/jira/browse/ATLAS-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharth Kumar Mishra updated ATLAS-3921: - Issue Type: Improvement (was: Bug) > Need migration path from AWS s3 v1 to v2 entities > - > > Key: ATLAS-3921 > URL: https://issues.apache.org/jira/browse/ATLAS-3921 > Project: Atlas > Issue Type: Improvement >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > > We have introduced the new AWS S3 V2 entity at Atlas. After upgrade the > service like Hive will create the new V2 entities at Atlas, but the old v1 > Aws S3 entity will not be migrated to new one. This will cause missing > relationship and/or lineage. We should have a migration path from the old v1 > entity to new v2 entity . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3921) Need migration path from AWS s3 v1 to v2 entities
Sidharth Kumar Mishra created ATLAS-3921: Summary: Need migration path from AWS s3 v1 to v2 entities Key: ATLAS-3921 URL: https://issues.apache.org/jira/browse/ATLAS-3921 Project: Atlas Issue Type: Bug Reporter: Sidharth Kumar Mishra Assignee: Sidharth Kumar Mishra We have introduced the new AWS S3 V2 entity at Atlas. After upgrade the service like Hive will create the new V2 entities at Atlas, but the old v1 Aws S3 entity will not be migrated to new one. This will cause missing relationship and/or lineage. We should have a migration path from the old v1 entity to new v2 entity . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3875) Adding missing APIs in AtlasClient with test cases
[ https://issues.apache.org/jira/browse/ATLAS-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17177100#comment-17177100 ] ASF subversion and git services commented on ATLAS-3875: Commit 17e0c06829796e2481c047886d1d17e3bf8091f4 in atlas's branch refs/heads/branch-2.0 from jyoti0208 [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=17e0c06 ] ATLAS-3875: updated sample client to improve logging Signed-off-by: Madhan Neethiraj (cherry picked from commit 83e9c21f7805b7badc9390a15fd747e1e6a7f8e2) > Adding missing APIs in AtlasClient with test cases > -- > > Key: ATLAS-3875 > URL: https://issues.apache.org/jira/browse/ATLAS-3875 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 2.0.0, 2.1.0 >Reporter: Jyoti Singh >Assignee: Jyoti Singh >Priority: Major > Labels: api, client > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3875-1.patch, ATLAS-3875-2.patch, > ATLAS-3875-4.patch > > > 1. There are many new APIs added to Atlas Project but the corresponding APIs > are missing from AtlasClientv2. The aim of this task is to complete the gap > amongst existing APIs and their endpoints in Atls client. This will also > include adding test cases via integration testing. > There are functions from AtlasClient for the following REST endpoints > * TypeRest > * EntityRest > * LineageRest > * DiscoveryRest > * GlossaryRest > * RelationshipRest > 2. Added Sample-Project to showcase how to integrate with Atlas using > AtlasCleint. This helps the user to understand the basic rest functionality > of Atlas. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3875) Adding missing APIs in AtlasClient with test cases
[ https://issues.apache.org/jira/browse/ATLAS-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17177099#comment-17177099 ] ASF subversion and git services commented on ATLAS-3875: Commit 4b350f85bdf930cac815e3ba1c7ebdda0450e5e8 in atlas's branch refs/heads/branch-2.0 from jyoti0208 [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=4b350f8 ] ATLAS-3875: adding sample client change Signed-off-by: Madhan Neethiraj (cherry picked from commit b7255ec7e24f87da6f2dba47965a4e22e94c2250) > Adding missing APIs in AtlasClient with test cases > -- > > Key: ATLAS-3875 > URL: https://issues.apache.org/jira/browse/ATLAS-3875 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 2.0.0, 2.1.0 >Reporter: Jyoti Singh >Assignee: Jyoti Singh >Priority: Major > Labels: api, client > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3875-1.patch, ATLAS-3875-2.patch, > ATLAS-3875-4.patch > > > 1. There are many new APIs added to Atlas Project but the corresponding APIs > are missing from AtlasClientv2. The aim of this task is to complete the gap > amongst existing APIs and their endpoints in Atls client. This will also > include adding test cases via integration testing. > There are functions from AtlasClient for the following REST endpoints > * TypeRest > * EntityRest > * LineageRest > * DiscoveryRest > * GlossaryRest > * RelationshipRest > 2. Added Sample-Project to showcase how to integrate with Atlas using > AtlasCleint. This helps the user to understand the basic rest functionality > of Atlas. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3875) Adding missing APIs in AtlasClient with test cases
[ https://issues.apache.org/jira/browse/ATLAS-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17177088#comment-17177088 ] ASF subversion and git services commented on ATLAS-3875: Commit 83e9c21f7805b7badc9390a15fd747e1e6a7f8e2 in atlas's branch refs/heads/master from jyoti0208 [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=83e9c21 ] ATLAS-3875: updated sample client to improve logging Signed-off-by: Madhan Neethiraj > Adding missing APIs in AtlasClient with test cases > -- > > Key: ATLAS-3875 > URL: https://issues.apache.org/jira/browse/ATLAS-3875 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 2.0.0, 2.1.0 >Reporter: Jyoti Singh >Assignee: Jyoti Singh >Priority: Major > Labels: api, client > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3875-1.patch, ATLAS-3875-2.patch, > ATLAS-3875-4.patch > > > 1. There are many new APIs added to Atlas Project but the corresponding APIs > are missing from AtlasClientv2. The aim of this task is to complete the gap > amongst existing APIs and their endpoints in Atls client. This will also > include adding test cases via integration testing. > There are functions from AtlasClient for the following REST endpoints > * TypeRest > * EntityRest > * LineageRest > * DiscoveryRest > * GlossaryRest > * RelationshipRest > 2. Added Sample-Project to showcase how to integrate with Atlas using > AtlasCleint. This helps the user to understand the basic rest functionality > of Atlas. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3827) UI: Use moment date format instead of default date format.
[ https://issues.apache.org/jira/browse/ATLAS-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3827: --- Fix Version/s: 2.2.0 > UI: Use moment date format instead of default date format. > -- > > Key: ATLAS-3827 > URL: https://issues.apache.org/jira/browse/ATLAS-3827 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > > Date Format should be > /MM/DD hh:mm:ss -- This message was sent by Atlassian Jira (v8.3.4#803005)
