Suggestions for SHOW STATS

[randomJoe211]

1. SUBMIT JOB STATS and SHOW STATS is a combined workflow, instead of running them separately, why not make them one statement?
2. If a user has never run SUBMIT JOB STATS but tries to run SHOW STATS directly, the error Key not existed is returned. This error message is confusing. Maybe it should say something like "To make statistics of the graph space, run SUBMIT JOB STATS first, and then run SHOW STATS." And if suggestion 1 is adapted, there would be no such issue.
   

[HarrisChu]

for question 1,
SUBMIT JOB STATS statement starts a job that makes the statistics of the CURRENT graph space.
SHOW STATS means show the previous job statistics.

if make them one statement, it would alway start a new job, it's not comfortable for big data.

[randomJoe211]

for question 1,
SUBMIT JOB STATS statement starts a job that makes the statistics of the CURRENT graph space.
SHOW STATS means show the preview job statistics.

if make them one statement, it would alway start a new job, it's not comfortable for big data.

That makes sense. Thank you for the explanation. Then there is only question 2 left.

[panda-sheep]

Good catch, the problem of error message, I will improve it later, thank you

[panda-sheep]

has fixed.

[panda-sheep]

refer to vesoft-inc/nebula#2577