CODEWITHSUNDEEP
databasefirebasegoogle-cloud-platformgoogle-cloud-firestore
SebScoFr
SebScoFr

Reputation: 901

Managing createdAt timestamp in Firestore

Every day I am importing products from external retailers into a Google Cloud Firestore database.

During that process, products can be either new (a new document will be added to the database) or existing (an existing document will be updated in the database).

Should be noted that I am importing about 10 million products each day so I am not querying the database for each product to check if it exists already.

I am currently using set with merge, which is exactly what I need as it creates a document if it doesn't exist or updates specific fields of an existing document.

Now the question is, how could I achieve a createdAt timestamp given that provided fields will be updated, therefore the original createdAt timestamp will be lost on update? Is there any way to not update a specific field if that field already exists in the document?

Upvotes: 7

Views: 11723

Answers (2)

luis urdaneta
luis urdaneta

Reputation: 85

in version firebase 9 the correct way is:

import { serverTimestamp } from "firebase/firestore";
....
return snap.ref.set(
      {
        calculatedCreatedAt: serverTimestamp();
.....

Upvotes: 4

Renaud Tarnec
Renaud Tarnec

Reputation: 83153

I suggest that you use a Cloud Function that would create a new dedicated field when a Firestore doc is created. This field shall not be included in the object you pass to the set() method when you update the docs.

Here is a proposal for the Cloud Function code:

const functions = require('firebase-functions');

const admin = require('firebase-admin');

admin.initializeApp();


exports.productsCreatedDate = functions.firestore
  .document('products/{productId}')
  .onCreate((snap, context) => {

    return snap.ref.set(
      {
        calculatedCreatedAt: admin.firestore.FieldValue.serverTimestamp()
      },
      { merge: true }
    )
    .catch(error => {
       console.log(error);
       return false;
    });
  });

Based on Bob Snyder comment above, note that you could also do:

const docCreatedTimestamp = snap.createTime;
return snap.ref.set(
  {
    calculatedCreatedAt: docCreatedTimestamp
  },
  { merge: true }
)
.catch(...)

Upvotes: 7

Related Questions