You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Interesting find, thank you @sfilipi. As far as I can see, elsewhere when we have options, we have only those options, and they are non-optional. This pursuant to #1798. So it seems like the second signature should not take inputColumnNames, but it should instead have an input column names on its options. (Which as far as I can tell it does.) By having both, we are inviting the potential of the question "who wins" on these two settings. (See again #1798.)
So I would prefer to solve this in another way:
The first one stays as is.
The second one does not accept IEnumerable, but instead takes an option.
If we find that some advanced options are in fact valuable, we should consider adding them as (probably) optional parameters to the first one.
The are two extensions for Featurize text.
IMO,
ATM, if i want to use the TextFeaturizingEstimator.Options, i have to create an IEnumerable for inputColumnNames and give it the output column name.
The text was updated successfully, but these errors were encountered: