Hi Misgana,

I have two issues:
1. Issue:

Exception in thread "pool-17-thread-7" java.lang.IllegalArgumentException:
> No enum constant org.wso2.carbon.ml.commons.con
> stants.MLConstants.SUPERVISED_ALGORITHM.STACKING
>     at java.lang.Enum.valueOf(Enum.java:238)
>     at org.wso2.carbon.ml.commons.constants.MLConstants$SUPERVISED_
> ALGORITHM.valueOf(MLConstants.java:225)
>     at org.wso2.carbon.ml.core.spark.algorithms.SupervisedSparkMode
> lBuilder.build(SupervisedSparkModelBuilder.java:158)

Which approach did you try? putting the jar as a patch (patch9999)? or
build the carbon-ml and product ml respectively? If it was patching method,
did you build org.wso2.carbon.ml.commons as well?

Caused by: org.wso2.carbon.ml.database.exceptions.DatabaseHandlerException:
> An error occurred while inserting hyper parameter  to the database: Value
> too long for column "VALUE VARCHAR(50)": "'rO0ABXNyABNqYXZhLnV0aWwuQXJy
> YXlMaXN0eIHSHZnHYZ0DAAFJAARzaXpleHAAAAACdwQAAAACc3IAEWphdmEu
> dXRpbC5IYXNoTWFwBQfawcMWYNEDAAJGAApsb2F... (372)"; SQL statement:
> INSERT INTO ML_HYPER_PARAMETER(ANALYSIS_ID, ALGORITHM_NAME, NAME, VALUE,
> LAST_MODIFIED_TIME) VALUES(?,?,?,?, CURRENT_TIMESTAMP()) [90005-140]
> The Logic is: The hyperparameters of base-algorithms are serialized and
> passed in the product-ml hyperparamters script file.This is a serialized
> string of List of Maps, where each map contains hyperparameters of each
> base-algorithm and will be deserialized in buildStackingModel() in
> SupervisedSparkModelBuilder and fed to Stacking train().
> Current idea to solve it is:
>  1. Increase column capacity more than VALUE VARCHAR(50)
>  2. Change serialization logic
> What do you think?


I believe we don't need to pass a serialized a map and put the string in
DB. Can we store the hyperparamerets as follows, in the ML_HYPER_PARAMETER
table?

*ANALYSIS_ID* *ALGORITHM_NAME* *NAME* *VALUE* *LAST_MODIFIED_TIME*
123 Meta_Algorithm_1 Learning Rate 0.001 <some_timestamp>
123 Meta_Algorithm_1 Num_Trees 10 <some_timestamp>
123 Meta_Algorithm_1 Max_Depth 0.001 <some_timestamp>
123 Meta_Algorithm_1 Seed 4567 <some_timestamp>
123 Meta_Algorithm_2 Learning Rate 0.001 <some_timestamp>
123 Meta_Algorithm_2 Iterations 100 <some_timestamp>
123 Meta_Algorithm_2 Seed 789 <some_timestamp>
… … … … …
123 Base_Algorithm Learning Rate 0.001 <some_timestamp>
123 Base_Algorithm Iterations 100 <some_timestamp>
123 Base_Algorithm Seed 6325 <some_timestamp>

Do you see any complications/issues in doing so?



Thanks,
Supun

On Mon, Jun 20, 2016 at 6:58 PM, Misgana Negassi <
[email protected]> wrote:

> Hi Supun,
>
> I have two issues:
> 1. Issue:
>
> Exception in thread "pool-17-thread-7" java.lang.IllegalArgumentException:
> No enum constant
> org.wso2.carbon.ml.commons.constants.MLConstants.SUPERVISED_ALGORITHM.STACKING
>     at java.lang.Enum.valueOf(Enum.java:238)
>     at
> org.wso2.carbon.ml.commons.constants.MLConstants$SUPERVISED_ALGORITHM.valueOf(MLConstants.java:225)
>     at
> org.wso2.carbon.ml.core.spark.algorithms.SupervisedSparkModelBuilder.build(SupervisedSparkModelBuilder.java:158)
>
>
> It doesn't recognize STACKING although I have built carbonml as you have
> described.
>
> 2. Issue
>
>
> Caused by:
> org.wso2.carbon.ml.database.exceptions.DatabaseHandlerException: An error
> occurred while inserting hyper parameter  to the database: Value too long
> for column "VALUE VARCHAR(50)":
> "'rO0ABXNyABNqYXZhLnV0aWwuQXJyYXlMaXN0eIHSHZnHYZ0DAAFJAARzaXpleHAAAAACdwQAAAACc3IAEWphdmEudXRpbC5IYXNoTWFwBQfawcMWYNEDAAJGAApsb2F...
> (372)"; SQL statement:
> INSERT INTO ML_HYPER_PARAMETER(ANALYSIS_ID, ALGORITHM_NAME, NAME, VALUE,
> LAST_MODIFIED_TIME) VALUES(?,?,?,?, CURRENT_TIMESTAMP()) [90005-140]
>
> The Logic is: The hyperparameters of base-algorithms are serialized and
> passed in the product-ml hyperparamters script file.This is a serialized
> string of List of Maps, where each map contains hyperparameters of each
> base-algorithm and will be deserialized in buildStackingModel() in
> SupervisedSparkModelBuilder and fed to Stacking train().
>
> Current idea to solve it is:
>  1. Increase column capacity more than VALUE VARCHAR(50)
>  2. Change serialization logic
>
> What do you think?
>
> Regards,
> Misgana
>
>
>
>
> Can you specify why what was the error? Is there any error/stack trace?
>>
>
>


-- 
*Supun Sethunga*
Senior Software Engineer
WSO2, Inc.
http://wso2.com/
lean | enterprise | middleware
Mobile : +94 716546324
Blog: http://supunsetunga.blogspot.com
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to