Re: [Dev] Requesting a new jenkins build for jaggery-extensions

Hi Ayesha Created [1] as requested. Please check. [1] https://wso2.org/jenkins/job/jaggery-extensions_1.4.x/ On Tue, Jan 19, 2016 at 12:40 PM, Sagara Gunathunga wrote: > > > On Tue, Jan 19, 2016 at 12:34 PM, Ayesha Dissanayaka > wrote: > >> Hi Maheshika, >> >> Can we get a new jenkins build j

Re: [Dev] Requesting a new jenkins build for jaggery-extensions

Hi Maheshika, On Tue, Jan 19, 2016 at 12:34 PM, Ayesha Dissanayaka wrote: > Can we get a new jenkins build job for the "1.4.5-SNAPSHOT-temp" branch of > jaggery-extensions repository [1]. Branch to be pointed by new jenkins build should be 1.4.x [5] Sorry about the mistake. [5] https://github

Re: [Dev] Requesting a new jenkins build for jaggery-extensions

On Tue, Jan 19, 2016 at 12:34 PM, Ayesha Dissanayaka wrote: > Hi Maheshika, > > Can we get a new jenkins build job for the "1.4.5-SNAPSHOT-temp" branch of > jaggery-extensions repository [1]. > Please don't use "-temp" use something meaningful so that others can understand the purpose of this jo

[Dev] Requesting a new jenkins build for jaggery-extensions

Hi Maheshika, Can we get a new jenkins build job for the "1.4.5-SNAPSHOT-temp" branch of jaggery-extensions repository [1]. This is because, as of now we are maintaining two active branches of jaggery-extensions [2]. -master - depend on 0.12.0 -1.4.5-SNAPSHOT-temp - dep

Re: [Dev] [ML] Are we using correct names for feature types?

No. The only reason is we need a name for the features that actually have a numerical meanings. Numerical may mean "numbers" (which can be categorical as well) to users. In that case we need an alternative. Is there a better name we can use? Or we need to keep numerical as it is and assume it means

Re: [Dev] [ML] Are we using correct names for feature types?

On Tue, Jan 19, 2016 at 11:58 AM, Maheshakya Wijewardena < mahesha...@wso2.com> wrote: > Note that only continuous is not sufficient since there can be numerical > attributes that are not continuous like number of wins, etc. > > On Tue, Jan 19, 2016 at 11:57 AM, Maheshakya Wijewardena < > mahesha.

Re: [Dev] [ML] Are we using correct names for feature types?

> > Since the concern is about the suitability of the term "numerical", what > if we add two new feature types: > >1. Continues numerical > > >1. Discrete numerical > > -1. Guess the right terms are "Qualitative" and "Quantitative" :) On Tue, Jan 19, 2016 at 11:58 AM, Maheshakya Wijeward

Re: [Dev] [ML] Are we using correct names for feature types?

Note that only continuous is not sufficient since there can be numerical attributes that are not continuous like number of wins, etc. On Tue, Jan 19, 2016 at 11:57 AM, Maheshakya Wijewardena < mahesha...@wso2.com> wrote: > Since the concern is about the suitability of the term "numerical", what >

Re: [Dev] [ML] Are we using correct names for feature types?

Since the concern is about the suitability of the term "numerical", what if we add two new feature types: 1. Continues numerical 2. Discrete numerical to represent the features that actually have some numerical meaning and then eliminate "numerical". That way we can get rid of the confusion

Re: [Dev] WSO2 Data Analytics Server 3.0.1 Released!

[+announce] On Tue, Jan 19, 2016 at 11:14 AM, Sachith Withana wrote: > WSO2 Data Analytics Server (DAS) v3.0.1 Released! > > WSO2 Data Analytics Server development team is pleased to announce the > release of WSO2 Data Analytics Server 3.0.1 > > WSO2 Data Analytics Server combines real-time, bat

Re: [Dev] Requeting release of hadoop-client 2.6.0.wso2v3

New request with proposed changes available @ [1]. [1] - https://github.com/wso2/orbit/pull/166 Thanks and Regards, Ruwan Yatawara Senior Software Engineer, WSO2 Inc. email : ruw...@wso2.com mobile : +94 77 9110413 blog : http://ruwansrants.blogspot.com/ www: :http://wso2.com On Mon, Jan 18,

[Dev] WSO2 Data Analytics Server 3.0.1 Released!

WSO2 Data Analytics Server (DAS) v3.0.1 Released! WSO2 Data Analytics Server development team is pleased to announce the release of WSO2 Data Analytics Server 3.0.1 WSO2 Data Analytics Server combines real-time, batch, interactive, and predictive (via machine learning) analysis of data into one i

Re: [Dev] [ML] Are we using correct names for feature types?

Should there be an issue, since we are already considering these type of "numerical" features as categorical? On Tue, Jan 19, 2016 at 10:57 AM, Nirmal Fernando wrote: > > On Tue, Jan 19, 2016 at 10:53 AM, Supun Sethunga wrote: > >> IMO, 0 & 1 is still categorical. Its an equivalent to a encoded

Re: [Dev] [ML] Are we using correct names for feature types?

On Tue, Jan 19, 2016 at 10:53 AM, Supun Sethunga wrote: > IMO, 0 & 1 is still categorical. Its an equivalent to a encoded string > variable, isn't it? > Question is about what we should name current 'numerical' type. 0, 1 is of course categorical :) > On Tue, Jan 19, 2016 at 10:49 AM, Nirmal F

Re: [Dev] [ML] Are we using correct names for feature types?

On Tue, Jan 19, 2016 at 10:53 AM, Supun Sethunga wrote: > IMO, 0 & 1 is still categorical. Its an equivalent to a encoded string > variable, isn't it? > +1 > > On Tue, Jan 19, 2016 at 10:49 AM, Nirmal Fernando wrote: > >> All, >> >> Currently we have; numerical and categorical. But there can b

Re: [Dev] [ML] Are we using correct names for feature types?

IMO, 0 & 1 is still categorical. Its an equivalent to a encoded string variable, isn't it? On Tue, Jan 19, 2016 at 10:49 AM, Nirmal Fernando wrote: > All, > > Currently we have; numerical and categorical. But there can be categorical > features with numerical values for an example if a feature h

[Dev] [ML] Are we using correct names for feature types?

All, Currently we have; numerical and categorical. But there can be categorical features with numerical values for an example if a feature has only 0 & 1 we say it's a categorical feature. What should be the appropriate names? -- Thanks & regards, Nirmal Team Lead - WSO2 Machine Learner Associ

[Dev] PPaaS artifact conversion tool- Creating multi tenant PPaaS applications

Hi All, We are currently implementing a tool to convert artifact json files of PPaaS 4.0.0 to PPaaS 4.1.x. In the implemented tool we have considered only the single tenant cartridges. We are improving the tool to convert multi tenant cartridges to multi tenant applications. The approach we are ta

Re: [Dev] How to select Leader/Contributer node in a cluster

Hi Nipuna, Think you can check for the coordinator in clustering agent. There will be only one coordinator for a cluster domain. Clustering agent is in AxisConfiguration which is in server configuration context. Thanks Danesh On Mon, Jan 18, 2016 at 6:24 PM, Nipuna Prashan wrote: > Hi all, >

[Dev] Can we run schedule tasks in IS510?

Hi, I tried by adding below configs to registry.xml file but did not work. -Roshan -- Roshan Wijesena. Senior Software Engineer-WSO2 Inc. Mobile: *+94719154640* Email: ros...@wso2.com *WSO2, Inc. :** wso2.com * lean.enterprise.middleware. ___

Re: [Dev] puppet modules - validating yaml files

On Sun, Jan 17, 2016 at 2:24 AM, Sajith Kariyawasam wrote: > Hi Devs, > > While implementing puppet modules in [1] I came across with syntax errors > (using tabs, missing semicolons etc) in yaml files and which was detected > only at the puppet runtime. > True that some editors do syntax validati

Re: [Dev] Improvements to WSO2 Puppet Modules

On Mon, Jan 18, 2016 at 11:51 PM, Imesh Gunaratne wrote: > On Mon, Jan 18, 2016 at 8:50 AM, Akila Ravihansa Perera < > raviha...@wso2.com> wrote: > >> Hi, >> >> This is to summarize few improvements that I'd like to propose for WSO2 >> Puppet modules. >> >> 1. Remove conditional checks for Factor

Re: [Dev] Improvements to WSO2 Puppet Modules

On Mon, Jan 18, 2016 at 8:50 AM, Akila Ravihansa Perera wrote: > Hi, > > This is to summarize few improvements that I'd like to propose for WSO2 > Puppet modules. > > 1. Remove conditional checks for Factor facts in the Puppet manifest. > > For eg. we do conditional check for $::vm_type facto

[Dev] WebSphere MQ: Simple java client- IVTRun.bat -nojndi returns null [Images attached]

Hi all, I was about to deploy the JMS listener proxy service and pass a test message from WSMQ to ESB mgmt console, but suddenly IVTRun.bat failed to show the configuration message, which* I already got* in the early step. So I am pretty sure that all my other configurations are correct. Now, it s

Re: [Dev] [DEV][VOTE] Release WSO2 Data Analytics Server 3.0.1 RC3

Thank you all for testing and voting. Since no blocking issues have been reported, we are now closing the vote with 5 +1s and 0 -1s and proceeding with the DAS 3.0.1 release. Thanks, Sachith. On Mon, Jan 18, 2016 at 5:04 PM, Seshika Fernando wrote: > Hi, > > I've tested DAS 3.0.1 RC3 with the

[Dev] Requeting release of hadoop-client 2.6.0.wso2v3

Hi Team, We recently ran in to an issue when trying to install DAS features on top of MB, wherein when a higher version of com.google.common.* is available (MB exports version 18 via the guava library) hadoop client gets bound to the latest version of the library, rendering it unusable. This is d

[Dev] How to select Leader/Contributer node in a cluster

Hi all, I am building an osgi component for tenant deletion task. This will be deployed in every server (APIM, AS, AF, BAM, IS..). I have a requirement to do this task in one node in the cluster while there is no single point of failure. Only one node should start deletion while other nodes waitin

Re: [Dev] Error wile building carbon-feature-repository (branch: release-4.2.x)

adding Manu and Sinthuja On Mon, Jan 18, 2016 at 5:07 PM, Lahiru Cooray wrote: > Hi Dakshika, > Currently we are using Jaggery Server Feature 0.10.1 and this particular > dependency is not included in released P2 repo. > (https://github.com/wso2/carbon-feature-repository > release-4.2.x branch)

Re: [Dev] Error wile building carbon-feature-repository (branch: release-4.2.x)

Hi Dakshika, Currently we are using Jaggery Server Feature 0.10.1 and this particular dependency is not included in released P2 repo. (https://github.com/wso2/carbon-feature-repository > release-4.2.x branch) Could you please update the repo with relevant dependencies so we can proceed further. T

[Dev] WSO2 IoT Server 1.0.0 M1 Released

*WSO2 IoT Server 1.0.0 M1 Released!* We are pleased to announce the very first public milestone of WSO2 IoT Server (IoTS). It is available for download at http://builder1.us1.wso2.org/~iots/M1/. WSO2 IoT Server bundles together essentials capabilities to implement a scaleable server side IoT Pla

Re: [Dev] [DEV][VOTE] Release WSO2 Data Analytics Server 3.0.1 RC3

Hi, I've tested DAS 3.0.1 RC3 with the following - complex execution plans that test - event tables, indexing, patterns, windows, joins etc; - data persistence - event tracing - data explorer - event publisher - stream simulation. All works well. My vote - [x] Stable - Go

Re: [Dev] [DEV][VOTE] Release WSO2 Data Analytics Server 3.0.1 RC3

Hi all, Tested, - stream creation, indexing and persistence - Merge schema from spark - facets with spark - HTTPD sample My vote is [x] Stable - Go ahead and release Thanks, Sachith On Mon, Jan 18, 2016 at 4:18 PM, Dunith Dhanushka wrote: > Hi, > > Tested below areas and all worked fine. > >

Re: [Dev] [DEV][VOTE] Release WSO2 Data Analytics Server 3.0.1 RC3

Tested Following and all worked fine. REST APIs - Indexing, Drilldown, Aggregates JS APIs - Indexing Drilldown, Aggregates. [x] Stable - Go ahead and release On Mon, Jan 18, 2016 at 4:18 PM, Dunith Dhanushka wrote: > Hi, > > Tested below areas and all worked fine. > > - Analytics Dashboard > -

[Dev] [Architecture] WSO2 Message Broker 3.1.0 Beta Released !

Hi All, WSO2 MB Team is pleased to announce the release of WSO2 Message Broker 3.1.0 Beta. You can download this distribution from [1]. All the known issues identified are listed in JIRA [2]. Following are the bug fixes and improvements included in this release. Bug - [MB-1432

Re: [Dev] [DEV][VOTE] Release WSO2 Data Analytics Server 3.0.1 RC3

Hi, Tested below areas and all worked fine. - Analytics Dashboard - Gadget generation - Samples (Smart Home/HTTPD) - Stream persistence - CApp deployment My vote is [x] Stable - Go ahead and release Regards, Dunith On Mon, Jan 18, 2016 at 4:13 PM, Anjana Fernando wrote: > Hi, > > * Tested t

Re: [Dev] [DEV][VOTE] Release WSO2 Data Analytics Server 3.0.1 RC3

Hi, * Tested the Spark SQL functionality with a 2 node DAS cluster, by using the full Wikipedia data set (55 GB, 16M records). [x] Stable - Go ahead and release Cheers, Anjana. On Mon, Jan 18, 2016 at 3:36 PM, Sachith Withana wrote: > Hi all, > > This is the third release candidate of WSO2 DA

[Dev] [DEV][VOTE] Release WSO2 Data Analytics Server 3.0.1 RC3

Hi all, This is the third release candidate of WSO2 DAS 3.0.1. Please download, test and vote. The vote will be open for 72 hours or as needed. This release fixes the following issues: https://wso2.org/jira/issues/?filter=12622 Binary distribution file: https://svn.wso2.org/repos/wso2/people/sa

Re: [Dev] Upgrading Swagger UI and Swagger Editor in APIM

Hi Jo, This is the customization diff we currently have in swagger-ui. I'm in the process of merging these fixes with new version. Thanks, Bhathiya On Thu, Jan 14, 2016 at 3:02 PM, Bhathiya Jayasekara wrote: > Thanks. Will do. > > On Thu, Jan 14, 2016 at 3:02 PM, Joseph Fonseka wrote: > >> Hi

Re: [Dev] Upgrading Swagger UI and Swagger Editor in APIM

Can we check the commit logs to identify the changes ? On Mon, Jan 18, 2016 at 2:32 PM, Bhathiya Jayasekara wrote: > Existing Swagger-ui.js has this in the very beginning. So I used v2.1.1 > > /** > * swagger-ui - Swagger UI is a dependency-free collection of HTML, > JavaScript, and CSS assets

Re: [Dev] Upgrading Swagger UI and Swagger Editor in APIM

Existing Swagger-ui.js has this in the very beginning. So I used v2.1.1 /** * swagger-ui - Swagger UI is a dependency-free collection of HTML, JavaScript, and CSS assets that dynamically generate beautiful documentation from a Swagger-compliant API * @version v2.1.1 * @link http://swagger.io *

Re: [Dev] Upgrading Swagger UI and Swagger Editor in APIM

Their cannot be this much of a diff did you compare it with the correct version ? may be you can compare with a older revision in repo. On Mon, Jan 18, 2016 at 2:23 PM, Bhathiya Jayasekara wrote: > Hi Jo, > > This is the customization diff we currently have in swagger-ui. I'm in the > process of

[Dev] [DEV] Getting some time to visible in Publisher

Hi All, We have done some fix on [1] . After done that fix due to Solr indexing it get some time to show in publisher. As per the offline discussion with Danesh I have got fixed for that by adding registry handler [2] in order to Invoke solr indexing when APIs getting published or any change . We

Re: [Dev] puppet modules - validating yaml files

On Mon, Jan 18, 2016 at 12:15 PM, Sajith Kariyawasam wrote: > Thanks for the feedback and suggestions guys.! > I will work on adding those validation to the maven build process, using > maven exec-plugin > +1 A great thought! > > On Mon, Jan 18, 2016 at 8:16 AM, Akila Ravihansa Perera < > ravih