Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

show stats report "key not existed" error before submit job stats #2573

Closed
yixinglu opened this issue Aug 25, 2021 · 2 comments · Fixed by #2577
Closed

show stats report "key not existed" error before submit job stats #2573

yixinglu opened this issue Aug 25, 2021 · 2 comments · Fixed by #2577

Comments

@yixinglu
Copy link
Contributor

version: 2.5.0

2021/08/25 17:13:53 [INFO] connection pool is initialized successfully

Welcome to Nebula Graph!

(root@nebula) [(none)]> use nba;
Execution succeeded (time spent 5821/6103 us)

Wed, 25 Aug 2021 17:13:55 CST

(root@nebula) [nba]> show stats
[ERROR (-1005)]: Key not existed!

Wed, 25 Aug 2021 17:14:13 CST

(root@nebula) [nba]> submit job stats
+------------+
| New Job Id |
+------------+
| 35         |
+------------+
Got 1 rows (time spent 6470/6997 us)

Wed, 25 Aug 2021 17:14:55 CST

(root@nebula) [nba]> show stats
+---------+------------+-------+
| Type    | Name       | Count |
+---------+------------+-------+
| "Tag"   | "bachelor" | 1     |
+---------+------------+-------+
| "Tag"   | "player"   | 56    |
+---------+------------+-------+
| "Tag"   | "team"     | 30    |
+---------+------------+-------+
| "Edge"  | "like"     | 81    |
+---------+------------+-------+
| "Edge"  | "serve"    | 152   |
+---------+------------+-------+
| "Edge"  | "teammate" | 10    |
+---------+------------+-------+
| "Space" | "vertices" | 86    |
+---------+------------+-------+
| "Space" | "edges"    | 243   |
+---------+------------+-------+
Got 8 rows (time spent 3744/4352 us)

Wed, 25 Aug 2021 17:14:59 CST
@panda-sheep
Copy link
Contributor

panda-sheep commented Aug 25, 2021

The original case was like this, which was in line with expectations.
Or need to update the error message.

@yixinglu
Copy link
Contributor Author

The original case was like this, which was in line with expectations.
Or need to update the error message.

There is no any stats info to show is better than The key not existed!. please give users a more user-friendly error message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants