[jira] [Updated] (ATLAS-1122) Change trait edge labels to have trait name alone
[
https://issues.apache.org/jira/browse/ATLAS-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-1122:
Fix Version/s: 0.7.1-incubating
Committed in 0.7-incubating branch:
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/dea202ca
> Change trait edge labels to have trait name alone
> -
>
> Key: ATLAS-1122
> URL: https://issues.apache.org/jira/browse/ATLAS-1122
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1122.2.patch, ATLAS-1122.patch
>
>
> Currently when traits are added to classes they are added with
> {{typeName.traitName}} and this is causing edge label creation to fail when
> concurrent threads are running transactions. Event though adding retries
> mitigates the issue to some extent in ATLAS-1119 and lets the transactions
> succeed, there is lesser chance of them failing with edge label creation due
> to concurrent transactions with the proposed change since this is a one time
> operation that is done once per trait when it is added the first time to any
> entity. Also this could potentially be moved to type creation phase when the
> trait is created.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1122) Change trait edge labels to have trait name alone
[
https://issues.apache.org/jira/browse/ATLAS-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-1122:
---
Attachment: ATLAS-1122.2.patch
Have fixed the test. +1 for the patch
> Change trait edge labels to have trait name alone
> -
>
> Key: ATLAS-1122
> URL: https://issues.apache.org/jira/browse/ATLAS-1122
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1122.2.patch, ATLAS-1122.patch
>
>
> Currently when traits are added to classes they are added with
> {{typeName.traitName}} and this is causing edge label creation to fail when
> concurrent threads are running transactions. Event though adding retries
> mitigates the issue to some extent in ATLAS-1119 and lets the transactions
> succeed, there is lesser chance of them failing with edge label creation due
> to concurrent transactions with the proposed change since this is a one time
> operation that is done once per trait when it is added the first time to any
> entity. Also this could potentially be moved to type creation phase when the
> trait is created.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1122) Change trait edge labels to have trait name alone
[
https://issues.apache.org/jira/browse/ATLAS-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-1122:
---
Description: Currently when traits are added to classes they are added with
{{typeName.traitName}} and this is causing edge label creation to fail when
concurrent threads are running transactions. Event though adding retries
mitigates the issue to some extent in ATLAS-1119 and lets the transactions
succeed, there is lesser chance of them failing with edge label creation due to
concurrent transactions with the proposed change since this is a one time
operation that is done once per trait when it is added the first time to any
entity. Also this could potentially be moved to type creation phase when the
trait is created. (was: Currently when traits are added to classes they are
added with {typeName}.{traitName} and this is causing edge label creation to
fail when concurrent threads are running transactions. Event though adding
retries mitigates the issue to some extent in ATLAS-1119 and lets the
transactions succeed, there is lesser chance of them failing with edge label
creation due to concurrent transactions with the proposed change since this is
a one time operation that is done once per trait when it is added the first
time to any entity. Also this could potentially be moved to type creation phase
when the trait is created.)
> Change trait edge labels to have trait name alone
> -
>
> Key: ATLAS-1122
> URL: https://issues.apache.org/jira/browse/ATLAS-1122
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1122.patch
>
>
> Currently when traits are added to classes they are added with
> {{typeName.traitName}} and this is causing edge label creation to fail when
> concurrent threads are running transactions. Event though adding retries
> mitigates the issue to some extent in ATLAS-1119 and lets the transactions
> succeed, there is lesser chance of them failing with edge label creation due
> to concurrent transactions with the proposed change since this is a one time
> operation that is done once per trait when it is added the first time to any
> entity. Also this could potentially be moved to type creation phase when the
> trait is created.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1122) Change trait edge labels to have trait name alone
[
https://issues.apache.org/jira/browse/ATLAS-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suma Shivaprasad updated ATLAS-1122:
Description: Currently when traits are added to classes they are added with
{typeName}.{traitName} and this is causing edge label creation to fail when
concurrent threads are running transactions. Event though adding retries
mitigates the issue to some extent in ATLAS-1119 and lets the transactions
succeed, there is lesser chance of them failing with edge label creation due to
concurrent transactions with the proposed change since this is a one time
operation that is done once per trait when it is added the first time to any
entity. Also this could potentially be moved to type creation phase when the
trait is created. (was: Currently when traits are added to classes they are
added with {typeName}.{traitName} and this is causing edge label creation to
fail when concurrent threads are running transactions. Event though adding
retries mitigates the issue to some extent in ATLAS-1119 and lets the
transactions succeed, there is lesser chance of them failing with edge label
creation due to concurrent transactions. Also this could potentially be moved
to type creation phase when the trait is created.)
> Change trait edge labels to have trait name alone
> -
>
> Key: ATLAS-1122
> URL: https://issues.apache.org/jira/browse/ATLAS-1122
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1122.patch
>
>
> Currently when traits are added to classes they are added with
> {typeName}.{traitName} and this is causing edge label creation to fail when
> concurrent threads are running transactions. Event though adding retries
> mitigates the issue to some extent in ATLAS-1119 and lets the transactions
> succeed, there is lesser chance of them failing with edge label creation due
> to concurrent transactions with the proposed change since this is a one time
> operation that is done once per trait when it is added the first time to any
> entity. Also this could potentially be moved to type creation phase when the
> trait is created.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1122) Change trait edge labels to have trait name alone
[
https://issues.apache.org/jira/browse/ATLAS-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suma Shivaprasad updated ATLAS-1122:
Description: Currently when traits are added to classes they are added with
{typeName}.{traitName} and this is causing edge label creation to fail when
concurrent threads are running transactions. Event though adding retries
mitigates the issue to some extent in ATLAS-1119 and lets the transactions
succeed, there is lesser chance of them failing with edge label creation due to
concurrent transactions. Also this could potentially be moved to type creation
phase when the trait is created. (was: Currently when traits are added to
classes they are added with {typeName}.{traitName} and this is causing edge
label creation to fail when concurrent threads are running transactions. Event
though adding retries mitigates the issue to some extent and lets the
tranasactions succeed, there is lesser chance of them failing with edge label
creation due to concurrent transactions. Also this could potentially be moved
to type creation phase when the trait is created.)
> Change trait edge labels to have trait name alone
> -
>
> Key: ATLAS-1122
> URL: https://issues.apache.org/jira/browse/ATLAS-1122
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1122.patch
>
>
> Currently when traits are added to classes they are added with
> {typeName}.{traitName} and this is causing edge label creation to fail when
> concurrent threads are running transactions. Event though adding retries
> mitigates the issue to some extent in ATLAS-1119 and lets the transactions
> succeed, there is lesser chance of them failing with edge label creation due
> to concurrent transactions. Also this could potentially be moved to type
> creation phase when the trait is created.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1122) Change trait edge labels to have trait name alone
[
https://issues.apache.org/jira/browse/ATLAS-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suma Shivaprasad updated ATLAS-1122:
Attachment: ATLAS-1122.patch
> Change trait edge labels to have trait name alone
> -
>
> Key: ATLAS-1122
> URL: https://issues.apache.org/jira/browse/ATLAS-1122
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1122.patch
>
>
> Currently when traits are added to classes they are added with
> {typeName}.{traitName} and this is causing edge label creation to fail when
> concurrent threads are running transactions. Event though adding retries
> mitigates the issue to some extent and lets the tranasactions succeed, there
> is lesser chance of them failing with edge label creation due to concurrent
> transactions. Also this could potentially be moved to type creation phase
> when the trait is created.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
