I deployed the Nebula Graph services with Docker Compose, as described in this article.
When the last command
docker run --rm -ti --network=host vesoft/nebula-console:nightly --addr=127.0.0.1 --port=3699 is run, the connection to the graph service is successful. But I found something weird when I granted a role to a user.
For example, I created a space named
test1 and a user named
user2, and granted the GUEST role to user2 in the test1 space. Then I connected to the graph service by running this command
docker run --rm -ti --network=host vesoft/nebula-console:nightly --addr=127.0.0.1 --port=3699 --u="user2" (The
--u="user2" configuration is from the “Console Configurations”. I hope it is right). When I ran the
SHOW ROLES IN test1 statement, it works - only user2 and its role are shown. But when I run the
CREATE TAG team(name, string) statement, it was supposed to fail, but actually the tag was created. According to the “Built-in Roles” article, a guest must not write schema. So which one is right?