Solr/rdbms，在何处存储附加数据 [英] Solr / rdbms, where to store additonal data

问题描述

当您需要有关方面结果的其他数据时，什么是最佳做法.

What would be considered best practice when you need additional data about facet results.

即.我需要商品名称的友好名称/图片/元关键字/说明/等等. (在分类时)

ie. i need a friendlyname / image / meta keywords / description / and more.. for product categories. (when faceting on categories)

• 将其包括在文档中吗? (可能会导致重复的抢劫)
• 在solr中引入类别作为新索引(或在solr中由doctype = category字段伪造)
• 使用rdbms通过SELECT WHERE IN(..类别构面结果ID ..)查找其他数据

谢谢

Remco

推荐答案

我会考虑2种选择:

1.)加强每个文档的信息，但不对其进行索引(以使索引尽可能小).关键是，我不会存储图像洞察力Lucene/Solr-仅存储文件指针.

1.) strong the informations for every document without indexing it (to keep the index small as possible). The point is, that i would not store the image insight Lucene/Solr - only an file pointer.

2.)如您所写，将其他数据存储在rdbms或nosql(链接mongoDB)上以进行查找.

2.) store the additional data on an rdbms or nosql (linke mongoDB) to lookup, as you wrote.

我最喜欢的是第二名.一种，因为数据库是存储数据的传统方式，也是最优化的方式. 但是最后，这取决于您的系统，因为您应该牢记，您需要时间来连接数据库，搜索数据并将其他信息发送回应用程序. 因此，将所有内容存储在lucene上可能会更快.

My favorite is the 2nd. one, because an database is the traditional and most optimized way to storing data. But finally it depends on your system, because you should keep in mind, that you need time for connecting an database, searching through the data and sending the additional information back to the application. So it could be faster to store everything on lucene.

可能需要进行小的性能测试.

Probably an small performance test would be useful.

这篇关于Solr/rdbms，在何处存储附加数据的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！