Fwd: [jira] [Created] (CAY-2228) Deprecate multiple cache groups in caching and query API

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Fwd: [jira] [Created] (CAY-2228) Deprecate multiple cache groups in caching and query API

Andrus Adamchik
FYI... I really hope no one depends on multiple cache groups per query, as we can't support those going forward.  

Andrus



> Begin forwarded message:
>
> From: "Nikita Timofeev (JIRA)" <[hidden email]>
> Subject: [jira] [Created] (CAY-2228) Deprecate multiple cache groups in caching and query API
> Date: February 15, 2017 at 12:07:41 PM GMT+3
> To: [hidden email]
> Reply-To: [hidden email]
>
> Nikita Timofeev created CAY-2228:
> ------------------------------------
>
>             Summary: Deprecate multiple cache groups in caching and query API
>                 Key: CAY-2228
>                 URL: https://issues.apache.org/jira/browse/CAY-2228
>             Project: Cayenne
>          Issue Type: Improvement
>          Components: Core Library
>            Reporter: Nikita Timofeev
>            Assignee: Nikita Timofeev
>             Fix For: 4.0.M5
>
>
> We should drop support for multiple cache groups as it have little practical sense.
> Only available caching provider with proper support for it is OS Cache and it is obsolete and should be actually deprecated too.
>
> So here is required API changes:
> - replace internally multiple cache groups with single group
> - deprecate corresponding 3.1 API and warn when multiple cache groups provided
> - remove corresponding 4.0 API completely (e.g. in fluent queries API)
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.15#6346)

Reply | Threaded
Open this post in threaded view
|

Re: Fwd: [jira] [Created] (CAY-2228) Deprecate multiple cache groups in caching and query API

Aristedes Maniatis-2
It was a really neat feature and we used it. But we had to come up with different solutions when we moved away from OSCache some time ago.

Ari


On 15/2/17 8:34pm, Andrus Adamchik wrote:

> FYI... I really hope no one depends on multiple cache groups per query, as we can't support those going forward.  
>
> Andrus
>
>
>
>> Begin forwarded message:
>>
>> From: "Nikita Timofeev (JIRA)" <[hidden email]>
>> Subject: [jira] [Created] (CAY-2228) Deprecate multiple cache groups in caching and query API
>> Date: February 15, 2017 at 12:07:41 PM GMT+3
>> To: [hidden email]
>> Reply-To: [hidden email]
>>
>> Nikita Timofeev created CAY-2228:
>> ------------------------------------
>>
>>             Summary: Deprecate multiple cache groups in caching and query API
>>                 Key: CAY-2228
>>                 URL: https://issues.apache.org/jira/browse/CAY-2228
>>             Project: Cayenne
>>          Issue Type: Improvement
>>          Components: Core Library
>>            Reporter: Nikita Timofeev
>>            Assignee: Nikita Timofeev
>>             Fix For: 4.0.M5
>>
>>
>> We should drop support for multiple cache groups as it have little practical sense.
>> Only available caching provider with proper support for it is OS Cache and it is obsolete and should be actually deprecated too.
>>
>> So here is required API changes:
>> - replace internally multiple cache groups with single group
>> - deprecate corresponding 3.1 API and warn when multiple cache groups provided
>> - remove corresponding 4.0 API completely (e.g. in fluent queries API)
>>
>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v6.3.15#6346)
>
>

--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
Reply | Threaded
Open this post in threaded view
|

Re: [jira] [Created] (CAY-2228) Deprecate multiple cache groups in caching and query API

Andrus Adamchik
Same here. None of the modern providers supports this.

Andrus

> On Feb 15, 2017, at 12:46 PM, Aristedes Maniatis <[hidden email]> wrote:
>
> It was a really neat feature and we used it. But we had to come up with different solutions when we moved away from OSCache some time ago.
>
> Ari
>
>
> On 15/2/17 8:34pm, Andrus Adamchik wrote:
>> FYI... I really hope no one depends on multiple cache groups per query, as we can't support those going forward.  
>>
>> Andrus
>>
>>
>>
>>> Begin forwarded message:
>>>
>>> From: "Nikita Timofeev (JIRA)" <[hidden email]>
>>> Subject: [jira] [Created] (CAY-2228) Deprecate multiple cache groups in caching and query API
>>> Date: February 15, 2017 at 12:07:41 PM GMT+3
>>> To: [hidden email]
>>> Reply-To: [hidden email]
>>>
>>> Nikita Timofeev created CAY-2228:
>>> ------------------------------------
>>>
>>>            Summary: Deprecate multiple cache groups in caching and query API
>>>                Key: CAY-2228
>>>                URL: https://issues.apache.org/jira/browse/CAY-2228
>>>            Project: Cayenne
>>>         Issue Type: Improvement
>>>         Components: Core Library
>>>           Reporter: Nikita Timofeev
>>>           Assignee: Nikita Timofeev
>>>            Fix For: 4.0.M5
>>>
>>>
>>> We should drop support for multiple cache groups as it have little practical sense.
>>> Only available caching provider with proper support for it is OS Cache and it is obsolete and should be actually deprecated too.
>>>
>>> So here is required API changes:
>>> - replace internally multiple cache groups with single group
>>> - deprecate corresponding 3.1 API and warn when multiple cache groups provided
>>> - remove corresponding 4.0 API completely (e.g. in fluent queries API)
>>>
>>>
>>>
>>> --
>>> This message was sent by Atlassian JIRA
>>> (v6.3.15#6346)
>>
>>
>
> --
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A