Skip to content

chore(searchIndex): remove unused ReindexingMetrics methods - #35392

Closed
detail-app[bot] wants to merge 1 commit into
mainfrom
detail/dead-code/chore-searchindex-remove-unused-reindexingmetrics-3b1ca4
Closed

detail-app[bot] wants to merge 1 commit into
mainfrom
detail/dead-code/chore-searchindex-remove-unused-reindexingmetrics-3b1ca4

Conversation

@detail-app

@detail-app detail-app Bot commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

Remove three public methods from ReindexingMetrics that have no production
callers, plus the BackpressureTests nested class that covered one of them.

  • recordBackpressureEvent() — its only caller lived in SearchIndexExecutor,
    which was deleted in Make SearchIndexing distributed-only #27971 ("Make SearchIndexing distributed-only").
  • recordVectorTimeout(int pendingCount) — its only caller was in
    OpenSearchBulkSink and was removed in a later commit; the parameter was
    ignored by the body. No callers remained anywhere (not even tests).
  • updateQueueFillRatio(int percent) — its only caller lived in
    SearchIndexExecutor, deleted in Make SearchIndexing distributed-only #27971. No callers remained anywhere.

The backing meter registrations (reindexing.backpressure.events,
reindexing.vector.timeouts, reindexing.queue.fill_ratio) are intentionally
kept: they are observability outputs analogous to logging/debug tooling with
potential external consumers (dashboards/alerts), and write-only/read-only
variables are treated as living code.

History

Describe your changes:

N/A — small dead-code cleanup, no linked issue.

Type of change:

  • Improvement

High-level design:

N/A — small change. Removed three uncalled public methods and their orphaned
test; nothing else wired to them.

Tests:

Use cases covered

  • Existing ReindexingMetricsTest continues to cover initialization, job
    lifecycle, stage counters, bulk request metrics, payload size, pending
    bulk requests, and promotion metrics.

Unit tests

  • Removed BackpressureTests (tested the removed recordBackpressureEvent).
  • Verified: mvn test -pl openmetadata-service -Dtest=ReindexingMetricsTest
    → 23/23 passing.
  • Verified: mvn spotless:check -pl openmetadata-service passes.

Backend integration tests

  • Not applicable (no API/backend behavior changes).

Ingestion integration tests

  • Not applicable (no ingestion changes).

Playwright (UI) tests

  • Not applicable (no UI changes).

Manual testing performed

  • None beyond the unit-test run above.

UI screen recording:

Not applicable — backend dead-code removal, no UI impact.

Checklist:

  • I have read the CONTRIBUTING document.
  • My PR title is Fixes <issue-number>: <short explanation>
  • My PR is linked to a GitHub issue via Fixes #<issue-number> above.
  • 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.
  • For a UI feature or feature task: as part of PR creation, I ran the PR build in Docker with sample data and embedded a verified GitHub-hosted recording plus build/health evidence above (or explained why this requirement is not applicable).
  • I have added tests (unit / integration / Playwright as applicable) and listed them above.
  • Decision check: if this PR decides something the next contributor could undo — a schema field, REST path or format another component or repo must agree with, a new default or limit, an ordering that must hold, or a rule stated only in this description — it adds a record under docs/decisions/ (see its README.md). This description is gone from git log after the squash-merge.

Dead Code PRs can be configured here.

@detail-app
detail-app Bot requested a review from a team as a code owner October 13, 2026 20:34
@detail-app
detail-app Bot requested a review from mohityadav766 October 13, 2026 20:34
@github-actions

Copy link
Copy Markdown
Contributor

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!

@detail-app detail-app Bot added the safe to test Add this label to run secure Github workflows on PRs label Oct 13, 2026
@shah-harshit

Copy link
Copy Markdown
Contributor

Superseded by #35537, which combines this change with other queued fixes.

@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to a manual request Oct 15, 2026
@github-actions

Copy link
Copy Markdown
Contributor

🚦 Removed from the merge queue — manual (2026-10-15T12:26:47Z)

The entry left the queue before it was built, so no checks ran against it.

timothybrush pushed a commit to timothybrush/OpenMetadata that referenced this pull request Oct 16, 2026
…, SAML tenant GUIDs, dead-code removals (open-metadata#35537)

* Fixes open-metadata#35106: gate certification tag strip on supportsCertification in BundleWarmupBatcher (open-metadata#35167)

* chore(searchIndex): remove unused ReindexingMetrics methods (open-metadata#35392)

* chore: remove unused TeamsMessage Fact/Action model classes (open-metadata#35386)

* chore: remove unused awaitVectorCompletionWithDetails and VectorCompletionResult (open-metadata#35389)

* Fixes open-metadata#35078: authorize VIEW_BASIC on lineage edge-details read endpoints (open-metadata#35140)

* Fixes open-metadata#34464: Accept upper/mixed-case Azure AD tenant GUIDs in SAML validation (open-metadata#34522)

---------

Co-authored-by: mohitdeuex <mohit.y@deuexsolutions.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

safe to test Add this label to run secure Github workflows on PRs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants