Running scripts with a size bigger than 15KB (Where supposedly the limit we have is 1MB)
Save queries where big tables are called
To me it seems that the something somewhere is trying to save computational/processing effort, but it comes from the product (MB) and not changes in the way we work.
Hi @perfuses
The problem comes from your reverse-proxy in front of Metabase, not Metabase itself.
You are using Nginx, so you'll need to make sure the configuration can handle what you need.
I'm working as data scientist and not data engineer, and I'm not fully familiar with the concept.
(1) Do you mean that MB runs behind the reverse-proxy, so the script size is maxed out via Nginx configuration? (2) Could you describe what is Nginx in simple terms?
(3) What about saving queries? Would the problem come from the same source (Nginx configuration)?
After some checks, I've found that we use Beanstalk. This NGINX is set up automatically with the software that MB people offer on the website.
Therefore, agreed, the mistake does not seem to be from the product. Still it's still something that people from MB has done instead of coming from the configuration.
We use the last version of Metabase. Checked. We're investigating this further.