nic-6443 opened a new pull request, #12474: URL: https://github.com/apache/apisix/pull/12474
### Description When merging the configurations of service and route, APISIX will first perform a deepcopy on the configuration of the service. https://github.com/apache/apisix/blob/e3e5a99d0fab06d920707a8731401b72341aabfa/apisix/plugin.lua#L585-L586 This results in each route associated with this service getting an independent plugin configuration table, causing the cache in `batch-processor-manager.lua` that is based on table memory addresses as keys to not work properly. <!-- Please include a summary of the change and which issue is fixed. --> <!-- Please also include relevant motivation and context. --> #### Which issue(s) this PR fixes: <!-- *Automatically closes linked issue when PR is merged. Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`. --> Fixes # ### Checklist - [ ] I have explained the need for this PR and the problem it solves - [ ] I have explained the changes or the new features added to this PR - [ ] I have added tests corresponding to this change - [ ] I have updated the documentation to reflect this change - [ ] I have verified that this change is backward compatible (If not, please discuss on the [APISIX mailing list](https://github.com/apache/apisix/tree/master#community) first) <!-- Note 1. Mark the PR as draft until it's ready to be reviewed. 2. Always add/update tests for any changes unless you have a good reason. 3. Always update the documentation to reflect the changes made in the PR. 4. Make a new commit to resolve conversations instead of `push -f`. 5. To resolve merge conflicts, merge master instead of rebasing. 6. Use "request review" to notify the reviewer after making changes. 7. Only a reviewer can mark a conversation as resolved. --> -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
