Zhen Ye da601d2a3c

fix: remove the streamingnode checking when loading segment (#45860) ...

issue: #43117
pr: #45859

If we enable checking when loading segments, all segment should always
be loaded by streamingnode but not 2.5 querynode, make some search and
query failure when upgrading. Otherwise, some search and query result
will be wrong when upgrading. We choose to disable this checking for now
to promise available search and query when upgrading.

also see pr: #43346

Signed-off-by: chyezh <chyezh@outlook.com>

2025-11-28 11:23:08 +08:00

..

action.go

feat: support dropping index without releasing collection (#42941)

2025-09-02 16:17:52 +08:00

executor.go

fix: remove the streamingnode checking when loading segment (#45860)

2025-11-28 11:23:08 +08:00

mock_scheduler.go

fix: mockery too unavailable after upgrade golang version (#41481)

2025-04-24 10:46:43 +08:00

OWNERS

Add OWNERS files for querycoordv2 sub pkgs (#23489)

2023-04-18 15:52:30 +08:00

scheduler.go

fix: executor/scheduler should be latest replica meta but not replica copy (#45878)

2025-11-28 08:49:08 +08:00

task_test.go

fix: executor/scheduler should be latest replica meta but not replica copy (#45878)

2025-11-28 08:49:08 +08:00

task.go

feat: support dropping index without releasing collection (#42941)

2025-09-02 16:17:52 +08:00

utils_test.go

fix: LoadSegment failed for dup field mmap.enabel props (#44465)

2025-09-22 14:40:06 +08:00

utils.go

fix: alter collection failed with MMAP setting for STRUCT [2.6] (#45240)

2025-11-04 20:25:37 +08:00