[EXCONTRANS-329] Batches with multiple submissions only return one item Created: 27/Jan/20 Updated: 25/Mar/20 Resolved: 21/Feb/20 |
|
| Status: | Closed |
| Project: | Content Translation Extended (CTX) |
| Component/s: | Core |
| Affects Version/s: | 2.9, 3.0.1 |
| Fix Version/s: | 2.9, 3.0.2 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Richard Gange | Assignee: | Teresa Miyar |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
When we submit multiple nodes (ready batches) for translation in GLOBAL LINK PDF, all of them are correctly transfered to GLOBAL LINK Project Director with the executeSubmissionTranslationCommand job. Then we execute the next job executeGetTranslationCommand and this job/command is NOT working properly. If we send 2 batch items for translation to PD we expect 2 translated documents to be returned from Global Link PD to Magnolia CMS with this job (executeGetTranslationCommand). But the job/command returns only one document back because not all submitted items are processed but only one of them, which is processed multiple times (as much as we have SUBMITTED, IMPORTED… items for processing). Sometimes no translated document is returned at all to Magnolia although in Global Link PD submitted items exist that are ready for delivery back to Magnolia. The last scenario (when no document is returned) is because the first submission for processing has a status IMPORTED and then the rest of the items are not processed. We think there is a problem in the threading of the submissions in the CTSX module (all of the SubmissionThread's are working on one same submission). This should be fixed for the translation workflow to be able to return translated batches. |
| Comments |
| Comment by Ronald Kerstens [ 03/Feb/20 ] |
|
Hi,
This is the last bug we found while implementing the CTSX module for GlobalLink of translation.com or our customer Goudsmit. Can you please indicate when it will be fixed in the module, as this one currently impedes delivery of the translations.com interface an therefore content authoring and a golive of the new Goudsmit website. Thanks in advance
regards
ronald kerstens |
| Comment by Richard Gange [ 04/Feb/20 ] |
|
Hello ronald.kerstens- We will let you know as soon as it's ready. Cheers |
| Comment by Richard Gange [ 11/Feb/20 ] |
|
Hello ronald.kerstens- We have a new SNAPSHOT for this issue ready. 3.0.2-SNAPSHOT. Could you see if that resolves your problem? Thanks! |
| Comment by Ronald Kerstens [ 19/Feb/20 ] |
|
Hi Richard We have tested the 3.0.2 snapshot, but we seem to face the same issue: if we submit a batch for translation into multiple target languages (let say 2), the module job still retrieves only the first translation instead for GPD and then changes the job status to DELIVERED, effectively not retrieving the second translation from GPD. Ljubica will provide a detailed description of our test findings of the 3.0.2 snapshot, which I will add to this ticket. However, would it not be better if we setup a call to discuss this pending CTSX issue with you, Theresa, me and Ljubica? Can we arrange such a call on short notice? |
| Comment by Ronald Kerstens [ 19/Feb/20 ] |
|
The test findings/scenarios of Ljubica for implementing snapshot 3.0.2. I hope this helps to clarify the issue we are still facing: Hello, Unfortunately I'm still facing the same bug. This is my first test scenario:
My second testing scenario:
|
| Comment by Teresa Miyar [ 19/Feb/20 ] |
|
Hi, Let me review your test scenarios and get back to you, there is no problem to set up a call any time. |
| Comment by Teresa Miyar [ 19/Feb/20 ] |
|
It does not work for you because you run the command once, I do let the command in the scheduler to run every 2 minutes, after several runs I have all the documents translated, probably because of the asynchronous nature of this translation and also we have one submission per document while PD has a submission with several files. I need to investigate further, but maybe you can confirm that after several runs of the command all translations are back. |
| Comment by Teresa Miyar [ 19/Feb/20 ] |
|
Could you share the class nl.dept.magnolia.goudsmit.translationscom.TranslationsComCustomTranslator? |
| Comment by Ronald Kerstens [ 19/Feb/20 ] |
|
Hi Teresa, Ljubica has sent met TranslationsComCustomTranslator.java, which I have uploaded as an attachment. She is also going to e-mail you to set up a call to align on the issue, as she does not have access herself to Magnolia Jira to add comments etc. Thanks for the quick response regards |