---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/65176/
---
Review request for atlas.
Bugs: ATLAS-2369
https://issues.apache.org/jira/b
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/65102/
---
(Updated Jan. 16, 2018, 2:43 a.m.)
Review request for atlas, Ashutosh Mestry, M
Hi Mandy,
Thanks for the extra detail, I can see the need to keep BOTH now. I like
your proposal on how to resolve conflicts - I had not seen this; I assume
removing a classification from an entity could enable tags to propagate to
it. I suggest including the proposed tag propagation values on t
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/65163/#review195423
---
Ship it!
Ship It!
- David Radley
On Jan. 15, 2018, 11:08 a.m
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/65163/#review195420
---
Ship it!
Ship It!
- Mandy Chessell
On Jan. 15, 2018, 11:08 a
Dear All,
I have an answer from Bogdan on the REST URL. Basically if there is no
userId, the URL collapses.
Eg /users/{userId}/entities/{guid} would be /entities/{guid} if there is
no end user associated with the request. So no need for a dodgy fake
userId for the server to server requests
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/65163/#review195419
---
Ship it!
Ship It!
- keval bhatt
On Jan. 15, 2018, 11:08 a.m.
[
https://issues.apache.org/jira/browse/ATLAS-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nixon Rodrigues updated ATLAS-2352:
---
Attachment: ATLAS-2352.2.patch
> Atlas server should provide configuration to specify validity
[
https://issues.apache.org/jira/browse/ATLAS-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16326270#comment-16326270
]
Nixon Rodrigues commented on ATLAS-2352:
[^ATLAS-2352.2.patch]
> Atlas server sho
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/65121/
---
(Updated Jan. 15, 2018, 2:12 p.m.)
Review request for atlas, Apoorv Naik, Ashut
Hello David,
There is only on instance of a classification allowed on an entity. A
propagated classification can not override an explicitly set
classification. When it comes to managing conflicts, there is nothing
special about propagated classifications. A new entity, or a new
classificatio
Hi Mandy,
I think you use cases make sense.
For the first use case, I am not sure what the confidential classification
is here - is it a classification that is shipped with the open types? I
assume that confidentiality would be a classification that has an ordered
set of enumerated values, like
Dear All,
I have been thinking through the implications of our discussion last week
on userIds. We agreed that the end user's userId would become a part of
the URL for the OMAS REST calls. This means it is explicitly passed to
the Java classes server-side.
There are some repository calls that
Hello David,
I am not sure how many examples you need. But here are a couple of
patterns ...
When we have a cluster of entities that make up a logical collection of
information - such as a NoteLog and its Notes nested inside (area 1) - and
a classification applied to any one element needs to b
[
https://issues.apache.org/jira/browse/ATLAS-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16326132#comment-16326132
]
Madhan Neethiraj commented on ATLAS-2364:
-
Review board URL: https://reviews.apach
[
https://issues.apache.org/jira/browse/ATLAS-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2364:
Attachment: ATLAS-2364.patch
> Update Asset typedef to list Referenceable as its super-type
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/65163/
---
Review request for atlas, David Radley and Mandy Chessell.
Bugs: ATLAS-2364
Hi Mandy,
From what I recall, we discussed some scenarios that we felt Tag
propagation would be useful. I think the use cases we are thinking of are
now indicated by the model files that have "propagateTags" set. The
examples include the semanticClassification and the
"hbase_table_column_famili
Madhan Neethiraj created ATLAS-2364:
---
Summary: Update Asset typedef to list Referenceable as its
super-type
Key: ATLAS-2364
URL: https://issues.apache.org/jira/browse/ATLAS-2364
Project: Atlas
[
https://issues.apache.org/jira/browse/ATLAS-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2364:
Issue Type: Improvement (was: Bug)
> Update Asset typedef to list Referenceable as its supe
20 matches
Mail list logo