Eric Coissac
5c1584967f
The command now supports reopening existing indexes instead of failing when the output file exists. Control flow branches between opening an existing index and constructing a new one, moving configuration setup exclusively to the creation path. Directory existence is enforced upfront with proper I/O error propagation. The --force flag retains its original semantics by removing the target directory before proceeding with a fresh build.
1.1 KiB
1.1 KiB
Coverage: implementation/merge.md
Code couvert
obikindex/src/merge.rs—KmerIndex::merge(), validation de compatibilité d'évidence,validate_evidence_compat()obikindex/src/partition/merge_layer.rs—merge_partition(), construction de la nouvelle layer, paramètreblock_bitsobikindex/src/partition/rebuild_layer.rs—rebuild_partition(), paramètreblock_bitsobikindex/src/layer/typed_layer.rs—Layer::append_genome_column()(PersistentCompactIntMatrix et PersistentBitMatrix)obicompactvec/src/intmatrix.rs—append_columnpour PersistentCompactIntMatrixobicompactvec/src/bitmatrix.rs—append_columnpour PersistentBitMatrix
Notes
FORT RISQUE DE DÉRIVE. Changements récents :
- Ajout de la validation de compatibilité d'évidence : merge exact+approx → erreur (OKIError::IncompatibleEvidence)
merge_partitionreçoit maintenantblock_bits: u8- La commande
reindexa été ajoutée comme outil de conversion exact↔approx avant merge Vérifier que la doc décrit la politique de merge mixed-evidence et le recours àreindex.