#!/bin/bash
# Read the file around line 220
wc -l lib/collection/src/shards/local_shard/telemetry.rs

#!/bin/bash
# Read the relevant section
sed -n '200,260p' lib/collection/src/shards/local_shard/telemetry.rs

#!/bin/bash
# Search for available_point_count method definition
rg -n 'fn available_point_count' --type rust

#!/bin/bash
# Search for methods in SegmentState or similar that provide point counts
rg -n 'available_point_count|point_count|points_count' --type rust -A 2 | head -50

#!/bin/bash
# Search for vector-specific count methods
rg -n 'fn.*vector.*count|fn.*available.*vector' --type rust | head -30

#!/bin/bash
# Read the implementation of available_point_count in entry.rs
sed -n '448,460p' lib/segment/src/segment/entry.rs

#!/bin/bash
# Read the implementation in entry_point.rs (trait definition)
sed -n '236,250p' lib/segment/src/entry/entry_point.rs

#!/bin/bash
# Search for multi-vector related tests or code
rg -n 'multi.*vector|optional.*vector' --type rust -i | head -20

#!/bin/bash
# Check if there's any mention of vector sparsity or optional vectors
rg -n 'sparse.*vector|optional.*vector|vector.*sparse' --type rust -B 2 -A 2 | head -40

#!/bin/bash
# Search for vector_data structure definition
rg -n 'struct VectorDataConfig|pub vector_data' --type rust -A 5 | head -50

#!/bin/bash
# Check the multi-vector test case
sed -n '421,480p' lib/shard/src/proxy_segment/tests.rs

#!/bin/bash
# Search for vector insertion/update validation
rg -n 'insert.*vector|add.*point' --type rust lib/segment/src/entry/ -A 3 | head -50

#!/bin/bash
# Check if there's any optional vector tracking or per-vector availability
rg -n 'available_vectors|vector_exists|has_vector' --type rust | head -20

#!/bin/bash
# Look at vector storage trait to understand how vectors are stored per point
rg -n 'fn get_vector|get_raw_vector' --type rust lib/segment/src/vector_storage/ -A 2 | head -50

#!/bin/bash
# Check if VectorStorage methods work per-vector or segment-wide
sed -n '1,100p' lib/segment/src/vector_storage/vector_storage.rs

#!/bin/bash
# Search for HasVectorCondition usage
rg -n 'HasVectorCondition|has_vector' --type rust -B 2 -A 2 | head -40

#!/bin/bash
# Check point insertion to verify if all vectors are required
rg -n 'upsert_point|insert_point' --type rust lib/segment/src/entry/ -A 5 | head -60

#!/bin/bash
# Check the id_tracker implementation to understand point lifecycle
sed -n '100,150p' lib/segment/src/id_tracker/id_tracker_base.rs

#!/bin/bash
# Verify that points are tracked at segment level, not per-vector
rg -n 'available_point_count|deleted_point_count' --type rust lib/segment/src/id_tracker/ -A 2 | head -40

#!/bin/bash
# Check the available_vector_count method in vector storage
rg -n 'fn available_vector_count' --type rust -A 2 | head -30

#!/bin/bash
# Look at the is_deleted_vector implementation to understand vector-level deletion
rg -n 'fn is_deleted_vector' --type rust -A 3 | head -40

#!/bin/bash
# Verify how vectors are updated/deleted independently from points
rg -n 'delete_vector|remove_vector' --type rust lib/segment/src/ -B 1 -A 2 | head -50

#!/bin/bash
# Check the full implementation of available_vector_count in segment_ops.rs
sed -n '624,635p' lib/segment/src/segment/segment_ops.rs

#!/bin/bash
# Verify the method is called in the entry.rs (SegmentEntry trait)
rg -n 'fn available_vector_count' lib/segment/src/entry/ -A 3

#!/bin/bash
# Check if available_vector_count is used elsewhere correctly
rg -n 'available_vector_count.*vector_name' --type rust | head -15