Maximum number of rows to fetch - filter already applied

Regarding “maximum number of rows to fetch” in Data. Is this the raw data fetched or after filter applied?
For example we have 1 week of data for 2M records, if the maximum is raw fetched so we never get the full picture data. I believe it is the latter which filter is already applied (limit XXX in SQL)

Please help confirm.
Thank you very much.

@Stima_Livingpresent are you referring to the maximum rows to fetch option inside the Filter settings?

No, it is the maximum rows in data

Thank you very much.

@Stima_Livingpresent this is essentially another way to set a LIMIT statement for the query. Normally for Table Visuals the limit starts at 100, and then if you clear out that limit it will use a the default “Maximum number of rows to fetch” limit of 5000 so that you don’t fetch the entire set of rows from the table. Your query will scan the entire table, but the result set will be limited to either this value or possibly the limit that sets below the Visual shelves if you’re using a table visual. Normally you don’t want to set this limit very high as it will slow down performance, and also it may be difficult to digest that many data points in a single Visual.

This article also has more details on limits inside of Arcadia if you’re interested.