Losting metadata in C# RavenDb client when using IAsyncDocumentSession.StoreAsync()

[elitonlunardi]

Hello dear, how are your? Wish you're good!

I'm trying to use the metadata "@expires" in my code as showed in the example below:

await Foo()
await Foo1()

async Task Foo( Foo foo)
{
    var asyncDocumentSession = store.OpenAsyncSession();

    await asyncDocumentSession.StoreAsync(foo);

    var metadata = asyncDocumentSession.Advanced.GetMetadataFor(foo);
    metadata[Raven.Client.Constants.Documents.Metadata.Expires] = DateTime.Now.AddSeconds(20);

    await asyncDocumentSession.SaveChangesAsync();
}


//here I'm lost the expire's metadata. How can I use this without losing the metadata previously setted? 
async Task Foo1(Foo foo)
{
    var asyncDocumentSession = store.OpenAsyncSession();
    await asyncDocumentSession.StoreAsync(foo);
    foo.Number = 9090;

    await asyncDocumentSession.SaveChangesAsync();
}

In some of projects that I work we use StoreAsync to bring some entity from a session to a different and new session on actual service (as example above Foo and Foo1). I don't want to lost the metadata I've set in previous session.

Below I'm putting the entire code to reproduce case is needed. Tks for the help!

using Raven.Client.Documents;
using Raven.Client.Documents.Operations;
using Raven.Client.Exceptions;
using Raven.Client.Exceptions.Database;
using Raven.Client.ServerWide;
using Raven.Client.ServerWide.Operations;

IHost host = Host.CreateDefaultBuilder(args)
    .ConfigureServices(services =>
    {
        services.AddSingleton<IDocumentStore>(sp =>
        {
            var documentStore = new DocumentStore()
            {
                Database = "test",
                Urls = new[]
                {
                    "http://localhost:8080"
                }
            };

            documentStore.Initialize();

            try
            {
                documentStore.Maintenance.ForDatabase("test").Send(new GetStatisticsOperation());
            }
            catch (DatabaseDoesNotExistException)
            {
                try
                {
                    documentStore.Maintenance.Server.Send(new CreateDatabaseOperation(new DatabaseRecord("test")));
                }
                catch (ConcurrencyException)
                { }
            }

            return documentStore;
        });
    })
    .Build();


var foo = new Foo()
{
    Number = new Random(1).NextInt64(100000)
};

var store = host.Services.GetRequiredService<IDocumentStore>();

await Foo(foo);
await Foo1(foo);

return;

async Task Foo( Foo foo)
{
    var asyncDocumentSession = store.OpenAsyncSession();

    await asyncDocumentSession.StoreAsync(foo);

    var metadata = asyncDocumentSession.Advanced.GetMetadataFor(foo);
    metadata[Raven.Client.Constants.Documents.Metadata.Expires] = DateTime.Now.AddSeconds(20);

    await asyncDocumentSession.SaveChangesAsync();
}

//here I'm lost the expire's metadata. How can I use this without losing the metadata previously setted? 
async Task Foo1(Foo foo)
{
    var asyncDocumentSession = store.OpenAsyncSession();
    await asyncDocumentSession.StoreAsync(foo);
    
    foo.Number = 9090;
    
    await asyncDocumentSession.SaveChangesAsync();
}

public class Foo
{
    public string Id { get; set; }
    public long Number { get; set; }
}

[ppekrol]

Hi, the metadata is not transferred between the sessions when entity is passes (Foo in your case), you would have to perform session.LoadAsync in the 2nd session to get the metadata.

[elitonlunardi]

Hello @ppekrol! I have cases that I do 5 or 6 openSession, store and saveChanges. If I do Load operations I'll make a more calls to the server. Can you have other suggestion?

[ppekrol]

Can you share the session between those operations and avoid opening multiple of them? You can call SaveChanges multiple times per session, on save changes only tracked entities that changed are being sent to the server. Please remember that session cannot be used concurrently.

[elitonlunardi]

Share the session means basically use that as a scoped object right? Maybe I can do this. It's a trickier by my side, but I agree with you that this approach make sense...

Thanks for the help. Regards to you!