The specified column query is invalid

[yangjinming1062]

Describe the bug
.
The fuzzy query lists some existing data, and then queries according to the id result but cannot find the content.

Expected behavior
How to find specific document.

Configuration:
Please provide:

1. quickwit --version: 0.3.1
2. The index_config.yaml
   

[fulmicoton]

I am not sure how to fix this but this is a UI bug.

The first screen is actually the wrong one.
The JSON API is returning a different value, but the browser, as it parses the JSON, uses a 64 bit float point, and cannot represent this number

One easy way to confirm is to run this in a browser console.

s = "{\"id\": 106698291236395745351}";
'{"id": 106698291236395745351}'
v = JSON.parse(s)
{id: 106698291236395750000}

Two workarounds in the meanwhile:

• Redo you test without using the UI. You can hit the API with query=*, get the real id, and run the search query with the correct id value.
• Index your id as a raw text.

You can also wait for us to come up with a fix :)

[yangjinming1062]

I am not sure how to fix this but this is a UI bug.

The first screen is actually the wrong one. The JSON API is returning a different value, but the browser, as it parses the JSON, uses a 64 bit float point, and cannot represent this number

One easy way to confirm is to run this in a browser console.

s = "{\"id\": 106698291236395745351}";
'{"id": 106698291236395745351}'
v = JSON.parse(s)
{id: 106698291236395750000}

Two workarounds in the meanwhile:

• Redo you test without using the UI. You can hit the API with query=*, get the real id, and run the search query with the correct id value.
• Index your id as a raw text.

You can also wait for us to come up with a fix :)

Thanks, I confim that is a BUG of UI

[fulmicoton]

I'll create a separate issue so we can track it.

[fulmicoton]

@yangjinming1062 thank you for all of the bug reports! It is really helpful for us.