[Proposal] Vectorized querying for lookups

[a2l007]

Presently, QTL objects are resolved by the LookupExtractor one key at a time. This proposal is to support a vectorized query model for lookup keys. LookupExtractor presently has an applyAll() method which would be utilized for this case. Based on the LookupExtractor implementation, this would increase the query execution performance for lookups. For the existing design to support this functionality, it would require a configurable number of rows to be buffered before the lookups are resolved.

[gianm]

I have been working on vectorized query engines and I think this would dovetail great with them. Hope to have something to post up soon.

[a2l007]

Looking forward to that. Is your implementation already taking care of lookup query vectorization? If not I can come back to this and work on it once your PR is out.

[gianm]

It's not, just the inner parts of the query engines.

[stale]

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.

[a2l007]

@gianm Since #6794 is merged, I'll start working on this and hopefully post a detailed proposal soon.

[gianm]

Ah nice!

[stale]

This issue has been marked as stale due to 280 days of inactivity. It will be closed in 4 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.

[github-actions]

This issue has been marked as stale due to 280 days of inactivity.
It will be closed in 4 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.

[github-actions]

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.