与Azure搜索连接后使用Document DB的好处 [英] Benefits of using Document DB after connecting with Azure Search

查看:81
本文介绍了与Azure搜索连接后使用Document DB的好处的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我将其数据存储在Azure Document DB中.为了允许在数据的描述字段中进行搜索,我已将文档数据库存储库与Azure搜索相连,如下所述:

I'm storing the data for my in Azure Document DB. In order to allow search over the description field of my data, I've connected my document DB repository with Azure Search, as explained here: https://docs.microsoft.com/en-us/azure/documentdb/documentdb-search-indexer

我还需要通过几个参数过滤搜索结果.我发现自己向Azure搜索索引器添加了更多字段,直到几乎将数据库实体复制到Azure搜索实体为止.

I also need to filter the results of the search via several parameters. I find myself adding more an more fields to my Azure Search indexers, up to the point where I'm almost duplicating my database entities to the Azure search entities.

问题-如果我需要搜索我的数据并决定使用Azure搜索,那么将数据保留在Document DB中有什么好处,或者使用它再次建模会更好只有Azure搜索?

The question - If I need to search over my data and decide to use Azure search, is there any benefit to keeping the data in Document DB, or will it be better to model it again using only Azure Search?

推荐答案

文档数据库提供了Azure搜索不提供的一致性保证.通常,我们不建议将Azure搜索用作主存储.请参阅我对其他SO问题的回答以获取特定的警告:

Document DB provides consistency guarantees that Azure Search does not. In general we don't recommend using Azure Search as a primary store. See my answer to this other SO question for specific caveats: Can Azure Search be used as a primary database for some data?

这篇关于与Azure搜索连接后使用Document DB的好处的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆