-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
expose limit to be configurable from UI / command line #1050
Comments
Please note few things:
It would be impossible to create one setting for this. And I'm afraid it will be very hard to understand what it really does. I much prefer to avoid unnecessary configurations - they have very high maintenance cost. |
With regard to point number 2 , where it can be customized ?
…On Thu, 16 Mar 2023, 18:30 Adrian Mróź, ***@***.***> wrote:
Please note few things:
1. The '100' is not a hardcoded value. Default limit for Splits is
chosen based on Dimension available limits.
2. Dimension limits are already customisable - each dimension can have
different limits.
3. Visualisations can affect limits so it is not set in stone.
It would be impossible to create one setting for this. And I'm afraid it
will be very hard to understand what it really does. I much prefer to avoid
unnecessary configurations - they have very high maintenance cost.
—
Reply to this email directly, view it on GitHub
<#1050 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAXXXNTANGJGZJOMKSNIV6LW4M5YVANCNFSM6AAAAAAV2BB2GI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
It's just property I see it's not in the documentation. I'll add it tomorrow! |
Hey any update on this , documentation change ? |
Documentation added in #1058 |
saw that on 1.39.0 the default limit is 100 for sort by
can we configure the default limit to be smaller .. so on the first query hit ..
query will not process 100 entries by default ..
default will be 100 , but in case limit value is provided it will overwrite the default value with the provided value
I asume smaller limit can improve performance ..in case user need smaller limit
The text was updated successfully, but these errors were encountered: