Handling uint64 in Typesense
TLDR JinW inquired about handling uint64 in Typesense. Jason suggested using strings or reducing the granularity of values. Meanwhile, Harrison raised a point about database types.
Apr 14, 2022 (17 months ago)
JinW
12:12 AMJason
12:13 AMJinW
12:13 AMJason
12:14 AMJason
12:15 AMJason
12:16 AMJinW
12:27 AMHarrison
08:03 AMTypesense
Indexed 2764 threads (79% resolved)
Similar Threads
Discussion on Capacity to Represent BigInt
ilia inquired about adding unsigned int64 for BigInt representation. Kishore Nallan suggested no immediate plans, but highlighted a workaround and also warned about misusing float for large values.
Posting int64 values to API using JSON in Typesense
Patrick requested assistance in posting an int64 document to an API using JSON with Typesense due to JSON's large number limitations. Jason clarified the JSON library at Typesense does support int64.
Resolving Typesense Cloud and Firebase Timestamp Error
Eoin faced an issue with Firebase timestamp when setting up Typesense Cloud. Jason suggested converting timestamps to Unix and sync them as int64 fields in Typesense.
Typesense Non-String Field Query Workarounds
Carl seeks advice on querying non-string fields in Typesense. Kishore Nallan suggests using a string version, and Jason proposes the string* data type. Carl is considering these options.

Troubleshooting Typesense Document Import Error
Christopher had trouble importing 2.1M documents into Typesense due to memory errors. Jason clarified the system requirements, explaining the correlation between RAM and dataset size, and ways to tackle the issue. They both also discussed database-like query options.

