Jan Jansen

https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/commit/bf287978a095372fcda6574a5b6ddfdf43a799ea perhaps.

It would be cool to have a manual fast scaling option for all service as a beginning.

If you can click on the current replica number and than can select a number of instances. For example in this view: 

It should be fixable by a basic check during the insert. For already inserted connections it will be more complicated.

@ammarove I tried to create a test for it, but wasn't able. ```java @Test public void testDeletionOfSchemaProperties(){ mgmt.makePropertyKey("propertyKey").dataType(String.class).cardinality(Cardinality.SINGLE).make(); graph.traversal().addV("vertexLabel").property("propertyKey", "test").next(); mgmt.getPropertyKey("propertyKey").remove(); \\clopen(); graph.traversal().addV("vertexLabel").property("propertyKey", "test").next(); List maps = graph.traversal().V().valueMap().toList(); assertEquals(2, maps.size());...

@mohamad-haddad-tribo The exception from above clear comes from berkeley. I'm sure you did get a berkeley exception in cassandra setup.

Everything is tested against java so we can close this issue.

@porunov Do you want to review it again?

Suffix 000 is for NormalVertex. The suffix are described in the following file: https://github.com/JanusGraph/janusgraph/blob/master/janusgraph-core/src/main/java/org/janusgraph/graphdb/idmanagement/IDManager.java#L35-L55

> In the future, we could probably use some GitHub Action like https://github.com/benchmark-action/github-action-benchmark to auto-detect performance dip. They don't have JMH support yet but there is a PR: https://github.com/benchmark-action/github-action-benchmark/pull/64/files