.@databricks.com]
> *Sent:* Wednesday, September 16, 2015 5:35 PM
> *To:* Feynman Liang
> *Cc:* Ulanov, Alexander; dev@spark.apache.org
> *Subject:* Re: Enum parameter in ML
>
>
>
> I've tended to use Strings. Params can be created with a validator
> (isValid) which can e
>>
>>
>> *From:* Feynman Liang [mailto:fli...@databricks.com]
>> *Sent:* Monday, September 14, 2015 5:27 PM
>> *To:* Ulanov, Alexander
>> *Cc:* dev@spark.apache.org
>> *Subject:* Re: Enum parameter in ML
>>
>>
>>
>> Since PipelineStages
, September 16, 2015 5:35 PM
To: Feynman Liang
Cc: Ulanov, Alexander; dev@spark.apache.org
Subject: Re: Enum parameter in ML
I've tended to use Strings. Params can be created with a validator (isValid)
which can ensure users get an immediate error if they try to pass an
unsupported String
>>
>> *From:* Joseph Bradley [mailto:jos...@databricks.com]
>> *Sent:* Wednesday, September 16, 2015 5:35 PM
>> *To:* Feynman Liang
>> *Cc:* Ulanov, Alexander; dev@spark.apache.org
>> *Subject:* Re: Enum parameter in ML
>>
>>
>>
>> I'v
Subject: Re: Enum parameter in ML
Since PipelineStages are serializable, the params must also be serializable. We
also have to keep the Java API in mind. Introducing a new enum Param type may
work, but we will have to ensure that Java users can use it without dealing
with ClassTags (I believe Scala
Since PipelineStages are serializable, the params must also be
serializable. We also have to keep the Java API in mind. Introducing a new
enum Param type may work, but we will have to ensure that Java users can
use it without dealing with ClassTags (I believe Scala will create new
types for each
for suggestion. How can I ensure that there will be no problems
> for Java users? (I only use Scala API)
>
>
>
> Best regards, Alexander
>
>
>
> *From:* Feynman Liang [mailto:fli...@databricks.com]
> *Sent:* Monday, September 14, 2015 5:27 PM
> *To:* Ulanov, Alexander