[
https://issues.apache.org/jira/browse/ATLAS-5073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18007613#comment-18007613
]
ASF subversion and git services commented on ATLAS-5073:
--------------------------------------------------------
Commit 0c1c390dd94b6aed05b0386f80c43fb5de5d4566 in atlas's branch
refs/heads/master from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=0c1c390dd ]
ATLAS-5073: ensure propertyKey is created before using it (#401)
> Create Janus property keys before using them
> --------------------------------------------
>
> Key: ATLAS-5073
> URL: https://issues.apache.org/jira/browse/ATLAS-5073
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
> Reporter: Madhan Neethiraj
> Assignee: Madhan Neethiraj
> Priority: Major
> Fix For: 3.0.0, 2.5.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Atlas stores entity attributes as graph vertex/edge properties; a
> property-key (describing characteristics like datatype, cardinality) should
> be created before read/write of values in a vertex/edge property. If a
> property-key doesn't exist, JanusGraph will create one on first reference to
> the vertex/edge property. However, JanusGraph recommends explictly creating
> property-keys before using them - see the following at
> [https://docs.janusgraph.org/schema/:|https://docs.janusgraph.org/schema/]
> {noformat}
> It is strongly encouraged to explicitly define all schema elements and to
> disable automatic schema creation by setting schema.default=none in the
> JanusGraph graph configuration.{noformat}
>
> Atlas does create property-keys while loading typedefs; however, this is
> missed in few cases, resulting in such property-keys to be created on first
> reference. This should be fixed to avoid automatic creation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
