-
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
Piped fetch clause failed reporting error on legal input #2545
Comments
kikimo
changed the title
Bug in fetch clause
Piped fetch clause failed report error on legal input
Aug 20, 2021
It's the expected result. We don't allow multiple input in sentence. |
kikimo
changed the title
Piped fetch clause failed report error on legal input
Piped fetch clause failed reporting error on legal input
Aug 20, 2021
I see, fetch support two types of input:
right? @Shylock-Hg |
Yes. |
yixinglu
pushed a commit
to yixinglu/nebula
that referenced
this issue
Sep 14, 2023
…#2545) Co-authored-by: Yichen Wang <18348405+Aiee@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please check the FAQ documentation before raising an issue
Please check the FAQ documentation and old issues before raising an issue in case someone has asked the same question that you are asking.
Describe the bug (must be provided)
A clear and concise description of what the bug is.
Your Environments (must be provided)
v2-nightly
How To Reproduce(must be provided)
Steps to reproduce the behavior:
Expected behavior
Piped fetch clause should yield correct result.
Additional context
Provide logs and configs, or any other context to trace the problem.
The text was updated successfully, but these errors were encountered: