You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[QTL]Cached lookup module for JDBC connectors. #2819 is another implementation of lookup caching (with eviction and cache per lookup) and will need to be reconciled with prior methodologies at some point so we don't have two lookup caching things. How to handle this extension in the mean time is under discussion. It was discussed between @b-slim and myself that the two extensions should eventually be merged into one, but that is not required for 0.9.1
This issue has been marked as stale due to 280 days of inactivity. It will be closed in 2 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@druid.apache.org list. Thank you for your contributions.
This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.
Here is a general overview of the QTL related items (kind of like an epic)
[QTL] Move kafka-extraction-namespace to the Lookup framework. #2800 needs merged as soon as possible to take the kafka extension off the table for other discussions for the time being.[QTL] Make URI Exctraction Namespace take more sane arguments #2738 is independent of the other 0.9.1 QTL changes, but may have (minor) merge conflicts with the other QTL changes.[QTL] Implement LookupExtractorFactory of namespaced lookup #2716--> [QTL] Implement LookupExtractorFactory of namespaced lookup #2926 moves the existing lookup-namespace extension to the lookup framework.and will need to be reconciled with prior methodologies at some point so we don't have two lookup caching things. How to handle this extension in the mean time is under discussion.It was discussed between @b-slim and myself that the two extensions should eventually be merged into one, but that is not required for 0.9.1This issue is not a blocker for 0.9.1, and should be moved to 0.9.2 when it is time.
The text was updated successfully, but these errors were encountered: