-
Notifications
You must be signed in to change notification settings - Fork 318
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
Database uses Varchar(64) for connection URIs, which is too short #2120
Comments
Thanks for opening your first issue in the Marquez project! Please be sure to follow the issue template! |
|
Thanks for opening such a detailed issue, @mlecuyer-dna. We did increase the |
I was running it out of the repo cloned at hash df8cc76, which I think should have been merged by then... unless the docker image used by the quick-start script is wrong |
@mlecuyer-dna , could you please check if the newer version of Marquez is not causing this issue? If verified, we can close this off. |
@howardyoo Okay, I'm in the process of testing this. It looks like the docker file is pinned to |
@howardyoo I think this can be closed, as the newer version, while creating additional/new issues, don't seem to be having issues with long fields. Closed. |
Thank you for verifying and closing!
…Sent from my iPhone
On Sep 15, 2022, at 10:43 AM, mlecuyer-dna ***@***.***> wrote:
@howardyoo I think this can be closed, as the newer version, while creating additional/new issues, don't seem to be having issues with long fields.
Closed.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
|
Background
It seems the data model uses
varchar(64)
for fields that are meant to store connection URIs. When sending a lineage event, especially from OpenLineage's airflow integration, that contains a URI that is longer than 64 characters in various fields, an error is thrown.Expected Behavior
Lineage events with a source name > 64 characters, or namespace > 64, should be accepted as a valid event
Observed Behavior
A stack trace is thrown
Test Data
Proposed Fix
Most fields that store metadata should be bumped to
varchar(256)
or some larger field to support longer URLs, and the UI should simply truncate to accomodateThe text was updated successfully, but these errors were encountered: