Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
 
Answered
Set timeout per q2_request or per extension?

I see in the docs that q2_requests timeouts can be set at the Environment level. Is it possible to set a timeout for a specific request, or even set it just for a single extension? From what I can tell, q2_requests is largely a wrapper for python's Requests library, which does appear to let you set the timeout on a specific request, but I don't see anything in the SDK docs to confirm if q2_requests supports that.

Posted 3 years ago
Votes Newest

Answers


Hi Steven,

q2_requests wraps python's request library so it will have the same interface with the added benefit of logging and asynchronous call handling. Anything you have in the python request library documentation will also be applicable to q2_requests. You can set a timeout the way you normally would and expect it to behave the same way. We also provide the ability to set timeouts at the environment level (the default is 30 seconds), but I believe that would be applicable to all of your extensions
 

135 Views
1 Answer
3 years ago
3 years ago
Tags