[
https://issues.apache.org/jira/browse/IGNITE-28590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov updated IGNITE-28590:
------------------------------------
Description:
The QUERY_CACHE parameter in Hibernate allows you to write operation results
along with operation statistics to a separate cache.
Starting with version 2.16, the use of atomic caches within transactions is
prohibited.
Therefore, if the query cache is atomic, we will receive an exception when
writing statistics before the transaction commits, since the use of atomic
caches within transactions is prohibited.
If the query cache is transactional, we will receive an exception when writing
statistics after the transaction commits, since at that point the JPA
transaction has already been closed for the thread and no further operations
are expected.
was:
The QUERY_CACHE parameter in Hibernate allows you to write operation results
along with operation statistics to a separate cache.
Starting with version 2.16, the use of atomic caches within transactions is
prohibited.
Therefore, if the cache is atomic, we will receive an exception when writing
statistics before the transaction commits, since the use of atomic caches
within transactions is prohibited.
If the cache is transactional, we will receive an exception when writing
statistics after the transaction commits, since at that point the JPA
transaction has already been closed for the thread and no further operations
are expected.
> [Extensions] Hibernate USE_QUERY_CACHE is no longer possible to enable for
> transactional caches
> -----------------------------------------------------------------------------------------------
>
> Key: IGNITE-28590
> URL: https://issues.apache.org/jira/browse/IGNITE-28590
> Project: Ignite
> Issue Type: Bug
> Reporter: Mikhail Petrov
> Priority: Major
> Labels: ise
>
> The QUERY_CACHE parameter in Hibernate allows you to write operation results
> along with operation statistics to a separate cache.
> Starting with version 2.16, the use of atomic caches within transactions is
> prohibited.
> Therefore, if the query cache is atomic, we will receive an exception when
> writing statistics before the transaction commits, since the use of atomic
> caches within transactions is prohibited.
> If the query cache is transactional, we will receive an exception when
> writing statistics after the transaction commits, since at that point the JPA
> transaction has already been closed for the thread and no further operations
> are expected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
