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/02/17 10:18:00 UTC

[jira] [Commented] (IGNITE-27829) Java Thin: Cache name is not stored to exception with cache operation.

    [ https://issues.apache.org/jira/browse/IGNITE-27829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18059033#comment-18059033 ] 

Ignite TC Bot commented on IGNITE-27829:
----------------------------------------

{panel:title=Branch: [pull/12732/head] Base: [master] : Possible Blockers (1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}SPI{color} [[tests 1|https://ci2.ignite.apache.org/viewLog.html?buildId=8868756]]
* IgniteSpiTestSuite: TcpCommunicationSpiDropNodesTest.testOneNode - Test has low fail rate in base branch 0,0% and is not flaky

{panel}
{panel:title=Branch: [pull/12732/head] Base: [master] : New Tests (1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Thin Client: Java{color} [[tests 1|https://ci2.ignite.apache.org/viewLog.html?buildId=8865248]]
* {color:#013220}ClientTestSuite: CacheExceptionsTest.testCacheExceptionWrapped - PASSED{color}

{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8858076&amp;buildTypeId=IgniteTests24Java8_RunAll]

> Java Thin: Cache name is not stored to exception with cache operation.
> ----------------------------------------------------------------------
>
>                 Key: IGNITE-27829
>                 URL: https://issues.apache.org/jira/browse/IGNITE-27829
>             Project: Ignite
>          Issue Type: Improvement
>          Components: thin client
>            Reporter: Aleksey Plekhanov
>            Assignee: Aleksey Plekhanov
>            Priority: Major
>              Labels: ise, thin
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> Currently, thin client sends only cache id to server when performing cache operation. But in case of any error on server side (for example, cache not found) we even don't know cache name caused problem (we can't transform cache id back to cache name). For calls like:
> {code:java}
> client.cache("testCacheName").get(0);
> {code}
> Exception contains only test: 
> {noformat}
> Cache does not exist [cacheId= 115928251]
> {noformat}
> But cache name is always present on client side and we easily can enrich cache exception with the cache name. 



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