Tekijä | SHA1 | Viesti | Päivämäärä |
---|---|---|---|
Matthias Sohn | 53160ee12b |
Externalize error message in ReftableWriter#throwIllegalEntry
Also use MessageFormat as done elsewhere. Change-Id: I36a4df9002310fa28321de9d325ee213f3cbd433 Signed-off-by: Matthias Sohn <matthias.sohn@sap.com> |
4 vuotta sitten |
Han-Wen Nienhuys | 9f9163cbca |
reftable: enforce ordering for ref and log writes
Previously, the API did not enforce ordering of writes. Misuse of this API would lead to data effectively being lost. Guard against that with IllegalArgumentException, and add a test. Change-Id: I04f55c481d60532fc64d35fa32c47037a03988ae Signed-off-by: Han-Wen Nienhuys <hanwen@google.com> |
4 vuotta sitten |
Matthias Sohn | 43e26de7ec |
Fix javadoc in org.eclipse.jgit storage/reftable package
Change-Id: I14764c5d5b2309d82fe2ccc0593120b51328bf41 Signed-off-by: Matthias Sohn <matthias.sohn@sap.com> |
6 vuotta sitten |
Shawn Pearce | 44a75d9ea8 |
reftable: explicitly store update_index per ref
Add an update_index to every reference in a reftable, storing the exact transaction that last modified the reference. This is necessary to fix some merge race conditions. Consider updates at T1, T3 are present in two reftables. Compacting these will create a table with range [T1,T3]. If T2 arrives during or after the compaction its impossible for readers to know how to merge the [T1,T3] table with the T2 table. With an explicit update_index per reference, MergedReftable is able to individually sort each reference, merging individual entries at T3 from [T1,T3] ahead of identically named entries appearing in T2. Change-Id: Ie4065d4176a5a0207dcab9696ae05d086e042140 |
6 vuotta sitten |
Shawn Pearce | 0ecc8367e6 |
reftable: create and write reftable files
This is a simple writer to create reftable formatted files. Follow-up commits will add support for reading from reftable, debugging utilities, and tests. Change-Id: I3d520c3515c580144490b0b45433ea175a3e6e11 |
7 vuotta sitten |