将图像存储在SOLR搜索结果中显示 [英] Store Images to display in SOLR search results

问题描述

我已经建立了有，我想与搜索结果一起呈现的图像的图像缩略图URL的SOLR指数。问题是，这些图像可以运行到数以百万计，我认为存储图像索引二进制数据将赚了指数堆积如山。

I have built a SOLR Index which has the image thumbnail urls that I want to render an image along with the search results. The problem is that those images can run into millions and I think storing the images in index as binary data would make the index humongous.

我对如何有效地从网址，使他们以后这些图像存储寻求指导，我应该使用普通的文件系统，并让他们通过tomcat的渲染，或者我应该使用JCR资源库，如Apache兔崽子？

I am seeking guidance on how to efficiently store those images after rendering them from the URLs , should I use the plain file system and have them rendered by tomcat , or should I use a JCR repository like Apache Jackrabbit ?

任何指导，将大大AP preciated。

Any guidance would be greatly appreciated.

感谢你。

推荐答案

我最后才决定如何坚持图像评估有效requiriments。

I would evaluate the effective requiriments before finally deciding how to persist the images.

你需要的版本？
您是否计划eonly搅拌图像或其他元数据？
你有在水平缩放什么要求吗？
你需要的任何图像处理或缩放？
你需要访问图像metatdata？
你需要管理的图像附加工具？
你是否愿意在学习额外的技术投入时间？

Do you require versioning? Are you planning to stir eonly the images or additional metadata? Do you have any requirements in horizontal scaling? Do you require any image processing or scaling? Do you need access to the image metatdata? Do you require additional tooling for managing the images? Are you willing to invest time in learning an additional technology?

在文件系统上存储并使其可通过图像sppoler实现的是坚持你的图像的最简单方法。
但是，如果您发现了一些上述要求（这是典型的内容回购或坝系统），那么最终会与文件系统的方式重新发明轮子。

Storing on the file system and making them available by an image sppoler implementation is the most simple way to persist your images. But if you identify some of the above mentioned requirements (which are typical for a content repo or a dam system), then would end up reinventing the wheel with the filesystem approach.

另一种选择是使用一种内容存储库中。一个JCR回购例如像兔崽子或它的商业实现CRX是一种选择。露天（CMIS支持）将是另一个有效。
喜欢的版本，后期处理（缩放...），元数据提取和管理功能只被两个提到库解决方案提供支持。但是，这需要你学习一门新技术，它可能会非常耗时。提到这两个库的技术可以变得很复杂。
如果横向扩展是一个要求，因为communty版本缺少这个功能，我会考虑一个商业支持的存储库实现（CRX或露天的企业）。

The other option is using a kind of content repository. A JCR repo like for example Jackrabbit or it's commercial implementation CRX is one option. Alfresco (supports CMIS) would be the another valid. Features like versioning, post processing (scaling ...), metadata extraction and management belong are supported by both mentioned repository solutions. But this requires you to learn a new technology which can be time consuming. Both mentioned repository technologies can get complex. If horizontal scaling is a requirement I would consider a commercially supported repository implementations (CRX or Alfresco Enterprise) because the communty releases are lacking this functionality.

我个人而言，我真的取决于上述要求的任何决定。
我广泛地与兔崽子，CRX和露天CE和EE工作，亲自我会去的露天因为我经历了它与大量数据更好的扩展。

Me personally I would really depend any decision on the above mentioned requirements. I extensively worked with Jackrabbit, CRX and Alfresco CE and EE and personally I would go for the Alfresco as I experienced it to scale better with larger amounts of data.

这篇关于将图像存储在SOLR搜索结果中显示的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！