Hi,
On Wed, Jun 22, 2016 at 3:25 PM, Isabelle Mauny wrote:
> Great! So that's for Spark.. You mentioned CEP as a big issue as well. Any
> hope to fix in CEP too ??
>
As per Suho's reply in this thread, it wouldn't be an issue, it just
consumed a little bit of extra memory,
Great! So that's for Spark.. You mentioned CEP as a big issue as well. Any
hope to fix in CEP too ??
-
*Isabelle Mauny*
VP, Product Strategy - WSO2, Inc. - http://wso2.com/
email: isabe...@wso2.com - mobile
Hi,
On Wed, Jun 22, 2016 at 11:38 AM, Selvaratnam Uthaiyashankar <
shan...@wso2.com> wrote:
>
>
> On Tue, Jun 21, 2016 at 11:31 AM, Buddhima Wijeweera
> wrote:
>
>> Hi,
>>
>> At the moment ESB can publish tenant-wise. I tried it with a latest ESB
>> and following are the
Hi,
I've updated the thread "Cross Tenant Data Reading from Spark Queries in
DAS", where I've done the implementation on writing back to the tenant
space also from the super tenant space as well. This basically just
eliminates the current requirement of executing identical Spark scripts in
all
On Tue, Jun 21, 2016 at 11:31 AM, Buddhima Wijeweera
wrote:
> Hi,
>
> At the moment ESB can publish tenant-wise. I tried it with a latest ESB
> and following are the steps need to follow:
> 1. Enable statistics for global level.
> 2. Add eventpublisher & eventstream files to
I think having separate execution plans for each tenant will not be a
problem. Though this consumes some amount of memory to construct multiple
execution plans it will improve the performance as data is not partitioned
by tenants by default.
Regards
Suho
On Tue, Jun 21, 2016 at 8:05 AM, Anjana
Hi,
Yeah, as Srinath mentioned, we do have MT support there, where each ESB
analytics data/queryeis/dashboards would be fully isolated. This is the
usual desirable mode, when different tenants deploy their own analytics
scripts and all, and there is no connection at all with other tenants, and
Hi,
At the moment ESB can publish tenant-wise. I tried it with a latest ESB and
following are the steps need to follow:
1. Enable statistics for global level.
2. Add eventpublisher & eventstream files to tenant's deployment folder
3. Create a proxy (or API, inbound EP) and Enable Statistics.
4.
We had a chat about this.
This is supported. However, current implementation will run spark jobs per
each tenant. So it will have performance concerns with a large number of
tenants.
Anjana, can you give the details and potential solutions?
Summary is that DAS team has implemented the support
Please note that this will be an essential feature for our integration
cloud. So, we need to decide how should we proceed with this soon.
On Fri, Jun 17, 2016 at 1:57 AM, Kasun Indrasiri wrote:
> How about the $subject? I don't think there's no any limitation from the
>
How about the $subject? I don't think there's no any limitation from the
mediation engine side on collecting these stats. We need to have this for
ESB 5.
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog :
11 matches
Mail list logo