You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For deeply nested queries, Plywood by default spawns up to 500 queries and this is a root cause of incomplete results, really hard to spot. The results from N-th row on the most deeply dimension(s) contain only "undefined" due to missing/skipped results.
returnnull;// Query limit reached, don't do any more queries.
I fully understand that limit is pretty high and could be changed via API but when the limit is reached I would expect an exception from Plywood rather than silently skipping queries/results. It gives me a clue that something is wrong with my query.
Also, I'm considering switching to regular "group by" query instead of tons of "top N" queries for deeply nested Plywood expressions. Is it possible with current Plywood version?
The text was updated successfully, but these errors were encountered:
For deeply nested queries, Plywood by default spawns up to 500 queries and this is a root cause of incomplete results, really hard to spot. The results from N-th row on the most deeply dimension(s) contain only "undefined" due to missing/skipped results.
plywood/src/expressions/baseExpression.ts
Line 1742 in 5d2ee0c
I fully understand that limit is pretty high and could be changed via API but when the limit is reached I would expect an exception from Plywood rather than silently skipping queries/results. It gives me a clue that something is wrong with my query.
Also, I'm considering switching to regular "group by" query instead of tons of "top N" queries for deeply nested Plywood expressions. Is it possible with current Plywood version?
The text was updated successfully, but these errors were encountered: