How to avoid Slow Filter or million limit reached
Options
Harald Hotz-Behofsits
Member Posts: 157
At the end both may have the same root cause.
If there is a filter query doing a downstream or upstream check having no restrictions on the project to search in.
In jama instances with millions of items this might result in long response times or million limit error messages.
How to restrict a subquery on a project, as project(s) are not selectable?
Ad into the subquery a check for ID contains projectkey*, then this subquery will only search in projects starting with that projectkey resulting in a quick response and avoiding the million error message.
If there is a filter query doing a downstream or upstream check having no restrictions on the project to search in.
In jama instances with millions of items this might result in long response times or million limit error messages.
How to restrict a subquery on a project, as project(s) are not selectable?
Ad into the subquery a check for ID contains projectkey*, then this subquery will only search in projects starting with that projectkey resulting in a quick response and avoiding the million error message.
0
Comments
-
Hi Harald,
I have exactly this problem -> I have submitted a feature request here https://community.jamasoftware.com/product-ideas-suggest/ideation-home/viewidea?IdeationKey=2f2c3a73-748a-458e-a770-6b7181191e18
Workaround : at the end of the day I am working with SQL queries for myself. Non-Admin users get a custom BIRT report for this.
Best,
AlessandroAlessandro
Systems Engineer
SICK AG0
