search

metabase / metabase

The simplest, fastest way to get business intelligence and analytics to everyone in your company :yum:
https://metabase.com
Other
38.65k stars 5.13k forks source link

Feature : Configurable default limit #2328

Closed anthony-foulfoin closed 8 years ago

anthony-foulfoin commented 8 years ago

It would be great to be able to configure the default limit for pulses in the settings. 2000 is too much for me, and on large tables with a lot a columns it makes the ui freezing

agilliland commented 8 years ago

You are talking about the # of rows shown in the data table after running a query for Raw data correct?

Can I ask how many columns you have in the table you are viewing?

anthony-foulfoin commented 8 years ago

Yes that's correct. The table has 86 columns :s (

agilliland commented 8 years ago

Okay, that makes a lot of sense then. The 2000 row limit is likely not the problem in this case. We are using a data grid component for rendering tables which is generally pretty solid, but it is not very well optimized for tables with a large number of columns :disappointed: So it sounds like what you really want is to vote for this issue ... https://github.com/metabase/metabase/issues/664

anthony-foulfoin commented 8 years ago

done :)

mknippen commented 7 years ago

Is this still a possible feature? +1

sorrell commented 6 years ago

I would also love to see the row limit exposed to the user.

knes1 commented 6 years ago

Hi, I'm also voting for row limit exposed to the user for slightly different reason. My DB is highly normalized and we don't have OLAP database or ETL setup yet so we're using views for answering questions on joined data. If I give these views to my non-sql savvy users, they often run queries with all columns without any filters when exploring the data which are then slow to them. Limiting results to something like 300 might speed things up a bit in this case.