Skip to content

Update DecisionLog.md #2600

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Jul 20, 2021
Merged

Update DecisionLog.md #2600

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6826bd5
Update DecisionLog.md
16lim21 Jul 15, 2021
5bd6a0f
Merge branch 'master' into patch-2
zoewangg Jul 20, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 15 additions & 3 deletions docs/design/core/batch-utilities/DecisionLog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,6 @@

## Log Entry Template

* * *
**Source**: (Meeting/aside/pair programming discussion/daily standup) to (discuss/implement) X

**Attendees**: Anna-Karin, Irene, Dongie, Matt, Vinod, John, Zoe, Debora, Bennett, Michael
Expand All @@ -15,6 +14,20 @@

1. (Old/Reopened/new) Question?

## 7/15/2021

**Source:** Quick meeting to naming for batch utility

**Attendees:** Anna-Karin, Dongie, Matt, Vinod, John, Zoe, Debora, Bennett, Michael

**Closed Decisions:**

1. What should we name the batching utility to make it more discoverable and easy to understand? We will name it {Service}BatchManager. Since the batching utility operates on a low-level service client, it is not much of a utility. At the same time, it does not replace methods implemented by the low-level client so it is not an enhanced client either. It operates similarly to the TransferManager so we will name it BatchManager.

**Open Decisions:**

None

## 7/13/2021

**Source:** Follow-up meeting to discuss open decisions from last meeting and to address any new issues.
Expand All @@ -36,7 +49,6 @@

## 6/29/21

* * *
**Source:** Meeting to discuss initial design for Batch Utility: https://github.com/aws/aws-sdk-java-v2/pull/2563

**Attendees:** Dongie, Matt, Vinod, John, Zoe, Debora, Bennett, Michael
Expand All @@ -58,4 +70,4 @@
1. If not, how will Customers using `sendMessages()` correlate the request message with the response messages?
2. (New) Should we accept streams or iterators to `sendMessages()`?
1. Note: A decision on this runs counter to open decision #1. i.e. If we decide on a 1:1 correlation between request and response, we will not accept streams or iterators and vice versa.
3. (New) What should we name the batching utility to make it more discoverable and easy to understand?
3. (New) What should we name the batching utility to make it more discoverable and easy to understand?