RenameClass
Rename one exact node or customer connection category. Requires
objects.update permission. Supply new_class in addition to the selector.
An exact node target is its type and class, for example
{"target":"image","class":"Photos"}.
For a connection, class names the source class, connection class, and
destination class. target supplies the corresponding endpoint types.
{
"class": {"src": "People", "connection": "AppearsIn", "dst": "Photos"},
"target": {"src": "entity", "dst": "image"}
}
Metadata mutations require all five values for a connection. Class names are
nonempty, cannot begin with _, and are matched without case sensitivity.
Index selectors also include property and kind. With GetIndexes and
GetAggregates you can supply only the fields you want to match, such as
{"class":{"connection":"AppearsIn"},"target":{"dst":"image"}}.
The new name must not collide with another category of the same type or connection endpoint pair. Renaming preserves identities, properties, connections, ownership and indexes. Display names and schema cache entries follow the executing transaction; pinned older readers retain their original names.
[{"RenameClass":{"target":"image","class":"Photos","new_class":"Pictures"}}]
Success returns status: 0. Invalid selectors and name collisions fail the
transaction.