[jira] [Created] (ATLAS-3534) EntityREST changes to allow namespace attributes to be added to an entity instance
Aadarsh Jajodia created ATLAS-3534: -- Summary: EntityREST changes to allow namespace attributes to be added to an entity instance Key: ATLAS-3534 URL: https://issues.apache.org/jira/browse/ATLAS-3534 Project: Atlas Issue Type: New Feature Reporter: Aadarsh Jajodia Assignee: Aadarsh Jajodia -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3501) Update guava version to 28.0-jre
[ https://issues.apache.org/jira/browse/ATLAS-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3501: --- Attachment: 0001-ATLAS-3501-Update-guava-version-to-28.0-jre.patch > Update guava version to 28.0-jre > > > Key: ATLAS-3501 > URL: https://issues.apache.org/jira/browse/ATLAS-3501 > Project: Atlas > Issue Type: Bug >Reporter: Aadarsh Jajodia >Assignee: Aadarsh Jajodia >Priority: Major > Attachments: 0001-ATLAS-3501-Update-guava-version-to-28.0-jre.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3501) Update guava version to 28.0-jre
Aadarsh Jajodia created ATLAS-3501: -- Summary: Update guava version to 28.0-jre Key: ATLAS-3501 URL: https://issues.apache.org/jira/browse/ATLAS-3501 Project: Atlas Issue Type: Bug Reporter: Aadarsh Jajodia Assignee: Aadarsh Jajodia -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3452) Update jackson.databind.version to 2.10.0
[ https://issues.apache.org/jira/browse/ATLAS-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3452: --- Summary: Update jackson.databind.version to 2.10.0 (was: Update jackson.databind.version to 2.10.0 and Guava Version to 28.0-jre) > Update jackson.databind.version to 2.10.0 > - > > Key: ATLAS-3452 > URL: https://issues.apache.org/jira/browse/ATLAS-3452 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Kalman >Assignee: Aadarsh Jajodia >Priority: Major > Fix For: trunk, 2.1.0 > > Attachments: > 0001-ATLAS-3452-Update-jackson.databind.version-to-2.10.0.patch > > > Atlas uses jackson-databind 2.9.9.1, but there is a patch release, 2.10.0 to > address a CVE vulnerability, to make static code analysis tool happy, we need > to upgrade it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3452) Update jackson.databind.version to 2.10.0 and Guava Version to 28.0-jre
[ https://issues.apache.org/jira/browse/ATLAS-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3452: --- Attachment: 0001-ATLAS-3452-Update-jackson.databind.version-to-2.10.0.patch > Update jackson.databind.version to 2.10.0 and Guava Version to 28.0-jre > --- > > Key: ATLAS-3452 > URL: https://issues.apache.org/jira/browse/ATLAS-3452 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Kalman >Assignee: Aadarsh Jajodia >Priority: Major > Fix For: trunk, 2.1.0 > > Attachments: > 0001-ATLAS-3452-Update-jackson.databind.version-to-2.10.0.patch > > > Atlas uses jackson-databind 2.9.9.1, but there is a patch release, 2.10.0 to > address a CVE vulnerability, to make static code analysis tool happy, we need > to upgrade it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3452) Update jackson.databind.version to 2.10.0 and Guava Version to 28.0-jre
[ https://issues.apache.org/jira/browse/ATLAS-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3452: --- Attachment: (was: 0001-ATLAS-3452-Updating-jackson.databind.version-to-2.10 and Guava Version to 28.0-jre.patch) > Update jackson.databind.version to 2.10.0 and Guava Version to 28.0-jre > --- > > Key: ATLAS-3452 > URL: https://issues.apache.org/jira/browse/ATLAS-3452 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Kalman >Assignee: Aadarsh Jajodia >Priority: Major > Fix For: trunk, 2.1.0 > > Attachments: > 0001-ATLAS-3452-Update-jackson.databind.version-to-2.10.0.patch > > > Atlas uses jackson-databind 2.9.9.1, but there is a patch release, 2.10.0 to > address a CVE vulnerability, to make static code analysis tool happy, we need > to upgrade it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3452) Update jackson.databind.version to 2.10.0 and Guava Version to 28.0-jre
[ https://issues.apache.org/jira/browse/ATLAS-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3452: --- Attachment: 0001-ATLAS-3452-Updating-jackson.databind.version-to-2.10 and Guava Version to 28.0-jre.patch > Update jackson.databind.version to 2.10.0 and Guava Version to 28.0-jre > --- > > Key: ATLAS-3452 > URL: https://issues.apache.org/jira/browse/ATLAS-3452 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Kalman >Assignee: Aadarsh Jajodia >Priority: Major > Fix For: trunk, 2.1.0 > > Attachments: > 0001-ATLAS-3452-Updating-jackson.databind.version-to-2.10 and Guava Version > to 28.0-jre.patch > > > Atlas uses jackson-databind 2.9.9.1, but there is a patch release, 2.10.0 to > address a CVE vulnerability, to make static code analysis tool happy, we need > to upgrade it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3452) Update jackson.databind.version to 2.10.0 and Guava Version to 28.0-jre
[ https://issues.apache.org/jira/browse/ATLAS-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3452: --- Attachment: (was: 0001-ATLAS-3452-Updating-jackson.databind.version-to-2.10 and Guava Version to 28.0-jre.patch) > Update jackson.databind.version to 2.10.0 and Guava Version to 28.0-jre > --- > > Key: ATLAS-3452 > URL: https://issues.apache.org/jira/browse/ATLAS-3452 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Kalman >Assignee: Aadarsh Jajodia >Priority: Major > Fix For: trunk, 2.1.0 > > Attachments: > 0001-ATLAS-3452-Updating-jackson.databind.version-to-2.10 and Guava Version > to 28.0-jre.patch > > > Atlas uses jackson-databind 2.9.9.1, but there is a patch release, 2.10.0 to > address a CVE vulnerability, to make static code analysis tool happy, we need > to upgrade it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3452) Update jackson.databind.version to 2.10.0 and Guava Version to 28.0-jre
[ https://issues.apache.org/jira/browse/ATLAS-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3452: --- Attachment: 0001-ATLAS-3452-Updating-jackson.databind.version-to-2.10 and Guava Version to 28.0-jre.patch > Update jackson.databind.version to 2.10.0 and Guava Version to 28.0-jre > --- > > Key: ATLAS-3452 > URL: https://issues.apache.org/jira/browse/ATLAS-3452 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Kalman >Assignee: Aadarsh Jajodia >Priority: Major > Fix For: trunk > > Attachments: > 0001-ATLAS-3452-Updating-jackson.databind.version-to-2.10 and Guava Version > to 28.0-jre.patch > > > Atlas uses jackson-databind 2.9.9.1, but there is a patch release, 2.10.0 to > address a CVE vulnerability, to make static code analysis tool happy, we need > to upgrade it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3452) Update jackson.databind.version to 2.10.0 and Guava Version to 28.0-jre
[ https://issues.apache.org/jira/browse/ATLAS-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3452: --- Summary: Update jackson.databind.version to 2.10.0 and Guava Version to 28.0-jre (was: Update jackson.databind.version to 2.10.0) > Update jackson.databind.version to 2.10.0 and Guava Version to 28.0-jre > --- > > Key: ATLAS-3452 > URL: https://issues.apache.org/jira/browse/ATLAS-3452 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Kalman >Assignee: Aadarsh Jajodia >Priority: Major > Fix For: trunk > > > Atlas uses jackson-databind 2.9.9.1, but there is a patch release, 2.10.0 to > address a CVE vulnerability, to make static code analysis tool happy, we need > to upgrade it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3452) Update jackson.databind.version to 2.10.0
[ https://issues.apache.org/jira/browse/ATLAS-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia reassigned ATLAS-3452: -- Assignee: Aadarsh Jajodia > Update jackson.databind.version to 2.10.0 > - > > Key: ATLAS-3452 > URL: https://issues.apache.org/jira/browse/ATLAS-3452 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Kalman >Assignee: Aadarsh Jajodia >Priority: Major > Fix For: trunk > > > Atlas uses jackson-databind 2.9.9.1, but there is a patch release, 2.10.0 to > address a CVE vulnerability, to make static code analysis tool happy, we need > to upgrade it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3494) Build failure in branch-2.0
[ https://issues.apache.org/jira/browse/ATLAS-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3494: --- Attachment: 0001-ATLAS-3494-Fixing-build-failure-in-branch-2.0.patch > Build failure in branch-2.0 > --- > > Key: ATLAS-3494 > URL: https://issues.apache.org/jira/browse/ATLAS-3494 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.1.0 >Reporter: Aadarsh Jajodia >Assignee: Aadarsh Jajodia >Priority: Major > Attachments: 0001-ATLAS-3494-Fixing-build-failure-in-branch-2.0.patch > > > Incorrect version number in these pom files > * tools/atlas-index-repair/pom.xml, tools/classification-updater/pom.xml > * tools/classification-updater/pom.xml > is causing the build to fail on branch-2.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3494) Build failure in branch-2.0
[ https://issues.apache.org/jira/browse/ATLAS-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia reassigned ATLAS-3494: -- Assignee: Aadarsh Jajodia > Build failure in branch-2.0 > --- > > Key: ATLAS-3494 > URL: https://issues.apache.org/jira/browse/ATLAS-3494 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.1.0 >Reporter: Aadarsh Jajodia >Assignee: Aadarsh Jajodia >Priority: Major > > Incorrect version number in thse pom file > fortools/atlas-index-repair/pom.xml, tools/classification-updater/pom.xml -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3494) Build failure in branch-2.0
[ https://issues.apache.org/jira/browse/ATLAS-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3494: --- Description: Incorrect version number in these pom files * tools/atlas-index-repair/pom.xml, tools/classification-updater/pom.xml * tools/classification-updater/pom.xml is causing the build to fail on branch-2.0 was:Incorrect version number in thse pom file fortools/atlas-index-repair/pom.xml, tools/classification-updater/pom.xml > Build failure in branch-2.0 > --- > > Key: ATLAS-3494 > URL: https://issues.apache.org/jira/browse/ATLAS-3494 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.1.0 >Reporter: Aadarsh Jajodia >Assignee: Aadarsh Jajodia >Priority: Major > > Incorrect version number in these pom files > * tools/atlas-index-repair/pom.xml, tools/classification-updater/pom.xml > * tools/classification-updater/pom.xml > is causing the build to fail on branch-2.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3494) Build failure in branch-2.0
[ https://issues.apache.org/jira/browse/ATLAS-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3494: --- Description: Incorrect version number in thse pom file fortools/atlas-index-repair/pom.xml, tools/classification-updater/pom.xml > Build failure in branch-2.0 > --- > > Key: ATLAS-3494 > URL: https://issues.apache.org/jira/browse/ATLAS-3494 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.1.0 >Reporter: Aadarsh Jajodia >Priority: Major > > Incorrect version number in thse pom file > fortools/atlas-index-repair/pom.xml, tools/classification-updater/pom.xml -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3494) Build failure in branch-2.0
Aadarsh Jajodia created ATLAS-3494: -- Summary: Build failure in branch-2.0 Key: ATLAS-3494 URL: https://issues.apache.org/jira/browse/ATLAS-3494 Project: Atlas Issue Type: Bug Affects Versions: 2.1.0 Reporter: Aadarsh Jajodia -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3486) Define Data Models For Namespaces and Namespace Attributes in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3486: --- Description: This change defines the data models needed for namespace definition and namespace attribute definitions > Define Data Models For Namespaces and Namespace Attributes in Atlas > --- > > Key: ATLAS-3486 > URL: https://issues.apache.org/jira/browse/ATLAS-3486 > Project: Atlas > Issue Type: Sub-task >Reporter: Aadarsh Jajodia >Assignee: Aadarsh Jajodia >Priority: Major > > This change defines the data models needed for namespace definition and > namespace attribute definitions -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3486) Define Data Models For Namespaces and Namespace Attributes in Atlas
Aadarsh Jajodia created ATLAS-3486: -- Summary: Define Data Models For Namespaces and Namespace Attributes in Atlas Key: ATLAS-3486 URL: https://issues.apache.org/jira/browse/ATLAS-3486 Project: Atlas Issue Type: Sub-task Reporter: Aadarsh Jajodia Assignee: Aadarsh Jajodia -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3485) Introducing attribute namespaces In Atlas(Managed Metadata)
Aadarsh Jajodia created ATLAS-3485: -- Summary: Introducing attribute namespaces In Atlas(Managed Metadata) Key: ATLAS-3485 URL: https://issues.apache.org/jira/browse/ATLAS-3485 Project: Atlas Issue Type: New Feature Reporter: Aadarsh Jajodia Assignee: Aadarsh Jajodia As a data steward I would like to be able to add additional custom attributes to existing types and set their values on existing entities for the following use case: I want to be able to add organizationally relevant 'sanctioned and curated' master data: extend my enterprise data model with attributes that have specific meaning for my business and a domain of values that I can define and enforce. For e.g. I can augment technical metadata with business level master data such as setting my lines of business with an enumerated list of values such as Commercial, Personal Banking, Retail banking, Small Business Banking, Global Wealth management. Implementation considerations: * Freeform key-value pairs * Managed data attributes with specific domain of values and enforcement. * Be able to associate additional attributes (name/value pairs) with existing entities * Both UI based addition/management of properties but also an API bridge or scripts/utility for setting/updating such custom properties in bulk (for bootstrapping or periodic updates) across multiple entities need to be supported -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3336) Propagating Dynamic Attribute changes
[
https://issues.apache.org/jira/browse/ATLAS-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aadarsh Jajodia updated ATLAS-3336:
---
Description:
attr1
attr2 - \{attr1}_name
attr3 : \{attr2}_value
Here attr2 and attr3 are dynamic attributes
The order in which these should be computed is
# attr2
# attr3
The reason is attr3 is dependent on attr2
The same propagation logic should hold when we change a database name
table - \{db.name}..
column - \{table.db.name}.\{table.name}
Here table's qualifiedName should be updated first and then the column's name
was:
attr1
attr2 - \{attr1}_name
attr3 : \{attr2}_value
Here attr2 and attr3 are dynamic attributes
The order in which these should be computed is that first attr2 and then attr3.
The same propagation logic should hold when we change a database name
table - \{db.name}..
column - \{table.db.name}.\{table.name}
Here table's qualifiedName should be updated first and then the column's name
> Propagating Dynamic Attribute changes
> -
>
> Key: ATLAS-3336
> URL: https://issues.apache.org/jira/browse/ATLAS-3336
> Project: Atlas
> Issue Type: Bug
>Reporter: Aadarsh Jajodia
>Assignee: Merryle Wang
>Priority: Major
>
> attr1
> attr2 - \{attr1}_name
> attr3 : \{attr2}_value
>
> Here attr2 and attr3 are dynamic attributes
> The order in which these should be computed is
> # attr2
> # attr3
> The reason is attr3 is dependent on attr2
>
> The same propagation logic should hold when we change a database name
> table - \{db.name}..
> column - \{table.db.name}.\{table.name}
>
> Here table's qualifiedName should be updated first and then the column's name
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (ATLAS-3336) Propagating Dynamic Attribute changes
Aadarsh Jajodia created ATLAS-3336:
--
Summary: Propagating Dynamic Attribute changes
Key: ATLAS-3336
URL: https://issues.apache.org/jira/browse/ATLAS-3336
Project: Atlas
Issue Type: Bug
Reporter: Aadarsh Jajodia
Assignee: Merryle Wang
attr1
attr2 - \{attr1}_name
attr3 : \{attr2}_value
Here attr2 and attr3 are dynamic attributes
The order in which these should be computed is that first attr2 and then attr3.
The same propagation logic should hold when we change a database name
table - \{db.name}..
column - \{table.db.name}.\{table.name}
Here table's qualifiedName should be updated first and then the column's name
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (ATLAS-3289) Add a configuration to population dynamic attributes. If the config is disabled, read the value from the Hook
Aadarsh Jajodia created ATLAS-3289: -- Summary: Add a configuration to population dynamic attributes. If the config is disabled, read the value from the Hook Key: ATLAS-3289 URL: https://issues.apache.org/jira/browse/ATLAS-3289 Project: Atlas Issue Type: Sub-task Reporter: Aadarsh Jajodia -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3288) Implement the DynamicAttributesEvaluator method
Aadarsh Jajodia created ATLAS-3288: -- Summary: Implement the DynamicAttributesEvaluator method Key: ATLAS-3288 URL: https://issues.apache.org/jira/browse/ATLAS-3288 Project: Atlas Issue Type: Sub-task Reporter: Aadarsh Jajodia -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3286) Populate the dynamic attribute flag for each AtlasAttribute in each AltasEntityType along with attributes which might trigger re evaluation of Dynamic Attributes
[ https://issues.apache.org/jira/browse/ATLAS-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3286: --- Description: We aim to implement the following methods in this Jira AtlasAttributes isDynAttribute() - An example of this is qualifiedName for hive_db isDynAttributeEvalTrigger() - An example of this is clusterName for hive_db For AtlasEntityTypes - getDynEvalAttributes() was: We aim to implement the following methods in this Jira AtlasAttributes isDynAttribute() - An example of this is qualifiedName for hive_db isDynAttributeEvalTrigger() - An example of this is clusterName for hive_db For AtlasEntityTypes - getDynEvalAttributes() dynValueEval(AtlasEntity entity) - Takes in the entity instance and evaluates the dynamic attributes for that entity > Populate the dynamic attribute flag for each AtlasAttribute in each > AltasEntityType along with attributes which might trigger re evaluation of > Dynamic Attributes > - > > Key: ATLAS-3286 > URL: https://issues.apache.org/jira/browse/ATLAS-3286 > Project: Atlas > Issue Type: Sub-task >Reporter: Aadarsh Jajodia >Assignee: Merryle Wang >Priority: Major > Original Estimate: 168h > Remaining Estimate: 168h > > We aim to implement the following methods in this Jira > AtlasAttributes > isDynAttribute() - An example of this is qualifiedName for hive_db > isDynAttributeEvalTrigger() - An example of this is clusterName for hive_db > For AtlasEntityTypes - > getDynEvalAttributes() -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3287) Populate Dynamic Relationship Attributes
Aadarsh Jajodia created ATLAS-3287: -- Summary: Populate Dynamic Relationship Attributes Key: ATLAS-3287 URL: https://issues.apache.org/jira/browse/ATLAS-3287 Project: Atlas Issue Type: Sub-task Reporter: Aadarsh Jajodia -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3286) Populate the dynamic attribute flag for each AtlasAttribute in each AltasEntityType along with attributes which might trigger re evaluation of Dynamic Attributes
[ https://issues.apache.org/jira/browse/ATLAS-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3286: --- Description: We aim to implement the following methods in this Jira AtlasAttributes isDynAttribute() - An example of this is qualifiedName for hive_db isDynAttributeEvalTrigger() - An example of this is clusterName for hive_db For AtlasEntityTypes - getDynEvalAttributes() dynValueEval(AtlasEntity entity) - Takes in the entity instance and evaluates the dynamic attributes for that entity was: We aim to implement the following methods in this Jira isDynAttribute() - An example of this is qualifiedName for hive_db isDynAttributeEvalTrigger() - An example of this is clusterName for hive_db > Populate the dynamic attribute flag for each AtlasAttribute in each > AltasEntityType along with attributes which might trigger re evaluation of > Dynamic Attributes > - > > Key: ATLAS-3286 > URL: https://issues.apache.org/jira/browse/ATLAS-3286 > Project: Atlas > Issue Type: Sub-task >Reporter: Aadarsh Jajodia >Assignee: Merryle Wang >Priority: Major > Original Estimate: 168h > Remaining Estimate: 168h > > We aim to implement the following methods in this Jira > AtlasAttributes > isDynAttribute() - An example of this is qualifiedName for hive_db > isDynAttributeEvalTrigger() - An example of this is clusterName for hive_db > For AtlasEntityTypes - > getDynEvalAttributes() > dynValueEval(AtlasEntity entity) - Takes in the entity instance and evaluates > the dynamic attributes for that entity -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3286) Populate the dynamic attribute flag for each AtlasAttribute in each AltasEntityType along with attributes which might trigger re evaluation of Dynamic Attributes
[ https://issues.apache.org/jira/browse/ATLAS-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3286: --- Description: We aim to implement the following methods in this Jira isDynAttribute() - An example of this is qualifiedName for hive_db isDynAttributeEvalTrigger() - An example of this is clusterName for hive_db > Populate the dynamic attribute flag for each AtlasAttribute in each > AltasEntityType along with attributes which might trigger re evaluation of > Dynamic Attributes > - > > Key: ATLAS-3286 > URL: https://issues.apache.org/jira/browse/ATLAS-3286 > Project: Atlas > Issue Type: Sub-task >Reporter: Aadarsh Jajodia >Priority: Major > > We aim to implement the following methods in this Jira > isDynAttribute() - An example of this is qualifiedName for hive_db > isDynAttributeEvalTrigger() - An example of this is clusterName for hive_db -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3286) Populate the dynamic attribute flag for each AtlasAttribute in each AltasEntityType along with attributes which might trigger re evaluation of Dynamic Attributes
[ https://issues.apache.org/jira/browse/ATLAS-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3286: --- Summary: Populate the dynamic attribute flag for each AtlasAttribute in each AltasEntityType along with attributes which might trigger re evaluation of Dynamic Attributes (was: Populate the dynamic attribute flag for each AtlasAttribute in each AltasEntityType) > Populate the dynamic attribute flag for each AtlasAttribute in each > AltasEntityType along with attributes which might trigger re evaluation of > Dynamic Attributes > - > > Key: ATLAS-3286 > URL: https://issues.apache.org/jira/browse/ATLAS-3286 > Project: Atlas > Issue Type: Sub-task >Reporter: Aadarsh Jajodia >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3286) Populate the dynamic attribute flag for each AtlasAttribute in each AltasEntityType
Aadarsh Jajodia created ATLAS-3286: -- Summary: Populate the dynamic attribute flag for each AtlasAttribute in each AltasEntityType Key: ATLAS-3286 URL: https://issues.apache.org/jira/browse/ATLAS-3286 Project: Atlas Issue Type: Sub-task Reporter: Aadarsh Jajodia -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3285) Defining the template version for QualifiedName in the models file for hive entity types
[
https://issues.apache.org/jira/browse/ATLAS-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aadarsh Jajodia updated ATLAS-3285:
---
Description:
An example of a Dynamic Attribute for a Hive Column looks something like this
in the hive models file
{code:java}
"options": {
"dynAttribute:qualifiedName":
"{table.db.name}.{table.name}.{name}@{table.db.clusterName}"
}
{code}
was:
An example of a Dynamic Attribute for a Hive Column something like this
{code:java}
"options": {
"dynAttribute:qualifiedName":
"{table.db.name}.{table.name}.{name}@{table.db.clusterName}"
}
{code}
> Defining the template version for QualifiedName in the models file for hive
> entity types
>
>
> Key: ATLAS-3285
> URL: https://issues.apache.org/jira/browse/ATLAS-3285
> Project: Atlas
> Issue Type: Sub-task
>Reporter: Aadarsh Jajodia
>Assignee: Merryle Wang
>Priority: Major
>
> An example of a Dynamic Attribute for a Hive Column looks something like this
> in the hive models file
> {code:java}
> "options": {
> "dynAttribute:qualifiedName":
> "{table.db.name}.{table.name}.{name}@{table.db.clusterName}"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-3285) Defining the template version for QualifiedName in the models file for hive entity types
[
https://issues.apache.org/jira/browse/ATLAS-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aadarsh Jajodia updated ATLAS-3285:
---
Description:
An example of a Dynamic Attribute for a Hive Column something like this
{code:java}
"options": {
"dynAttribute:qualifiedName":
"{table.db.name}.{table.name}.{name}@{table.db.clusterName}"
}
{code}
> Defining the template version for QualifiedName in the models file for hive
> entity types
>
>
> Key: ATLAS-3285
> URL: https://issues.apache.org/jira/browse/ATLAS-3285
> Project: Atlas
> Issue Type: Sub-task
>Reporter: Aadarsh Jajodia
>Assignee: Merryle Wang
>Priority: Major
>
> An example of a Dynamic Attribute for a Hive Column something like this
> {code:java}
> "options": {
> "dynAttribute:qualifiedName":
> "{table.db.name}.{table.name}.{name}@{table.db.clusterName}"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ATLAS-3285) Defining the template version for QualifiedName in the models file for hive entity types
Aadarsh Jajodia created ATLAS-3285: -- Summary: Defining the template version for QualifiedName in the models file for hive entity types Key: ATLAS-3285 URL: https://issues.apache.org/jira/browse/ATLAS-3285 Project: Atlas Issue Type: Sub-task Reporter: Aadarsh Jajodia -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3284) Adding functionality to compute dynamic attributes for an entity.
Aadarsh Jajodia created ATLAS-3284: -- Summary: Adding functionality to compute dynamic attributes for an entity. Key: ATLAS-3284 URL: https://issues.apache.org/jira/browse/ATLAS-3284 Project: Atlas Issue Type: New Feature Reporter: Aadarsh Jajodia This task aims at computing dynamic attributes for an entity. The first one we are going to take up in qualifiedName -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3130) Atlas stops reporting CTAS tables once an invalid relationshipDef is created
[
https://issues.apache.org/jira/browse/ATLAS-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851328#comment-16851328
]
Aadarsh Jajodia commented on ATLAS-3130:
[~umesh.padashetty] could you give us the steps to reproduce this?
[~merrylewang] tried to reproduce this but he could not.
> Atlas stops reporting CTAS tables once an invalid relationshipDef is created
> -
>
> Key: ATLAS-3130
> URL: https://issues.apache.org/jira/browse/ATLAS-3130
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Umesh Padashetty
>Priority: Minor
>
> Created an invalid relationshipDef with the following body
> {code:java}
> {
> "relationshipDefs": [{
> "propagateTags": "ONE_TO_TWO",
> "description": "default relationshipDef description with name:
> sample_dcef_KcFcR3xIN",
> "relationshipCategory": "ASSOCIATION",
> "typeVersion": "1.0",
> "attributeDefs": [],
> "endDef2": {
> "name": "inputs",
> "isLegacyAttribute": false,
> "isContainer": false,
> "cardinality": "SINGLE",
> "type": "Process",
> "description": "default relationshipEndDef description with name: inputs"
> },
> "endDef1": {
> "name": "hive_table_to_process",
> "isLegacyAttribute": false,
> "isContainer": false,
> "cardinality": "SET",
> "type": "hive_table",
> "description": "default relationshipEndDef description with name:
> hive_table_to_process"
> },
> "guid": "-302256315524233986",
> "name": "sample_dcef_KcFcR3xIN"
> }]
> }{code}
> After this, all the CTAS queries start failing with the following error
> {code:java}
> 2019-04-09 17:47:38,992 ERROR - [NotificationHookConsumer thread-0:] ~ graph
> rollback due to exception (GraphTransactionInterceptor:154)
> org.apache.atlas.exception.AtlasBaseException: invalid relationshipDef:
> sample_dcef_KcFcR3xIN: end type 1: Process, end type 2:
> hive_column_lineage{code}
> The tables are created in the hive, but they are not reported in Atlas.
> Creation of such an invalid relationshipDef should ideally be blocked.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ATLAS-3235) Change the display name of hive process and hive process execution
Aadarsh Jajodia created ATLAS-3235: -- Summary: Change the display name of hive process and hive process execution Key: ATLAS-3235 URL: https://issues.apache.org/jira/browse/ATLAS-3235 Project: Atlas Issue Type: Improvement Reporter: Aadarsh Jajodia Assignee: Aadarsh Jajodia Currently the display name of a process and a process execution shows the query text. This needs to change because the query text can become too large. Either the qualifiedName or some other text needs to be shown for the display name of these -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2779) Create Hive Metastore Event listener to push table changes to Atlas.
[ https://issues.apache.org/jira/browse/ATLAS-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847785#comment-16847785 ] Aadarsh Jajodia commented on ATLAS-2779: This is duplicate of ATLAS-3148 which is resolved. Hence closing this one > Create Hive Metastore Event listener to push table changes to Atlas. > > > Key: ATLAS-2779 > URL: https://issues.apache.org/jira/browse/ATLAS-2779 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.0.0-alpha >Reporter: Tiffany Nguyen >Priority: Major > Fix For: 1.0.0-alpha > > > Create Hive Metastore Event listener to push table changes to Atlas. This > will help push changes done via SparkSQL which does not go through hivehook > to reflect in Atlas. > Furthermore, this will eliminate the need to set hook on the client side to > capture DDL. For example, using hive CLI (by typing hive at command line) > would require changes in hive-site.xml on the client side to include hook > property (hive.exec.post.hooks). The benefit of no change needed on client > side is amplified in environment where there are hundreds of clients. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-3100) Enhance Full Text Search backend implementation to use SOLR request handler.
[ https://issues.apache.org/jira/browse/ATLAS-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841746#comment-16841746 ] Aadarsh Jajodia edited comment on ATLAS-3100 at 5/16/19 10:02 PM: -- Guidelines followed for adding Search Weight * 10: name, displayName, fullName, topic * 9: description, comment, userName, owner, queryText, owners, doc * 8: clusterName, namespace, hostName, uri, contactInfo, pipelines, avroclass, namespace, domain, region subdomain * 5: for all other searchable attributes was (Author: django): Guidelines followed for adding Search Weight * 10: name, displayName, fullName, topic * 9: description, comment, userName, owner, queryText * 8: clusterName, namespace, hostName, uri, contactInfo * 5: for all other searchable attributes > Enhance Full Text Search backend implementation to use SOLR request handler. > > > Key: ATLAS-3100 > URL: https://issues.apache.org/jira/browse/ATLAS-3100 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.1.0 >Reporter: Sridhar >Assignee: Sridhar >Priority: Major > Attachments: Atlas Improvements--Support for Free text search, > Auto-Suggestion and Faceting..pdf > > > For full text search, Atlas is using separate collection with name > "Full-Text-Search" for text searches. This collection maintains index on a > Full Text string that is created using all the attributes of the Entity. This > improvement will try to eliminate the need to maintain this collection and > use SOLR search more efficiently. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3100) Enhance Full Text Search backend implementation to use SOLR request handler.
[ https://issues.apache.org/jira/browse/ATLAS-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841746#comment-16841746 ] Aadarsh Jajodia commented on ATLAS-3100: Guidelines followed for adding Search Weight * 10: name, displayName, fullName, topic * 9: description, comment, userName, owner, queryText * 8: clusterName, namespace, hostName, uri, contactInfo * 5: for all other searchable attributes > Enhance Full Text Search backend implementation to use SOLR request handler. > > > Key: ATLAS-3100 > URL: https://issues.apache.org/jira/browse/ATLAS-3100 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.1.0 >Reporter: Sridhar >Assignee: Sridhar >Priority: Major > Attachments: Atlas Improvements--Support for Free text search, > Auto-Suggestion and Faceting..pdf > > > For full text search, Atlas is using separate collection with name > "Full-Text-Search" for text searches. This collection maintains index on a > Full Text string that is created using all the attributes of the Entity. This > improvement will try to eliminate the need to maintain this collection and > use SOLR search more efficiently. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3214) Create Spark Models in Atlas to support Spark Lineage
Aadarsh Jajodia created ATLAS-3214: -- Summary: Create Spark Models in Atlas to support Spark Lineage Key: ATLAS-3214 URL: https://issues.apache.org/jira/browse/ATLAS-3214 Project: Atlas Issue Type: New Feature Reporter: Aadarsh Jajodia Assignee: Aadarsh Jajodia -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-3209) Add unit tests to verify no process and process executions are created by HMS Hook
[ https://issues.apache.org/jira/browse/ATLAS-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia reassigned ATLAS-3209: -- Assignee: Aadarsh Jajodia > Add unit tests to verify no process and process executions are created by HMS > Hook > -- > > Key: ATLAS-3209 > URL: https://issues.apache.org/jira/browse/ATLAS-3209 > Project: Atlas > Issue Type: Test >Reporter: Aadarsh Jajodia >Assignee: Aadarsh Jajodia >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3209) Add unit tests to verify no process and process executions are created by HMS Hook
Aadarsh Jajodia created ATLAS-3209: -- Summary: Add unit tests to verify no process and process executions are created by HMS Hook Key: ATLAS-3209 URL: https://issues.apache.org/jira/browse/ATLAS-3209 Project: Atlas Issue Type: Test Reporter: Aadarsh Jajodia -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3133) Capture metadata for different executions of the same process in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3133: --- Attachment: Adding Process Executions In Atlas(Community).pdf > Capture metadata for different executions of the same process in Atlas > -- > > Key: ATLAS-3133 > URL: https://issues.apache.org/jira/browse/ATLAS-3133 > Project: Atlas > Issue Type: New Feature > Components: atlas-core, atlas-webui >Reporter: Srikanth Venkat >Assignee: Aadarsh Jajodia >Priority: Critical > Attachments: > 0001-ATLAS-3133-Adding-support-for-Process-Executions-in-.patch, Adding > Process Executions In Atlas(Community).pdf > > > Background: The current Atlas process metadata model within Atlas does not > track multiple instances of execution of the same process. For example if we > run same DDL (e.g. insert into table A select * from table B, C) multiple > times Atlas does not capture the multiple instances of execution of the same > logical process. > User story: As a compliance admin or data steward, I need to be able to track > multiple executions of the same process or pipeline that were done at > different times and relate them to the logical process so that I can provide > traceability and understand how different instances of my data pipelining > operations performed over time. > Acceptance Criteria: > 1) Every new instance of process execution is captured with the appropriate > metadata for the process along with context (who, what, when) > 2) One can navigate between process and process execution in Atlas UI and > explore relevant metadata > 3) Process nodes in lineage display high level information about number of > process executions associated with a particular process node. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3133) Capture metadata for different executions of the same process in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16825587#comment-16825587 ] Aadarsh Jajodia commented on ATLAS-3133: Here is the review request for the same [https://reviews.apache.org/r/70462/] > Capture metadata for different executions of the same process in Atlas > -- > > Key: ATLAS-3133 > URL: https://issues.apache.org/jira/browse/ATLAS-3133 > Project: Atlas > Issue Type: New Feature > Components: atlas-core, atlas-webui >Reporter: Srikanth Venkat >Assignee: Aadarsh Jajodia >Priority: Critical > Attachments: > 0001-ATLAS-3133-Adding-support-for-Process-Executions-in-.patch > > > Background: The current Atlas process metadata model within Atlas does not > track multiple instances of execution of the same process. For example if we > run same DDL (e.g. insert into table A select * from table B, C) multiple > times Atlas does not capture the multiple instances of execution of the same > logical process. > User story: As a compliance admin or data steward, I need to be able to track > multiple executions of the same process or pipeline that were done at > different times and relate them to the logical process so that I can provide > traceability and understand how different instances of my data pipelining > operations performed over time. > Acceptance Criteria: > 1) Every new instance of process execution is captured with the appropriate > metadata for the process along with context (who, what, when) > 2) One can navigate between process and process execution in Atlas UI and > explore relevant metadata > 3) Process nodes in lineage display high level information about number of > process executions associated with a particular process node. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3133) Capture metadata for different executions of the same process in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3133: --- Attachment: (was: 0001-ATLAS-3133-Adding-support-for-Process-Executions-in-.patch) > Capture metadata for different executions of the same process in Atlas > -- > > Key: ATLAS-3133 > URL: https://issues.apache.org/jira/browse/ATLAS-3133 > Project: Atlas > Issue Type: New Feature > Components: atlas-core, atlas-webui >Reporter: Srikanth Venkat >Assignee: Aadarsh Jajodia >Priority: Critical > Attachments: > 0001-ATLAS-3133-Adding-support-for-Process-Executions-in-.patch > > > Background: The current Atlas process metadata model within Atlas does not > track multiple instances of execution of the same process. For example if we > run same DDL (e.g. insert into table A select * from table B, C) multiple > times Atlas does not capture the multiple instances of execution of the same > logical process. > User story: As a compliance admin or data steward, I need to be able to track > multiple executions of the same process or pipeline that were done at > different times and relate them to the logical process so that I can provide > traceability and understand how different instances of my data pipelining > operations performed over time. > Acceptance Criteria: > 1) Every new instance of process execution is captured with the appropriate > metadata for the process along with context (who, what, when) > 2) One can navigate between process and process execution in Atlas UI and > explore relevant metadata > 3) Process nodes in lineage display high level information about number of > process executions associated with a particular process node. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3133) Capture metadata for different executions of the same process in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3133: --- Attachment: 0001-ATLAS-3133-Adding-support-for-Process-Executions-in-.patch > Capture metadata for different executions of the same process in Atlas > -- > > Key: ATLAS-3133 > URL: https://issues.apache.org/jira/browse/ATLAS-3133 > Project: Atlas > Issue Type: New Feature > Components: atlas-core, atlas-webui >Reporter: Srikanth Venkat >Assignee: Aadarsh Jajodia >Priority: Critical > Attachments: > 0001-ATLAS-3133-Adding-support-for-Process-Executions-in-.patch > > > Background: The current Atlas process metadata model within Atlas does not > track multiple instances of execution of the same process. For example if we > run same DDL (e.g. insert into table A select * from table B, C) multiple > times Atlas does not capture the multiple instances of execution of the same > logical process. > User story: As a compliance admin or data steward, I need to be able to track > multiple executions of the same process or pipeline that were done at > different times and relate them to the logical process so that I can provide > traceability and understand how different instances of my data pipelining > operations performed over time. > Acceptance Criteria: > 1) Every new instance of process execution is captured with the appropriate > metadata for the process along with context (who, what, when) > 2) One can navigate between process and process execution in Atlas UI and > explore relevant metadata > 3) Process nodes in lineage display high level information about number of > process executions associated with a particular process node. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3133) Capture metadata for different executions of the same process in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3133: --- Attachment: (was: 0001-ATLAS-3133-Adding-support-for-Process-Executions-in-.patch) > Capture metadata for different executions of the same process in Atlas > -- > > Key: ATLAS-3133 > URL: https://issues.apache.org/jira/browse/ATLAS-3133 > Project: Atlas > Issue Type: New Feature > Components: atlas-core, atlas-webui >Reporter: Srikanth Venkat >Assignee: Aadarsh Jajodia >Priority: Critical > Attachments: > 0001-ATLAS-3133-Adding-support-for-Process-Executions-in-.patch > > > Background: The current Atlas process metadata model within Atlas does not > track multiple instances of execution of the same process. For example if we > run same DDL (e.g. insert into table A select * from table B, C) multiple > times Atlas does not capture the multiple instances of execution of the same > logical process. > User story: As a compliance admin or data steward, I need to be able to track > multiple executions of the same process or pipeline that were done at > different times and relate them to the logical process so that I can provide > traceability and understand how different instances of my data pipelining > operations performed over time. > Acceptance Criteria: > 1) Every new instance of process execution is captured with the appropriate > metadata for the process along with context (who, what, when) > 2) One can navigate between process and process execution in Atlas UI and > explore relevant metadata > 3) Process nodes in lineage display high level information about number of > process executions associated with a particular process node. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3133) Capture metadata for different executions of the same process in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3133: --- Attachment: (was: 0001-ATLAS-3133-Adding-support-for-Process-Executions-in-.patch) > Capture metadata for different executions of the same process in Atlas > -- > > Key: ATLAS-3133 > URL: https://issues.apache.org/jira/browse/ATLAS-3133 > Project: Atlas > Issue Type: New Feature > Components: atlas-core, atlas-webui >Reporter: Srikanth Venkat >Assignee: Aadarsh Jajodia >Priority: Critical > Attachments: > 0001-ATLAS-3133-Adding-support-for-Process-Executions-in-.patch > > > Background: The current Atlas process metadata model within Atlas does not > track multiple instances of execution of the same process. For example if we > run same DDL (e.g. insert into table A select * from table B, C) multiple > times Atlas does not capture the multiple instances of execution of the same > logical process. > User story: As a compliance admin or data steward, I need to be able to track > multiple executions of the same process or pipeline that were done at > different times and relate them to the logical process so that I can provide > traceability and understand how different instances of my data pipelining > operations performed over time. > Acceptance Criteria: > 1) Every new instance of process execution is captured with the appropriate > metadata for the process along with context (who, what, when) > 2) One can navigate between process and process execution in Atlas UI and > explore relevant metadata > 3) Process nodes in lineage display high level information about number of > process executions associated with a particular process node. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3133) Capture metadata for different executions of the same process in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16823535#comment-16823535 ] Aadarsh Jajodia commented on ATLAS-3133: Updated Latest Patch > Capture metadata for different executions of the same process in Atlas > -- > > Key: ATLAS-3133 > URL: https://issues.apache.org/jira/browse/ATLAS-3133 > Project: Atlas > Issue Type: New Feature > Components: atlas-core, atlas-webui >Reporter: Srikanth Venkat >Assignee: Aadarsh Jajodia >Priority: Critical > Attachments: > 0001-ATLAS-3133-Adding-support-for-Process-Executions-in-.patch, > 0001-ATLAS-3133-Adding-support-for-Process-Executions-in-.patch > > > Background: The current Atlas process metadata model within Atlas does not > track multiple instances of execution of the same process. For example if we > run same DDL (e.g. insert into table A select * from table B, C) multiple > times Atlas does not capture the multiple instances of execution of the same > logical process. > User story: As a compliance admin or data steward, I need to be able to track > multiple executions of the same process or pipeline that were done at > different times and relate them to the logical process so that I can provide > traceability and understand how different instances of my data pipelining > operations performed over time. > Acceptance Criteria: > 1) Every new instance of process execution is captured with the appropriate > metadata for the process along with context (who, what, when) > 2) One can navigate between process and process execution in Atlas UI and > explore relevant metadata > 3) Process nodes in lineage display high level information about number of > process executions associated with a particular process node. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3133) Capture metadata for different executions of the same process in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3133: --- Attachment: 0001-ATLAS-3133-Adding-support-for-Process-Executions-in-.patch > Capture metadata for different executions of the same process in Atlas > -- > > Key: ATLAS-3133 > URL: https://issues.apache.org/jira/browse/ATLAS-3133 > Project: Atlas > Issue Type: New Feature > Components: atlas-core, atlas-webui >Reporter: Srikanth Venkat >Assignee: Aadarsh Jajodia >Priority: Critical > Attachments: > 0001-ATLAS-3133-Adding-support-for-Process-Executions-in-.patch, > 0001-ATLAS-3133-Adding-support-for-Process-Executions-in-.patch > > > Background: The current Atlas process metadata model within Atlas does not > track multiple instances of execution of the same process. For example if we > run same DDL (e.g. insert into table A select * from table B, C) multiple > times Atlas does not capture the multiple instances of execution of the same > logical process. > User story: As a compliance admin or data steward, I need to be able to track > multiple executions of the same process or pipeline that were done at > different times and relate them to the logical process so that I can provide > traceability and understand how different instances of my data pipelining > operations performed over time. > Acceptance Criteria: > 1) Every new instance of process execution is captured with the appropriate > metadata for the process along with context (who, what, when) > 2) One can navigate between process and process execution in Atlas UI and > explore relevant metadata > 3) Process nodes in lineage display high level information about number of > process executions associated with a particular process node. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3133) Capture metadata for different executions of the same process in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3133: --- Attachment: (was: 0001-ATLAS-3133-Adding-support-for-Process-Executions-in-.patch) > Capture metadata for different executions of the same process in Atlas > -- > > Key: ATLAS-3133 > URL: https://issues.apache.org/jira/browse/ATLAS-3133 > Project: Atlas > Issue Type: New Feature > Components: atlas-core, atlas-webui >Reporter: Srikanth Venkat >Assignee: Aadarsh Jajodia >Priority: Critical > Attachments: > 0001-ATLAS-3133-Adding-support-for-Process-Executions-in-.patch > > > Background: The current Atlas process metadata model within Atlas does not > track multiple instances of execution of the same process. For example if we > run same DDL (e.g. insert into table A select * from table B, C) multiple > times Atlas does not capture the multiple instances of execution of the same > logical process. > User story: As a compliance admin or data steward, I need to be able to track > multiple executions of the same process or pipeline that were done at > different times and relate them to the logical process so that I can provide > traceability and understand how different instances of my data pipelining > operations performed over time. > Acceptance Criteria: > 1) Every new instance of process execution is captured with the appropriate > metadata for the process along with context (who, what, when) > 2) One can navigate between process and process execution in Atlas UI and > explore relevant metadata > 3) Process nodes in lineage display high level information about number of > process executions associated with a particular process node. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-3133) Capture metadata for different executions of the same process in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia reassigned ATLAS-3133: -- Assignee: Aadarsh Jajodia > Capture metadata for different executions of the same process in Atlas > -- > > Key: ATLAS-3133 > URL: https://issues.apache.org/jira/browse/ATLAS-3133 > Project: Atlas > Issue Type: New Feature > Components: atlas-core, atlas-webui >Reporter: Srikanth Venkat >Assignee: Aadarsh Jajodia >Priority: Critical > > Background: The current Atlas process metadata model within Atlas does not > track multiple instances of execution of the same process. For example if we > run a CTAS command (e.g. insert into table A select * from table B, C) > multiple times Atlas does not capture the multiple instances of execution of > the same logical process. > User story: As a compliance admin or data steward, I need to be able to track > multiple executions of the same process or pipeline that were done at > different times and relate them to the logical process so that I can provide > traceability and understand how different instances of my data pipelining > operations performed over time. > Acceptance Criteria: > 1) Every new instance of process execution is captured with the appropriate > metadata for the process along with context (who, what, when) > 2) One can navigate between process and process execution in Atlas UI and > explore relevant metadata > 3) Process nodes in lineage display high level information about number of > process executions associated with a particular process node. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3041) Cannot delete relationship types using the types/typedef/name REST API
[ https://issues.apache.org/jira/browse/ATLAS-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3041: --- Attachment: (was: ATLAS-3041.patch) > Cannot delete relationship types using the types/typedef/name REST API > -- > > Key: ATLAS-3041 > URL: https://issues.apache.org/jira/browse/ATLAS-3041 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Chris Clohosy >Assignee: Aadarsh Jajodia >Priority: Major > Attachments: ATLAS-3041.patch > > Time Spent: 40m > Remaining Estimate: 0h > > It appears that relationship types cannot be deleted by doing a HTTP DELETE > to the types/typedef/name REST API endpoint. Upon further exploration of the > source code (org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore) > the problem seems to lie within the deleteTypeByName method - this calls the > getByName method and from logging we can observe it correctly gets back the > AtlasRelationshipType. However there is no subsequent check for this type > within deleteTypeByName, and as AtlasRelationshipTime extends AtlasStructType > the code then thinks it needs to delete a struct instead of a relationship > and therefore fails. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3041) Cannot delete relationship types using the types/typedef/name REST API
[ https://issues.apache.org/jira/browse/ATLAS-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3041: --- Attachment: ATLAS-3041.patch > Cannot delete relationship types using the types/typedef/name REST API > -- > > Key: ATLAS-3041 > URL: https://issues.apache.org/jira/browse/ATLAS-3041 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Chris Clohosy >Assignee: Aadarsh Jajodia >Priority: Major > Attachments: ATLAS-3041.patch > > Time Spent: 40m > Remaining Estimate: 0h > > It appears that relationship types cannot be deleted by doing a HTTP DELETE > to the types/typedef/name REST API endpoint. Upon further exploration of the > source code (org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore) > the problem seems to lie within the deleteTypeByName method - this calls the > getByName method and from logging we can observe it correctly gets back the > AtlasRelationshipType. However there is no subsequent check for this type > within deleteTypeByName, and as AtlasRelationshipTime extends AtlasStructType > the code then thinks it needs to delete a struct instead of a relationship > and therefore fails. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3041) Cannot delete relationship types using the types/typedef/name REST API
[ https://issues.apache.org/jira/browse/ATLAS-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aadarsh Jajodia updated ATLAS-3041: --- Attachment: ATLAS-3041.patch > Cannot delete relationship types using the types/typedef/name REST API > -- > > Key: ATLAS-3041 > URL: https://issues.apache.org/jira/browse/ATLAS-3041 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Chris Clohosy >Assignee: Aadarsh Jajodia >Priority: Major > Attachments: ATLAS-3041.patch > > Time Spent: 10m > Remaining Estimate: 0h > > It appears that relationship types cannot be deleted by doing a HTTP DELETE > to the types/typedef/name REST API endpoint. Upon further exploration of the > source code (org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore) > the problem seems to lie within the deleteTypeByName method - this calls the > getByName method and from logging we can observe it correctly gets back the > AtlasRelationshipType. However there is no subsequent check for this type > within deleteTypeByName, and as AtlasRelationshipTime extends AtlasStructType > the code then thinks it needs to delete a struct instead of a relationship > and therefore fails. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
