-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Wrong error msg of matching on vertex properties #3492
Comments
It's expected.
There is a vertex filter |
See the case nebula/tests/tck/features/match/Base.feature Line 601 in e6ddeb2
|
@Shylock-Hg Thanks for the reply. Yes, from the code's point of view, your answer may be logical. But such an answer cannot resolve the real issue, which is that the error code does not help uses to solve the problem. Suppose you were a user, and after running a query you saw such an error code, wouldn't you modify the query according to the hint, add |
This is what you expected ???? ARE YOU SURE ??? |
The query like |
It's OK if Nebula Graph does not support The problem here is, running Again, it is OK if Nebula Graph does not support such a feature, but it cannot mislead users with such a wrong return. This is the real concern. BTW, it is not related to any specific PR. I'm not saying that a certain PR created such an issue. I just hope that this issue can be resolved. For example: Running |
In this case, we have two error:
But in implementation, these two cases will be checked in same process. We could change error message to more friendly to user, but can't provide two error message. |
What message do you plan to code? |
If want to provide two error message
Do you have suggestion? |
If we can have two different messages for the two situations, then they may be But if you wish to explain the two situations in one message, maybe |
This error is not just for scan vertices and with properties, how about |
You decide. |
Please check the FAQ documentation before raising an issue
Been there.
Describe the bug (required)
When executing
MATCH (v{name: "Tim Duncan"}) return v
, it shows[ERROR (-1005)]: Scan vertices must specify limit number
.If I add LIMIT, it still tells me the same thing.
The error message is wrong. If matching on vertex properties is not supported, then the error message should tell me this, not a wrong reason.
Plus I have the following tag indexes:
Your Environments (required)
The text was updated successfully, but these errors were encountered: