feat(azure-cosmosdb): add AzureCosmosDBMongoChatMessageHistory

[fatmelon]

Add AzureCosmosDBMongoChatMessageHistory for langchain-azure-cosmosdb.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
langchainjs-docs	✅ Ready (Inspect)	Visit Preview		Dec 16, 2024 6:52am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
langchainjs-api-refs	⬜️ Ignored (Inspect)			Dec 16, 2024 6:52am

[jacoblee93]

Small nit but looks reasonable - @sinedied are you able to have a look as well?

[sinedied]

Thanks for you contribution!

This looks like almost the same implementation as the @langchain/community mongodb one (which is also compatible with Azure BTW), though for this package we would prefer to have something more in-line with what we have in AzureCosmosDBMongoDBVectorStore for example, ie provide a dbConfig object with either:

• mongo Client
• connectionString
• collectionName
  and initialise the mongo client directly if it's not provided (see AzureCosmosDBMongoDBVectorStore` implementation).

Do you think you could implement these changes? You can also look at AzureCosmosDBNoSQLChatMessageHistoryInput for an example implementation.

Thanks

[sinedied]

Could you also have a look to add the related documentation?
You can ping me on Teams if needed I can help you with what's missing.

[fatmelon]

Thanks for you contribution!

This looks like almost the same implementation as the @langchain/community mongodb one (which is also compatible with Azure BTW), though for this package we would prefer to have something more in-line with what we have in AzureCosmosDBMongoDBVectorStore for example, ie provide a dbConfig object with either:

• mongo Client
• connectionString
• collectionName
  and initialise the mongo client directly if it's not provided (see AzureCosmosDBMongoDBVectorStore` implementation).

Do you think you could implement these changes? You can also look at AzureCosmosDBNoSQLChatMessageHistoryInput for an example implementation.

Thanks

Yep, I'll implement these changes together with Jacob's comments

[sinedied]

Thanks for the update!

I suggest changing the default DB/collection name to align with the other Cosmos Chat history implementation and avoid potential conflicts with vector storage.

Another nit (could be a another PR): test files could be restructured the same way as the implementation, ie:

tests/
  - chat_histories/
    - mongodb.int.test.ts
    - nosql.ts

From our offline chat, docs will be added in another PR.

[fatmelon]

@jacoblee93 could you help review the PR? I think it's ready to merge :)

[jacoblee93]

Thank you!