---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/61100/
---
Review request for atlas.
Bugs: ATLAS-1989
[
https://issues.apache.org/jira/browse/ATLAS-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apoorv Naik updated ATLAS-1989:
---
Attachment: 0001-ATLAS-1989-Hooks-to-include-atlas-model-classes-atla.patch
> Atlas Hooks should
Apoorv Naik created ATLAS-1989:
--
Summary: Atlas Hooks should package atlas-intg jar
Key: ATLAS-1989
URL: https://issues.apache.org/jira/browse/ATLAS-1989
Project: Atlas
Issue Type: Bug
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/61088/
---
Review request for atlas, keval bhatt and Madhan Neethiraj.
Bugs: ATLAS-1988
[
https://issues.apache.org/jira/browse/ATLAS-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian updated ATLAS-1988:
--
Description:
Add a new endpoint in DiscoveryREST to search for related entities.
[
https://issues.apache.org/jira/browse/ATLAS-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian updated ATLAS-1988:
--
Description:
Add a new endpoint (v2/search/relationship) in DiscoveryREST to search for
Sarath Subramanian created ATLAS-1988:
-
Summary: Implement REST API to search for related entities
Key: ATLAS-1988
URL: https://issues.apache.org/jira/browse/ATLAS-1988
Project: Atlas
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/61085/#review181253
---
[
https://issues.apache.org/jira/browse/ATLAS-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098905#comment-16098905
]
Sarath Subramanian commented on ATLAS-1986:
---
Yes, once the change is committed to the right
[
https://issues.apache.org/jira/browse/ATLAS-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098880#comment-16098880
]
David Radley commented on ATLAS-1986:
-
Hi Sarath,
Sorry about that - I am still quite new to this -
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/61085/
---
Review request for atlas, Madhan Neethiraj and Sarath Subramanian.
Repository:
[
https://issues.apache.org/jira/browse/ATLAS-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian reopened ATLAS-1986:
---
This change is not committed yet, moving to patch available state
> Rename
Hello Nigel,
This makes a lot of sense to me.
Does the Audit log interface assume a transactional backing store -so that
data updates and the audit log entry are committed in the same
transaction? If not then we might also want to consider a simple file
based audit log as the entry level
[
https://issues.apache.org/jira/browse/ATLAS-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Radley updated ATLAS-1987:
Attachment: 0005LinkedMediaTypes.json
0210Glossary.json
David Radley created ATLAS-1987:
---
Summary: Relationship creation for many to many does not work.
Key: ATLAS-1987
URL: https://issues.apache.org/jira/browse/ATLAS-1987
Project: Atlas
Issue
[
https://issues.apache.org/jira/browse/ATLAS-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Radley updated ATLAS-1986:
Attachment: ATLAS-1986.patch
> Rename relationshipAttributes in Entity to relationships.
>
On 12/07/2017 13:17, David Radley wrote:
> will derive the tags associated with an entity. We have not designed yet
> how to override this behaviour, when the propagation behaviour in the Def
> is not appropriate. I have not got the Jira number for this : by copy
> Madhan - do you have this for
[
https://issues.apache.org/jira/browse/ATLAS-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098330#comment-16098330
]
David Radley commented on ATLAS-1986:
-
https://reviews.apache.org/r/61077/
> Rename
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/61077/
---
Review request for atlas, Madhan Neethiraj and Sarath Subramanian.
Repository:
[
https://issues.apache.org/jira/browse/ATLAS-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098207#comment-16098207
]
Israel Varea commented on ATLAS-1955:
-
I think these two validations will cover most of the basic
Hi all,
I have just had a chat with Graham. we are thinking that we should go with
relationships as the top level name. We also think we could helpfully add
in the related entity in the new class like this:
class AtlasRelationshipObjectId {
AtlasObjectId relatedEntity;
String
On 22/07/2017 00:00, Madhan Neethiraj (JIRA) wrote:
> Madhan Neethiraj created ATLAS-1982:
> Summary: Update referenced to "incubator" in website
>
When INFRA update the mailing lists, I presume the old subscriber list
is still in place?
-> Users should update any email filters
On 23/07/2017 10:36, David Radley (JIRA) wrote:
>
> [~ivarea] some thoughts:
> I think there is a value in Atlas having the capability to validate
attribute values conform to a certain pattern.
I think there's 2 forms of validation here..
a) Capturing validation rules in Atlas - ie more
On 19/07/2017 16:45, David Radley wrote:
for Hadoop 3 to bring in Java 8 and Janus? We should look to see what the
migration considerations are for Hadoop 2 customers to move to Janus.
It's probably worth creating a subtask, or separate JIRA for the
specific data migration work.
Initially
I'm good with relatedEntities
- relationshipAttributes is definately confusing
- relationships isn't clear to me
other options could include
- relatedEntityAttributes - but is a little longwinded
- injectedAttributes - another option but perhaps unclear for some
Nigel Jones, Analytics
David Radley created ATLAS-1986:
---
Summary: Rename relationshipAttributes in Entity to relationships.
Key: ATLAS-1986
URL: https://issues.apache.org/jira/browse/ATLAS-1986
Project: Atlas
Issue
Personally I think 'relatedEntities' is clearer.
Best regards,
Graham
Graham Wallis
IBM Analytics Emerging Technology Center
Internet: graham_wal...@uk.ibm.com
IBM Laboratories, Hursley Park, Hursley, Hampshire SO21 2JN
Tel: +44-1962-815356Tie: 7-245356
From: Madhan Neethiraj
[
https://issues.apache.org/jira/browse/ATLAS-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098097#comment-16098097
]
David Radley commented on ATLAS-1984:
-
As per my dev list comment, I like the way of using an existing
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/61076/
---
Review request for atlas.
Repository: atlas
Description
---
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/61040/#review181193
---
Ship it!
Ship It!
- Nixon Rodrigues
On July 24, 2017, 3:50
Current name of ‘relationshipAttributes’ makes sense looking from an entity
point-of-view – it distinguishes regular-attributes of an entity from
attributes injected by relationships. However, given that relationships can
themselves might have attributes, it can be confusing.
I was going to
Hi Sarath,
Great, personally for the Entity's current relationshipAttributes, I
prefer relationships as it is simpler - is there a reason you need
attribute in the name?
all the best, David.
From: Sarath Subramanian
To: dev@atlas.apache.org
Cc: Madhan
Sharmadha Sainath created ATLAS-1985:
Summary: Regression : Basic/DSL Query fired on PASSIVE server
redirects to ACTIVE server , adding an extra "amp;" to the parameters
Key: ATLAS-1985
URL:
Hi David,
I agree with using the term 'relationship attributes' for attributes of
relationship, I suggest we use "relatedAttributes" for relationship
attributes of entity.
Thanks,
Sarath Subramanian
On Sun, Jul 23, 2017 at 2:22 AM, David Radley
wrote:
> Hi Madhan,
>
34 matches
Mail list logo