# Inconsistent behaviour of with\_where search

**URL:** <https://forum.weaviate.io/t/inconsistent-behaviour-of-with-where-search/4468>\
**Category:** Support\
**Tags:** bug\
**Created:** [October 8, 2024, 10:07am UTC](https://forum.weaviate.io/t/inconsistent-behaviour-of-with-where-search/4468 "2024-10-08T10:07:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lrx](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/lrx/32/2472_2.png) [@lrx](https://forum.weaviate.io/u/lrx)\
**Post date:** [October 8, 2024, 10:07am UTC](https://forum.weaviate.io/t/inconsistent-behaviour-of-with-where-search/4468/1 "2024-10-08T10:07:59Z")

</div>

### Description

Hello dear weaviate team,

I have came accross an issue using a with\_where simple query. Most of previous queries where succesful, without any problem, but somehow, regarding a handful of entries, I have the following behaviour:

Let’s say I do a simple filter query on my database, that contains, among others, infos on documents. (we focus here on their unique id (uid) and version (version))

```python3
res = (db_client.query
.get(    
    collection,
    ["uid","version"]
    )
.with_where(    
    {
        "operator": "And",
        "operands": [
        {            
             "path": ["uid"],
             "operator": "Equal",
             "valueText": "QXM8H7",
         }
        ]
    }
)
.do())
print(res)

```

The output is

```auto
{'data': {'Get': {'collection_name': [{'uid': 'QXM8H7', 'version': 'v2_14'}]}}}

```

but when I add a condition on the version

```python3
res = (db_client.query
.get(    
    collection,
    ["uid","version"]
    )
.with_where(    
    {
        "operator": "And",
        "operands": [
        {            
             "path": ["uid"],
             "operator": "Equal",
             "valueText": "QXM8H7",
         },
        {
            "path": ["version"],
            "operator": "Equal",
            "valueText": "v2_14"
        }
        ]
    }
)
.do())
print(res)

```

The output becomes

```auto
{'data': {'Get': {'collection_name': []}}}

```

So, what is happening here ? FYI,

- the tokenization used are both `word`, but I am looking or exact matches anyways, so it seems unlikely to be the cause.
- Both previous queries worked well on other documents
- The collection on which I’m performing queries contains around 990 000 entries, maybe the indexing method struggles with this many entries ?
- there are other “fields” (other than `uid` and `version`), around 30, but they aren’t all filterable nor searchable.

### Server Setup Information

- Deployment Method: Don’t have the details yet, custom installation
- Multi Node? No.
- Client Language and Version: Python 3.12.3 (API v3)
- Multitenancy? No.

### Any additional Information

Tell me if you need me to provide additional information

Thank you for your time!

---

<div class="post-metadata">

**Author:** ![lrx](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/lrx/32/2472_2.png) [@lrx](https://forum.weaviate.io/u/lrx)\
**Post date:** [October 31, 2024, 8:59am UTC](https://forum.weaviate.io/t/inconsistent-behaviour-of-with-where-search/4468/2 "2024-10-31T08:59:43Z")

</div>

behaviour fixed by improving the RAM of the server hosting the deployment.

---

<div class="post-metadata">

**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\
**Post date:** [October 31, 2024, 12:48pm UTC](https://forum.weaviate.io/t/inconsistent-behaviour-of-with-where-search/4468/3 "2024-10-31T12:48:00Z")

</div>

Oh Wow!

First thanks for sharing, @lrx

and secondly sorry, as we missed this message 😬

When you say improved, you mean you have increased weaviate allocated memory, right?

Can you share the version you are running? Even with less memory, this isn’t the expected behavior. 🤔