Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-existent datasource shouldn't affect schema rebuilding for other datasources #15355

Merged
merged 2 commits into from
Nov 14, 2023

Conversation

findingrish
Copy link
Contributor

@findingrish findingrish commented Nov 9, 2023

Parent issue: #14989

In pull request #14985, a bug was introduced where periodic refresh would skip rebuilding a datasource's schema after encountering a non-existent datasource. This resulted in remaining datasources having stale schema information.

This change addresses the bug and adds a unit test to validate the refresh mechanism's behaviour when a datasource is removed, and other datasources have schema changes.

This PR has:

  • been self-reviewed.
  • added documentation for new or modified features or behaviors.
  • a release note entry in the PR description.
  • added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
  • added or updated version, license, or notice information in licenses.yaml
  • added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
  • added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
  • added integration tests.
  • been tested in a test Druid cluster.

@findingrish findingrish changed the title Non-existant datasource shouldn't affect schema rebuilding for other datasources Non-existent datasource shouldn't affect schema rebuilding for other datasources Nov 9, 2023
@findingrish findingrish closed this Nov 9, 2023
@somu-imply
Copy link
Contributor

@findingrish any reasons for closing it ?

@findingrish
Copy link
Contributor Author

@somu-imply @pranavbhole Thanks for the review.
I wanted to push another commit to improve the UT. I will reopen it shortly.

@findingrish findingrish reopened this Nov 14, 2023
@cryptoe cryptoe merged commit 5446494 into apache:master Nov 14, 2023
87 of 101 checks passed
CaseyPan pushed a commit to CaseyPan/druid that referenced this pull request Nov 17, 2023
…datasources (apache#15355)

In pull request apache#14985, a bug was introduced where periodic refresh would skip rebuilding a datasource's schema after encountering a non-existent datasource. This resulted in remaining datasources having stale schema information.

This change addresses the bug and adds a unit test to validate the refresh mechanism's behaviour when a datasource is removed, and other datasources have schema changes.
yashdeep97 pushed a commit to yashdeep97/druid that referenced this pull request Dec 1, 2023
…datasources (apache#15355)

In pull request apache#14985, a bug was introduced where periodic refresh would skip rebuilding a datasource's schema after encountering a non-existent datasource. This resulted in remaining datasources having stale schema information.

This change addresses the bug and adds a unit test to validate the refresh mechanism's behaviour when a datasource is removed, and other datasources have schema changes.
@LakshSingla LakshSingla added this to the 29.0.0 milestone Jan 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants