-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Lookup module not registered with overlord #5727
Comments
I think you are correct, would you be able to do a PR? |
👍Sure thing I will do that this weekend |
I think this isn't a bug but a missing feature. I'll change the label. |
I'm taking a stab at this. In my first attempt I added the
So I added However, it also attempts to load lookup values on the middle manager, which throws out of memory errors
Does anyone with a better understanding of the architecture have any ideas on how we could get the MiddleManager to recognize the lookup syntax without attempting to load them? We can't set For reference, my Indexing Task Spec:
|
How about setting |
Unfortunately it doesn't. It prevents lookups from loading on both the middle manager and the peons. The option is passed, but it's passed first, and then overridden by the configuration. Job Log:
|
I found the magic settings to prevent the lookups from loading on the middle manager.
Created #7082 |
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. |
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. |
Currently, the lookup module is only registered with peons, historicals, and brokers.
This makes it impossible to use lookups in a reindexing task filter.
Here is an example reindexing task spec that showcases the failure:
This task will produce the following error:
It might be sufficient to add a line like this to the overlord startup file, but I have not tested this
The text was updated successfully, but these errors were encountered: