-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cache API requests #7
Comments
I think caching all the content on the server before doing the actual import is the only thing that helped me finally import all 8 years worth of Zendesk data. Even with max_execution_time set to 0, the PHP requests would fail after a certain amount of time and it would half import the data and on the next try it would start from scratch. In AttachmentMapper.php I used this replacement function:
And in Inserter.php I used:
I think it would be great if there if the import was broken into two steps:
If the copying took too long it could pick up where it left off easily. Import would also pick up where it left off by referencing help desk ids as it does now. The importer as it currently is, does not pick up where it left off as far as data retrieval from the help desk. |
It would be great if there was an option to cache API requests. Sometimes on large import it throws an error after a certain amount of time. Also API requests for most of these service desks are rate limited - for example Zendesk only allows 10 requests per minute! If the requests were cached on the file system it would make the next try quicker to pick up where it left off. Right now I am using something like this in my ApiController.
If there was a way to clear the cache that would be good too. And a way to reset the state of Awesome Support (delete all posts and all associated postmeta) just for the purposes of resetting an import.
The text was updated successfully, but these errors were encountered: