feat: support iterable for druid lookups-cached-single extension #16124
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Relates to #15936.
Description
This PR aims to change the behavior of the druid
lookups-cached-single
extension. In fact, we aim to introduce the option to iterate over fetched data from thedataFetcher
. We need this in the case ofloadingLookups
, that's why these changes don't impact thepollingLookup
feature.I also added the handling of a use case where the data exists in Druid but not in the actual data fetcher, which is in our use-case JDBC Data fetcher.
Release note
Key changed/added classes in this PR
Support iterating over fetched data for the loadinglookups for the druid lookups-cached-single extension
This PR has: