Re: [Dev] ML 1.1.0 is not backward compatible with older models

2016-02-18 Thread Rukshani Weerasinha 
Hi all,

Please check the information note I added about ML models in [1] and [2]

Machine Learner models are not backward compatible. e.g., models generated
using WSO2 ML 1.0.0 cannot be used with WSO2 ML 1.1.0 functionality.

@ ML team, can you please check whether the draft ML guide [3] that is
currently not published is valid for ML 1.1.0, and whether we can add some
information on migrating artifacts?

[1]
https://docs.wso2.com/display/ML110/WSO2+CEP+Extension+for+ML+Predictions
[2]
https://docs.wso2.com/display/CEP410/Predictive+Analytics+with+WSO2+Machine+Learner
[3] https://docs.wso2.com/display/TESB/Upgrading+from+a+Previous+Release

Best Regards,
Rukshani.

On Thu, Feb 18, 2016 at 2:49 PM, Niranjan Karunanandham 
wrote:

> Hi Fazlan,
>
> On Thu, Feb 18, 2016 at 2:47 PM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
>>
>>
>> On Thu, Feb 18, 2016 at 2:42 PM, Fazlan Nazeem  wrote:
>>
>>> Hi NIranjan,
>>>
>>> Yes, but currently we do not have a migration guide for ML. The changes
>>> needed were minimal and hence was decided not to include a migration guide.
>>>
>>
>> No Fazlan.. It is not correct.. Eventhough changes are minimal we need a
>> migration guide specifying those minimal things or to say there is nothing
>> to migrate.. It is a mandatory doc requirement for a release..
>>
> I agree with Mohan. We need to mention this in the migration doc and
> provide a guide to migrate it.
>
>
>>
>>
>>
>>>
>>> On Thu, Feb 18, 2016 at 12:27 PM, Niranjan Karunanandham <
>>> niran...@wso2.com> wrote:
>>>
 Hi Fazlan,

 IMO we need to also mention this in the ML migration doc from 1.0.0 to
 1.1.0.

 Regards,
 Nira

 On Thu, Feb 18, 2016 at 12:22 PM, Fazlan Nazeem 
 wrote:

> Hi Tishan,
>
> This is an expected behaviour since we have changed the model classes
> in ML 1.1.0.
>
> @Rukshani can you please document this under [1].
>
> [1]
> https://docs.wso2.com/display/ML110/WSO2+CEP+Extension+for+ML+Predictions
>
> On Thu, Feb 18, 2016 at 12:12 PM, Tishan Dahanayakage  > wrote:
>
>> Hi all,
>>
>> ML models built with ML 1.0.0 is not compatible with ML 1.1.0. If we
>> try to use a model build with 1.0.0 against ML 1.1.0 features following
>> exception is generated. Came across this when testing ML extension for 
>> CEP.
>>
>>
>> org.wso2.carbon.event.processor.core.exception.ExecutionPlanConfigurationException:
>> org.wso2.siddhi.core.exception.ExecutionPlanCreationException: Error 
>> while
>> retrieving ML-model :
>> registry:/_system/governance/2.Model.2015-12-22_19-47-59
>> org.wso2.carbon.ml.core.spark.models.MLGeneralizedLinearModel; local
>> class incompatible: stream classdesc serialVersionUID =
>> -1410218250358516850, local class serialVersionUID = 8020448562088344988 
>> in
>> execution plan "ExecutionPlanML"
>> at
>> org.wso2.carbon.event.processor.core.internal.util.helper.EventProcessorHelper.validateExecutionPlan(EventProcessorHelper.java:193)
>> ...
>> Caused by:
>> org.wso2.siddhi.core.exception.ExecutionPlanCreationException: Error 
>> while
>> retrieving ML-model :
>> registry:/_system/governance/2.Model.2015-12-22_19-47-59
>> org.wso2.carbon.ml.core.spark.models.MLGeneralizedLinearModel; local
>> class incompatible: stream classdesc serialVersionUID =
>> -1410218250358516850, local class serialVersionUID = 8020448562088344988
>> at
>> org.wso2.carbon.ml.siddhi.extension.PredictStreamProcessor.logError(PredictStreamProcessor.java:350)
>> at
>> org.wso2.carbon.ml.siddhi.extension.PredictStreamProcessor.init(PredictStreamProcessor.java:187)
>> ... 82 more
>>
>> Is this expected behavior? If so ​I think we need to mention that
>> models are not backward compatible in docs.​
>>
>>
>> --
>> Tishan Dahanayakage
>> Software Engineer
>> WSO2, Inc.
>> Mobile:+94 716481328
>>
>> Disclaimer: This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may have
>> received this communication in error, please reply to the sender 
>> indicating
>> that fact and delete the copy you received and in addition, you should 
>> not
>> print, copy, re-transmit, disseminate, or otherwise use the information
>> contained in this communication. Internet communications cannot be
>> guaranteed to be timely, secure, error or virus-free. The sender does not
>> accept liability for any errors or omissions.
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
>

Re: [Dev] ML 1.1.0 is not backward compatible with older models

2016-02-18 Thread Niranjan Karunanandham 
Hi Fazlan,

On Thu, Feb 18, 2016 at 2:47 PM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

>
>
> On Thu, Feb 18, 2016 at 2:42 PM, Fazlan Nazeem  wrote:
>
>> Hi NIranjan,
>>
>> Yes, but currently we do not have a migration guide for ML. The changes
>> needed were minimal and hence was decided not to include a migration guide.
>>
>
> No Fazlan.. It is not correct.. Eventhough changes are minimal we need a
> migration guide specifying those minimal things or to say there is nothing
> to migrate.. It is a mandatory doc requirement for a release..
>
I agree with Mohan. We need to mention this in the migration doc and
provide a guide to migrate it.


>
>
>
>>
>> On Thu, Feb 18, 2016 at 12:27 PM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi Fazlan,
>>>
>>> IMO we need to also mention this in the ML migration doc from 1.0.0 to
>>> 1.1.0.
>>>
>>> Regards,
>>> Nira
>>>
>>> On Thu, Feb 18, 2016 at 12:22 PM, Fazlan Nazeem 
>>> wrote:
>>>
 Hi Tishan,

 This is an expected behaviour since we have changed the model classes
 in ML 1.1.0.

 @Rukshani can you please document this under [1].

 [1]
 https://docs.wso2.com/display/ML110/WSO2+CEP+Extension+for+ML+Predictions

 On Thu, Feb 18, 2016 at 12:12 PM, Tishan Dahanayakage 
 wrote:

> Hi all,
>
> ML models built with ML 1.0.0 is not compatible with ML 1.1.0. If we
> try to use a model build with 1.0.0 against ML 1.1.0 features following
> exception is generated. Came across this when testing ML extension for 
> CEP.
>
>
> org.wso2.carbon.event.processor.core.exception.ExecutionPlanConfigurationException:
> org.wso2.siddhi.core.exception.ExecutionPlanCreationException: Error while
> retrieving ML-model :
> registry:/_system/governance/2.Model.2015-12-22_19-47-59
> org.wso2.carbon.ml.core.spark.models.MLGeneralizedLinearModel; local
> class incompatible: stream classdesc serialVersionUID =
> -1410218250358516850, local class serialVersionUID = 8020448562088344988 
> in
> execution plan "ExecutionPlanML"
> at
> org.wso2.carbon.event.processor.core.internal.util.helper.EventProcessorHelper.validateExecutionPlan(EventProcessorHelper.java:193)
> ...
> Caused by:
> org.wso2.siddhi.core.exception.ExecutionPlanCreationException: Error while
> retrieving ML-model :
> registry:/_system/governance/2.Model.2015-12-22_19-47-59
> org.wso2.carbon.ml.core.spark.models.MLGeneralizedLinearModel; local
> class incompatible: stream classdesc serialVersionUID =
> -1410218250358516850, local class serialVersionUID = 8020448562088344988
> at
> org.wso2.carbon.ml.siddhi.extension.PredictStreamProcessor.logError(PredictStreamProcessor.java:350)
> at
> org.wso2.carbon.ml.siddhi.extension.PredictStreamProcessor.init(PredictStreamProcessor.java:187)
> ... 82 more
>
> Is this expected behavior? If so ​I think we need to mention that
> models are not backward compatible in docs.​
>
>
> --
> Tishan Dahanayakage
> Software Engineer
> WSO2, Inc.
> Mobile:+94 716481328
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender 
> indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, re-transmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Thanks & Regards,

 Fazlan Nazeem

 *Software Engineer*

 *WSO2 Inc*
 Mobile : +94772338839
 <%2B94%20%280%29%20773%20451194>
 fazl...@wso2.com

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>>
>>> *Niranjan Karunanandham*
>>> Senior Software Engineer - WSO2 Inc.
>>> WSO2 Inc.: http://www.wso2.com
>>>
>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> Fazlan Nazeem
>>
>> *Software Engineer*
>>
>> *WSO2 Inc*
>> Mobile : +94772338839
>> <%2B94%20%280%29%20773%20451194>
>> fazl...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *V. Mohanadarshan*
> *Senior Software Engineer,*
> *Data Technologies Team,*
> *WSO2, Inc.

Re: [Dev] ML 1.1.0 is not backward compatible with older models

2016-02-18 Thread Mohanadarshan Vivekanandalingam 
On Thu, Feb 18, 2016 at 2:42 PM, Fazlan Nazeem  wrote:

> Hi NIranjan,
>
> Yes, but currently we do not have a migration guide for ML. The changes
> needed were minimal and hence was decided not to include a migration guide.
>

No Fazlan.. It is not correct.. Eventhough changes are minimal we need a
migration guide specifying those minimal things or to say there is nothing
to migrate.. It is a mandatory doc requirement for a release..



>
> On Thu, Feb 18, 2016 at 12:27 PM, Niranjan Karunanandham <
> niran...@wso2.com> wrote:
>
>> Hi Fazlan,
>>
>> IMO we need to also mention this in the ML migration doc from 1.0.0 to
>> 1.1.0.
>>
>> Regards,
>> Nira
>>
>> On Thu, Feb 18, 2016 at 12:22 PM, Fazlan Nazeem  wrote:
>>
>>> Hi Tishan,
>>>
>>> This is an expected behaviour since we have changed the model classes in
>>> ML 1.1.0.
>>>
>>> @Rukshani can you please document this under [1].
>>>
>>> [1]
>>> https://docs.wso2.com/display/ML110/WSO2+CEP+Extension+for+ML+Predictions
>>>
>>> On Thu, Feb 18, 2016 at 12:12 PM, Tishan Dahanayakage 
>>> wrote:
>>>
 Hi all,

 ML models built with ML 1.0.0 is not compatible with ML 1.1.0. If we
 try to use a model build with 1.0.0 against ML 1.1.0 features following
 exception is generated. Came across this when testing ML extension for CEP.


 org.wso2.carbon.event.processor.core.exception.ExecutionPlanConfigurationException:
 org.wso2.siddhi.core.exception.ExecutionPlanCreationException: Error while
 retrieving ML-model :
 registry:/_system/governance/2.Model.2015-12-22_19-47-59
 org.wso2.carbon.ml.core.spark.models.MLGeneralizedLinearModel; local
 class incompatible: stream classdesc serialVersionUID =
 -1410218250358516850, local class serialVersionUID = 8020448562088344988 in
 execution plan "ExecutionPlanML"
 at
 org.wso2.carbon.event.processor.core.internal.util.helper.EventProcessorHelper.validateExecutionPlan(EventProcessorHelper.java:193)
 ...
 Caused by:
 org.wso2.siddhi.core.exception.ExecutionPlanCreationException: Error while
 retrieving ML-model :
 registry:/_system/governance/2.Model.2015-12-22_19-47-59
 org.wso2.carbon.ml.core.spark.models.MLGeneralizedLinearModel; local
 class incompatible: stream classdesc serialVersionUID =
 -1410218250358516850, local class serialVersionUID = 8020448562088344988
 at
 org.wso2.carbon.ml.siddhi.extension.PredictStreamProcessor.logError(PredictStreamProcessor.java:350)
 at
 org.wso2.carbon.ml.siddhi.extension.PredictStreamProcessor.init(PredictStreamProcessor.java:187)
 ... 82 more

 Is this expected behavior? If so ​I think we need to mention that
 models are not backward compatible in docs.​


 --
 Tishan Dahanayakage
 Software Engineer
 WSO2, Inc.
 Mobile:+94 716481328

 Disclaimer: This communication may contain privileged or other
 confidential information and is intended exclusively for the addressee/s.
 If you are not the intended recipient/s, or believe that you may have
 received this communication in error, please reply to the sender indicating
 that fact and delete the copy you received and in addition, you should not
 print, copy, re-transmit, disseminate, or otherwise use the information
 contained in this communication. Internet communications cannot be
 guaranteed to be timely, secure, error or virus-free. The sender does not
 accept liability for any errors or omissions.

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Thanks & Regards,
>>>
>>> Fazlan Nazeem
>>>
>>> *Software Engineer*
>>>
>>> *WSO2 Inc*
>>> Mobile : +94772338839
>>> <%2B94%20%280%29%20773%20451194>
>>> fazl...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Niranjan Karunanandham*
>> Senior Software Engineer - WSO2 Inc.
>> WSO2 Inc.: http://www.wso2.com
>>
>
>
>
> --
> Thanks & Regards,
>
> Fazlan Nazeem
>
> *Software Engineer*
>
> *WSO2 Inc*
> Mobile : +94772338839
> <%2B94%20%280%29%20773%20451194>
> fazl...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*V. Mohanadarshan*
*Senior Software Engineer,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: mo...@wso2.com
phone:(+94) 771117673
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ML 1.1.0 is not backward compatible with older models

2016-02-18 Thread Rukshani Weerasinha 
Hi all,

I will be adding a note in ML-CEP integration docs in both ML and CEP
documentation.

Best Regards,
Rukshani.

On Thu, Feb 18, 2016 at 2:42 PM, Fazlan Nazeem  wrote:

> Hi NIranjan,
>
> Yes, but currently we do not have a migration guide for ML. The changes
> needed were minimal and hence was decided not to include a migration guide.
>
> On Thu, Feb 18, 2016 at 12:27 PM, Niranjan Karunanandham <
> niran...@wso2.com> wrote:
>
>> Hi Fazlan,
>>
>> IMO we need to also mention this in the ML migration doc from 1.0.0 to
>> 1.1.0.
>>
>> Regards,
>> Nira
>>
>> On Thu, Feb 18, 2016 at 12:22 PM, Fazlan Nazeem  wrote:
>>
>>> Hi Tishan,
>>>
>>> This is an expected behaviour since we have changed the model classes in
>>> ML 1.1.0.
>>>
>>> @Rukshani can you please document this under [1].
>>>
>>> [1]
>>> https://docs.wso2.com/display/ML110/WSO2+CEP+Extension+for+ML+Predictions
>>>
>>> On Thu, Feb 18, 2016 at 12:12 PM, Tishan Dahanayakage 
>>> wrote:
>>>
 Hi all,

 ML models built with ML 1.0.0 is not compatible with ML 1.1.0. If we
 try to use a model build with 1.0.0 against ML 1.1.0 features following
 exception is generated. Came across this when testing ML extension for CEP.


 org.wso2.carbon.event.processor.core.exception.ExecutionPlanConfigurationException:
 org.wso2.siddhi.core.exception.ExecutionPlanCreationException: Error while
 retrieving ML-model :
 registry:/_system/governance/2.Model.2015-12-22_19-47-59
 org.wso2.carbon.ml.core.spark.models.MLGeneralizedLinearModel; local
 class incompatible: stream classdesc serialVersionUID =
 -1410218250358516850, local class serialVersionUID = 8020448562088344988 in
 execution plan "ExecutionPlanML"
 at
 org.wso2.carbon.event.processor.core.internal.util.helper.EventProcessorHelper.validateExecutionPlan(EventProcessorHelper.java:193)
 ...
 Caused by:
 org.wso2.siddhi.core.exception.ExecutionPlanCreationException: Error while
 retrieving ML-model :
 registry:/_system/governance/2.Model.2015-12-22_19-47-59
 org.wso2.carbon.ml.core.spark.models.MLGeneralizedLinearModel; local
 class incompatible: stream classdesc serialVersionUID =
 -1410218250358516850, local class serialVersionUID = 8020448562088344988
 at
 org.wso2.carbon.ml.siddhi.extension.PredictStreamProcessor.logError(PredictStreamProcessor.java:350)
 at
 org.wso2.carbon.ml.siddhi.extension.PredictStreamProcessor.init(PredictStreamProcessor.java:187)
 ... 82 more

 Is this expected behavior? If so ​I think we need to mention that
 models are not backward compatible in docs.​


 --
 Tishan Dahanayakage
 Software Engineer
 WSO2, Inc.
 Mobile:+94 716481328

 Disclaimer: This communication may contain privileged or other
 confidential information and is intended exclusively for the addressee/s.
 If you are not the intended recipient/s, or believe that you may have
 received this communication in error, please reply to the sender indicating
 that fact and delete the copy you received and in addition, you should not
 print, copy, re-transmit, disseminate, or otherwise use the information
 contained in this communication. Internet communications cannot be
 guaranteed to be timely, secure, error or virus-free. The sender does not
 accept liability for any errors or omissions.

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Thanks & Regards,
>>>
>>> Fazlan Nazeem
>>>
>>> *Software Engineer*
>>>
>>> *WSO2 Inc*
>>> Mobile : +94772338839
>>> <%2B94%20%280%29%20773%20451194>
>>> fazl...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Niranjan Karunanandham*
>> Senior Software Engineer - WSO2 Inc.
>> WSO2 Inc.: http://www.wso2.com
>>
>
>
>
> --
> Thanks & Regards,
>
> Fazlan Nazeem
>
> *Software Engineer*
>
> *WSO2 Inc*
> Mobile : +94772338839
> <%2B94%20%280%29%20773%20451194>
> fazl...@wso2.com
>



-- 
Rukshani Weerasinha

WSO2 Inc.
Web:http://wso2.com
Mobile: 0777 683 738
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ML 1.1.0 is not backward compatible with older models

2016-02-18 Thread Fazlan Nazeem 
Hi NIranjan,

Yes, but currently we do not have a migration guide for ML. The changes
needed were minimal and hence was decided not to include a migration guide.

On Thu, Feb 18, 2016 at 12:27 PM, Niranjan Karunanandham 
wrote:

> Hi Fazlan,
>
> IMO we need to also mention this in the ML migration doc from 1.0.0 to
> 1.1.0.
>
> Regards,
> Nira
>
> On Thu, Feb 18, 2016 at 12:22 PM, Fazlan Nazeem  wrote:
>
>> Hi Tishan,
>>
>> This is an expected behaviour since we have changed the model classes in
>> ML 1.1.0.
>>
>> @Rukshani can you please document this under [1].
>>
>> [1]
>> https://docs.wso2.com/display/ML110/WSO2+CEP+Extension+for+ML+Predictions
>>
>> On Thu, Feb 18, 2016 at 12:12 PM, Tishan Dahanayakage 
>> wrote:
>>
>>> Hi all,
>>>
>>> ML models built with ML 1.0.0 is not compatible with ML 1.1.0. If we try
>>> to use a model build with 1.0.0 against ML 1.1.0 features following
>>> exception is generated. Came across this when testing ML extension for CEP.
>>>
>>>
>>> org.wso2.carbon.event.processor.core.exception.ExecutionPlanConfigurationException:
>>> org.wso2.siddhi.core.exception.ExecutionPlanCreationException: Error while
>>> retrieving ML-model :
>>> registry:/_system/governance/2.Model.2015-12-22_19-47-59
>>> org.wso2.carbon.ml.core.spark.models.MLGeneralizedLinearModel; local
>>> class incompatible: stream classdesc serialVersionUID =
>>> -1410218250358516850, local class serialVersionUID = 8020448562088344988 in
>>> execution plan "ExecutionPlanML"
>>> at
>>> org.wso2.carbon.event.processor.core.internal.util.helper.EventProcessorHelper.validateExecutionPlan(EventProcessorHelper.java:193)
>>> ...
>>> Caused by:
>>> org.wso2.siddhi.core.exception.ExecutionPlanCreationException: Error while
>>> retrieving ML-model :
>>> registry:/_system/governance/2.Model.2015-12-22_19-47-59
>>> org.wso2.carbon.ml.core.spark.models.MLGeneralizedLinearModel; local
>>> class incompatible: stream classdesc serialVersionUID =
>>> -1410218250358516850, local class serialVersionUID = 8020448562088344988
>>> at
>>> org.wso2.carbon.ml.siddhi.extension.PredictStreamProcessor.logError(PredictStreamProcessor.java:350)
>>> at
>>> org.wso2.carbon.ml.siddhi.extension.PredictStreamProcessor.init(PredictStreamProcessor.java:187)
>>> ... 82 more
>>>
>>> Is this expected behavior? If so ​I think we need to mention that models
>>> are not backward compatible in docs.​
>>>
>>>
>>> --
>>> Tishan Dahanayakage
>>> Software Engineer
>>> WSO2, Inc.
>>> Mobile:+94 716481328
>>>
>>> Disclaimer: This communication may contain privileged or other
>>> confidential information and is intended exclusively for the addressee/s.
>>> If you are not the intended recipient/s, or believe that you may have
>>> received this communication in error, please reply to the sender indicating
>>> that fact and delete the copy you received and in addition, you should not
>>> print, copy, re-transmit, disseminate, or otherwise use the information
>>> contained in this communication. Internet communications cannot be
>>> guaranteed to be timely, secure, error or virus-free. The sender does not
>>> accept liability for any errors or omissions.
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> Fazlan Nazeem
>>
>> *Software Engineer*
>>
>> *WSO2 Inc*
>> Mobile : +94772338839
>> <%2B94%20%280%29%20773%20451194>
>> fazl...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Niranjan Karunanandham*
> Senior Software Engineer - WSO2 Inc.
> WSO2 Inc.: http://www.wso2.com
>



-- 
Thanks & Regards,

Fazlan Nazeem

*Software Engineer*

*WSO2 Inc*
Mobile : +94772338839
<%2B94%20%280%29%20773%20451194>
fazl...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ML 1.1.0 is not backward compatible with older models

2016-02-17 Thread Niranjan Karunanandham 
Hi Fazlan,

IMO we need to also mention this in the ML migration doc from 1.0.0 to
1.1.0.

Regards,
Nira

On Thu, Feb 18, 2016 at 12:22 PM, Fazlan Nazeem  wrote:

> Hi Tishan,
>
> This is an expected behaviour since we have changed the model classes in
> ML 1.1.0.
>
> @Rukshani can you please document this under [1].
>
> [1]
> https://docs.wso2.com/display/ML110/WSO2+CEP+Extension+for+ML+Predictions
>
> On Thu, Feb 18, 2016 at 12:12 PM, Tishan Dahanayakage 
> wrote:
>
>> Hi all,
>>
>> ML models built with ML 1.0.0 is not compatible with ML 1.1.0. If we try
>> to use a model build with 1.0.0 against ML 1.1.0 features following
>> exception is generated. Came across this when testing ML extension for CEP.
>>
>>
>> org.wso2.carbon.event.processor.core.exception.ExecutionPlanConfigurationException:
>> org.wso2.siddhi.core.exception.ExecutionPlanCreationException: Error while
>> retrieving ML-model :
>> registry:/_system/governance/2.Model.2015-12-22_19-47-59
>> org.wso2.carbon.ml.core.spark.models.MLGeneralizedLinearModel; local
>> class incompatible: stream classdesc serialVersionUID =
>> -1410218250358516850, local class serialVersionUID = 8020448562088344988 in
>> execution plan "ExecutionPlanML"
>> at
>> org.wso2.carbon.event.processor.core.internal.util.helper.EventProcessorHelper.validateExecutionPlan(EventProcessorHelper.java:193)
>> ...
>> Caused by: org.wso2.siddhi.core.exception.ExecutionPlanCreationException:
>> Error while retrieving ML-model :
>> registry:/_system/governance/2.Model.2015-12-22_19-47-59
>> org.wso2.carbon.ml.core.spark.models.MLGeneralizedLinearModel; local
>> class incompatible: stream classdesc serialVersionUID =
>> -1410218250358516850, local class serialVersionUID = 8020448562088344988
>> at
>> org.wso2.carbon.ml.siddhi.extension.PredictStreamProcessor.logError(PredictStreamProcessor.java:350)
>> at
>> org.wso2.carbon.ml.siddhi.extension.PredictStreamProcessor.init(PredictStreamProcessor.java:187)
>> ... 82 more
>>
>> Is this expected behavior? If so ​I think we need to mention that models
>> are not backward compatible in docs.​
>>
>>
>> --
>> Tishan Dahanayakage
>> Software Engineer
>> WSO2, Inc.
>> Mobile:+94 716481328
>>
>> Disclaimer: This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may have
>> received this communication in error, please reply to the sender indicating
>> that fact and delete the copy you received and in addition, you should not
>> print, copy, re-transmit, disseminate, or otherwise use the information
>> contained in this communication. Internet communications cannot be
>> guaranteed to be timely, secure, error or virus-free. The sender does not
>> accept liability for any errors or omissions.
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks & Regards,
>
> Fazlan Nazeem
>
> *Software Engineer*
>
> *WSO2 Inc*
> Mobile : +94772338839
> <%2B94%20%280%29%20773%20451194>
> fazl...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ML 1.1.0 is not backward compatible with older models

2016-02-17 Thread Fazlan Nazeem 
Hi Tishan,

This is an expected behaviour since we have changed the model classes in ML
1.1.0.

@Rukshani can you please document this under [1].

[1]
https://docs.wso2.com/display/ML110/WSO2+CEP+Extension+for+ML+Predictions

On Thu, Feb 18, 2016 at 12:12 PM, Tishan Dahanayakage 
wrote:

> Hi all,
>
> ML models built with ML 1.0.0 is not compatible with ML 1.1.0. If we try
> to use a model build with 1.0.0 against ML 1.1.0 features following
> exception is generated. Came across this when testing ML extension for CEP.
>
>
> org.wso2.carbon.event.processor.core.exception.ExecutionPlanConfigurationException:
> org.wso2.siddhi.core.exception.ExecutionPlanCreationException: Error while
> retrieving ML-model :
> registry:/_system/governance/2.Model.2015-12-22_19-47-59
> org.wso2.carbon.ml.core.spark.models.MLGeneralizedLinearModel; local class
> incompatible: stream classdesc serialVersionUID = -1410218250358516850,
> local class serialVersionUID = 8020448562088344988 in execution plan
> "ExecutionPlanML"
> at
> org.wso2.carbon.event.processor.core.internal.util.helper.EventProcessorHelper.validateExecutionPlan(EventProcessorHelper.java:193)
> ...
> Caused by: org.wso2.siddhi.core.exception.ExecutionPlanCreationException:
> Error while retrieving ML-model :
> registry:/_system/governance/2.Model.2015-12-22_19-47-59
> org.wso2.carbon.ml.core.spark.models.MLGeneralizedLinearModel; local class
> incompatible: stream classdesc serialVersionUID = -1410218250358516850,
> local class serialVersionUID = 8020448562088344988
> at
> org.wso2.carbon.ml.siddhi.extension.PredictStreamProcessor.logError(PredictStreamProcessor.java:350)
> at
> org.wso2.carbon.ml.siddhi.extension.PredictStreamProcessor.init(PredictStreamProcessor.java:187)
> ... 82 more
>
> Is this expected behavior? If so ​I think we need to mention that models
> are not backward compatible in docs.​
>
>
> --
> Tishan Dahanayakage
> Software Engineer
> WSO2, Inc.
> Mobile:+94 716481328
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, re-transmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

Fazlan Nazeem

*Software Engineer*

*WSO2 Inc*
Mobile : +94772338839
<%2B94%20%280%29%20773%20451194>
fazl...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] ML 1.1.0 is not backward compatible with older models

2016-02-17 Thread Tishan Dahanayakage 
Hi all,

ML models built with ML 1.0.0 is not compatible with ML 1.1.0. If we try to
use a model build with 1.0.0 against ML 1.1.0 features following exception
is generated. Came across this when testing ML extension for CEP.


org.wso2.carbon.event.processor.core.exception.ExecutionPlanConfigurationException:
org.wso2.siddhi.core.exception.ExecutionPlanCreationException: Error while
retrieving ML-model :
registry:/_system/governance/2.Model.2015-12-22_19-47-59
org.wso2.carbon.ml.core.spark.models.MLGeneralizedLinearModel; local class
incompatible: stream classdesc serialVersionUID = -1410218250358516850,
local class serialVersionUID = 8020448562088344988 in execution plan
"ExecutionPlanML"
at
org.wso2.carbon.event.processor.core.internal.util.helper.EventProcessorHelper.validateExecutionPlan(EventProcessorHelper.java:193)
...
Caused by: org.wso2.siddhi.core.exception.ExecutionPlanCreationException:
Error while retrieving ML-model :
registry:/_system/governance/2.Model.2015-12-22_19-47-59
org.wso2.carbon.ml.core.spark.models.MLGeneralizedLinearModel; local class
incompatible: stream classdesc serialVersionUID = -1410218250358516850,
local class serialVersionUID = 8020448562088344988
at
org.wso2.carbon.ml.siddhi.extension.PredictStreamProcessor.logError(PredictStreamProcessor.java:350)
at
org.wso2.carbon.ml.siddhi.extension.PredictStreamProcessor.init(PredictStreamProcessor.java:187)
... 82 more

Is this expected behavior? If so ​I think we need to mention that models
are not backward compatible in docs.​


-- 
Tishan Dahanayakage
Software Engineer
WSO2, Inc.
Mobile:+94 716481328

Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
re-transmit, disseminate, or otherwise use the information contained in
this communication. Internet communications cannot be guaranteed to be
timely, secure, error or virus-free. The sender does not accept liability
for any errors or omissions.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev