Core Server
  1. Core Server
  2. SERVER-610

Temp Collections for Non Map-Reduce Queries

    Details

    • Type: New Feature New Feature
    • Status: Open Open
    • Priority: Minor - P4 Minor - P4
    • Resolution: Unresolved
    • Affects Version/s: None
    • Component/s: Querying
    • Labels:
      None
    • Environment:
      All
    • Backport:
      No
    • # Replies:
      1
    • Last comment by Customer:
      true

      Description

      I would like to request the ability to have the results of a query stored in a temporary collection without using Map/Reduce. The query could be executed and return the name of the temporary collection, and options could be passed to define options of the collection, for instance if it's capped or not.

      There are certain cases where this "query and forget until later" could be quite useful... For instance a long running operation over a large dataset where we don't expect results to get returned immediately. An example of this is providing a custom external DSL for users to perform queries against the database, but the DSL to Javascript translation would be an extremely large overhead in order to leverage Map/Reduce.

      The current workaround for this is to put the query on another long running background process and manually put the results in a new collection, I am just looking for a nice way to simplify this.

        Activity

        • Comments
        Hide
        Kostyantin Voz
        added a comment -

        What if that collections won't be temp ? What if that will be [capped] collections working like views in CouchDB ? That could make possible such a thing : querying data from collection, than creating another collection to save the results, when new data added to source collection, it will be queried with the same query and than if match stored in target collection.

        Show
        Kostyantin Voz
        added a comment - What if that collections won't be temp ? What if that will be [capped] collections working like views in CouchDB ? That could make possible such a thing : querying data from collection, than creating another collection to save the results, when new data added to source collection, it will be queried with the same query and than if match stored in target collection.

          People

          • Votes:
            6 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Days since reply:
              4 years, 5 weeks, 1 day ago
              Date of 1st Reply: