-
Hi Open Metadata team, For MySQL view DDL lineage deduction via UI, based on this https://docs.open-metadata.org/v1.0.0/connectors/ingestion/lineage, which already addresses how to create that lineage for tables of database service. I thought it was already implemented in the MySQL service connector but it looks like OpenMetadata UI could only deduct the source table on the CREATE VIEW order_incomes AS We could only get a lineage such as order_details => order_incomes but should we get a lineage such as So is this by design and users have to implement this feature themselves? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Hey @whossa, thanks for raising this. we have already identified this issue. we fetch the view ddl from mysql by running this query This query returns a compiled version of the create view like this
and the parser that we use i.e sqlfluff fails to parse the table reference and joins due to the complex bracketed structure for example in your case this would be
we are working on improving this, we already have a ticket open for this ref |
Beta Was this translation helpful? Give feedback.
-
@ulixius9 can we transfer this discussion to appropriate GitHub issue |
Beta Was this translation helpful? Give feedback.
Hey @whossa, thanks for raising this. we have already identified this issue. we fetch the view ddl from mysql by running this query
SHOW CREATE VIEW <view_name>
.This query returns a compiled version of the create view like this