fix(tableau): fixes missed lineage

[sgomezvillamor]

Checklist

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
• For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

Files with missing lines	Coverage Δ
...on/src/datahub/ingestion/source/tableau/tableau.py	89.15% <100.00%> (+0.03%)	⬆️
...datahub/ingestion/source/tableau/tableau_common.py	92.23% <ø> (ø)

... and 1345 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f527c5e...b7bc056. Read the comment docs.

[mayurinehate]

the field database is Optional in GraphQL Spec, i.e. the key database can have value set as None. This case does not get covered by the statement datasource.get(c.DATABASE, {}).get(c.ID) which would throw error. Maybe replace it by (datasource.get(c.DATABASE) or {}).get(c.ID) ?

I'd also suggest a refactor to avoid this clause repeated over 3 times, if that makes sense.

[sgomezvillamor]

indeed

>>> {'database': None}.get('database', {}).get('id')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: 'NoneType' object has no attribute 'get'
>>> 

I always thought get could handle None, but nope, it's just for missing keys! 🤦