polardb / polardb/polardbx-sql

How to change password for user `polardbx_root`

Open
#103 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
1.7k
Forks
337
PR merge metrics
No merged PRs in 30d

Description

mysql>select user();
+--------------------------+
| USER()                   |
+--------------------------+
| polardbx_root@172.17.0.1 |
+--------------------------+
1 row in set (0.00 sec)

mysql>select current_user();
+----------------+
| current_user() |
+----------------+
| d1@pxc-tryout  |
+----------------+
1 row in set (0.01 sec)

mysql>set password for current_user() = password('pXVwPKGrG');
ERROR 3009 (HY000): [154bfae7a9c01000][172.17.0.5:54645][d1]syntax error, error in :'password for current_user() = password('pXV', expect =, actual (, pos 30, line 1, column 30, token (

mysql>SET PASSWORD FOR 'polardbx_root'@'pxc-tryout' = PASSWORD('654321');
ERROR 3009 (HY000): [154bfb2645801000][172.17.0.5:54645][d1]Illegal host: pxc-tryout

mysql>SET PASSWORD FOR 'polardbx_root'@'%' = PASSWORD('654321');
ERROR 5107 (HY000): [154bfb2f25801000][172.17.0.5:54645][d1]ERR-CODE: [PXC-5107][ERR_OPERATION_NOT_ALLOWED] Can not modify polardbx_root since it is reserved for system

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names no source files or tests; it provides SQL statements and server errors for changing the polardbx_root password. Start by reviewing the handling of SET PASSWORD and the reserved system user behavior. Done means documenting the supported password-change procedure or clarifying that the operation is not allowed.

Written by the indexing model from the issue text.

Assessment

Tech stack
mysql, sql
Domain
authentication, databases
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.