[ 
https://issues.apache.org/jira/browse/IGNITE-12622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-12622:
--------------------------------------
    Description: 
Apparently it's possible in Ignite to configure a cache group with both ATOMIC 
and TRANSACTIONAL caches.
IgniteCacheGroupsTest#testContinuousQueriesMultipleGroups* tests.
As per discussed on dev list 
(http://apache-ignite-developers.2346864.n4.nabble.com/Forbid-mixed-cache-groups-with-both-atomic-and-transactional-caches-td45586.html),
 the community has concluded that such configurations should be prohibited.

Forbidden at IGNITE-20575 


  was:
Apparently it's possible in Ignite to configure a cache group with both ATOMIC 
and TRANSACTIONAL caches.
IgniteCacheGroupsTest#testContinuousQueriesMultipleGroups* tests.
As per discussed on dev list 
(http://apache-ignite-developers.2346864.n4.nabble.com/Forbid-mixed-cache-groups-with-both-atomic-and-transactional-caches-td45586.html),
 the community has concluded that such configurations should be prohibited.


> Forbid mixed cache groups with both atomic and transactional caches
> -------------------------------------------------------------------
>
>                 Key: IGNITE-12622
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12622
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: cache
>            Reporter: Ivan Rakov
>            Priority: Major
>              Labels: IEP-80, newbie
>
> Apparently it's possible in Ignite to configure a cache group with both 
> ATOMIC and TRANSACTIONAL caches.
> IgniteCacheGroupsTest#testContinuousQueriesMultipleGroups* tests.
> As per discussed on dev list 
> (http://apache-ignite-developers.2346864.n4.nabble.com/Forbid-mixed-cache-groups-with-both-atomic-and-transactional-caches-td45586.html),
>  the community has concluded that such configurations should be prohibited.
> Forbidden at IGNITE-20575 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to