ge of this opportunity please visit
http://wso2.com/support/. <http://wso2.com/support/>
For further information on WSO2 Analytics, visit the WSO2 Analytics Page
<http://wso2.com/analytics>.
- WSO2 Analytics Team.
--
Gokul Balakrishnan
Senior Software Engineer,
WSO2, Inc. http://wso2.com
M
ure>
>>>
>>> ___
>>> Dev mailing list
>>> d...@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Blog: http://blog.napagoda.
g/~hemapani/
>>http://srinathsview.blogspot.com/
>>
>
>
>
> --
> *Anjana Fernando*
> Associate Director / Architect
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
--
Gokul Balakrishnan
Senior Software Engineer,
WSO2, Inc. http://wso2.com
M +94 77 5935 789 | +44 7563 570502
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
s/d/1Ng7pTR0MpSg3Asn02idBIZaq8AhdNd24HySKp37GzK8/edit?usp=drive_web>
--
Gokul Balakrishnan
Senior Software Engineer,
WSO2, Inc. http://wso2.com
M +94 77 5935 789 | +44 7563 570502
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/li
k at all.
>>
>> While doing the implementation, we identified some of these concerns, and
>> had some chats with Srinath and all, but we decided to finish the
>> implementation and see how it will work out anyway. But now, I guess we
>> should make the final decision on wheth
reporting: https://wso2.org/jira/browse/DAS
[3] WSO2 Developers List: d...@wso2.org
--
Gokul Balakrishnan
Senior Software Engineer,
WSO2, Inc. http://wso2.com
M +94 77 5935 789 | +44 7563 570502
___
Architecture mailing list
Architecture@wso2.org
https
t endpoint (with a log printed stating this fact). The client is then
able to send events to the Thrift server with zero configuration from the
user's part.
Questions/comments welcome.
Thanks,
[1] https://github.com/wso2/carbon-analytics-common/pull/270
On 30 June 2016 at 16:49, Gokul Balakrishnan &
n 30, 2016 at 8:09 AM, Gokul Balakrishnan <go...@wso2.com>
> wrote:
>
>> Hi Srinath,
>>
>> As per our offline chat earlier, the initial plan is to locate the Thrift
>> endpoint through mDNS service discovery, considering the host and port
>> first.
&g
s it hits a filter rule.
>
> Gokul, please give an update on this?
>
> --Srinath
>
--
Gokul Balakrishnan
Senior Software Engineer,
WSO2, Inc. http://wso2.com
M +94 77 5935 789 | +44 7563 570502
___
Architecture mailing list
Arc
/4bdbf68833bd2bc8a20549eaf726873cacde468f
Thanks,
On 13 June 2016 at 17:37, Gokul Balakrishnan <go...@wso2.com> wrote:
> Hi Anjana, Nirmal,
>
> The schema being mandatory is an architectural decision we've had to take.
> If I go into a bit more detail as to the reasons, Spark requires its own
s not mandatory, and may be used to denote
>>> unique key fields in the underlying RDBMS table. It is based on this option
>>> that INSERT or UPSERT queries will be chosen when doing Spark INSERT INTO
>>> queries, as explained above.
>>>
>>> We're in the process
vider so
that they can be better understood.
Thanks,
On 10 June 2016 at 15:16, Inosh Goonewardena <in...@wso2.com> wrote:
> Hi Gokul,
>
>
> On Fri, Jun 10, 2016 at 2:08 PM, Gokul Balakrishnan <go...@wso2.com>
> wrote:
>
>> Hi all,
>>
>> In DAS 3
as part of the first
cut, and we will be testing against all DBs supported by DAS over the
following days. The connector is expected to be shipped with the DAS 3.1.0
release.
Thoughts welcome.
[1] https://github.com/wso2/carbon-analytics/pull/187
Thanks,
--
Gokul Balakrishnan
Senior Software
t;>>>>>>>> --
>>>>>>>>>
>>>>>>>>> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera
>>>>>>>>> Site: http://people.apache
>>>>>>>> directly from raw tables. As mentioned above, with MyISAM this could
>>>>>>>>> lead
>>>>>>>>> to performance issues if data publishing and spark analytics happens
>>>>>>>>> in
>>>>>>>>> parallel. So considering that I think we should change the default
>>>>>>>>> configuration to use InnoDB. WDYT?
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Thanks & Regards,
>>>>>>>>>
>>>>>>>>> Inosh Goonewardena
>>>>>>>>> Associate Technical Lead- WSO2 Inc.
>>>>>>>>> Mobile: +94779966317
>>>>>>>>>
>>>>>>>>> ___
>>>>>>>>> Architecture mailing list
>>>>>>>>> Architecture@wso2.org
>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> ___
>>>>>>>> Architecture mailing list
>>>>>>>> Architecture@wso2.org
>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> W.G. Gihan Anuruddha
>>>>>>> Senior Software Engineer | WSO2, Inc.
>>>>>>> M: +94772272595
>>>>>>>
>>>>>>> ___
>>>>>>> Architecture mailing list
>>>>>>> Architecture@wso2.org
>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Thanks & Regards,
>>>>>>
>>>>>> Inosh Goonewardena
>>>>>> Associate Technical Lead- WSO2 Inc.
>>>>>> Mobile: +94779966317
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Thanks & regards,
>>>>> Nirmal
>>>>>
>>>>> Team Lead - WSO2 Machine Learner
>>>>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>>>>> Mobile: +94715779733
>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> Thanks & Regards,
>>>>
>>>> Inosh Goonewardena
>>>> Associate Technical Lead- WSO2 Inc.
>>>> Mobile: +94779966317
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Team Lead - WSO2 Machine Learner
>>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>>> Mobile: +94715779733
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>>
>>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> Inosh Goonewardena
>> Associate Technical Lead- WSO2 Inc.
>> Mobile: +94779966317
>>
>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
--
Gokul Balakrishnan
Senior Software Engineer,
WSO2, Inc. http://wso2.com
M +94 77 5935 789 | +44 7563 570502
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
ist: d...@wso2.org
--
Gokul Balakrishnan
Senior Software Engineer,
WSO2, Inc. http://wso2.com
M +94 77 5935 789 | +44 7563 570502
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Sachith Withana
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> E-mail: sachith AT wso2.com
>> M: +94715518127
>> Linked-In: <http://goog_416592669>
>> https://lk.linkedi
more details and to take advantage of this unique opportunity please
visit http://wso2.com/support.
For more information about WSO2 DAS please see
wso2.com/products/data-analytics-server.
*-- The WSO2 DAS Team --*
--
Gokul Balakrishnan
Senior Software Enginee
SO2 DAS Issue Tracking
<https://wso2.org/jira/browse/DAS> page. When reporting issues, please be
kind enough to set the affected version as DAS 3.0.0-Beta2.
We value your feedback, and suggestions are welcome.
Thanks,
WSO2 DAS Development Team.
[*] Download:
*https://svn.wso2.org/repos/wso2/peo
Balakrishnan
Senior Software Engineer,
WSO2, Inc. http://wso2.com
Mob: +94 77 593 5789 | +1 650 272 9927
--
Gokul Balakrishnan
Senior Software Engineer,
WSO2, Inc. http://wso2.com
Mob: +94 77 593 5789 | +1 650 272 9927
___
Architecture mailing list
that without
much trouble)
On Tue, May 12, 2015 at 8:38 PM, Gokul Balakrishnan go...@wso2.com
wrote:
Hi all,
As part of the HBase analytics datasource implementation for DAS 3.0, we
have come up with $subject which is envisioned to offer a standardised way
to specify connectivity parameters
Gokul,
When allowing a user to connect to a remote HDFS namenode, are we assuming
that it will always access the root (/) ? or do we have a way to specify
which folder the data source should point to?
On Thu, May 21, 2015 at 12:05 PM, Gokul Balakrishnan go...@wso2.com
wrote:
Hi Srinath
* : @maninda
On Mon, Mar 16, 2015 at 11:25 AM, Gokul Balakrishnan go...@wso2.com
wrote:
Hi all,
For BAM 3.0, we are introducing a data layer which handles all
operations intended for the back-end storage mechanism in a transparent
manner. The data layer consists of two parts: the data source
of actual
records.
Highly appreciate any feedback/comments on the above.
Thanks,
Gokul.
--
*Balakrishnan Gokulakrishnan*
Software Engineer,
WSO2, Inc. http://wso2.com
Mob: +94 77 593 5789 | +1 650 272 9927
___
Architecture mailing list
Architecture
Hi all,
I have started working on $subject, which is will serve to add another
back-end record storage atop which the BAM 3.0 Data Layer would be able to
operate. In this implementation, all records will be stored in a Hadoop
Distributed Filesystem (HDFS) deployment, and it will provide a new
WSO2 Business Activity Monitor 2.4.0 Released!
The WSO2 Business Activity Monitor development team is pleased to announce
the release of WSO2 Business Activity Monitor
2.4.0http://wso2.org/projects/bam
WSO2 Business Activity Monitor (WSO2 BAM) is a comprehensive framework
designed to solve the
WSO2 Business Activity Monitor 2.4.0-RC Released!
Date: 22nd October 2013.
The WSO2 Business Activity Monitor team is pleased to announce
the release of 2.4.0-RC version of the WSO2 Business Activity Monitor.
This release candidate build could be downloaded from
27 matches
Mail list logo
