You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 17, 2024. It is now read-only.
Describe the bug
If you run a paperless-cli documents list on a large Paperless instance this will cause a serial lookup of the correspondent and each tag on that document because of what the Paperless API returns -- a link to the tag/correspondent and not it's name. This lookup should be optimized.
To Reproduce
Steps to reproduce the behavior:
paperless-cli documents list on a large paperless instance
You'll wait 2-3m for a response in the experience of my dataset.
Expected behavior
Implement some optimization so that this is completed faster.
Screenshots
n/a
Desktop (please complete the following information):
Version: 0.6.1
The text was updated successfully, but these errors were encountered:
* Added two map[int]string lookup tables to resolve correspondent/tag names and some helper functions: mapCorrespondents, mapTags, and urlToID to help fix#6.
* Added two map[int]string lookup tables to resolve correspondent/tag names and some helper functions: mapCorrespondents, mapTags, and urlToID to help fix#6.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugSomething isn't workingenhancementNew feature or request
Describe the bug
If you run a
paperless-cli documents list
on a large Paperless instance this will cause a serial lookup of the correspondent and each tag on that document because of what the Paperless API returns -- a link to the tag/correspondent and not it's name. This lookup should be optimized.To Reproduce
Steps to reproduce the behavior:
paperless-cli documents list
on a large paperless instanceExpected behavior
Implement some optimization so that this is completed faster.
Screenshots
n/a
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: