Fixing Partition-Range Errors in BigQuant Stock Data Queries

Summary

This forum post documents a PermissionException encountered when a copied visual stock-selection strategy runs a BigQuant query. The generated SQL joins daily stock bars with basic information, factor, and status tables, then applies universe and factor filters. The query fails because it accesses the partitioned daily bar table without specifying a partition range through the query’s filters argument. The error message shows a date-range filter as an example and notes that full-table access requires explicitly enabling full database scans.

The post is useful as a data-access troubleshooting example: query-level restrictions can apply to tables brought into a generated query through upstream modules, even when a later factor expression uses another table. The excerpt does not show a confirmed fix, a successful rerun, or performance implications. The displayed full-scan flag appears in a separate SQL example and does not establish that it resolves the failing module’s permission check; the appropriate remedy depends on how that module passes filters and scan settings.

Key ideas

• BigQuant can reject queries against the daily stock-bar table when partition bounds are missing.
• The error recommends supplying a partition filter, commonly by date or instrument.
• The failing generated query joins daily bars with stock metadata, factors, and status information.
• A full database scan may require an explicit setting, but the post does not confirm a successful resolution.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.