-
Notifications
You must be signed in to change notification settings - Fork 4.5k
adds back ErasureMeta::first_coding_index field #21623
adds back ErasureMeta::first_coding_index field #21623
Conversation
Codecov Report
@@ Coverage Diff @@
## master #21623 +/- ##
=========================================
- Coverage 81.6% 81.4% -0.2%
=========================================
Files 511 511
Lines 143320 143440 +120
=========================================
- Hits 116976 116856 -120
- Misses 26344 26584 +240 |
9b4b15c
to
5ce0c60
Compare
self.set_index..self.set_index + num_coding | ||
// first_coding_index == 0 may imply that the field is not populated. | ||
// self.set_index to be backward compatible. | ||
// TODO remove this once cluster is upgraded to always populate |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be good to create an issue as a reminder to track this and other TODOs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, already have draft follow up changes.
There is no harm in keeping this code as is, until those upcoming changes are ready to go.
I just need to merge this commit in an earlier release to avoid any compatibility issues.
let first_coding_index = if self.first_coding_index == 0 { | ||
self.set_index | ||
} else { | ||
self.first_coding_index | ||
}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice, this was pretty subtle to maintain backwards compatibility
solana-labs#16646 removed first_coding_index since the field is currently redundant and always equal to fec_set_index. However, with upcoming changes to erasure coding schema, this will no longer be the same as fec_set_index and so requires a separate field to represent.
5ce0c60
to
282f10d
Compare
#16646 removed first_coding_index since the field is currently redundant and always equal to fec_set_index. However, with upcoming changes to erasure coding schema, this will no longer be the same as fec_set_index and so requires a separate field to represent. (cherry picked from commit 49ba09b) Co-authored-by: behzad nouri <[email protected]>
#16646 removed first_coding_index since the field is currently redundant and always equal to fec_set_index. However, with upcoming changes to erasure coding schema, this will no longer be the same as fec_set_index and so requires a separate field to represent. (cherry picked from commit 49ba09b) # Conflicts: # ledger/src/blockstore.rs
…2912) * adds back ErasureMeta::first_coding_index field (#21623) #16646 removed first_coding_index since the field is currently redundant and always equal to fec_set_index. However, with upcoming changes to erasure coding schema, this will no longer be the same as fec_set_index and so requires a separate field to represent. (cherry picked from commit 49ba09b) # Conflicts: # ledger/src/blockstore.rs * removes mergify merge conflicts Co-authored-by: behzad nouri <[email protected]>
Problem
#16646
removed first_coding_index since the field is currently redundant and
always equal to fec_set_index.
However, with upcoming changes to erasure coding schema, this will no
longer be the same as fec_set_index and so requires a dedicated field to
represent.
Summary of Changes
ErasureMeta::first_coding_index
.ErasureMeta
construction andfec_set_index
.