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
{{ message }}
This repository has been archived by the owner on Jun 22, 2018. It is now read-only.
For a stored field, given the row key order of field/term - should be straight-forward.
A configurable scan limit can be given, that in turn refers to the number of unique terms across the given field to be sorted.
A reasonable default value can be placed, with expert level hints about the domain size of the field term ( number of unique terms ) given , that affects the memory on the regionservers and the performance of the scan query for sorting.
The text was updated successfully, but these errors were encountered:
For a stored field, given the row key order of field/term - should be straight-forward.
A configurable scan limit can be given, that in turn refers to the number of unique terms across the given field to be sorted.
A reasonable default value can be placed, with expert level hints about the domain size of the field term ( number of unique terms ) given , that affects the memory on the regionservers and the performance of the scan query for sorting.
The text was updated successfully, but these errors were encountered: