imbajin opened a new pull request, #3350:
URL: https://github.com/apache/hugegraph/pull/3350

   ## Purpose of the PR
   
   An authenticated Gremlin request that creates an index can return 403 when 
its schema task needs a new worker thread. The existing async-task permission 
list covers `SchemaTransaction`, but HStore uses `SchemaTransactionV2`, so its 
legitimate task submission is rejected by the thread-group check.
   
   ## Main Changes
   
   - Apply the existing four per-method schema-task allowances to V2 as well.
   - Reproduce the failing path through a real Gremlin engine, V2 index rebuild 
and JobBuilder; construct a cold worker without starting it.
   - Check that ordinary Gremlin thread creation and system-property access 
remain denied. Index-cache consistency is outside this fix.
   
   ## Verifying these changes
   
   - [x] Need tests and can be verified as follows: the focused regression 
fails with the reported thread-group exception before the patch and passes 
afterward. Java 17 formatting and full compilation pass; the final diff 
received independent review. No services, listeners, containers or clusters 
were started. Fresh-cluster validation with a rebuilt Server image remains 
pending.
   
   ## Does this PR potentially affect the following parts?
   
   - [ ] Dependencies
   - [ ] Modify configurations
   - [ ] The public API
   - [x] Other affects (authorized asynchronous schema task execution)
   - [ ] Nope
   
   ## Documentation Status
   
   - [ ] `Doc - TODO`
   - [ ] `Doc - Done`
   - [x] `Doc - No Need`: restores the existing schema-task contract through an 
internal caller mapping; no API, configuration or deployment procedure is added.
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to