-
Notifications
You must be signed in to change notification settings - Fork 323
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
Unable to check the column lineage and dataset lineage and got below error need some attention #2921
Comments
Thanks for opening your first issue in the Marquez project! Please be sure to follow the issue template! |
Hello, Do you happen to have any logs on the server that indicate what your issue is? |
@phixMe Here I have attached the logs |
@phixMe - need some inside on the below logs! | ERROR [2024-10-14 17:55:05,492] marquez.logging.LoggingMdcFilter: status: 500 |
@phixMe |
Yes, it looks like you have the same issue as: |
@phixMe Yes, is there any solution to fix it! |
This is logistically a complicated thing for us to fix because it is everywhere including our docs and website and promotional materials... Essentially, we are in this difficult position where we cannot parse connection strings and use the I think the only way to rectify this is to change the delimiter character for our notational, but it's a breaking change for all kinds of users. |
I put together a branch of what this would look like on the api server. it would need to be done on the clients as well of course, and maybe others would prefer a different delimiter. |
@phixMe tried with the above branch which you mentioned: could you please provide me sample for the node id with delimeter, as I tried end up with below error ERROR [2024-10-17 15:16:52,766] io.dropwizard.jersey.errors.LoggingExceptionMapper: Error handling a request: 11abd68c1ed35ebb Requesting Url format : |
Yes, the UI would also need an update... I think the easiest way for you to get around this is to intercept the OpenLineage events and prepend a string to the job names, or rename the jobs that you are testing with to not have this property. I don't think we can realistically merge anything here without quite a bit of forethought and communication, so that's probably the best I can recommend for now. |
Read from oracle : oracle://oracledb.cydlut9zgajr.us-east-1.rds.amazonaws.com:1521
The text was updated successfully, but these errors were encountered: