Querying BigQuant Factor Tables with Partition Filters

Summary

This note explains why querying an entire BigQuant factor table can fail with a permission error. The example selects dates, instruments, and a factor from a named table, then sorts the rows, but the query does not constrain the table's partitions. The error message identifies the issue as a requirement to specify a partition range, usually by date or instrument, through query filters.

For a genuinely necessary full-table scan, the message says to enable the full-scan option explicitly. The example is diagnostic rather than a trading method: it provides no factor definition, performance evidence, or advice on whether the factor is useful. Its guidance is limited to access and query scope, so users still need to select an appropriate partition range for their research task.

Key ideas

• Unfiltered queries against the example factor table may be rejected because they scan all partitions.
• Specify a partition range, commonly by date or instrument, in the query filters.
• Enable the full-scan option when a full-table scan is genuinely required.
• The note explains query access behavior and does not evaluate the factor's trading value.

Tags

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