alteryx / alteryx/evalml

Refactor how Featuretools 1.0.0 compatibility was handled

Abierto
#2,910 0 comentarios 1 reacción 1 asignado Reclamado por @asniyaz Ver en GitHub
refactor spike
Lenguaje dominante
Python
Estrellas
850
Forks
96
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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.

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.