Open lndigoIife opened 1 week ago
Hey @lndigoIife, I'm here to help you with this bug report. I'm a bot designed to assist with bug fixes, answer questions, and guide you to become a contributor. Let's work together to resolve this issue.
I found a similar closed issue regarding the row limit being hardcoded at 100,000 in the UI. This issue was resolved by a pull request that fixed the hardcoded row limit [1]. However, the specific changes made in the pull request and how they relate to the "Maximum call stack size exceeded" error are not detailed in the available information.
To address the "Maximum call stack size exceeded" error, you might want to consider the following:
Optimize Query Performance: Ensure that your database can handle large queries efficiently. This might involve indexing, query optimization, or using materialized views.
Adjust Configuration Settings: Check if there are any configuration settings related to memory or stack size that can be adjusted to better handle large datasets.
Limit Data Processed: Consider reducing the number of rows processed at once or using pagination to handle large datasets more effectively.
These steps can help mitigate issues when working with large datasets in Superset.
To continue talking to Dosu, mention @dosu.
Bug description
Screenshots/recordings
Superset version
4.0.2
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist