[jira] [Updated] (ATLAS-3695) [Business Metadata] Special characters are being allowed in Attribute Name
[
https://issues.apache.org/jira/browse/ATLAS-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian updated ATLAS-3695:
--
Fix Version/s: 2.1.0
> [Business Metadata] Special characters are being allowed in Attribute Name
> --
>
> Key: ATLAS-3695
> URL: https://issues.apache.org/jira/browse/ATLAS-3695
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core, atlas-webui
>Affects Versions: 2.0.0
>Reporter: Umesh Padashetty
>Assignee: Mandar Ambawane
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: Screenshot 2020-03-26 at 8.09.45 PM.png, Screenshot
> 2020-03-26 at 8.10.11 PM.png
>
>
> Special characters are not being allowed in the Business Metadata Name, but
> are being allowed in the Attribute Name and Description.
> Having special characters in Description should be fine, but not in
> Attributes name. Attached screenshots. This is reproducible both from UI and
> API. Screenshots attached.
> {code:java}
> curl -X POST \
> 'https://:31443/api/atlas/v2/types/typedefs?type=business_metadata' \
> -H 'cache-control: no-cache' \
> -H 'content-type: application/json' \
> -H 'postman-token: e91ead11-8ff2-8919-3d3e-133a213cd226' \
> -H 'x-xsrf-header: \"\"' \
> -d
> '{"enumDefs":[],"structDefs":[],"classificationDefs":[],"entityDefs":[],"businessMetadataDefs":[{"category":"BUSINESS_METADATA","createdBy":"admin","updatedBy":"admin","version":1,"typeVersion":"1.1","name":"Special
> Character
> Test","description":"^%*()*^*()","attributeDefs":[{"name":"&(*^%&*()*&^%$^&*()","typeName":"string","isOptional":true,"cardinality":"SINGLE","valuesMinCount":0,"valuesMaxCount":1,"isUnique":false,"isIndexable":false,"options":{"maxStrLength":"50"}}]}]}'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-3695) [Business Metadata] Special characters are being allowed in Attribute Name
[
https://issues.apache.org/jira/browse/ATLAS-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian reassigned ATLAS-3695:
-
Assignee: Mandar Ambawane
> [Business Metadata] Special characters are being allowed in Attribute Name
> --
>
> Key: ATLAS-3695
> URL: https://issues.apache.org/jira/browse/ATLAS-3695
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core, atlas-webui
>Reporter: Umesh Padashetty
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: Screenshot 2020-03-26 at 8.09.45 PM.png, Screenshot
> 2020-03-26 at 8.10.11 PM.png
>
>
> Special characters are not being allowed in the Business Metadata Name, but
> are being allowed in the Attribute Name and Description.
> Having special characters in Description should be fine, but not in
> Attributes name. Attached screenshots. This is reproducible both from UI and
> API. Screenshots attached.
> {code:java}
> curl -X POST \
> 'https://:31443/api/atlas/v2/types/typedefs?type=business_metadata' \
> -H 'cache-control: no-cache' \
> -H 'content-type: application/json' \
> -H 'postman-token: e91ead11-8ff2-8919-3d3e-133a213cd226' \
> -H 'x-xsrf-header: \"\"' \
> -d
> '{"enumDefs":[],"structDefs":[],"classificationDefs":[],"entityDefs":[],"businessMetadataDefs":[{"category":"BUSINESS_METADATA","createdBy":"admin","updatedBy":"admin","version":1,"typeVersion":"1.1","name":"Special
> Character
> Test","description":"^%*()*^*()","attributeDefs":[{"name":"&(*^%&*()*&^%$^&*()","typeName":"string","isOptional":true,"cardinality":"SINGLE","valuesMinCount":0,"valuesMaxCount":1,"isUnique":false,"isIndexable":false,"options":{"maxStrLength":"50"}}]}]}'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3695) [Business Metadata] Special characters are being allowed in Attribute Name
[
https://issues.apache.org/jira/browse/ATLAS-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian updated ATLAS-3695:
--
Affects Version/s: 2.0.0
> [Business Metadata] Special characters are being allowed in Attribute Name
> --
>
> Key: ATLAS-3695
> URL: https://issues.apache.org/jira/browse/ATLAS-3695
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core, atlas-webui
>Affects Versions: 2.0.0
>Reporter: Umesh Padashetty
>Assignee: Mandar Ambawane
>Priority: Major
> Attachments: Screenshot 2020-03-26 at 8.09.45 PM.png, Screenshot
> 2020-03-26 at 8.10.11 PM.png
>
>
> Special characters are not being allowed in the Business Metadata Name, but
> are being allowed in the Attribute Name and Description.
> Having special characters in Description should be fine, but not in
> Attributes name. Attached screenshots. This is reproducible both from UI and
> API. Screenshots attached.
> {code:java}
> curl -X POST \
> 'https://:31443/api/atlas/v2/types/typedefs?type=business_metadata' \
> -H 'cache-control: no-cache' \
> -H 'content-type: application/json' \
> -H 'postman-token: e91ead11-8ff2-8919-3d3e-133a213cd226' \
> -H 'x-xsrf-header: \"\"' \
> -d
> '{"enumDefs":[],"structDefs":[],"classificationDefs":[],"entityDefs":[],"businessMetadataDefs":[{"category":"BUSINESS_METADATA","createdBy":"admin","updatedBy":"admin","version":1,"typeVersion":"1.1","name":"Special
> Character
> Test","description":"^%*()*^*()","attributeDefs":[{"name":"&(*^%&*()*&^%$^&*()","typeName":"string","isOptional":true,"cardinality":"SINGLE","valuesMinCount":0,"valuesMaxCount":1,"isUnique":false,"isIndexable":false,"options":{"maxStrLength":"50"}}]}]}'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-3695) [Business Metadata] Special characters are being allowed in Attribute Name
[
https://issues.apache.org/jira/browse/ATLAS-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17086160#comment-17086160
]
ASF subversion and git services commented on ATLAS-3695:
Commit 7c2c83a528b4c52c15a1160cca70a2604ec3c687 in atlas's branch
refs/heads/branch-2.0 from Mandar Ambawane
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=7c2c83a ]
ATLAS-3695 [Business Metadata] Special characters are being allowed in
Attribute Name
Signed-off-by: Sarath Subramanian
(cherry picked from commit e6de42b7a3da6ebc6326813108d2b0cbcacac0f1)
> [Business Metadata] Special characters are being allowed in Attribute Name
> --
>
> Key: ATLAS-3695
> URL: https://issues.apache.org/jira/browse/ATLAS-3695
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core, atlas-webui
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: Screenshot 2020-03-26 at 8.09.45 PM.png, Screenshot
> 2020-03-26 at 8.10.11 PM.png
>
>
> Special characters are not being allowed in the Business Metadata Name, but
> are being allowed in the Attribute Name and Description.
> Having special characters in Description should be fine, but not in
> Attributes name. Attached screenshots. This is reproducible both from UI and
> API. Screenshots attached.
> {code:java}
> curl -X POST \
> 'https://:31443/api/atlas/v2/types/typedefs?type=business_metadata' \
> -H 'cache-control: no-cache' \
> -H 'content-type: application/json' \
> -H 'postman-token: e91ead11-8ff2-8919-3d3e-133a213cd226' \
> -H 'x-xsrf-header: \"\"' \
> -d
> '{"enumDefs":[],"structDefs":[],"classificationDefs":[],"entityDefs":[],"businessMetadataDefs":[{"category":"BUSINESS_METADATA","createdBy":"admin","updatedBy":"admin","version":1,"typeVersion":"1.1","name":"Special
> Character
> Test","description":"^%*()*^*()","attributeDefs":[{"name":"&(*^%&*()*&^%$^&*()","typeName":"string","isOptional":true,"cardinality":"SINGLE","valuesMinCount":0,"valuesMaxCount":1,"isUnique":false,"isIndexable":false,"options":{"maxStrLength":"50"}}]}]}'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-3695) [Business Metadata] Special characters are being allowed in Attribute Name
[
https://issues.apache.org/jira/browse/ATLAS-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17086159#comment-17086159
]
ASF subversion and git services commented on ATLAS-3695:
Commit e6de42b7a3da6ebc6326813108d2b0cbcacac0f1 in atlas's branch
refs/heads/master from Mandar Ambawane
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=e6de42b ]
ATLAS-3695 [Business Metadata] Special characters are being allowed in
Attribute Name
Signed-off-by: Sarath Subramanian
> [Business Metadata] Special characters are being allowed in Attribute Name
> --
>
> Key: ATLAS-3695
> URL: https://issues.apache.org/jira/browse/ATLAS-3695
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core, atlas-webui
>Reporter: Umesh Padashetty
>Priority: Major
> Attachments: Screenshot 2020-03-26 at 8.09.45 PM.png, Screenshot
> 2020-03-26 at 8.10.11 PM.png
>
>
> Special characters are not being allowed in the Business Metadata Name, but
> are being allowed in the Attribute Name and Description.
> Having special characters in Description should be fine, but not in
> Attributes name. Attached screenshots. This is reproducible both from UI and
> API. Screenshots attached.
> {code:java}
> curl -X POST \
> 'https://:31443/api/atlas/v2/types/typedefs?type=business_metadata' \
> -H 'cache-control: no-cache' \
> -H 'content-type: application/json' \
> -H 'postman-token: e91ead11-8ff2-8919-3d3e-133a213cd226' \
> -H 'x-xsrf-header: \"\"' \
> -d
> '{"enumDefs":[],"structDefs":[],"classificationDefs":[],"entityDefs":[],"businessMetadataDefs":[{"category":"BUSINESS_METADATA","createdBy":"admin","updatedBy":"admin","version":1,"typeVersion":"1.1","name":"Special
> Character
> Test","description":"^%*()*^*()","attributeDefs":[{"name":"&(*^%&*()*&^%$^&*()","typeName":"string","isOptional":true,"cardinality":"SINGLE","valuesMinCount":0,"valuesMaxCount":1,"isUnique":false,"isIndexable":false,"options":{"maxStrLength":"50"}}]}]}'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-3733) Upgrade JanusGraph version to 0.5.1
[ https://issues.apache.org/jira/browse/ATLAS-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17086154#comment-17086154 ] ASF subversion and git services commented on ATLAS-3733: Commit c8e89b47e33ec7cc73987ccfce76ac6513eb3add in atlas's branch refs/heads/branch-2.0 from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=c8e89b4 ] ATLAS-3733: upgraded JanusGraph version to 0.5.1, and Tinkerpop to 3.4.6 (cherry picked from commit 750646e75f870be1f5d1c67aa23933c6bb453c40) > Upgrade JanusGraph version to 0.5.1 > --- > > Key: ATLAS-3733 > URL: https://issues.apache.org/jira/browse/ATLAS-3733 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 2.1.0, 3.0.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3733.patch > > > JanusGraph version 0.5.1 is now available, and has a large number of > fixes/improvements since 0.4.1 version used in Apache Atlas. This JIRA is to > track updates to use the latest JanusGraph version available, and > corresponding Tinkerpop version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3733) Upgrade JanusGraph version to 0.5.1
[ https://issues.apache.org/jira/browse/ATLAS-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17086152#comment-17086152 ] ASF subversion and git services commented on ATLAS-3733: Commit 750646e75f870be1f5d1c67aa23933c6bb453c40 in atlas's branch refs/heads/master from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=750646e ] ATLAS-3733: upgraded JanusGraph version to 0.5.1, and Tinkerpop to 3.4.6 > Upgrade JanusGraph version to 0.5.1 > --- > > Key: ATLAS-3733 > URL: https://issues.apache.org/jira/browse/ATLAS-3733 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 2.1.0, 3.0.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3733.patch > > > JanusGraph version 0.5.1 is now available, and has a large number of > fixes/improvements since 0.4.1 version used in Apache Atlas. This JIRA is to > track updates to use the latest JanusGraph version available, and > corresponding Tinkerpop version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3727) Add get result details REST for admin audit record
[
https://issues.apache.org/jira/browse/ATLAS-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17086150#comment-17086150
]
ASF subversion and git services commented on ATLAS-3727:
Commit 2a569145071a2343b2f828ca1ad47794decef4b3 in atlas's branch
refs/heads/branch-2.0 from sidmishra
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=2a56914 ]
ATLAS-3727: Added REST API to get Admin Audit Details for an Admin Audit Guid
and Changed get entity audit Rest to support operation based filter
Signed-off-by: Sarath Subramanian
(cherry picked from commit b866e48f1ecd3d66d5383585a6c88093a374c065)
> Add get result details REST for admin audit record
> --
>
> Key: ATLAS-3727
> URL: https://issues.apache.org/jira/browse/ATLAS-3727
> Project: Atlas
> Issue Type: New Feature
> Components: atlas-core
>Affects Versions: 2.0.0
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3727.patch
>
>
> Right now purge admin audit result stores purged entities guids. We need :
> * Separate REST call to get more details summary of the entities purged.
> * Add audit operation as a parameter to v2/entity/\{guid}/audit
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-3727) Add get result details REST for admin audit record
[
https://issues.apache.org/jira/browse/ATLAS-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17086149#comment-17086149
]
ASF subversion and git services commented on ATLAS-3727:
Commit b866e48f1ecd3d66d5383585a6c88093a374c065 in atlas's branch
refs/heads/master from sidmishra
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=b866e48 ]
ATLAS-3727: Added REST API to get Admin Audit Details for an Admin Audit Guid
and Changed get entity audit Rest to support operation based filter
Signed-off-by: Sarath Subramanian
> Add get result details REST for admin audit record
> --
>
> Key: ATLAS-3727
> URL: https://issues.apache.org/jira/browse/ATLAS-3727
> Project: Atlas
> Issue Type: New Feature
> Components: atlas-core
>Affects Versions: 2.0.0
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3727.patch
>
>
> Right now purge admin audit result stores purged entities guids. We need :
> * Separate REST call to get more details summary of the entities purged.
> * Add audit operation as a parameter to v2/entity/\{guid}/audit
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-3729) Add audit operation as a parameter to v2/entity/{guid}/audit
[
https://issues.apache.org/jira/browse/ATLAS-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian resolved ATLAS-3729.
---
Resolution: Duplicate
> Add audit operation as a parameter to v2/entity/{guid}/audit
>
>
> Key: ATLAS-3729
> URL: https://issues.apache.org/jira/browse/ATLAS-3729
> Project: Atlas
> Issue Type: New Feature
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3727) Add get result details REST for admin audit record
[
https://issues.apache.org/jira/browse/ATLAS-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian updated ATLAS-3727:
--
Description:
Right now purge admin audit result stores purged entities guids. We need :
* Separate REST call to get more details summary of the entities purged.
* Add audit operation as a parameter to v2/entity/\{guid}/audit
was:Right now purge admin audit result stores purged entities guids. We need
a separate REST call to get more details summary of the entities purged.
> Add get result details REST for admin audit record
> --
>
> Key: ATLAS-3727
> URL: https://issues.apache.org/jira/browse/ATLAS-3727
> Project: Atlas
> Issue Type: New Feature
> Components: atlas-core
>Affects Versions: 2.0.0
>Reporter: Sidharth Kumar Mishra
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3727.patch
>
>
> Right now purge admin audit result stores purged entities guids. We need :
> * Separate REST call to get more details summary of the entities purged.
> * Add audit operation as a parameter to v2/entity/\{guid}/audit
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3727) Add get result details REST for admin audit record
[ https://issues.apache.org/jira/browse/ATLAS-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-3727: -- Fix Version/s: 2.1.0 > Add get result details REST for admin audit record > -- > > Key: ATLAS-3727 > URL: https://issues.apache.org/jira/browse/ATLAS-3727 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > Fix For: 2.1.0 > > Attachments: ATLAS-3727.patch > > > Right now purge admin audit result stores purged entities guids. We need a > separate REST call to get more details summary of the entities purged. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3727) Add get result details REST for admin audit record
[ https://issues.apache.org/jira/browse/ATLAS-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-3727: -- Affects Version/s: 2.0.0 > Add get result details REST for admin audit record > -- > > Key: ATLAS-3727 > URL: https://issues.apache.org/jira/browse/ATLAS-3727 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Sidharth Kumar Mishra >Assignee: Sidharth Kumar Mishra >Priority: Major > Attachments: ATLAS-3727.patch > > > Right now purge admin audit result stores purged entities guids. We need a > separate REST call to get more details summary of the entities purged. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Review Request 72351: ATLAS-3727: Add get result details REST for admin audit record
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/72351/#review220360
---
Ship it!
Ship It!
- Sarath Subramanian
On April 13, 2020, 5:46 p.m., Sidharth Mishra wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72351/
> ---
>
> (Updated April 13, 2020, 5:46 p.m.)
>
>
> Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, and Sarath
> Subramanian.
>
>
> Bugs: ATLAS-3727
> https://issues.apache.org/jira/browse/ATLAS-3727
>
>
> Repository: atlas
>
>
> Description
> ---
>
> ATLAS-3727: Add get result details REST for admin audit record
> ATLAS-3729: Add audit operation as a parameter to v2/entity/{guid}/audit
>
>
> Diffs
> -
>
> intg/src/main/java/org/apache/atlas/model/audit/AtlasAuditEntry.java
> 98e56f2bb
> intg/src/main/java/org/apache/atlas/model/audit/EntityAuditEventV2.java
> bcfdd9466
>
> repository/src/main/java/org/apache/atlas/repository/audit/AbstractStorageBasedAuditRepository.java
> 0deb7295e
>
> repository/src/main/java/org/apache/atlas/repository/audit/AtlasAuditService.java
> 35bf1d07e
>
> repository/src/main/java/org/apache/atlas/repository/audit/CassandraBasedAuditRepository.java
> b8131bd39
>
> repository/src/main/java/org/apache/atlas/repository/audit/EntityAuditListenerV2.java
> 4c1e1a959
>
> repository/src/main/java/org/apache/atlas/repository/audit/EntityAuditRepository.java
> 2a47e39ed
>
> repository/src/main/java/org/apache/atlas/repository/audit/HBaseBasedAuditRepository.java
> 021ca43ab
>
> repository/src/main/java/org/apache/atlas/repository/audit/InMemoryEntityAuditRepository.java
> ad6ec94c0
>
> repository/src/main/java/org/apache/atlas/repository/audit/NoopEntityAuditRepository.java
> 4bb68d502
>
> repository/src/test/java/org/apache/atlas/repository/audit/AuditRepositoryTestBase.java
> aa175a229
> webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java
> 2ab8bdb03
> webapp/src/main/java/org/apache/atlas/web/rest/EntityREST.java 402a323dd
> webapp/src/test/java/org/apache/atlas/web/resources/AdminResourceTest.java
> 43b85efc0
>
>
> Diff: https://reviews.apache.org/r/72351/diff/3/
>
>
> Testing
> ---
>
> Manual Testing:
>
> curl -u admin:admin123 --location --request GET
> 'http://sid-ycloud-atlas1-1.sid-ycloud-atlas1.root.hwx.site:31000/api/atlas/admin/audit/706e6e32-b619-43f2-8587-f2877ee27582/details?limit=100=0'
> --header 'Content-Type: application/json'
>
> curl -u admin:admin123 --location --request GET
> 'http://sid-ycloud-atlas1-1.sid-ycloud-atlas1.root.hwx.site:31000/api/atlas/v2/entity/0b10d06b-6740-4550-a571-5be8ba1ea3ae/audit?count=1=0b10d06b-6740-4550-a571-5be8ba1ea3ae:1586797534411:0:1586797535131=ENTITY_UPDATE'
>
> curl -u admin:admin123 --location --request GET
> 'http://sid-ycloud-atlas1-1.sid-ycloud-atlas1.root.hwx.site:31000/api/atlas/v2/entity/0b10d06b-6740-4550-a571-5be8ba1ea3ae/audit?count=1=ENTITY_UPDATE'
>
>
> Thanks,
>
> Sidharth Mishra
>
>
Re: Review Request 72372: ATLAS-3695 [Business Metadata] Special characters are being allowed in Attribute Name
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72372/#review220359 --- Ship it! Ship It! - Sarath Subramanian On April 16, 2020, 10:27 a.m., Mandar Ambawane wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/72372/ > --- > > (Updated April 16, 2020, 10:27 a.m.) > > > Review request for atlas, Jayendra Parab, Madhan Neethiraj, Nixon Rodrigues, > and Sarath Subramanian. > > > Bugs: ATLAS-3695 > https://issues.apache.org/jira/browse/ATLAS-3695 > > > Repository: atlas > > > Description > --- > > ATLAS-3695 [Business Metadata] Special characters are being allowed in > Attribute Name > > > Diffs > - > > intg/src/main/java/org/apache/atlas/AtlasErrorCode.java 16947ec > > repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasBusinessMetadataDefStoreV2.java > 5f4136f > > > Diff: https://reviews.apache.org/r/72372/diff/2/ > > > Testing > --- > > Pre-commit: > https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/1815/console > > Pre-commit: > https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/1817/console > > Basic testing is done. > > > Thanks, > > Mandar Ambawane > >
[jira] [Updated] (ATLAS-3734) AtlasPatchRegistry changes to get all patch information from graph query instead index queryUpdate AtlasPatchRegistry to use graph query instead index query for retrievin
[ https://issues.apache.org/jira/browse/ATLAS-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-3734: -- Summary: AtlasPatchRegistry changes to get all patch information from graph query instead index queryUpdate AtlasPatchRegistry to use graph query instead index query for retrieving all patch information (was: AtlasPatchRegistry changes to get all patch information from graph query instead index query) > AtlasPatchRegistry changes to get all patch information from graph query > instead index queryUpdate AtlasPatchRegistry to use graph query instead index > query for retrieving all patch information > - > > Key: ATLAS-3734 > URL: https://issues.apache.org/jira/browse/ATLAS-3734 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 2.1.0 > > Attachments: > 0001-ATLAS-3734-AtlasPatchRegistry-changes-to-get-all-pat.patch > > > AtlasPatchRegistry changes to get all patch information from graph query > instead index query. > Currently the index query is used. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3734) Update AtlasPatchRegistry to use graph query instead index query for retrieving all patch information
[ https://issues.apache.org/jira/browse/ATLAS-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-3734: -- Summary: Update AtlasPatchRegistry to use graph query instead index query for retrieving all patch information (was: AtlasPatchRegistry changes to get all patch information from graph query instead index queryUpdate AtlasPatchRegistry to use graph query instead index query for retrieving all patch information) > Update AtlasPatchRegistry to use graph query instead index query for > retrieving all patch information > - > > Key: ATLAS-3734 > URL: https://issues.apache.org/jira/browse/ATLAS-3734 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 2.1.0 > > Attachments: > 0001-ATLAS-3734-AtlasPatchRegistry-changes-to-get-all-pat.patch > > > AtlasPatchRegistry changes to get all patch information from graph query > instead index query. > Currently the index query is used. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3734) AtlasPatchRegistry changes to get all patch information from graph query instead index query
[ https://issues.apache.org/jira/browse/ATLAS-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-3734: -- Component/s: atlas-core > AtlasPatchRegistry changes to get all patch information from graph query > instead index query > > > Key: ATLAS-3734 > URL: https://issues.apache.org/jira/browse/ATLAS-3734 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 2.1.0 > > Attachments: > 0001-ATLAS-3734-AtlasPatchRegistry-changes-to-get-all-pat.patch > > > AtlasPatchRegistry changes to get all patch information from graph query > instead index query. > Currently the index query is used. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3734) AtlasPatchRegistry changes to get all patch information from graph query instead index query
[ https://issues.apache.org/jira/browse/ATLAS-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17086140#comment-17086140 ] ASF subversion and git services commented on ATLAS-3734: Commit 89d0d2a088c778bd60f36338d162ad4795d73a16 in atlas's branch refs/heads/branch-2.0 from Nixon Rodrigues [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=89d0d2a ] ATLAS-3734: Update AtlasPatchRegistry to use graph query instead index query for retrieving all patch information Signed-off-by: Sarath Subramanian (cherry picked from commit c1779231cfff4a6f6d934a38a5094defed1e07e6) > AtlasPatchRegistry changes to get all patch information from graph query > instead index query > > > Key: ATLAS-3734 > URL: https://issues.apache.org/jira/browse/ATLAS-3734 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 2.1.0 > > Attachments: > 0001-ATLAS-3734-AtlasPatchRegistry-changes-to-get-all-pat.patch > > > AtlasPatchRegistry changes to get all patch information from graph query > instead index query. > Currently the index query is used. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3734) AtlasPatchRegistry changes to get all patch information from graph query instead index query
[ https://issues.apache.org/jira/browse/ATLAS-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17086139#comment-17086139 ] ASF subversion and git services commented on ATLAS-3734: Commit c1779231cfff4a6f6d934a38a5094defed1e07e6 in atlas's branch refs/heads/master from Nixon Rodrigues [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=c177923 ] ATLAS-3734: Update AtlasPatchRegistry to use graph query instead index query for retrieving all patch information Signed-off-by: Sarath Subramanian > AtlasPatchRegistry changes to get all patch information from graph query > instead index query > > > Key: ATLAS-3734 > URL: https://issues.apache.org/jira/browse/ATLAS-3734 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 2.1.0 > > Attachments: > 0001-ATLAS-3734-AtlasPatchRegistry-changes-to-get-all-pat.patch > > > AtlasPatchRegistry changes to get all patch information from graph query > instead index query. > Currently the index query is used. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3737) Refactoring: Improve AtlasGraph to Work with Externally Initialized Graph Object
Ashutosh Mestry created ATLAS-3737: -- Summary: Refactoring: Improve AtlasGraph to Work with Externally Initialized Graph Object Key: ATLAS-3737 URL: https://issues.apache.org/jira/browse/ATLAS-3737 Project: Atlas Issue Type: Improvement Components: atlas-core Affects Versions: trunk Reporter: Ashutosh Mestry Assignee: Ashutosh Mestry Fix For: trunk *Background* Existing _AtlasGraph_ does not honor the instance with which it is constructed. The _getGraph_ method always uses the default method. This makes it impossible to use instances of graph database that have been initialized with different configurations. *Solution* * Refactor: _AtlasGraph.getGraph_ method to use the instance it is constructed with. * Refactor: _GraphHelper_ to be initialized with _AtlasGraph_ instance. This is important since entity creation is one area where an alternate graph instance helps. * Refactor: _AtlasUtilsV2_. This is a utility class that uses _AtlasGraphDatabase.getInstance_ for performing all its operations. * Refactor: _AtlasEntityStoreV2_ and _AtlasRelationshipStoreV2_ should be initialized with _AtlasGraph_ instances. * Refactor: _EntityGraphRetriever_. Same as above. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Review Request 72375: ATLAS-3733: upgraded JanusGraph version to 0.5.1, and Tinkerpop to 3.4.6
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72375/#review220358 --- Ship it! Ship It! - Sarath Subramanian On April 17, 2020, 10:53 a.m., Madhan Neethiraj wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/72375/ > --- > > (Updated April 17, 2020, 10:53 a.m.) > > > Review request for atlas, Ashutosh Mestry, keval bhatt, Nikhil Bonte, Nixon > Rodrigues, Pinal Shah, Sarath Subramanian, Sharmadha Sainath, Sidharth > Mishra, and Umesh Padashetty. > > > Bugs: ATLAS-3733 > https://issues.apache.org/jira/browse/ATLAS-3733 > > > Repository: atlas > > > Description > --- > > - updated JanusGraph version from 0.4.1 to 0.5.1, and updated Tinkerpop > version correspondingly > - updated Atlas sources to for few class renames > - updated unit test configiration (to set storage.backend.transactions=true), > as BerkeleyDB no more support earliers value 'false' in a ll scenarios (like > multiple threads) > - TODO: UT UserProfileServiceTest.deleteUser() fails with assertion-error in > JanusGraph layer; this needs to be investigated > > > Diffs > - > > > graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/query/NativeJanusGraphQuery.java > a7a169a43 > graphdb/janus/src/main/java/org/janusgraph/diskstorage/solr/Solr6Index.java > d0d7fd7db > intg/src/test/resources/atlas-application.properties 159f98b86 > pom.xml 2a3adcdb7 > > repository/src/test/java/org/apache/atlas/repository/userprofile/UserProfileServiceTest.java > 2410a9c87 > > > Diff: https://reviews.apache.org/r/72375/diff/2/ > > > Testing > --- > > - pre-commit tests run: > https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1821/ > - successfully ran QuickStart with embedded-hbase & solr profile > > > Thanks, > > Madhan Neethiraj > >
[jira] [Updated] (ATLAS-3736) Atlas typedef for microservices
[ https://issues.apache.org/jira/browse/ATLAS-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Eckman updated ATLAS-3736: -- Attachment: all_relationship_types.json all_entity_types.json > Atlas typedef for microservices > --- > > Key: ATLAS-3736 > URL: https://issues.apache.org/jira/browse/ATLAS-3736 > Project: Atlas > Issue Type: New Feature >Reporter: Barbara Eckman >Assignee: Barbara Eckman >Priority: Major > Attachments: all_entity_types.json, all_relationship_types.json > > > Microservices are an increasingly important and pervasive part of modern > architectures. By definition, a microservice’s APIs provide the only access > to a dataset—the schema of the underlying RDBMS, NoSQL db, etc is not > exposed. Therefore, it would be nice if Atlas enabled microservices to be > discovered along with other dataset types. The microservice typedef would > include the top-level endpoint, plus each of its API resources (GETs, POSTs, > PUTs, DELETEs), with their URI, parameters, JSON request and response > objects, and http response messages (200: Success, 404: Not Found, etc). > One might ask, why put this metadata into Atlas when it can already be > searched in a Swagger/OpenAPI repository? Three main reasons: 1) > microservice metadata can be searched along with all other enterprise > datasets to find a complete set of datasets of interest for, say, a > cross-silo data science investigation; 2) we can express lineage between > microservices and other datasets that either feed the db underlying the > microservice or serve as historical repositories for transactional > microservices (eg S3 datalakes); 3) we can express semantic relationships > between microservices, eg the marketing contact microservice contains a > location id as a “FK” that is the “PK” of the location microservice. > Main Entities: > * microservice > * APIResource > * responseMessage > Main Relationships: > * microservice to APIResources > * APIResource to responseMessages > * APIResource to the schemas of its JSON request/response objects > * microservice to microservice link > Proposed typedefs are attached. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3736) Atlas typedef for microservices
[ https://issues.apache.org/jira/browse/ATLAS-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Eckman updated ATLAS-3736: -- Description: Microservices are an increasingly important and pervasive part of modern architectures. By definition, a microservice’s APIs provide the only access to a dataset—the schema of the underlying RDBMS, NoSQL db, etc is not exposed. Therefore, it would be nice if Atlas enabled microservices to be discovered along with other dataset types. The microservice typedef would include the top-level endpoint, plus each of its API resources (GETs, POSTs, PUTs, DELETEs), with their URI, parameters, JSON request and response objects, and http response messages (200: Success, 404: Not Found, etc). One might ask, why put this metadata into Atlas when it can already be searched in a Swagger/OpenAPI repository? Three main reasons: 1) microservice metadata can be searched along with all other enterprise datasets to find a complete set of datasets of interest for, say, a cross-silo data science investigation; 2) we can express lineage between microservices and other datasets that either feed the db underlying the microservice or serve as historical repositories for transactional microservices (eg S3 datalakes); 3) we can express semantic relationships between microservices, eg the marketing contact microservice contains a location id as a “FK” that is the “PK” of the location microservice. Main Entities: * microservice * APIResource * responseMessage Main Relationships: * microservice to APIResources * APIResource to responseMessages * APIResource to the schemas of its JSON request/response objects * microservice to microservice link Proposed typedefs are attached. was: Microservices are an increasingly important and pervasive part of modern architectures. By definition, a microservice’s APIs provide the only access to a dataset—the schema of the underlying RDBMS, NoSQL db, etc is not exposed. Therefore, it would be nice if Atlas enabled microservices to be discovered along with other dataset types. The microservice typedef would include the top-level endpoint, plus each of its API resources (GETs, POSTs, PUTs, DELETEs), with their URI, parameters, JSON request and response objects, and http response messages (200: Success, 404: Not Found, etc). One might ask, why put this metadata into Atlas when it can already be searched in a Swagger/OpenAPI repository? Three main reasons: 1) microservice metadata can be searched along with all other enterprise datasets to find a complete set of datasets of interest for, say, a cross-silo data science investigation; 2) we can express lineage between microservices and other datasets that either feed the db underlying the microservice or serve as historical repositories for transactional microservices (eg S3 datalakes); 3) we can express semantic relationships between microservices, eg the marketing contact microservice contains a location id as a “FK” that is the “PK” of the location microservice. more to come... > Atlas typedef for microservices > --- > > Key: ATLAS-3736 > URL: https://issues.apache.org/jira/browse/ATLAS-3736 > Project: Atlas > Issue Type: New Feature >Reporter: Barbara Eckman >Assignee: Barbara Eckman >Priority: Major > Attachments: all_entity_types.json, all_relationship_types.json > > > Microservices are an increasingly important and pervasive part of modern > architectures. By definition, a microservice’s APIs provide the only access > to a dataset—the schema of the underlying RDBMS, NoSQL db, etc is not > exposed. Therefore, it would be nice if Atlas enabled microservices to be > discovered along with other dataset types. The microservice typedef would > include the top-level endpoint, plus each of its API resources (GETs, POSTs, > PUTs, DELETEs), with their URI, parameters, JSON request and response > objects, and http response messages (200: Success, 404: Not Found, etc). > One might ask, why put this metadata into Atlas when it can already be > searched in a Swagger/OpenAPI repository? Three main reasons: 1) > microservice metadata can be searched along with all other enterprise > datasets to find a complete set of datasets of interest for, say, a > cross-silo data science investigation; 2) we can express lineage between > microservices and other datasets that either feed the db underlying the > microservice or serve as historical repositories for transactional > microservices (eg S3 datalakes); 3) we can express semantic relationships > between microservices, eg the marketing contact microservice contains a > location id as a “FK” that is the “PK” of the location microservice. > Main Entities: > * microservice > * APIResource >
Re: Review Request 72374: ATLAS-3734:AtlasPatchRegistry changes to get all patch information from graph query instead index query
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/72374/#review220355
---
Ship it!
Ship It!
- Sarath Subramanian
On April 17, 2020, 2:18 a.m., Nixon Rodrigues wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72374/
> ---
>
> (Updated April 17, 2020, 2:18 a.m.)
>
>
> Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Nikhil Bonte,
> and Sarath Subramanian.
>
>
> Repository: atlas
>
>
> Description
> ---
>
> This patch updates the AtlasPatchRegistry->getAllPatches method to read
> patch information from graph query instead index query.
>
>
> Diffs
> -
>
>
> repository/src/main/java/org/apache/atlas/repository/patches/AtlasPatchRegistry.java
> a251638e7
>
>
> Diff: https://reviews.apache.org/r/72374/diff/2/
>
>
> Testing
> ---
>
> tested patch on atlas restart multiple times
>
> 2020-04-16 15:48:48,478 INFO - [main:] ~ patch found ==>>
> AtlasPatch{id=TYPEDEF_PATCH_3000_137, description='Set serviceType 'aws' to
> aws_s3_pseudo_dir_avro_schema', type='TYPEDEF_PATCH',
> action='SET_SERVICE_TYPE', updatedBy='atlas', createdBy='atlas',
> createdTime=1584712881496, updatedTime=1584712881496, status=SKIPPED}
> (AtlasPatchRegistry:182)
>
> 2020-04-16 15:48:48,479 INFO - [main:] ~ patch found ==>>
> AtlasPatch{id=TYPEDEF_PATCH_3000_003_003, description='Remove legacy
> reference attribute 'avroSchema from aws_s3_object', type='TYPEDEF_PATCH',
> action='REMOVE_LEGACY_REF_ATTRIBUTES', updatedBy='atlas', createdBy='atlas',
> createdTime=1582720025472, updatedTime=1582720025472, status=SKIPPED}
> (AtlasPatchRegistry:182)
>
> 2020-04-16 15:48:48,479 INFO - [main:] ~ patch found ==>>
> AtlasPatch{id=JAVA_PATCH__001, description='Add __u_ property for each
> unique attribute of active entities', type='JAVA_PATCH', action='apply',
> updatedBy='atlas', createdBy='atlas', createdTime=1584712881496,
> updatedTime=1584712881496, status=APPLIED} (AtlasPatchRegistry:182)
>
>
> Thanks,
>
> Nixon Rodrigues
>
>
[jira] [Updated] (ATLAS-3736) Atlas typedef for microservices
[ https://issues.apache.org/jira/browse/ATLAS-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Eckman updated ATLAS-3736: -- Description: Microservices are an increasingly important and pervasive part of modern architectures. By definition, a microservice’s APIs provide the only access to a dataset—the schema of the underlying RDBMS, NoSQL db, etc is not exposed. Therefore, it would be nice if Atlas enabled microservices to be discovered along with other dataset types. The microservice typedef would include the top-level endpoint, plus each of its API resources (GETs, POSTs, PUTs, DELETEs), with their URI, parameters, JSON request and response objects, and http response messages (200: Success, 404: Not Found, etc). One might ask, why put this metadata into Atlas when it can already be searched in a Swagger/OpenAPI repository? Three main reasons: 1) microservice metadata can be searched along with all other enterprise datasets to find a complete set of datasets of interest for, say, a cross-silo data science investigation; 2) we can express lineage between microservices and other datasets that either feed the db underlying the microservice or serve as historical repositories for transactional microservices (eg S3 datalakes); 3) we can express semantic relationships between microservices, eg the marketing contact microservice contains a location id as a “FK” that is the “PK” of the location microservice. more to come... was: Microservices are an increasingly important and pervasive part of modern architectures. By definition, a microservice’s APIs provide the only access to a dataset—the schema of the underlying RDBMS, NoSQL db, etc is not exposed. Therefore, it would be nice if Atlas enabled microservices to be discovered along with other dataset types. The microservice typedef would include the top-level endpoint, plus each of its API resources (GETs, POSTs, PUTs, DELETEs), with their URI, parameters, JSON request and response objects, and http response messages (200: Success, 404: Not Found, etc). One might ask, why put this metadata into Atlas when it can already be searched in a Swagger/OpenAPI repository? Three main reasons: 1) microservice metadata can be searched along with all other enterprise datasets to find a complete set of datasets of interest for, say, a cross-silo data science investigation; 2) we can express lineage between microservices and other datasets that either feed the db underlying the microservice or serve as historical repositories for transactional microservices (eg S3 datalakes); 3) we can express semantic relationships between microservices, eg the marketing contact microservice contains a location id as a “FK” that is the “PK” of the location microservice. *** more to come *** > Atlas typedef for microservices > --- > > Key: ATLAS-3736 > URL: https://issues.apache.org/jira/browse/ATLAS-3736 > Project: Atlas > Issue Type: New Feature >Reporter: Barbara Eckman >Assignee: Barbara Eckman >Priority: Major > > Microservices are an increasingly important and pervasive part of modern > architectures. By definition, a microservice’s APIs provide the only access > to a dataset—the schema of the underlying RDBMS, NoSQL db, etc is not > exposed. Therefore, it would be nice if Atlas enabled microservices to be > discovered along with other dataset types. The microservice typedef would > include the top-level endpoint, plus each of its API resources (GETs, POSTs, > PUTs, DELETEs), with their URI, parameters, JSON request and response > objects, and http response messages (200: Success, 404: Not Found, etc). > One might ask, why put this metadata into Atlas when it can already be > searched in a Swagger/OpenAPI repository? Three main reasons: 1) > microservice metadata can be searched along with all other enterprise > datasets to find a complete set of datasets of interest for, say, a > cross-silo data science investigation; 2) we can express lineage between > microservices and other datasets that either feed the db underlying the > microservice or serve as historical repositories for transactional > microservices (eg S3 datalakes); 3) we can express semantic relationships > between microservices, eg the marketing contact microservice contains a > location id as a “FK” that is the “PK” of the location microservice. > more to come... > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3736) Atlas typedef for microservices
[ https://issues.apache.org/jira/browse/ATLAS-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Eckman updated ATLAS-3736: -- Description: Microservices are an increasingly important and pervasive part of modern architectures. By definition, a microservice’s APIs provide the only access to a dataset—the schema of the underlying RDBMS, NoSQL db, etc is not exposed. Therefore, it would be nice if Atlas enabled microservices to be discovered along with other dataset types. The microservice typedef would include the top-level endpoint, plus each of its API resources (GETs, POSTs, PUTs, DELETEs), with their URI, parameters, JSON request and response objects, and http response messages (200: Success, 404: Not Found, etc). One might ask, why put this metadata into Atlas when it can already be searched in a Swagger/OpenAPI repository? Three main reasons: 1) microservice metadata can be searched along with all other enterprise datasets to find a complete set of datasets of interest for, say, a cross-silo data science investigation; 2) we can express lineage between microservices and other datasets that either feed the db underlying the microservice or serve as historical repositories for transactional microservices (eg S3 datalakes); 3) we can express semantic relationships between microservices, eg the marketing contact microservice contains a location id as a “FK” that is the “PK” of the location microservice. *** more to come *** was: Microservices are an increasingly important and pervasive part of modern architectures. By definition, a microservice’s APIs provide the only access to a dataset—the schema of the underlying RDBMS, NoSQL db, etc is not exposed. Therefore, it would be nice if Atlas enabled microservices to be discovered along with other dataset types. The microservice typedef would include the top-level endpoint, plus each of its API resources (GETs, POSTs, PUTs, DELETEs), with their URI, parameters, JSON request and response objects, and http response messages (200: Success, 404: Not Found, etc). One might ask, why put this metadata into Atlas when it can already be searched in a Swagger/OpenAPI repository? Three main reasons: 1) microservice metadata can be searched along with all other enterprise datasets to find a complete set of datasets of interest for, say, a cross-silo data science investigation; 2) we can express lineage between microservices and other datasets that either feed the db underlying the microservice or serve as historical repositories for transactional microservices (eg S3 datalakes); 3) we can express semantic relationships between microservices, eg the marketing contact microservice contains a location id as a “FK” that is the “PK” of the location microservice. > Atlas typedef for microservices > --- > > Key: ATLAS-3736 > URL: https://issues.apache.org/jira/browse/ATLAS-3736 > Project: Atlas > Issue Type: New Feature >Reporter: Barbara Eckman >Assignee: Barbara Eckman >Priority: Major > > Microservices are an increasingly important and pervasive part of modern > architectures. By definition, a microservice’s APIs provide the only access > to a dataset—the schema of the underlying RDBMS, NoSQL db, etc is not > exposed. Therefore, it would be nice if Atlas enabled microservices to be > discovered along with other dataset types. The microservice typedef would > include the top-level endpoint, plus each of its API resources (GETs, POSTs, > PUTs, DELETEs), with their URI, parameters, JSON request and response > objects, and http response messages (200: Success, 404: Not Found, etc). > One might ask, why put this metadata into Atlas when it can already be > searched in a Swagger/OpenAPI repository? Three main reasons: 1) > microservice metadata can be searched along with all other enterprise > datasets to find a complete set of datasets of interest for, say, a > cross-silo data science investigation; 2) we can express lineage between > microservices and other datasets that either feed the db underlying the > microservice or serve as historical repositories for transactional > microservices (eg S3 datalakes); 3) we can express semantic relationships > between microservices, eg the marketing contact microservice contains a > location id as a “FK” that is the “PK” of the location microservice. > > *** more to come *** > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3736) Atlas typedef for microservices
Barbara Eckman created ATLAS-3736: - Summary: Atlas typedef for microservices Key: ATLAS-3736 URL: https://issues.apache.org/jira/browse/ATLAS-3736 Project: Atlas Issue Type: New Feature Reporter: Barbara Eckman Assignee: Barbara Eckman Microservices are an increasingly important and pervasive part of modern architectures. By definition, a microservice’s APIs provide the only access to a dataset—the schema of the underlying RDBMS, NoSQL db, etc is not exposed. Therefore, it would be nice if Atlas enabled microservices to be discovered along with other dataset types. The microservice typedef would include the top-level endpoint, plus each of its API resources (GETs, POSTs, PUTs, DELETEs), with their URI, parameters, JSON request and response objects, and http response messages (200: Success, 404: Not Found, etc). One might ask, why put this metadata into Atlas when it can already be searched in a Swagger/OpenAPI repository? Three main reasons: 1) microservice metadata can be searched along with all other enterprise datasets to find a complete set of datasets of interest for, say, a cross-silo data science investigation; 2) we can express lineage between microservices and other datasets that either feed the db underlying the microservice or serve as historical repositories for transactional microservices (eg S3 datalakes); 3) we can express semantic relationships between microservices, eg the marketing contact microservice contains a location id as a “FK” that is the “PK” of the location microservice. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Review Request 72375: ATLAS-3733: upgraded JanusGraph version to 0.5.1, and Tinkerpop to 3.4.6
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72375/ --- (Updated April 17, 2020, 5:53 p.m.) Review request for atlas, Ashutosh Mestry, keval bhatt, Nikhil Bonte, Nixon Rodrigues, Pinal Shah, Sarath Subramanian, Sharmadha Sainath, Sidharth Mishra, and Umesh Padashetty. Changes --- - updates to avoid changes in multiple configuration files used in UTs/ITs - fixed unit test to avoid failure due to timing issue Bugs: ATLAS-3733 https://issues.apache.org/jira/browse/ATLAS-3733 Repository: atlas Description --- - updated JanusGraph version from 0.4.1 to 0.5.1, and updated Tinkerpop version correspondingly - updated Atlas sources to for few class renames - updated unit test configiration (to set storage.backend.transactions=true), as BerkeleyDB no more support earliers value 'false' in a ll scenarios (like multiple threads) - TODO: UT UserProfileServiceTest.deleteUser() fails with assertion-error in JanusGraph layer; this needs to be investigated Diffs (updated) - graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/query/NativeJanusGraphQuery.java a7a169a43 graphdb/janus/src/main/java/org/janusgraph/diskstorage/solr/Solr6Index.java d0d7fd7db intg/src/test/resources/atlas-application.properties 159f98b86 pom.xml 2a3adcdb7 repository/src/test/java/org/apache/atlas/repository/userprofile/UserProfileServiceTest.java 2410a9c87 Diff: https://reviews.apache.org/r/72375/diff/2/ Changes: https://reviews.apache.org/r/72375/diff/1-2/ Testing --- - pre-commit tests run: https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1821/ - successfully ran QuickStart with embedded-hbase & solr profile Thanks, Madhan Neethiraj
[jira] [Updated] (ATLAS-3735) CustomAttributes: Conditionally Allow Setting of Values Larger than Default Length
[ https://issues.apache.org/jira/browse/ATLAS-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3735: --- Attachment: ATLAS-3735-CustomAttribute-length-validation-bypass-.patch > CustomAttributes: Conditionally Allow Setting of Values Larger than Default > Length > -- > > Key: ATLAS-3735 > URL: https://issues.apache.org/jira/browse/ATLAS-3735 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Attachments: > ATLAS-3735-CustomAttribute-length-validation-bypass-.patch > > > *Background* > The new customAttribute has a limit of set on the default value. This can be > restricting. > *Solution* > * Define special prefix. > * If this is set, bypass the length validation. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3735) CustomAttributes: Conditionally Allow Setting of Values Larger than Default Length
Ashutosh Mestry created ATLAS-3735: -- Summary: CustomAttributes: Conditionally Allow Setting of Values Larger than Default Length Key: ATLAS-3735 URL: https://issues.apache.org/jira/browse/ATLAS-3735 Project: Atlas Issue Type: Improvement Components: atlas-core Affects Versions: trunk Reporter: Ashutosh Mestry Assignee: Ashutosh Mestry *Background* The new customAttribute has a limit of set on the default value. This can be restricting. *Solution* * Define special prefix. * If this is set, bypass the length validation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [atlas] dwarszawski closed pull request #95: Feature/enable freetext sort
dwarszawski closed pull request #95: Feature/enable freetext sort URL: https://github.com/apache/atlas/pull/95 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [atlas] dwarszawski opened a new pull request #95: Feature/enable freetext sort
dwarszawski opened a new pull request #95: Feature/enable freetext sort URL: https://github.com/apache/atlas/pull/95 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (ATLAS-3732) UI: Lineage graph improvement and lib version updated
[ https://issues.apache.org/jira/browse/ATLAS-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3732: --- Fix Version/s: 3.0.0 2.1.0 > UI: Lineage graph improvement and lib version updated > - > > Key: ATLAS-3732 > URL: https://issues.apache.org/jira/browse/ATLAS-3732 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3732.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3732) UI: Lineage graph improvement and lib version updated
[ https://issues.apache.org/jira/browse/ATLAS-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17085704#comment-17085704 ] Nixon Rodrigues commented on ATLAS-3732: +1 for the patch. Thanks [~kevalbhatt] > UI: Lineage graph improvement and lib version updated > - > > Key: ATLAS-3732 > URL: https://issues.apache.org/jira/browse/ATLAS-3732 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3732.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3732) UI: Lineage graph improvement and lib version updated
[ https://issues.apache.org/jira/browse/ATLAS-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3732: --- Attachment: ATLAS-3732.patch > UI: Lineage graph improvement and lib version updated > - > > Key: ATLAS-3732 > URL: https://issues.apache.org/jira/browse/ATLAS-3732 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Attachments: ATLAS-3732.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Review Request 72374: ATLAS-3734:AtlasPatchRegistry changes to get all patch information from graph query instead index query
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/72374/
---
(Updated April 17, 2020, 9:18 a.m.)
Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Nikhil Bonte, and
Sarath Subramanian.
Changes
---
Precommit passing for ATLAS-3734
https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/1822/consoleFull
Summary (updated)
-
ATLAS-3734:AtlasPatchRegistry changes to get all patch information from graph
query instead index query
Repository: atlas
Description
---
This patch updates the AtlasPatchRegistry->getAllPatches method to read patch
information from graph query instead index query.
Diffs (updated)
-
repository/src/main/java/org/apache/atlas/repository/patches/AtlasPatchRegistry.java
a251638e7
Diff: https://reviews.apache.org/r/72374/diff/2/
Changes: https://reviews.apache.org/r/72374/diff/1-2/
Testing
---
tested patch on atlas restart multiple times
2020-04-16 15:48:48,478 INFO - [main:] ~ patch found ==>>
AtlasPatch{id=TYPEDEF_PATCH_3000_137, description='Set serviceType 'aws' to
aws_s3_pseudo_dir_avro_schema', type='TYPEDEF_PATCH',
action='SET_SERVICE_TYPE', updatedBy='atlas', createdBy='atlas',
createdTime=1584712881496, updatedTime=1584712881496, status=SKIPPED}
(AtlasPatchRegistry:182)
2020-04-16 15:48:48,479 INFO - [main:] ~ patch found ==>>
AtlasPatch{id=TYPEDEF_PATCH_3000_003_003, description='Remove legacy reference
attribute 'avroSchema from aws_s3_object', type='TYPEDEF_PATCH',
action='REMOVE_LEGACY_REF_ATTRIBUTES', updatedBy='atlas', createdBy='atlas',
createdTime=1582720025472, updatedTime=1582720025472, status=SKIPPED}
(AtlasPatchRegistry:182)
2020-04-16 15:48:48,479 INFO - [main:] ~ patch found ==>>
AtlasPatch{id=JAVA_PATCH__001, description='Add __u_ property for each
unique attribute of active entities', type='JAVA_PATCH', action='apply',
updatedBy='atlas', createdBy='atlas', createdTime=1584712881496,
updatedTime=1584712881496, status=APPLIED} (AtlasPatchRegistry:182)
Thanks,
Nixon Rodrigues
Re: Review Request 72376: ATLAS-3731 : Add Documentation for Apache Atlas 2.1
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72376/ --- (Updated April 17, 2020, 8:54 a.m.) Review request for atlas, Madhan Neethiraj, Nixon Rodrigues, and Sarath Subramanian. Bugs: ATLAS-3731 https://issues.apache.org/jira/browse/ATLAS-3731 Repository: atlas Description --- Updated Documentation for Apache Atlas 2.1 with new improvements and features. Diffs - docs/src/documents/Whats-New/WhatsNew-2.1.md PRE-CREATION Diff: https://reviews.apache.org/r/72376/diff/1/ Testing --- Thanks, chaitali
[jira] [Updated] (ATLAS-3731) Add Documentation for Apache Atlas 2.1
[ https://issues.apache.org/jira/browse/ATLAS-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole updated ATLAS-3731: --- Summary: Add Documentation for Apache Atlas 2.1 (was: Update Documentation for Apache Atlas 2.1) > Add Documentation for Apache Atlas 2.1 > -- > > Key: ATLAS-3731 > URL: https://issues.apache.org/jira/browse/ATLAS-3731 > Project: Atlas > Issue Type: Task >Affects Versions: 2.1.0 >Reporter: chaitali borole >Assignee: chaitali borole >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
