Optimize tag and lock fetching when doing searches #519

New issue

Closed

opened 2025-12-28 17:37:40 +00:00 by sami · 0 comments

sami commented

2025-12-28 17:37:40 +00:00

Owner

Originally created by @roman-khimov on GitHub (May 6, 2025).

Originally assigned to: @smallhive on GitHub.

I'm always frustrated when we do requests we don't need. n.comprehensiveSearchAllVersionsInNeoFS or n.searchTagsAndLocksInNeoFS both have lock/tag OIDs after their searches, but we don't utilize them and doing n.GetObjectTagging and n.getLockDataFromObjects again in ComprehensiveObjectInfo() (likely in other places as well).

Describe the solution you'd like

For locks we can request lock-specific attributes and be done with it, that's everything needed.
For tags just reuse known tag OIDs and GET them, do not SEARCH again.

Originally created by @roman-khimov on GitHub (May 6, 2025). Originally assigned to: @smallhive on GitHub. ## Is your feature request related to a problem? Please describe. I'm always frustrated when we do requests we don't need. `n.comprehensiveSearchAllVersionsInNeoFS` or `n.searchTagsAndLocksInNeoFS` both have lock/tag OIDs after their searches, but we don't utilize them and doing `n.GetObjectTagging` and `n.getLockDataFromObjects` again in `ComprehensiveObjectInfo()` (likely in other places as well). ## Describe the solution you'd like 1. For locks we can request lock-specific attributes and be done with it, that's everything needed. 2. For tags just reuse known tag OIDs and GET them, do not SEARCH again.