ChrisHegarty commented on PR #12311:
URL: https://github.com/apache/lucene/pull/12311#issuecomment-1584844845
Currently in ES we have two potential ways to workaround this - they are
both crummy. :-(
1. Trigger initialisation of VectorUtils, and do a small operation, before
executing a painless script, or
2. Add a couple of permissions to the painless environment.
Not sure if Lucene could/should have a workaround hack put in place. It
would look something like: the do some dummy vector operation in the Panama
VectorUtil clinit, while asserting permissions (in a doPriv block). That would
force the JDK's vector implementation to initialise the class where the JDK-bug
lives, while asserting the property permission. This assumes that Lucene is
granted such a permission - it's a property read, which is not all that
interesting
The above is kinda similar the workaround, point no.1 above, that we're
considering for ES (and yes we can do it in ES, but it could bit other Lucene
consumers if not done in Lucene) ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
