Fixes #27487: Fix Glossary Import and Export buttons visibility for conditional permissions

[aniruddhaadak80]

Describe your changes:

Fixes #27487

I worked on resolving a bug where a user with conditional EditAll permissions mapped to their current Glossary (e.g., Data Producer) could not see the Import and Export buttons.

Previously, the buttons strictly validated against the global ResourceEntity.GLOSSARY_TERM instead of evaluating permissions.EditAll or permissions.All from the Glossary's own useGenericContext().

The Import and Export buttons now correctly consider the contextual conditions of the EditAll and All permissions, similar to other Manage action controls.

---

Type of change:

• Bug fix

---

Checklist:

• I have read the CONTRIBUTING document.
• My PR title is Fixes <issue-number>: <short explanation>
• I have commented on my code, particularly in hard-to-understand areas.
• For JSON Schema changes: I updated the migration scripts or explained why it is not needed.
• I have added a test that covers the exact scenario we are fixing.

---

Summary by Gitar

• Feature enhancement:
  • Increased maxResultSize upper bound to 10,000 in queryRunner to accommodate larger data retrieval operations.

_{This will update automatically on new commits.}

[github-actions]

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

[Copilot]

Pull request overview

Fixes the Glossary header’s Import/Export buttons visibility when users have conditional permissions (e.g., conditional EditAll) on the currently viewed Glossary by checking the entity-scoped permissions from useGenericContext() instead of relying only on global UI permissions.

Changes:

• Extend the Import/Export visibility check to allow permissions.All or permissions.EditAll from the Glossary’s useGenericContext() permissions.
• Update the useMemo dependency list so the computed visibility updates when permissions changes.

[github-actions]

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

[aniruddhaadak80]

Merged upstream main to fix stale CI errors (java-checkstyle, py-checkstyle, build).

[github-actions]

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

[gitar-bot]

Code Review ✅ Approved

Restores visibility for Glossary import and export buttons by correctly applying conditional permission checks. No issues found.

Options

Display: compact → Showing less information.

Comment with these commands to change:

Compact

gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[Copilot]

Pull request overview

Fixes a UI permissions bug in the Glossary header where Import/Export actions were hidden for users whose EditAll permission was granted via conditional policies on the specific glossary entity, by incorporating entity-scoped permissions from useGenericContext() into the visibility check.

Changes:

• Update Import/Export visibility logic to allow contextual permissions.All / permissions.EditAll in addition to global checkPermission(...) checks.
• Update memo dependencies to include contextual permissions.

[github-actions]

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!