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
Execution of queries may use PushdownFunction which seems to partition queries based on tablet locations on tablet servers. When using scan servers these locations are not very meaningful for query planning. Looking forward to Accumulo 4 where tables can load tablets into tablet servers on demand attempting to obtain the location of an ondemand tablet would break the current PushdownFunction code.
What changes should be made to this code to make it work well scan servers and eventually on demand tablets?
The text was updated successfully, but these errors were encountered:
Seems like this code path can be toggled on/off by configuration here. Would using the SequentialScheduler be a good option when using scan severs, or should another type of partitioning be created for scan servers in addition to what is there for tablet servers?
Execution of queries may use PushdownFunction which seems to partition queries based on tablet locations on tablet servers. When using scan servers these locations are not very meaningful for query planning. Looking forward to Accumulo 4 where tables can load tablets into tablet servers on demand attempting to obtain the location of an ondemand tablet would break the current PushdownFunction code.
What changes should be made to this code to make it work well scan servers and eventually on demand tablets?
The text was updated successfully, but these errors were encountered: