Comments (4)
It looks like the discrepancy in row limits you're encountering could be due to different settings or contexts within your application. Here's a more focused approach to address your issue:
-
Review Component Settings: Ensure that all instances where the row limit is applied in your application are consistent. Different parts of your application might have different row limits set for performance or analysis purposes.
-
Configuration and Defaults: Check your application's configuration settings. For Apache Superset, for example, the default row limit can be adjusted in the
superset/config.py
file by modifying theROW_LIMIT
variable. -
Understand Contextual Use: The difference in row limits might be intentional, based on the functionality of different parts of your application. For instance, one section might limit data display for quick performance, while another allows more data for in-depth analysis.
-
Adjust Limits if Necessary: If the varying limits are not intentional and cause confusion, consider harmonizing them across your application to ensure a consistent user experience.
The components like RowCountLabel
and QueryLimitSelect
in Apache Superset are designed to inform users about the number of rows returned and allow them to select query limits. These components do not directly affect the overall row limit but serve to enhance user interaction and understanding of data limits.
If filtering is causing confusion due to the row limit, remember that filtering actions only affect the visible subset of data and do not fetch additional data to meet the row limit. This means the displayed data after filtering is still within the initial fetch limit, not extending to the maximum row limit unless explicitly fetched.
If you need further assistance or clarification, feel free to ask.
Details
Sources
- SQL Lab Row Limit feature request / Bug fix
- Superset Inconsistent with SQL LAB csv downloads
- superset-frontend/src/explore/components/RowCountLabel/RowCountLabel.test.tsx
- superset/config.py
- superset-frontend/src/SqlLab/components/QueryLimitSelect/QueryLimitSelect.test.tsx
- superset-frontend/src/explore/components/RowCountLabel/index.tsx
- superset-frontend/src/SqlLab/components/ResultSet/index.tsx
- superset-frontend/src/SqlLab/components/QueryLimitSelect/index.tsx
- superset-frontend/plugins/plugin-chart-handlebars/src/plugin/controls/limits.ts
- superset/sql_lab.py
- superset-frontend/packages/superset-ui-core/test/query/buildQueryObject.test.ts
About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.
Help me be more useful! Please leave a π if this is helpful and π if it is irrelevant.
To continue the conversation, mention @dosu.
from superset.
Hello,
Thank you for the clarifications provided.
There are several ways to limit the number of rows :
- config.py : ROW_LIMIT, DISPLAY_MAX_ROW (maybe others)
- the drop-down list in SQLLAB
The drop-down list could take the most restrictive of these variables as its maximum value.
Thus the user would make a choice that is always achievable.
This would also avoid having a surprising error message.
Currently the message tells the user to modify their query by adding a limit or a filter to display 100,000 values ββeven though they will technically never be able to reach this number of rows.
Sincerely
from superset.
Dosu is almost right. There is a ROW_LIMIT
config, but that's for chart data.
The error you see right there in the UI, however IS correct.
DISPLAY_MAX_ROW
in config.py
is set by default to 10,000, and that's the limit you're hitting, just like it says. You can raise it in your config if you'd like.
Admittedly, it's not a great experience that the UI even shows higher than you're allowed to request... maybe that Select menu should look up and respect the DISPLAY_MAX_ROW
setting, and/or display it in a tooltip so the user is more aware of it. If you feel like opening a PR to make it better, that would be cool!
from superset.
If you want to propose a change, and/or open a PR to that effect, I think folks would be supportive!
from superset.
Related Issues (20)
- Inconsistencies in the handling of misspelled URLs HOT 2
- AttributeError: 'Template' object has no attribute 'strip' HOT 3
- Embedded view shows only [Error: column "string" does not exist] HOT 2
- bug when updating chart /api/v1/chart/{pk} HOT 2
- Missing prefix in URLs of scripts and CSS files when STATIC_ASSETS_PREFIX config is set HOT 2
- Set Specific Time for Dashboard Refresh HOT 7
- Forbidden error when selecting database from Dataset creation or SQLab HOT 4
- Drill By Modal window disappear when chart is not in view in embedded mode HOT 4
- superset.exceptions.SupersetErrorsException: [SupersetError(message='questdb error: QuestDbEngineSpec.execute() takes 3 positional arguments but 4 were given', error_type=<SupersetErrorType.GENERIC_DB_ENGINE_ERROR: 'GENERIC_DB_ENGINE_ERROR'>, level=<ErrorLevel.ERROR: 'error'>, extra={'engine_name': 'QuestDB', 'issue_codes': [{'code': 1002, 'message': 'Issue 1002 - The database returned an unexpected error HOT 15
- An error occurred while rendering the visualization: TypeError: o.getTime is not a function HOT 2
- Dockerfile parse error line 40: Unknown flag: mount HOT 8
- [docker compose] Can't change default metadata database password HOT 7
- Starrocks executing a specific query will cause the Query history page to report an error and not load the data HOT 3
- Viz Plugin is not building anymore HOT 3
- Cant save Dataset with params HOT 6
- Cache setting Redis, still reporting exception upon startup! HOT 3
- Without "can write on DashboardPermalinkRestApi", a click on a anchor (tabs or header) redirect to login page HOT 1
- Without "can time range on Api", a click on a custom filter redirect to login page HOT 3
- Cannot generate translations HOT 2
- GET /api/v1/report/slack_channels is being called with ALERT_REPORT_SLACK_V2 off
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from superset.