#community-help

Handling Multiple Dates Search with Unix Timestamp in Int64

TLDR Akashchellakumar asked how to search multiple dates with Unix timestamp in int64. Kishore Nallan suggested inter-field filtering and storing timestamps as array of int64 or strings. Akashchellakumar thanked and agreed to try this method.

12mo

Join the chat

Oct 12, 2022 (12 months ago)

Photo of md5-f291ced1bc3cf23e7631bc5253ffb9dc

Akashchellakumar

06:59 AM

Hello guys,
How to handle multiple dates search using Unix timestamp with int64 data type?
Example :
• I have two different booked date slots for the car rental document (Oct 1 to Oct 10
Oct 21 to Oct 30).
• I need to fetch the same car rental document which is available on the specific date(Oct 11 to Oct 20).

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

07:13 AM

Hmm, this is like an inter-field filtering. Currently we don't have a way to do that. Filtering is applied at a global field context.

Akashchellakumar

07:21 AM

Kishore Nallan Global field context in the sense?

Kishore Nallan

07:27 AM

The filtering looks at all documents matching a value for a field. When you have a range like this, what we really need to do is to apply the filter within that document so that both the start and end date ranges match to the same document.

07:30

Kishore Nallan

07:30 AM

You could try storing the timestamps of each individual day that the car is booked as an array of int64. That way, this car in your example will have 20 values in the array.

Then when you search for the availability of a given date, you have to do != search.

07:30

Kishore Nallan

07:30 AM

But we currently don't support != on numerical fields yet.

07:30

Kishore Nallan

07:30 AM

So you could store the timestamps as string.

07:31

Kishore Nallan

07:31 AM

So a car could have:

"timestamps": ["A", "C", "D"]

where a, c, and d are timestamps as string. Now if you want to check availability for "B", you will do filter_by=timestamps:!=B

Akashchellakumar

07:37 AM

Kishore Nallan Thanks for your clarification, Will try it out and get back to you.

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2779 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Using Multisearch To Filter String Timestamps

Farid asked how to filter string timestamps with multisearch. Kishore Nallan advised indexing the timestamps as int64 for comparison.

13mo

UNIX Timestamps and Search Condition Operators

Eshwar asked about using `<=` `>=` operators for a date field search option. Jason confirmed the operators but asked for curl commands to replicate the issue.

1mo

Fuzzy Search Restrictions and num_typos Extension Request

Ashwin seeks to limit the fields covered by fuzzy search and wants specification of typo tolerance per field. Kishore Nallan suggests num_typos syntax to control the behavior, with Ashwin agreeing and planning to raise a related issue on Github. Jason advises on comparing integer time stamps for InstantSearch usage.

31mo

Efficient Method to Find Records at Interval Timestamps

Dan asked for an efficient method for counting frequency of record intervals. Jason suggested using multi_search or creating a new field for each record.

16mo

Multiple Filters and JSON Requests in Typesense

Manish asked about multiple filter_by arguments, JSON input, and using multisearch. Jason offered typesense documentation links, examples, and how to use JSON formatted requests with multisearch. Ed shared a similar use case.

3mo