pushshift / api

Pushshift API
1.3k stars 111 forks source link

`after` not respected when querying multiple ids #80

Open phipsgabler opened 3 years ago

phipsgabler commented 3 years ago

Have a look at this query: https://api.pushshift.io/reddit/comment/search/?ids=t1_gsymlgi,t1_gsytbi5,t1_gsuoodr&fields=created_utc&after=1617230175&before=1617314400&sort_type=created_utc&metadata=True&limit=497

It correctly returns the three comments sorted by created_utc, the last of which is 1617230175. However, it did not respect the after=1617230175 at all, which should have filtered out all three!

Since the metadata of the query is also quite unlike everything else I have seen before (not containing timed_out or shards), I suspect this is due to a different engine than ElasticSearch being used?