Skip to content

DOCS-11663 queries on views implementation (#6115) #6119

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 10, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions source/includes/extracts-views.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,23 @@ content: |
- If the aggregation pipeline used to create the view suppresses the
``_id`` field, documents in the view do not have the ``_id`` field.

When you query a view, the:

- Query ``filter``, ``projection``, ``sort``, ``skip``, ``limit``,
and other operations for :method:`db.collection.find()` are
converted to the equivalent :ref:`aggregation pipeline stages
<aggregation-pipeline-operator-reference>`.

- Converted aggregation pipeline stages are added to the end of the
:ref:`aggregation pipeline <aggregation-pipeline>` for the view.
This does not modify the view's underlying pipeline, which is set
when you create the view.

- :doc:`Aggregation pipeline optimizer
</core/aggregation-pipeline-optimization>` reshapes the view
aggregation pipeline stages to improve performance. This does not
change the query results.

Sharded View
~~~~~~~~~~~~

Expand Down