[
https://issues.apache.org/jira/browse/RANGER-5751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dhaval Rajpara updated RANGER-5751:
-----------------------------------
Description:
*Issue Summary:* Duplicate service configurations present in Trino service
definition causing incorrect database values during service creation
!Screenshot 2026-08-21 at 11.24.56 AM.png|width=862,height=512!
*Description:* In the Trino service definition, duplicate entries are appearing
for the following service configurations on the UI:
* Superusers ({{{}ranger.plugin.trino.superusers{}}})
* Superuser groups ({{{}ranger.plugin.trino.superuser.groups{}}})
* Service admin users ({{{}ranger.plugin.trino.service.admin.users{}}})
* Service admin usergroups
({{{}ranger.plugin.trino.service.admin.user.groups{}}})
*Root Cause:* The Trino service definition already includes these default
management configurations in its JSON file. However, following
{*}RANGER-3643{*}, these properties were added dynamically for all services
across the platform. As a result, Trino inherits both sets of definitions,
creating duplicate configuration fields in the service edit/creation UI.
Because of this duplication, when creating or updating a Trino service, invalid
or malformed configuration payloads are sent to the backend, leading to
incorrect values being written to the database and preventing service creation
from functioning as expected.
*Expected Behavior:*
# Trino service configuration page should only render a single instance of
each administrative configuration property.
# Saving or updating a Trino service should persist correct values to the
database and complete successfully.
was:
In TRINO service
config show dublicat entry for
Superusers
Superuser groups
Service admin users
Service admin usergroups
This is due to
Trino service already have this config in service defination json.
But after this jira RANGER-3643 Ui
> service-config UI show duplicate entries for trino plugin
> ---------------------------------------------------------
>
> Key: RANGER-5751
> URL: https://issues.apache.org/jira/browse/RANGER-5751
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Reporter: Dhaval Rajpara
> Assignee: Dhaval Rajpara
> Priority: Major
> Attachments: Screenshot 2026-08-21 at 11.24.56 AM.png
>
>
> *Issue Summary:* Duplicate service configurations present in Trino service
> definition causing incorrect database values during service creation
> !Screenshot 2026-08-21 at 11.24.56 AM.png|width=862,height=512!
> *Description:* In the Trino service definition, duplicate entries are
> appearing for the following service configurations on the UI:
> * Superusers ({{{}ranger.plugin.trino.superusers{}}})
> * Superuser groups ({{{}ranger.plugin.trino.superuser.groups{}}})
> * Service admin users ({{{}ranger.plugin.trino.service.admin.users{}}})
> * Service admin usergroups
> ({{{}ranger.plugin.trino.service.admin.user.groups{}}})
> *Root Cause:* The Trino service definition already includes these default
> management configurations in its JSON file. However, following
> {*}RANGER-3643{*}, these properties were added dynamically for all services
> across the platform. As a result, Trino inherits both sets of definitions,
> creating duplicate configuration fields in the service edit/creation UI.
> Because of this duplication, when creating or updating a Trino service,
> invalid or malformed configuration payloads are sent to the backend, leading
> to incorrect values being written to the database and preventing service
> creation from functioning as expected.
> *Expected Behavior:*
> # Trino service configuration page should only render a single instance of
> each administrative configuration property.
> # Saving or updating a Trino service should persist correct values to the
> database and complete successfully.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
