在 SOLR 数据库中，唯一的字符串字段是否会在 RAM 中多次存储？
我有一个 SOLR 数据库，需要一个新字段，其中包含类似于标签的字符串列表，只不过它们是预定义的并用于内部目的。该 SOLR 核心的搜索结果将通过公共互联网传送给第 3 方网站开发人员。因此，我想混淆标签，让别人不可能猜测出会泄露其他客户信息的标签。
我可以使用 GUID 轻松完成此任务，但我想知道 RAM 中包含数十万条记录且字段包含多个 GUID 的数组会产生什么影响。
如果 GUID 被记录为原子，即 GUID 的一份副本和对其的多次引用，那么这不是问题。但我无法确定 SOLR 或 Lucene 是否在 RAM 数据结构中使用原子。磁盘存储不是问题。
这与重复数据删除问题类似，但我的研究表明，人们最关心的是整个重复文档，而不是单个字段。
I have a SOLR database that needs to have a new field containing a list of strings that are kind of like tags, except they are predefined and used for an internal purpose. The search results from this SOLR core will go across the public Internet to 3rd party website developers. Therefore I want to obfuscate the tags, and make it impossible for someone to guess a tag that would reveal information about another customer.
I could easily accomplish this using GUIDs, but I wonder what the impact will be of having hundreds of thousands of records in RAM with a field containing an array of several GUIDs.
If the GUIDs were recorded as atoms, i.e. one copy of the GUID and many references to it, then this is a non-issue. But I cannot find out whether SOLR or Lucene use atoms in their in-RAM data structures. The disk storage is not an issue.
This is similar to dedup issues, but my research shows that people are mostly concerned with whole duplicate documents, not with individual fields.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
有两种索引：
There are two indexes: