about i64,u64 Maximum problem

[yangshike]

I have one number: 1678363872408121344

When I set the field to u64 and save it to quickwit, it becomes 1678363872408121300

How should I set this field property correctly

[fulmicoton]

Your ticket is incomplete. What do you mean exactly by "it becomes"?
How do you consume that value?

Is it aggregation?

[yangshike]

The last two digits have become 0, as if they have been truncated. It looks like it has exceeded the maximum supported value

[fulmicoton]

@yangshike This is not my question. Where do you see the values? Is it in the stored docs? Is it when you search for the values? Is it when you run an aggregation?

Even better: can you provide code to reproduce?

[yangshike]

in kafka source: {"fastId":1678358612977389568}
this is my quickwit config:
- name: fastId
type: u64
fast: true
indexed: true
Through quickwit ui：

I saw the fastId change to:
"fastId": 1678358612977389600

568 in the last three places becomes 600

[fulmicoton]

How do you get the query ? Is it an aggregation? We do cast all nums to f64 in aggregation .

If so can you send the specific type of aggreg you would like to see fixed?

[PSeitz]

Wasn't there an ui rendering issue for very large numbers? @fmassot

[yangshike]

I searched through the UI and it should be a collection. I just tried it out and found it through fastId: 1678358612977389568

Can search for this record, but when displayed on the UI, it shows 1678358612977389600

If it's just for display reasons, then this is not a problem

[fmassot]

@PSeitz I think so indeed.

@yangshike I think this is related to this issue #2013

[yangshike]

Okay, thank you very much！