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
What is the difference in usage of allocator and pool passed to QueryCtx constructor?
Is the memory allocated by allocator used for temporary usage of operators while pool is used for allocating returnable buffers? In a previous commit, the allocator passed to QueryCtx was used in Task::addOperatorMemory which is why this appeared to be the case. In the most recent commit, the allocator seems to be only used for constructing ConnectorQueryCtx.
Is it on the roadmap to completely remove allocator argument in the QueryCtx? If so, is there another plan to allow passing separate pools for temporary and returnable allocations?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
What is the difference in usage of
allocator
andpool
passed toQueryCtx
constructor?Is the memory allocated by
allocator
used for temporary usage of operators whilepool
is used for allocating returnable buffers? In a previous commit, theallocator
passed toQueryCtx
was used inTask::addOperatorMemory
which is why this appeared to be the case. In the most recent commit, theallocator
seems to be only used for constructingConnectorQueryCtx
.Is it on the roadmap to completely remove
allocator
argument in theQueryCtx
? If so, is there another plan to allow passing separate pools for temporary and returnable allocations?Beta Was this translation helpful? Give feedback.
All reactions