[
https://issues.apache.org/jira/browse/IGNITE-28856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18093528#comment-18093528
]
Ignite TC Bot commented on IGNITE-28856:
----------------------------------------
Docs Required triage: no user-facing documentation update is needed for this
ticket. The merged ignite-extensions change only restores compilation after
internal Ignite 2 core API/refactoring changes: HibernateCacheProxy now
delegates the new IgniteInternalCache lockTx* methods added by IGNITE-28727,
and a CDC test uses BinaryUtils::affinityFieldName after the internal helper
moved in IGNITE-28819. No public configuration, command, API, or documented
runtime behavior changes in this ticket.
> 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)
