.Net's QueryExample mixes everything in a single cache

[Denis Magda]

Pavel,

I found out today that our .Net’s QueryExample mixes data for both Employee and Organization entities in a single cache. Is there any significant reasons for that?

Basically I would prefer demonstrating how data can be logically divided among different caches and that cross-cache queries works out of the box. You can refer to the same example implemented for Java and C++ for more details.

Are you ok with suggested improvement of the example? Do you want me to open a JIRA ticket?

—
Denis

[dsetrakyan]

Denis, good catch! I would also prefer to split Orgs and Employees into
different caches, as putting them into the same cache is rather an
anti-pattern.

On Tue, Aug 9, 2016 at 6:28 PM, Denis Magda <[hidden email]> wrote:

> Pavel,
>
> I found out today that our .Net’s QueryExample mixes data for both
> Employee and Organization entities in a single cache. Is there any
> significant reasons for that?
>
> Basically I would prefer demonstrating how data can be logically divided
> among different caches and that cross-cache queries works out of the box.
> You can refer to the same example implemented for Java and C++ for more
> details.
>
> Are you ok with suggested improvement of the example? Do you want me to
> open a JIRA ticket?
>
> —
> Denis
>
>

[Pavel Tupitsyn-3]

Hi Denis,

It has always been this way, not sure why. Vladimir can probably clarify.
I agree that this is an anti-pattern, feel free to create a ticket.

Pavel.

On Wed, Aug 10, 2016 at 7:34 AM, Dmitriy Setrakyan <[hidden email]>
wrote:

> Denis, good catch! I would also prefer to split Orgs and Employees into
> different caches, as putting them into the same cache is rather an
> anti-pattern.
>
>
> On Tue, Aug 9, 2016 at 6:28 PM, Denis Magda <[hidden email]> wrote:
>
>> Pavel,
>>
>> I found out today that our .Net’s QueryExample mixes data for both
>> Employee and Organization entities in a single cache. Is there any
>> significant reasons for that?
>>
>> Basically I would prefer demonstrating how data can be logically divided
>> among different caches and that cross-cache queries works out of the box.
>> You can refer to the same example implemented for Java and C++ for more
>> details.
>>
>> Are you ok with suggested improvement of the example? Do you want me to
>> open a JIRA ticket?
>>
>> —
>> Denis
>>
>>
>

[Vladimir Ozerov]

I do not know the reason. Let's split.

On Wed, Aug 10, 2016 at 9:05 AM, Pavel Tupitsyn <[hidden email]>
wrote:

> Hi Denis,
>
> It has always been this way, not sure why. Vladimir can probably clarify.
> I agree that this is an anti-pattern, feel free to create a ticket.
>
> Pavel.
>
> On Wed, Aug 10, 2016 at 7:34 AM, Dmitriy Setrakyan <[hidden email]>
> wrote:
>
>> Denis, good catch! I would also prefer to split Orgs and Employees into
>> different caches, as putting them into the same cache is rather an
>> anti-pattern.
>>
>>
>> On Tue, Aug 9, 2016 at 6:28 PM, Denis Magda <[hidden email]> wrote:
>>
>>> Pavel,
>>>
>>> I found out today that our .Net’s QueryExample mixes data for both
>>> Employee and Organization entities in a single cache. Is there any
>>> significant reasons for that?
>>>
>>> Basically I would prefer demonstrating how data can be logically divided
>>> among different caches and that cross-cache queries works out of the box.
>>> You can refer to the same example implemented for Java and C++ for more
>>> details.
>>>
>>> Are you ok with suggested improvement of the example? Do you want me to
>>> open a JIRA ticket?
>>>
>>> —
>>> Denis
>>>
>>>
>>
>

[Sergi]

Yes, it is a good idea, because I think in 2.0 we will disallow having more
than a single type in a cache.

Sergi

2016-08-10 9:35 GMT+03:00 Vladimir Ozerov <[hidden email]>:

> I do not know the reason. Let's split.
>
> On Wed, Aug 10, 2016 at 9:05 AM, Pavel Tupitsyn <[hidden email]>
> wrote:
>
> > Hi Denis,
> >
> > It has always been this way, not sure why. Vladimir can probably clarify.
> > I agree that this is an anti-pattern, feel free to create a ticket.
> >
> > Pavel.
> >
> > On Wed, Aug 10, 2016 at 7:34 AM, Dmitriy Setrakyan <
> [hidden email]>
> > wrote:
> >
> >> Denis, good catch! I would also prefer to split Orgs and Employees into
> >> different caches, as putting them into the same cache is rather an
> >> anti-pattern.
> >>
> >>
> >> On Tue, Aug 9, 2016 at 6:28 PM, Denis Magda <[hidden email]>
> wrote:
> >>
> >>> Pavel,
> >>>
> >>> I found out today that our .Net’s QueryExample mixes data for both
> >>> Employee and Organization entities in a single cache. Is there any
> >>> significant reasons for that?
> >>>
> >>> Basically I would prefer demonstrating how data can be logically
> divided
> >>> among different caches and that cross-cache queries works out of the
> box.
> >>> You can refer to the same example implemented for Java and C++ for more
> >>> details.
> >>>
> >>> Are you ok with suggested improvement of the example? Do you want me to
> >>> open a JIRA ticket?
> >>>
> >>> —
> >>> Denis
> >>>
> >>>
> >>
> >
>

[Denis Magda]

Pavel, here is the ticket
https://issues.apache.org/jira/browse/IGNITE-3675 <https://issues.apache.org/jira/browse/IGNITE-3675>

—
Denis

> On Aug 9, 2016, at 11:40 PM, Sergi Vladykin <[hidden email]> wrote:
>
> Yes, it is a good idea, because I think in 2.0 we will disallow having more
> than a single type in a cache.
>
> Sergi
>
> 2016-08-10 9:35 GMT+03:00 Vladimir Ozerov <[hidden email]>:
>
>> I do not know the reason. Let's split.
>>
>> On Wed, Aug 10, 2016 at 9:05 AM, Pavel Tupitsyn <[hidden email]>
>> wrote:
>>
>>> Hi Denis,
>>>
>>> It has always been this way, not sure why. Vladimir can probably clarify.
>>> I agree that this is an anti-pattern, feel free to create a ticket.
>>>
>>> Pavel.
>>>
>>> On Wed, Aug 10, 2016 at 7:34 AM, Dmitriy Setrakyan <
>> [hidden email]>
>>> wrote:
>>>
>>>> Denis, good catch! I would also prefer to split Orgs and Employees into
>>>> different caches, as putting them into the same cache is rather an
>>>> anti-pattern.
>>>>
>>>>
>>>> On Tue, Aug 9, 2016 at 6:28 PM, Denis Magda <[hidden email]>
>> wrote:
>>>>
>>>>> Pavel,
>>>>>
>>>>> I found out today that our .Net’s QueryExample mixes data for both
>>>>> Employee and Organization entities in a single cache. Is there any
>>>>> significant reasons for that?
>>>>>
>>>>> Basically I would prefer demonstrating how data can be logically
>> divided
>>>>> among different caches and that cross-cache queries works out of the
>> box.
>>>>> You can refer to the same example implemented for Java and C++ for more
>>>>> details.
>>>>>
>>>>> Are you ok with suggested improvement of the example? Do you want me to
>>>>> open a JIRA ticket?
>>>>>
>>>>> —
>>>>> Denis
>>>>>
>>>>>
>>>>
>>>
>>

[Pavel Tupitsyn-3]

Thanks Denis, done.

On Thu, Aug 11, 2016 at 2:43 AM, Denis Magda <[hidden email]> wrote:

> Pavel, here is the ticket
> https://issues.apache.org/jira/browse/IGNITE-3675
>
> —
> Denis
>
> On Aug 9, 2016, at 11:40 PM, Sergi Vladykin <[hidden email]>
> wrote:
>
> Yes, it is a good idea, because I think in 2.0 we will disallow having more
> than a single type in a cache.
>
> Sergi
>
> 2016-08-10 9:35 GMT+03:00 Vladimir Ozerov <[hidden email]>:
>
> I do not know the reason. Let's split.
>
> On Wed, Aug 10, 2016 at 9:05 AM, Pavel Tupitsyn <[hidden email]>
> wrote:
>
> Hi Denis,
>
> It has always been this way, not sure why. Vladimir can probably clarify.
> I agree that this is an anti-pattern, feel free to create a ticket.
>
> Pavel.
>
> On Wed, Aug 10, 2016 at 7:34 AM, Dmitriy Setrakyan <
>
> [hidden email]>
>
> wrote:
>
> Denis, good catch! I would also prefer to split Orgs and Employees into
> different caches, as putting them into the same cache is rather an
> anti-pattern.
>
>
> On Tue, Aug 9, 2016 at 6:28 PM, Denis Magda <[hidden email]>
>
> wrote:
>
>
> Pavel,
>
> I found out today that our .Net’s QueryExample mixes data for both
> Employee and Organization entities in a single cache. Is there any
> significant reasons for that?
>
> Basically I would prefer demonstrating how data can be logically
>
> divided
>
> among different caches and that cross-cache queries works out of the
>
> box.
>
> You can refer to the same example implemented for Java and C++ for more
> details.
>
> Are you ok with suggested improvement of the example? Do you want me to
> open a JIRA ticket?
>
> —
> Denis
>
>
>
>
>
>
>