-
Notifications
You must be signed in to change notification settings - Fork 314
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
bug: cannot query lineage if job namespace contains colon character #2806
Comments
Thanks for opening your first issue in the Marquez project! Please be sure to follow the issue template! |
@wslulciuc and I spent a bit of time looking into this one today. The issue is actually related to the job_name that you have since it only has numbers it gets erroneously excluded from our regex processed in our Pattern p = Pattern.compile("(?:" + ID_DELIM + "(?!//|\\d+))");
This is because our regex is trying to exclude a colon following by one or more digits which works to skip over the We're going to change some processing around to handle this case. Thanks for reporting the bug with an example. |
if job namespace is:
{"job": {"namespace": "trino://trino-integration-test:1337" }}
then querying for lineage registered under this namespace results in error:
renaming job namespace to string not containing colon fixes the issue. This should not be the case and is not an issue if dataset name contains such characters.
Suggested fix woule be to base64 encode NodeId parts (and delimit using colon) before sending to api - and decode api-side after splitting by colon.
The text was updated successfully, but these errors were encountered: