Remaining chunk/bundle work
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Based on the following:
(master)$ gack max_chunk_
Open-ILS/
1447: max_chunk_count => 1
1790: max_chunk_count => 1
1847: max_chunk_count => 1
Open-ILS/
242: $client-
806: $conn->
908: $conn->
Open-ILS/
38: max_chunk_size => 0,
Open-ILS/
16: max_chunk_size => 0,
Open-ILS/
545: max_chunk_size => 0,
It looks like there are a couple places where we need to realign terminology, and we should probably do this for EG 3.0 since it will definitely require OpenSRF 2.5+ ... Specifically, I believe max_chunk_count needs to become max_bundle_count, and "max_chunk_size => 0" should become "max_bundle_count => 1" to have the desired effect.
I do not believe OpenSRF requires any change.
Changed in evergreen: | |
milestone: | 3.0-beta → 3.0-beta2 |
Changed in evergreen: | |
milestone: | 3.0-beta2 → 3.0-rc |
Changed in evergreen: | |
milestone: | 3.0-rc → 3.0.1 |
Changed in evergreen: | |
milestone: | 3.0.1 → 3.0.2 |
Changed in evergreen: | |
milestone: | 3.0.2 → 3.0.3 |
Changed in evergreen: | |
milestone: | 3.0.3 → 3.0.4 |
Changed in evergreen: | |
milestone: | 3.0.4 → 3.05 |
Changed in evergreen: | |
milestone: | 3.0.5 → 3.0.6 |
Changed in evergreen: | |
milestone: | 3.0.6 → 3.0.7 |
Changed in evergreen: | |
milestone: | 3.0.7 → 3.0.8 |
Changed in evergreen: | |
milestone: | 3.0.8 → 3.0.9 |
Changed in evergreen: | |
milestone: | 3.0.9 → 3.0.10 |
Changed in evergreen: | |
milestone: | 3.0.10 → 3.0.11 |
Changed in evergreen: | |
milestone: | 3.0.11 → 3.0.12 |
Changed in evergreen: | |
milestone: | 3.0.12 → 3.2.0 |
Changed in evergreen: | |
milestone: | 3.2.0 → 3.2.1 |
Changed in evergreen: | |
milestone: | 3.2.1 → 3.2.2 |
Changed in evergreen: | |
milestone: | 3.2.2 → 3.2.3 |
Changed in evergreen: | |
milestone: | 3.2.3 → 3.3-beta1 |
Changed in evergreen: | |
milestone: | 3.3-beta1 → 3.3-rc |
Changed in evergreen: | |
milestone: | 3.3-rc → 3.3.1 |
Changed in evergreen: | |
milestone: | 3.3.1 → 3.3.2 |
Changed in evergreen: | |
milestone: | 3.3.2 → 3.3.3 |
Changed in evergreen: | |
milestone: | 3.3.3 → 3.3.4 |
Changed in evergreen: | |
milestone: | 3.3.4 → 3.3.5 |
Changed in evergreen: | |
milestone: | 3.3.5 → 3.4.2 |
Changed in evergreen: | |
milestone: | 3.4.2 → 3.4.3 |
Changed in evergreen: | |
milestone: | 3.4.3 → 3.4.4 |
Changed in evergreen: | |
milestone: | 3.4.4 → 3.5.1 |
Changed in evergreen: | |
milestone: | 3.5.1 → 3.5.2 |
Changed in evergreen: | |
milestone: | 3.5.2 → 3.6.1 |
tags: | added: cleanup |
Changed in evergreen: | |
milestone: | 3.6.1 → 3.6.2 |
Changed in evergreen: | |
milestone: | 3.6.2 → 3.6.3 |
Changed in evergreen: | |
milestone: | 3.6.3 → 3.6.4 |
Changed in evergreen: | |
milestone: | 3.6.4 → 3.7.2 |
status: | New → Confirmed |
no longer affects: | evergreen/3.1 |
no longer affects: | evergreen/3.2 |
no longer affects: | evergreen/3.3 |
no longer affects: | evergreen/3.4 |
no longer affects: | evergreen/3.5 |
Changed in evergreen: | |
milestone: | 3.7.2 → 3.7.3 |
no longer affects: | evergreen/3.6 |
Changed in evergreen: | |
milestone: | 3.7.3 → none |
Note: This is unrelated to, but precipitated from initial investigation into, bug 1709710.