You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2026/07/03 20:05:00 UTC

[jira] [Updated] (IGNITE-28856) Fix ignite-extensions compilation after IGNITE-28727 and IGNITE-28819

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

Ignite TC Bot updated IGNITE-28856:
-----------------------------------
    Ignite Flags: Release Notes Required  (was: Docs Required,Release Notes Required)

> Fix ignite-extensions compilation after IGNITE-28727 and IGNITE-28819
> ---------------------------------------------------------------------
>
>                 Key: IGNITE-28856
>                 URL: https://issues.apache.org/jira/browse/IGNITE-28856
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Anton Vinogradov
>            Assignee: Anton Vinogradov
>            Priority: Major
>
> ignite-extensions master fails to compile against the current ignite 2.19.0-SNAPSHOT due to two recent core changes:
> 1. IGNITE-28727 added four abstract methods to IgniteInternalCache (lockTxEntry, lockTxEntries, lockTxEntryAsync, lockTxEntriesAsync). HibernateCacheProxy (hibernate-ext) does not implement them:
>    HibernateCacheProxy is not abstract and does not override abstract method lockTxEntriesAsync(Collection<CacheEntry<Object,Object>>, long)
> 2. IGNITE-28819 moved CU.affinityFieldName to BinaryUtils, breaking a method reference in KafkaToIgniteMetadataUpdaterTest (cdc-ext):
>    invalid method reference: cannot find symbol method affinityFieldName() in CU
> Fix: add delegating implementations of the four lockTx* methods to HibernateCacheProxy (same pattern as the neighboring lock/lockAll delegates); switch the test to BinaryUtils::affinityFieldName.



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