feature-engineering

The integration of Woodwork resulted in three lines in the EntitySet.__eq__ method that were previously covered by tests, now being uncovered. We should update the equality tests to make sure all conditions are properly covered by tests.

The conditions that are not covered are shown below:
![image.png](https://images.zenhubusercontent.com/5da89a3c8b7bd200019886b7/dbbaa7d5-9c2d-4b29-acbf-a0461af

• 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

Repro: run automl on city_rev.csv

TypeError using the default encoder: Object of type PipelineBaseMeta is not JSON serializable; Will use string representation instead.

Cloudwatch link