ChatGPT解决这个技术问题 Extra ChatGPT

How to get the last N records in mongodb?

I can't find anywhere it has been documented this. By default, the find() operation will get the records from beginning. How can I get the last N records in mongodb?

Edit: also I want the returned result ordered from less recent to most recent, not the reverse.

@Haim, plase be specific to answer, which part of the web page resolves my question?
Hi @BinChen, I have the same problem recently, is it solved?

J
Justin Jenkins

If I understand your question, you need to sort in ascending order.

Assuming you have some id or date field called "x" you would do ...

.sort()

db.foo.find().sort({x:1});

The 1 will sort ascending (oldest to newest) and -1 will sort descending (newest to oldest.)

If you use the auto created _id field it has a date embedded in it ... so you can use that to order by ...

db.foo.find().sort({_id:1});

That will return back all your documents sorted from oldest to newest.

Natural Order

You can also use a Natural Order mentioned above ...

db.foo.find().sort({$natural:1});

Again, using 1 or -1 depending on the order you want.

Use .limit()

Lastly, it's good practice to add a limit when doing this sort of wide open query so you could do either ...

db.foo.find().sort({_id:1}).limit(50);

or

db.foo.find().sort({$natural:1}).limit(50);

@MortezaM. I'm pretty sure you've got your query order mixed up ... your sort() should be run last, not first (much like a SQL ORDER BY) .find({}).skip(1).limit(50).sort({"date":-1})
What ever it is, the order of calling functions should have nothing to do with the end result.
@MortezaM. Of course the order matters. item = 3; item.add(3).divide(3) == 2; item.divide(3).add(3) == 4; With no order what would be the outcome??? I agree with you that this reversed order is not intuitive. This is no SQL after all it should follow normal OO paradigms.
and yet the order DOES NOT matter. All you have to do is try it to see that it does not. all of these are called on the cursor and passed to the server so the server limits the results of the sort (top N) as anything else wouldn't make sense.
Docs confirm that the order doesn't matter: link
G
Giacomo1968

The last N added records, from less recent to most recent, can be seen with this query:

db.collection.find().skip(db.collection.count() - N)

If you want them in the reverse order:

db.collection.find().sort({ $natural: -1 }).limit(N)

If you install Mongo-Hacker you can also use:

db.collection.find().reverse().limit(N)

If you get tired of writing these commands all the time you can create custom functions in your ~/.mongorc.js. E.g.

function last(N) {
    return db.collection.find().skip(db.collection.count() - N);
}

then from a mongo shell just type last(N)


db.collection.find().reverse().limit(1) gives me the error ... has no method reverse
@Catfish you are right, I just noticed that reverse() was added by [Mongo-Hacker ](tylerbrock.github.com/mongo-hacker), I'll update my answer. Thanks.
db.getCollection('COLLECTION_NAME').find().skip(db.getCollection('COLLECTION_NAME').count()-N) working great for me :)
This should be the answer to the question, and not the answer by Justin Jenkins.
Natural order should not be relied upon; if you are using a replica set (and you should be), different nodes might well have the same documents stored in a different order on disk.
J
João Otero

Sorting, skipping and so on can be pretty slow depending on the size of your collection.

A better performance would be achieved if you have your collection indexed by some criteria; and then you could use min() cursor:

First, index your collection with db.collectionName.setIndex( yourIndex ) You can use ascending or descending order, which is cool, because you want always the "N last items"... so if you index by descending order it is the same as getting the "first N items".

Then you find the first item of your collection and use its index field values as the min criteria in a search like:

db.collectionName.find().min(minCriteria).hint(yourIndex).limit(N)

Here's the reference for min() cursor: https://docs.mongodb.com/manual/reference/method/cursor.min/


Only answer that takes performance into account, great addition :)
Does this answer guarantees order?
Apparently you can just forget the min and use: db.collectionName.find().hint(yourIndex).limit(N) If the index is in descending order you get the N minimum values.
the order is guaranteed by your index
Great answer, should mark as correct. Thanks
t
turivishal

In order to get last N records you can execute below query:

db.yourcollectionname.find({$query: {}, $orderby: {$natural : -1}}).limit(yournumber)

if you want only one last record:

db.yourcollectionname.findOne({$query: {}, $orderby: {$natural : -1}})

Note: In place of $natural you can use one of the columns from your collection.


this works for me db.yourcollectionname.findOne({$query:{}, $orderby : {$natural : -1}}). I think last parathensis is missing in the answer
Natural order should not be relied upon; if you are using a replica set (and you should be), different nodes might well have the same documents stored in a different order on disk.
l
lauri108

@bin-chen,

You can use an aggregation for the latest n entries of a subset of documents in a collection. Here's a simplified example without grouping (which you would be doing between stages 4 and 5 in this case).

This returns the latest 20 entries (based on a field called "timestamp"), sorted ascending. It then projects each documents _id, timestamp and whatever_field_you_want_to_show into the results.

var pipeline = [
        {
            "$match": { //stage 1: filter out a subset
                "first_field": "needs to have this value",
                "second_field": "needs to be this"
            }
        },
        {
            "$sort": { //stage 2: sort the remainder last-first
                "timestamp": -1
            }
        },
        {
            "$limit": 20 //stage 3: keep only 20 of the descending order subset
        },
        {
            "$sort": {
                "rt": 1 //stage 4: sort back to ascending order
            }
        },
        {
            "$project": { //stage 5: add any fields you want to show in your results
                "_id": 1,
                "timestamp" : 1,
                "whatever_field_you_want_to_show": 1
            }
        }
    ]

yourcollection.aggregate(pipeline, function resultCallBack(err, result) {
  // account for (err)
  // do something with (result)
}

so, result would look something like:

{ 
    "_id" : ObjectId("5ac5b878a1deg18asdafb060"),
    "timestamp" : "2018-04-05T05:47:37.045Z",
    "whatever_field_you_want_to_show" : -3.46000003814697
}
{ 
    "_id" : ObjectId("5ac5b878a1de1adsweafb05f"),
    "timestamp" : "2018-04-05T05:47:38.187Z",
    "whatever_field_you_want_to_show" : -4.13000011444092
}

Hope this helps.


THANK YOU @lauri108! Of all the answers to this and related questions, this is THE ONLY working and reliable solution to "how to get the LAST N DOCS". And simple enough to do in one query. Job done.
c
csg

You can try this method:

Get the total number of records in the collection with

db.dbcollection.count() 

Then use skip:

db.dbcollection.find().skip(db.dbcollection.count() - 1).pretty()

M
Marty Hirsch

You can't "skip" based on the size of the collection, because it will not take the query conditions into account.

The correct solution is to sort from the desired end-point, limit the size of the result set, then adjust the order of the results if necessary.

Here is an example, based on real-world code.

var query = collection.find( { conditions } ).sort({$natural : -1}).limit(N);

query.exec(function(err, results) {
    if (err) { 
    }
    else if (results.length == 0) {
    }
    else {
        results.reverse(); // put the results into the desired order
        results.forEach(function(result) {
            // do something with each result
        });
    }
});

Nice workaround! Would be nice to be able to do the same at the query level though. Something like var query = collection.find( { conditions } ).sort({$natural : -1}).reverse().limit(N).
how can I use the same in springboot?
s
satywan kumar
 db.collection.find().sort({$natural: -1 }).limit(5)

Best and most simple answer in my opinion
How can I perform this query in springboot?
P
Praveen

you can use sort() , limit() ,skip() to get last N record start from any skipped value

db.collections.find().sort(key:value).limit(int value).skip(some int value);

S
Steve Wilhelm

Look under Querying: Sorting and Natural Order, http://www.mongodb.org/display/DOCS/Sorting+and+Natural+Order as well as sort() under Cursor Methods http://www.mongodb.org/display/DOCS/Advanced+Queries


Thanks for your anwser, it is close,but I want to retured records ordered from less recent to most recent, is it possible?
Natural order should not be relied upon; if you are using a replica set (and you should be), different nodes might well have the same documents stored in a different order on disk.
If you want to get the most recent records, you will have to rely on a date field in the document.
L
Lucbug

You may want to be using the find options : http://docs.meteor.com/api/collections.html#Mongo-Collection-find

db.collection.find({}, {sort: {createdAt: -1}, skip:2, limit: 18}).fetch();

I
Ishan Liyanage

If you use MongoDB compass, you can use sort filed to filter,

https://i.stack.imgur.com/YjVCJ.png


t
turivishal

use $slice operator to limit array elements

GeoLocation.find({},{name: 1, geolocation:{$slice: -5}})
    .then((result) => {
      res.json(result);
    })
    .catch((err) => {
      res.status(500).json({ success: false, msg: `Something went wrong. ${err}` });
});

where geolocation is array of data, from that we get last 5 record.


S
Sahil Thummar

Use .sort() and .limit() for that

Use Sort in ascending or descending order and then use limit

db.collection.find({}).sort({ any_field: -1 }).limit(last_n_records);

C
Community
db.collection.find().hint( { $natural : -1 } ).sort(field: 1/-1).limit(n)

according to mongoDB Documentation:

You can specify { $natural : 1 } to force the query to perform a forwards collection scan. You can also specify { $natural : -1 } to force the query to perform a reverse collection scan.


A
Asclepius

Last function should be sort, not limit.

Example:

db.testcollection.find().limit(3).sort({timestamp:-1}); 

This seems incorrect. Why would sort be after limit?