How to specify start and end times?

[nalcabio-tom]

I see these in the source code in this repo, but I don't know how to overwrite them from the superset dashboard. These appear to default to the last ten minutes from now. Thanks!

[nalcabio-tom]

Whoops. I think I understand now. p_timestamp is expected to be in the query and this is used to extract the start and end times. We have our own timestamp so we weren't including p_timestamp.

[AdheipSingh]

@nalcabio-tom every event ingested into parseable has p_timestamp by default

[nalcabio-tom]

Yes, I understand that. What I still don't understand however is how to set the start and end times in the data that's sent to parsable by sqlalchemy-parseable: #8. These start and end times are sent in separate fields in the json payload posted to parseable. It's not enough to simply include them in the SQL query: https://www.postman.com/parseable/parseable/documentation/ds62z97/log-stream-query?entity=request-22353706-7b281b33-2f37-4034-9386-9a78e37b1db1

What appears to be the case, what prompted this particular issue, is that a SQL query in superset must include p_timestamp or else sqlalchemy-parseable won't send any start and end times to parseable? Or at least no data will ever be returned by parseable. For data to be returned, p_timestamp must be included in the SQL query somewhere. But no matter what time range is used in the SQL query with p_timestamp, only the last 10 minutes will ever be searched by parseable.

Would it be possible to specify start and end times some other way than by grepping for p_timestamp in the SQL query? Could this be done in a specially formatted comment, for example?