Hi,
Is there any way to configure the row count threshold used to determine when a landing page query is 'expensive' and needs to be sent to the batch server?
I have a requester that queries the STOPREH table (>100k rows). Although the requester has a filter on the primary index and only returns less than 50 records, X3 thinks it is an 'expensive' landing page query and always sends it to batch whenever a user refreshes their landing page. I'm looking for a way for the query to be evaluated immediately and prevent it being sent to the batch server.
Thanks,
Martin