alteryx / alteryx/evalml

Refactor how Featuretools 1.0.0 compatibility was handled

Ouverte
#2,910 0 commentaires 1 réaction 1 personne assignée Réclamée par @asniyaz Voir sur GitHub
refactor spike
Langage dominant
Python
Étoiles
850
Forks
96
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

In #2848 , we went forward with an intermediate solution to maintain compatibility with the new featuretools v1.0.0 and nlp-primitives 2.0.0. This involved a deletion of a woodwork accessor in the DFSTransformer within the EvalML code. We want to revisit this after the related [Featuretools issue](https://github.com/alteryx/featuretools/issues/1740) is addressed.

One possible solution is to request that the Featuretools team handle the addition of dataframes to an entityset that possess no name but already have a valid woodwork schema (have been initialized). Another possible, but hackier, solution is to check for woodwork initialized dataframes without a name and give them a name.

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.