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

job commands and returns are not format and not carefully designed #2669

Closed
whitewum opened this issue Mar 26, 2021 · 0 comments
Closed

job commands and returns are not format and not carefully designed #2669

whitewum opened this issue Mar 26, 2021 · 0 comments
Labels
type/enhancement Type: make the code neat or more efficient

Comments

@whitewum
Copy link
Contributor

The studio display depends on show jobs show job 123 .

So I tried to add some tests to TCK

But. The following are the problems:

Problem 1:

show jobs and show job 67 column displays are different:
image

So clients ( studio and tck-tests) have to parse these two results separately.

Problem 2:

why the returns are different ?

image

Problem 3:

Why does job id start from 2?

I start a new cluster, but the job id sequence looks a bit wired.

Can you guarantee that the job id is in sequence order?

And why I'm try to reference id 2 in TCK tests (nba). It does not exist.

@CPWstatic CPWstatic transferred this issue from vesoft-inc/nebula-graph Aug 28, 2021
@CPWstatic CPWstatic added type/enhancement Type: make the code neat or more efficient type/question Type: question about the product labels Aug 28, 2021
@Sophie-Xie Sophie-Xie removed the type/question Type: question about the product label Aug 30, 2021
@whitewum whitewum closed this as completed Sep 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement Type: make the code neat or more efficient
Projects
None yet
Development

No branches or pull requests

3 participants