[BUG] namespace_plugin_rel resultMap maps wrong column to wrong property (enabled never populated)

Open Beginner friendly
#6,614 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
85/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
java
Domain
databases

Research direction

Inspect shenyu-admin/src/main/resources/mappers/namespace-plugin-rel-sqlmap.xml at line 29, then compare Base_Column_List, schema.sql:1428, and NamespacePluginRelDO. Trace listByNamespaceId at line 381 using BaseResultMap. Done means the enabled column populates enabled and sort is no longer overwritten by that mapping.

Written by the indexing model from the issue text.

Description

admin priority: high type: bug
  • severity: High
  • files: shenyu-admin/src/main/resources/mappers/namespace-plugin-rel-sqlmap.xml:29
  • description: BaseResultMap line 29 is <result column="enable" jdbcType="BOOLEAN" property="sort"/>. Two errors: (a) the real column is enabled (per Base_Column_List:38 and schema.sql:1428), not enable; (b) it maps to property sort instead of enabled. The enabled property of NamespacePluginRelDO has no mapping at all. listByNamespaceId (line 381, resultMap="BaseResultMap") is the consumer.
  • impact: Callers of namespacePluginRelMapper.listByNamespaceId observe null enabled and corrupted sort; downstream plugin-enable-state logic is silently wrong.
  • suggested_fix: Replace line 29 with <result column="enabled" jdbcType="TINYINT" property="enabled"/>.
  • confidence: High
  • related_existing: none. Pure mapper/XML defect not in baseline.

Identified during the 2026-08-02 deep re-scan; full list in docs/scan2-2026-08-02/00-consolidated-critical-high.md.

Dominant language
Java
Stars
8.8k
Forks
3.1k
Avg merge
4d 11h
Merged PRs (30d)
85

Contributor guide

No contributing guide indexed for this repository

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.

More from apache/shenyu

All issues in apache/shenyu

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.