[
https://issues.apache.org/jira/browse/ATLAS-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152383#comment-15152383
]
Hemanth Yamijala commented on ATLAS-476:
----------------------------------------
I think you mean the cache update should happen after the update to the backing
stores. I had considered that approach. Two points:
* We need to go to step5. The other 2 steps also do validations that seem
important to me.
* In the current flow, the updated typesystem cache is used by the
{{GraphBackedTypeStore.store}} method. It is possible that what information it
needs is already available via the return value of {{TypeSystem.defineTypes}}.
If that's the case we could use a different overloaded API to update the
backend stores.
Does this make sense?
> Update type attribute with Reserved characters updated the original type as
> unknown
> -----------------------------------------------------------------------------------
>
> Key: ATLAS-476
> URL: https://issues.apache.org/jira/browse/ATLAS-476
> Project: Atlas
> Issue Type: Bug
> Affects Versions: trunk
> Environment: sandbox
> Reporter: Chethana
> Assignee: Hemanth Yamijala
> Priority: Blocker
> Fix For: 0.7-incubating
>
> Attachments: 1.log
>
>
> create a type with required attribute
> try to get this type created - the type data is returned
> try update this type by adding attribute with attribute name consisting of a
> reserved character eg:test$
> this throws exception.
> Now use to get call to get the previously created type
> Expected:
> The type should not be updated.
> Actual:
> "error": "Unknown datatype: className_update_vsvrbzqaqg",
> "stackTrace": "org.apache.atlas.typesystem.exception.TypeNotFoundException:
> Unknown datatype: className_update_vsvrbzqaqg\n\tat
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
