-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Ranger: java.lang.IllegalArgumentException: bound must be positive #24464
Comments
Could you use |
This is red herring. The actual error isn't related to guice or jdk 23 but is "incorrect bounds" |
This is caused by
being called with an empty list. it seems like a misconfiguration issue. |
Config included the hadoop configmap delivered files at the specified paths based on a self authored chart and container based on 433 with Ranger 2.4.0 in production
|
What is the origin of the if not ASM? java.lang.IllegalArgumentException: Unsupported class file major version 67 |
@epheatt this is irrelevant part of the log. Used only to augment logging with the code line of the guice binding that failed |
I think you need ranger.plugin.config.resource=/etc/trino/ranger-trino-security.xml,/etc/trino/ranger-trino-audit.xml That's what's working for me with trino 466 Did you mean 433 in your message above or do you actually mean 466 Any chance you could share your helm chart for ranger somewhere? |
I'm using a self built container for 433 with Ranger 2.4.0 plugin patches to get it working with a Ranger container and chart based on the mr3project https://github.com/mr3project/mr3-run-k8s/tree/master/kubernetes/helm/ranger. Using the ranger.plugin.config.resource property instead of ranger.hadoop.config.resource solved the lookup issues.
|
Using trinodb/trino:467 image in Kubernetes the Guice-7.0.0 ASM related to google/guice#1822 fails to start the coordinator with stacktrace related to LineNumbers
The text was updated successfully, but these errors were encountered: