o:simon.willna...@googlemail.com]
> Sent: Wednesday, January 25, 2012 2:08 PM
> To: java-user
> Subject: Re: Multiple document types
>
> hey Frank,
>
> can you elaborate what you mean by different doc types? Are you
> referring to an entity ie. a table per entity to
al Message-
From: Simon Willnauer [mailto:simon.willna...@googlemail.com]
Sent: Wednesday, January 25, 2012 2:08 PM
To: java-user
Subject: Re: Multiple document types
hey Frank,
can you elaborate what you mean by different doc types? Are you
referring to an entity ie. a table per entity to sp
Hi Erick,
Your right I think. On resources we gain a little bit on:
disk (a production implementation with live data would be 500 mb saved
in disk usage on each slave and master)
some reduction in network traffic on replication (we do a full
re-index every 24 hours at present)
On design we gain a
Yes, stored fields are placed verbatim for every doc. But I wonder
at the utility of trying to share stored information. The stored
info is put in certain files in the index, see:
http://lucene.apache.org/java/3_0_2/fileformats.html#file-names
and the files that store data are pretty much irreleva
Just as a follow up
it looks like stored fields are stored verbatim for every doc.
hotel index and store dest attributes
index size: 131M
number of records 49147
hotel index only dest attributes
index size: 111m
number of records 49147
~400 chars(bytes) of destination data * 49147 (number of
Hi Chris thanks for the response
> It's an inverted index, so *tems* exist once (per segment) and those terms
> "point" to the documents -- so having the same terms (in the same fields)
> for multiple types of documents in one index is going to take up less
> overall space then having distinct col
: Basically we can search hotels using city attributes but to display
: city data for a chosen hotel we would search for that city document to
: retrieve values.
:
: Do we gain anything here ? Basically would the city fields associated
: with hotels be stored and repeated 74500 less times or are
