You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With pull queries we know we require bounds on ROWKEY and, optionally, WINDOWSTART.
Currently we compile such WHERE clauses on each qull query request. It would be nice if we could avoid this cost.
We can precompile these, but we'd need to a way to inject the value, i.e. the 'x' in WHERE ROWKEY='x', which is not currently possible. Alternatively, given we know these are simple expressions, we could just something other than compiled code.
The text was updated successfully, but these errors were encountered:
big-andy-coates
changed the title
Pull Queries: Use templated precompiled steps for expected WHERE clauses
Pull Queries: templated pre-compiled expected WHERE clauses
Oct 11, 2019
@big-andy-coates is this planned in the timeframe for november release? We did a small (unscientific) benchmark which seems to suggest a constant 5ms overhead on these queries.
Would be good to get this done before first release? Came up in a discussion with @derekjn@MichaelDrogalis
With pull queries we know we require bounds on ROWKEY and, optionally, WINDOWSTART.
Currently we compile such WHERE clauses on each qull query request. It would be nice if we could avoid this cost.
We can precompile these, but we'd need to a way to inject the value, i.e. the 'x' in
WHERE ROWKEY='x'
, which is not currently possible. Alternatively, given we know these are simple expressions, we could just something other than compiled code.The text was updated successfully, but these errors were encountered: