Bryan Chen

Make sure to address [this comment](https://github.com/alteryx/evalml/pull/3373/#discussion_r832499447) as well when closing out this issue

Closing this for now, will circle back in the future.

After discussion with @dsherry, we decided on - Merge Featuretools (single dataframe/datatable support) into Evalml components (not AutoML), create functionality for ingesting EntitySets (as support for multiple datatables/dataframes), - afterwards,...

Hey @leahmcguire, thanks for reporting this bug! What's happening is that our inference function for `IntegerNullable` purely checks whether or not the values are integer values (using mod logic), but...

No big change in runtime. Perf test report is attached [3109.html.zip](https://github.com/alteryx/woodwork/files/9881846/3109.html.zip)

Leaving this unmerged for the 0.20.0 release because it introduces a lot of breaking changes. Will aim to get in for 0.21.0 release.

Changing to `npartitions=-1`, as per @thehomebrewnerd's suggestion, leads to slightly better times on the perf tests. [3160.html.zip](https://github.com/alteryx/woodwork/files/9922790/3160.html.zip) Will keep this change over `.compute()`

Closing because this has been untouched for a while now.

Pandas 1.5 should solve this bug!

Looks like with `pandas==1.5.0`, this case passes! Would be worthwhile to look into this issue again and see if we can get this `string[pyarrow]` type back into WW