-
Notifications
You must be signed in to change notification settings - Fork 11.7k
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
NodeGraph: Fix edges dataframe miscategorization #76842
Conversation
A dataframe named "edges" could end up getting categorized as a nodes dataframe if it was missing a "source" field, resulting in a very confusing error message "id field is required for nodes dataframe" instead of a more sensible error message about the missing source field.
Additionally, I'd like to suggest that "display names" of fields are considered when looking up columns instead of just "source names". |
I wonder if we should be a bit more smart with the categorization. There are few required columns for both the node and edges data frames and maybe we could just check them thoroughly to make sure we don't pass on an invalid data frame. Would you have time to do that? If not we can merge this PR and just leave it for later.
This probably would not work well. The |
That was a quick test I was doing, I don't really have the time to hack on grafana at the moment. SQLPage is keeping me busy. And my day job, also ;)
Yes, that was my problem, and mapping column names in the config would solve it even better 🙂 |
here is the mapping pr btw #76009 Also I think this look good, will wait for the checks to pass and merge this. |
Thanks ! |
A dataframe named "edges" could end up getting categorized as a nodes dataframe if it was missing a "source" field, resulting in a very confusing error message "id field is required for nodes dataframe" instead of a more sensible error message about the missing source field.