[BUG] [SOURCE COLLECTION] during source collection, both i18n & l10n write same translation bundle when translations are in central place
@tigershi is already working on this.
Since Sep 23, 2021.
- Dominant language
- Java
- Stars
- 72
- Forks
- 69
- Avg merge
- 23h 32m
- Merged PRs (30d)
- 4
Description
Describe the bug
Preconditions：
Translation bundle are in stored in central place(like AWS S3), so i18n service will get translation from it and l10n service will write English source to it.
Description:
Based on precondition, in current process, when customer call source collection API, l10n service will write English source to translation bundle. But at that time, i18n service does not know about the new source collected. So, l10n service have to call i18n service to write same source to translation bundle again, the purpose is just to clean i18n service local cache.
Expected behavior
Write source twice is wasted for both S3 cost and Singleton instance resource, specially when source content are huge.
It is better for l10n to send a small call to i18n service to clean cache.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.