Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[BUG] Plugin exclusion search retains matches because negative predicates use OR

Open Beginner friendly
#7,690 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

@konlue is already working on this.

Since Oct 17, 2026.

  • #7691 by @konlue — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
java, sql
Domain
backend, databases

Research direction

The bad predicate is in shenyu-admin/src/main/resources/mappers/plugin-sqlmap.xml around lines 255-260 and namespace-plugin-rel-sqlmap.xml around lines 179-184; start with the searchByCondition statements and how PluginServiceImpl.searchByCondition() passes the excluded value. Replace the OR between the negative name and role predicates with AND, or negate the combined positive match, in both mappers. Done when excluding 'divide' removes the (divide, Proxy) row from the seeded H2 data, keeps (request, HttpProcess), and nullable fields still behave as before.

Written by the indexing model from the issue text.

Description

admin sql type: bug
Current behavior

Plugin search combines exclusions across name and role with OR:

name NOT LIKE :excluded OR role NOT LIKE :excluded

For the seeded plugin name='divide', role='Proxy', excluding divide still returns the plugin because role NOT LIKE '%divide%' is true. Excluding a role likewise retains its plugins whenever their names do not contain that role. A row is removed only if both columns contain the excluded term.

Locations

PluginServiceImpl.searchByCondition() initializes the keyword!excluded syntax before calling the mapper. NamespacePluginQueryCondition inherits the same exclusion field, and its paged search uses the namespace mapper.

Expected behavior / impact

P3 / Low. Exclusion search should remove a plugin when either searchable field contains the excluded term, i.e. negate the positive predicate (name LIKE term OR role LIKE term). This affects administrative search results and pagination, rather than gateway traffic.

Reproduction and evidence
  1. Use plugins (divide, Proxy) and (request, HttpProcess); these name/role combinations exist in the H2 seed data.
  2. Run a plugin search with excluded='divide' (or the ordinary plugin search keyword !divide).
  3. Expected: request only. Current predicate: both divide and request.

A local SQL predicate probe extracted each exclusion clause directly from its current MyBatis XML and executed it against these two rows in an in-memory SQLite database. Both returned the excluded plugin. The probe verifies standard SQL boolean semantics; a full running Admin/MyBatis request was not exercised.

Suggested fix

Use AND between the negative predicates in both mappers, or an equivalent explicit negation of the positive predicate. Preserve intended handling of nullable fields and existing include/exclude keyword semantics.

Related existing work

Searched the 3,074-issue baseline, 85 open PR titles, and live plugin/excluded searches. #6614 is a namespace-plugin enabled result-map typo; #6717 concerns the separate nameExistedExclude query and a missing column. Neither addresses boolean exclusion logic in these searchByCondition statements. The two affected mappers are grouped here because they share the same root cause.

Environment

Apache ShenYu 2.7.2-SNAPSHOT, master@66d7d954ca37d651a5ad916f988a8081157a7ab4. Unit-test and CI issue categories excluded.

Dominant language
Java
Stars
8.9k
Forks
3.1k
Avg merge
3d 19h
Merged PRs (30d)
374

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No 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.

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.