Tableau Lineage Implementation

[ayush-shah]

Describe your changes :

Worked on #2765

Type of change :

• New feature

Frontend Preview (Screenshots) :

For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.

Checklist:

• I have read the CONTRIBUTING document.
• I have performed a self-review of my own.
• I have tagged my reviewers below.
• I have commented on my code, particularly in hard-to-understand areas.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• All new and existing tests passed.

Reviewers

@harshach @pmbrull

[pmbrull]

Thanks for the PR, looks great!

[sonarcloud]

[open-metadata-ingestion] Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
3 Code Smells

0.0% Coverage
0.0% Duplication

[harshach]

@ayush-shah @pmbrull we should create util function that can return a table_fqdn.
We may have to change this logic in this release or next release as we are discussing about adding database.schema.table_name into the mix. If that happens then we need to change this parsing multiple places. It would be better to have this in a central place where we can add necessary changes

[ayush-shah]

@ayush-shah @pmbrull we should create util function that can return a table_fqdn. We may have to change this logic in this release or next release as we are discussing about adding database.schema.table_name into the mix. If that happens then we need to change this parsing multiple places. It would be better to have this in a central place where we can add necessary changes

Should we create a new ticket to keep track of the same and merge this PR?

[pmbrull]

@ayush-shah @pmbrull we should create util function that can return a table_fqdn. We may have to change this logic in this release or next release as we are discussing about adding database.schema.table_name into the mix. If that happens then we need to change this parsing multiple places. It would be better to have this in a central place where we can add necessary changes

Should we create a new ticket to keep track of the same and merge this PR?

@ayush-shah yeah let's open a separate issue and merge this in for now. Thanks!