-
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
RETURN timestamp(-1) returns BAD_DATA #2665
Comments
BAD_DATA is confusing. Maybe raise an error and list the supported argument type and range. |
All functions through return BAD_DATA to tell the user the calculation result is wrong. If the type is wrong, it will return an error. |
As @czpmango said, expression::eval() may return StatusOr to report detailed error msg |
Your are right. We will modify the error passing mechanism of the expression later. |
ACK. But it maybe a big change on implementation layer. |
There are so many differences between our time-related function and CYPHER's, some of which in https://github.com/vesoft-inc/nebula-graph/issues/676 |
Raise error in this case that meet the invalid parameter value is not well, some the input come from previous output and it's also get from previous executor so there may contain valid and invalid data together, user can't know is it valid always. |
It is in control, so we suggest to close it. |
As the title states. An error should be a more logical return, right?
The text was updated successfully, but these errors were encountered: