Implement fetch(long) method.

ORCHID Critical service patch details

1. Describe issue impact on business: Data import receives some timeouts. In order to implement MODSOURMAN-989, FOLIO needs an additional method of fetching records from Kafka

2. What institutions are affected? (field “Affected Institutions” in Jira to be populated): All who use Data Import

3. What is the workaround if exists? None, Data import continues to be less efficient

4. What areas will be impacted by fix (i.e. what areas need to be retested): Confirm Data import Smoke and Critical path work as expected

5. Brief explanation of technical implementation and the level of effort (in workdays) and technical risk (low/medium/high):
   Purpose
   For Flow Control, we need a method to get a given number of records from Kafka.
   Approach
   Added implementation of fetch(long) method.
   Technical risk: Low

6. Brief explanation of testing required and level of effort (in workdays). Provide test plan agreed with by QA Manager and PO: After the MODSOURCE and MODSOURMAN patches are applied, we need to retest the Smoke and Critical Path Data Import tests (most of which are automated), and perhaps selected Extended Manual tests. Manual testing across these MODSOURCE and MODSOURMAN changes are likely 3-5 days of work for manual QA, plus some input from PO.

7. What is the roll back plan in case the fix does not work? Revert to previous version

NOLANA Critical service patch details

1. Describe issue impact on business: Data import receives some timeouts. In order to implement MODSOURMAN-989, FOLIO needs an additional method of fetching records from Kafka

2. What institutions are affected? (field “Affected Institutions” in Jira to be populated): All who use Data Import

3. What is the workaround if exists? None, Data import continues to be less efficient

4. What areas will be impacted by fix (i.e. what areas need to be retested): Confirm Data import Smoke and Critical path work as expected

5. Brief explanation of technical implementation and the level of effort (in workdays) and technical risk (low/medium/high):
   Purpose
   For Flow Control, we need a method to get a given number of records from Kafka.
   Approach
   Added implementation of fetch(long) method.
   Technical risk: Low

6. Brief explanation of testing required and level of effort (in workdays). Provide test plan agreed with by QA Manager and PO: After the MODSOURCE and MODSOURMAN patches are applied, we need to retest the Smoke and Critical Path Data Import tests (most of which are automated), and perhaps selected Extended Manual tests. Manual testing across these MODSOURCE and MODSOURMAN changes are likely 3-5 days of work for manual QA, plus some input from PO.

7. What is the roll back plan in case the fix does not work? Revert to previous version