: So, let's assume you want to provide links to the images.
: Having a field (multiValued?) with index="false" and stored="true"
: would allow you to store all the img urls in a single field.
:
: All that said, now it's up to your application layer that
: constructs the pages for presentation to
You might be confusing indexing and storing. When you
specify index="true" in your field definition, the input
is tokenized, transformed, etc and the results of this
(see the admin/analysis) page is what is searched.
But when you specify stored="true", a literal, verbatim
copy of the text is put i
> Why would you store the actual images in SOLR?
No, the images are files on the filesystem. Only the path to the image should
be stored in Solr.
> And you are most likely looking at dynamic fields as the solution
>
> 1) Define *_Path, *_Size, *_Alt as a dynamic field with appropriate types
> 2
Why would you store the actual images in SOLR? There is no way to
really search the bytes of image, is there? What you probably want to
do is extract all searchable metadata out of that image, name, alt,
EXIF, etc.
And you are most likely looking at dynamic fields as the solution
1) Define *_Path
Hi,
I want to create a Solr index of articles. Each article should have a title,
content, published date and an arbitrary number of images attached to. An
article could look like this:
title: An article about Foo and Bar
content: This is some text about Foo and Bar.
published: 2012.09.07T
