Thanks Aurélien
On Aug 19, 2014 3:00 PM, "jmlucjav" wrote:
> In the sample schema.xml I can see this:
>
>
> multiValued="true"/>
>
>
> I am wondering, how does having this split in two fields text/content save
> space?
>
"indexed" means you can search it, "stored" means you can return the
value to the user or highlight it.
Both consum disk space.
A copyfield is not a kind of special field : it is a directive that
copies one field values to another field. They are many use cases for
using copy fields.
In the exa
no it does not.
Here the intent, I think, is not to duplicate stored info, as other
metadata fields like author, keywords etc already are stored, if 'text' was
stored (text is where all fields: content, author etc are copyed), then it
would contain some duplicate info.
On Tue, Aug 19, 2014 at 1:
I have a question, does storing the data in copyfields save space?
With Regards
Aman Tandon
On Tue, Aug 19, 2014 at 3:02 PM, jmlucjav wrote:
> ok, I had not noticed text contains also the other metadata like keywords,
> description etc, nevermind!
>
>
> On Tue, Aug 19, 2014 at 11:28 AM, jmlucj
ok, I had not noticed text contains also the other metadata like keywords,
description etc, nevermind!
On Tue, Aug 19, 2014 at 11:28 AM, jmlucjav wrote:
> In the sample schema.xml I can see this:
>
>
> stored="true" multiValued="true"/>
>
>
> I am wondering, how does having this split
In the sample schema.xml I can see this:
I am wondering, how does having this split in two fields text/content save
space?
