View definitions should permit specifying allowDiskUse:true and other aggregation options as part of the view.

The createView() command is just a wrapper for the create command That is why the view creation options are a subset of those available when creating collections, rather than those for aggregation statements.

When querying a view with an aggregate operation, users can specify allowDiskUse:true and non default values for allowDiskUse, cursor, maxTimeMS, and readConcern. But when querying a view with a find operation, users cannot do that.

When creating a view, I suggest allowDiskUse:true and perhaps some of the other aggregation options should be able to be included in the definition. The values for these fields would then become part of the aggregation statements generated for queries against the view.