meddieCzl

I encountered the same issue. After some testing, it turns out that the problem isn't related to the number of documents exceeding 100, but rather arises when the filtered results...

@fatelei I upgraded to version 1.11.2, but the same issue persists—just the line numbers reporting errors have changed。The result of metadata status=2 in my document exceeds 100, and it is...

@fatelei > > [@fatelei](https://github.com/fatelei) I upgraded to version 1.11.2, but the same issue persists—just the line numbers reporting errors have changed。The result of metadata status=2 in my document exceeds 100,...

@fatelei I copied the code and tried, but there were still issues. 2025-12-30 11:04:34.251 INFO [ThreadPoolExecutor-1_0] [_client.py:1038] - HTTP Request: GET [http://weaviate:8080/v1/schema/Vector_index_859f7a62_ba64_4d35_9ce3_930881adc4b8_Node⁠](http://weaviate:8080/v1/schema/Vector_index_859f7a62_ba64_4d35_9ce3_930881adc4b8_Node) "HTTP/1.1 200 OK" 2025-12-30 11:04:34.276 INFO [ThreadPoolExecutor-1_0] [weaviate_vector.py:389]...

@fatelei weaviate-client==4.17.0 and the weaviate server version should == 1.27.0,Then LOG_LEVEL: debug has logs, but when the log level is error, there are no logs.

@fatelei I set LOG_LEVEL=debug, and the printed log only contains the following content.