[fix] pydruid export_pandas

[john-bodley]

CATEGORY

Choose one

• Bug Fix
• Enhancement (new features, refinement)
• Refactor
• Add tests
• Build / Development Environment
• Documentation

SUMMARY

This PR fixes a regression introduced in #8948 where I mistook that the pydruid export_pandas method alway returned an pd.DataFrame object (I missed the if statement here and thus it could be None.

I noticed another case where we don't check whether the Pandas dataframe exists (see here) but this is outside of the scope of the original PR.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN

CI.

ADDITIONAL INFORMATION

• Has associated issue:
• Changes UI
• Requires DB Migration.
• Confirm DB Migration upgrade and downgrade tested.
• Introduces new feature or API
• Removes existing feature or API

REVIEWERS

to: @michellethomas @mistercrunch @villebro

[john-bodley]

@mistercrunch do you know if there are any plans to add typing to pydruid?

[mistercrunch]

No plans, but I think it depends on deprecating support for py<3.5, which is about time. Happy to review/merge in that direction

[codecov-io]

Codecov Report

Merging #9006 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #9006   +/-   ##
=======================================
  Coverage   59.16%   59.16%           
=======================================
  Files         367      367           
  Lines       11680    11680           
  Branches     2863     2863           
=======================================
  Hits         6910     6910           
  Misses       4591     4591           
  Partials      179      179

---

Continue to review full report at Codecov.

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