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

Posted to issues-all@impala.apache.org by "Aleksandr Efimov (Jira)" <ji...@apache.org> on 2026/09/19 16:47:00 UTC

[jira] [Assigned] (IMPALA-15382) Request pool resolution ignores JNI errors

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

Aleksandr Efimov reassigned IMPALA-15382:
-----------------------------------------

    Assignee: Aleksandr Efimov

> Request pool resolution ignores JNI errors
> ------------------------------------------
>
>                 Key: IMPALA-15382
>                 URL: https://issues.apache.org/jira/browse/IMPALA-15382
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>            Reporter: Aleksandr Efimov
>            Assignee: Aleksandr Efimov
>            Priority: Major
>
> RequestPoolService::ResolveRequestPool() stores the status returned by JniUtil::CallJniMethod() but does not check it before reading the result. If the Java call throws while converting a user principal or resolving a pool, the default result is read instead. The client can then receive a misleading denied-access error with an empty resolved pool, while the original JNI error is lost. Return the JNI status before inspecting the result and add a backend regression test that verifies a short-name conversion error is propagated.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org