feature-engineering

Bug/Feature Request Description

In [1]: import featuretools as ft                                                                                                                             

In [2]: es = ft.demo.load_mock_customer(return_entityset=True)                                                                                                

In [3]: import pandas as pd    

• src/CMakeLists.txt
• docs/cn/deploy.md
• python/test/sql_smoke_test.py
• src/codec/codec_bench_test.cc

Currently, if you try to use BQ and materialize a feature that is a list (of numbers, strings, etc), Feast will crash because in BQ, the value type of the feature is a dictionary, such as

{'list': [{'item': 3}, {'item': 3}]}
In materialize, we convert the latest values retrieval job to a pyarrow table and then converts to ValueProtos to write. This calls

`python_type_to_feast_value_type

Problem
Some of our transformers & estimators are not thoroughly tested or not tested at all.

Solution
Use OpTransformerSpec and OpEstimatorSpec base test specs to provide tests for all existing transformers & estimators.

Details in discussion mljar/mljar-supervised#421

Woodwork introduced the ability to initialize typing information with a partial schema in alteryx/woodwork#1100

This means that we can potentially get rid of _retain_custom_types_and_intialize_woodwork and therefore retain more than just the logical types after some components modify the input data in a way that breaks the woodwork schema.

For example, this is how t