How can we improve Azure Cosmos DB?

← Azure Cosmos DB

support COUNT of a query on a partitioned collection

db.collection.count() works just find but when attempting to count a filtered down collection db.collection.find({query...}).count() results in an Operation Failure that says 'query in command must target a single shard key' but need to be able to do counts across multiple partitions

151 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Mark shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

29 comments

Sign in
(thinking…)
Sign in with: Microsoft
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Balaji Arun commented  ·   ·  Flag as inappropriate

    this is one of the most important feature needed
    without the shared key specify document count should be shown

  • Gavin commented  ·   ·  Flag as inappropriate

    This is NOT completed.

    Now we can't query count in a single partition unless we add the partition key to the where clause.

    This means that working around the other thing that is not completed, skip and take, is not possible unless we write two queries, one of which has an extra where clause.

  • Daniel Vazquez Jimenez commented  ·   ·  Flag as inappropriate

    Hello,

    The main question said: "need to be able to do counts across multiple partitions"

    In my case i need the operation with the next query, because many clients need a total count of documents:

    db.collection.find({query...}).count()

    If i use aggregation pipeline the RUs is very expensive, how I said in other comment:

    - aggregation consumes more than 30k RUs (with 50k of documents) with match , order and count.

    I hope that soon will be possible do this count operation with cross partition.

    I believe the status of this feature should not be 'finished', honestly

  • proxy commented  ·   ·  Flag as inappropriate

    Hi ADMIN, you said that this feature is now avaiable, does this mean db.collection.find({query...}).count() can work?

  • Richa Garg commented  ·   ·  Flag as inappropriate

    Hi Azure team . I need to query count with filters . I see the issue 'query in command must target a single shard key' still exists . Can you please let me know if this is still work in progress ?

  • Sachin commented  ·   ·  Flag as inappropriate

    This is really needed. As a workaround since I am only interested in counts for investigative purposes against a DB, I use `db.vacancies.find().toArray().length` in a MongoShell/Robo3T

  • Daniel Vázquez Jiménez commented  ·   ·  Flag as inappropriate

    Currently I make this query with aggregation and consumes more than 30k RUS (50k documents) with match, order and count.

    This means that we constantly get many errors type: Request rate large.

    This feature is very necessary.

  • Abe commented  ·   ·  Flag as inappropriate

    This is a huge shortcoming that is preventing Cosmos from being a real player in the cloud database field. Please address it as quickly as possible.

  • alex commented  ·   ·  Flag as inappropriate

    This needs to get fixed.

    With the SQL API, you can Enable Cross Partition Queries.

    We either need this to work out of the box for the Mongo API or some way to override the restriction similar to the above flag.

← Previous 1

Azure Cosmos DB: MongoDB API

Categories

Feedback and Knowledge Base

(thinking…)
Hosted by UserVoice