RavenDB v4 - Node.js Client - Expiration

[Troy]

How can you set a collection to expire documents or when using the node.js client set an expiration time? I would like a collection to expire all documents if possible, but I don't see a way to set that in the v4 Studio...

Thanks.

[Oren Eini (Ayende Rahien)]

Expiration is set on a per document basis. 

This is done by putting a metadata value of `@expires': ISO8601Date in the metadata.

This is done something like this:

var tomorrow = new Date();

tomorrow.setDate(tomorrow.getDate()+1);

await session.store(

{
	content: content,
	createdAt: new Date(),
	isChecked: false, "@metadata": { "@expires": tomorrow .toISOString() }
	}

, null, "TodoItems");

Hibernating Rhinos Ltd  

Oren Eini l CEO l Mobile: + 972-52-548-6969

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811

 

On Sat, Oct 21, 2017 at 8:33 AM, Troy <tza...@gmail.com> wrote:

How can you set a collection to expire documents or when using the node.js client set an expiration time? I would like a collection to expire all documents if possible, but I don't see a way to set that in the v4 Studio...

Thanks.

--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Troy]

Thank Oren,

It doesn't appear to be working, nor does it appears the node client is actually adding the document @metadata other than the default metadata see what I see in Studio:

"@metadata": {

        "@collection": "Sessions",

        "Raven-Node-Type": "Sessions"

    }

even though store document with this:

 '@metadata': {

      '@expires': futureDate.toISOString(),

    },

I would have expected to see:

"@metadata": {

        "@collection": "Sessions",

        "@expires": "2017-10-22T06:37:20.145Z",

        "Raven-Node-Type": "Sessions"

    }

Is there anything you have to do to make sure that the database, or server, is actually looking for expiring documents? When I add the @expires to the document, that is not honored either...

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.

[Oren Eini (Ayende Rahien)]

Expiration runs every minute or so, IIRC.

Can you send the code that you are using so we can look at this?

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.

[Troy]

import DocumentStore from 'ravendb';

const config = {

  ravendb: {

    url: 'http://4.live-test.ravendb.net',

    database: 'node-app',

  },

};

const store = DocumentStore.create(config.ravendb.url, config.ravendb.database);

store.initialize();

const expiresAt = new Date(new Date().getTime() + (1 * 60000));

async function seed() {

  const session = store.openSession();

  await session.store({

    firstName: 'Delete',

    lastName: 'Me',

    email: 'dele...@test.com',

    password: 'TestPassword',

    seeIsoFormatTemp: expiresAt.toISOString(),

    '@metadata': {

      '@expires': expiresAt.toISOString(),

    },

  }, null, 'TestExpirationDocument');

  await session.saveChanges();

}

seed();

export default store;

[Oren Eini (Ayende Rahien)]

Thanks, looking into this. I think that this is probably just fixed.

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.

[Oren Eini (Ayende Rahien)]

Figure it out, there is an mismatch in the date handling, we don't have the JS value dates handled properly (missing 4 zeroes at the end).

We'll fix that today

[Fitzchak Yitzchaki]

http://issues.hibernatingrhinos.com/issue/RavenDB-9070

Best Regards,

Hibernating Rhinos Ltd  

Fitzchak Yitzchaki l Senior Software Engineer l Mobile:+972-58-345-9538

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811

[Troy]

Great, when will the nightly Docker be available? I am using the docker version and would love to get the fix via the Docker version.

[Grzegorz Lachowski]

Troy,

Here you go: https://hub.docker.com/r/ravendb/ravendb-nightly/

Regards,

Greg

[Troy]

Perfect! Thank you.

Should the latest nightly have the Expiration fix in it?

Running:

Server: 4.0.0-nightly-20171024-0909

Studio: 4.0.0-nightly-20171024-0909

And it seems to not be resolved.

[Oren Eini (Ayende Rahien)]

You also need to enable the expiration itself.

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.

[Marcelo Volmaro]

That seems not to be implemented in the public version of studio (as 4.0.0-nightly-20171024-0909 at least...) I'm waiting for that setting to be present in the UI since the first beta...

[Troy]

I don't see that... I see this in the Studio:

[Troy]

I realized I was not using the latest nightly as I spin the RC1 docker file... once I updated, I do see the Document Expiration using Server: 4.0.0-nightly-20171024-0909

Thanks Oren and Team!

On Tuesday, October 24, 2017 at 3:19:44 PM UTC-4, Oren Eini wrote:

[Troy]

Confirmed it works if I manually add the @expires metedata ... the NPM version of the node client has not been updated to actually add the @expires property even though I am setting it. Or the JS data format without the 0000 is still and issue?

On Tuesday, October 24, 2017 at 3:19:44 PM UTC-4, Oren Eini wrote:

[Oren Eini (Ayende Rahien)]

Okay

http://issues.hibernatingrhinos.com/issue/RDBC-45

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.

[Marcelo Volmaro]

Oren, I still don't see the expiration settings in studio. And I just downloaded the latest version just to be sure (Studio: 4.0.0-nightly-20170922-1004, Server 4.0.0-nightly-20171025-0705).

Tried deleting all the dbs, and also deleting both System/Databases folders and letting Raven create new ones... 

Opening the debugger in Chrome shows that studio throws an error (nor sure if it's related)

TypeError: Cannot read property 'database' of null
    at Function.e.forCurrentPage (http://localhost:8080/studio/App/main.js:3:20734)
    at e.navigateToResourceSpecificPage (http://localhost:8080/studio/App/main.js:19:23122)
    at Object.<anonymous> (http://localhost:8080/studio/App/main.js:19:22910)
    at u (http://localhost:8080/studio/App/external-libs.js:3:25419)
    at Object.fireWith [as resolveWith] (http://localhost:8080/studio/App/external-libs.js:3:26187)
    at Object.i.(anonymous function) [as resolve] (http://localhost:8080/studio/App/external-libs.js:3:27176)
    at t.e.onOpen (http://localhost:8080/studio/App/main.js:10:177)
    at t.onOpen (http://localhost:8080/studio/App/main.js:17:4409)
    at WebSocket.webSocket.onopen (http://localhost:8080/studio/App/main.js:10:3)

[mar...@ayende.com]

Hi,

Studio and server versions should match. Please make sure Raven.Studio.zip was updated during server update. 

Alternately please clear your browser cache. 

Best regards,

Marcin 

[Marcelo Volmaro]

Yes, thanks. It was the browser cache. What's strange is that I forced a refresh (was the first thing I though), but still have the old version of studio. Only after I opened chrome's inspector and checked the "disable cache" option, the refresh actually worked...

Are you using a too aggressive caching? Maybe service workers? I never had to do that (open the inspector) to force a refresh, and that could be an issue if you update studio too often...

[Marcelo Volmaro]

BTW: Since you already know that there is a version mismatch between studio/server, you can warn the user about that and ask him to force refresh the browser...

[Oren Eini (Ayende Rahien)]

That is a good idea, or maybe server the urls from the server version, to avoid it completely?

Hibernating Rhinos Ltd  

Oren Eini l CEO l Mobile: + 972-52-548-6969

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811