Interactive: using ID rather than names to represent a unique resource in AdminService

[lidongze0629]

Is your feature request related to a problem? Please describe.

As title says, based on the consideration of backward compatibility, for graph-related or procedure-related interfaces, we should use ID instead of name to represent a resource.

{
  "name": "mocking_graph",
  "store_type": "mutable_csr",
  "stored_procedures": {
    "directory": "plugins"
  },
  "schema": {
    "vertex_types": [
      {
        "type_id": 0,
        "type_name": "person",
        "properties": [
          {
            "property_id": 0,
            "property_name": "id",
            "property_type": "DT_STRING"
          },
          {
            "property_id": 1,
            "property_name": "name",
            "property_type": "DT_STRING"
          },
          {
            "property_id": 2,
            "property_name": "age",
            "property_type": "DT_SIGNED_INT32"
          }
        ],
        "primary_keys": [
          [
            "id"
          ]
        ]
      }
    ],
    "edge_types": [
      {
        "type_id": 0,
        "type_name": "knows",
        "vertex_type_pair_relations": [
          {
            "source_vertex": "person",
            "destination_vertex": "person",
            "relation": "MANY_TO_MANY"
          }
        ],
        "properties": [
          {
            "property_id": 0,
            "property_name": "weight",
            "property_type": "DT_DOUBLE"
          }
        ]
      }
    ]
  }
}

[lidongze0629]

/cc @longbinlai @zhanglei1949

[zhanglei1949]

Closed since already implemented.