In order to improve memory usage per shard, the _id field is not longer indexed by default. Note, no capability is lost except for the ability to use search queries using the _id field. For that, a new ids query / filter was introduced which does not require the _id field to be indexed (and is actually faster). There is a setting to bring it back if needed.
As a side note, the _type mapping can also be set to index : no, with almost all functionality retained (with a bit slower type filtering) and a new type filter, though this does not improve memory consumption by any noticeable measure.
I have seen there is also an indexed field in Lucene's indices called "uid",
concatenating "type#id", which is taking a lot of space because the ids are
already unique. Is this still going to be created with this change?
In order to improve memory usage per shard, the _id field is not longer
indexed by default. Note, no capability is lost except for the ability to
use search queries using the _id field. For that, a new ids query / filter
was introduced which does not require the _id field to be indexed (and is
actually faster). There is a setting to bring it back if needed.
As a side note, the _type mapping can also be set to index : no, with
almost all functionality retained (with a bit slower type filtering) and a
new type filter, though this does not improve memory consumption by any
noticeable measure.
Ids are not required to be unique across types. The uid will always be created, the _id will not. You need to have a way to identify the doc.
On Wednesday, April 20, 2011 at 5:08 AM, Sebastian Gavarini wrote:
Hi Shay,
I have seen there is also an indexed field in Lucene's indices called "uid", concatenating "type#id", which is taking a lot of space because the ids are already unique. Is this still going to be created with this change?
In order to improve memory usage per shard, the _id field is not longer indexed by default. Note, no capability is lost except for the ability to use search queries using the _id field. For that, a new ids query / filter was introduced which does not require the _id field to be indexed (and is actually faster). There is a setting to bring it back if needed.
As a side note, the _type mapping can also be set to index : no, with almost all functionality retained (with a bit slower type filtering) and a new type filter, though this does not improve memory consumption by any noticeable measure.
In order to improve memory usage per shard, the _id field is not longer indexed by default. Note, no capability is lost except for the ability to use search queries using the _id field. For that, a new ids query / filter was introduced which does not require the _id field to be indexed (and is actually faster). There is a setting to bring it back if needed.
As a side note, the _type mapping can also be set to index : no, with almost all functionality retained (with a bit slower type filtering) and a new type filter, though this does not improve memory consumption by any noticeable measure.
In order to improve memory usage per shard, the _id field is not longer indexed by default. Note, no capability is lost except for the ability to use search queries using the _id field. For that, a new ids query / filter was introduced which does not require the _id field to be indexed (and is actually faster). There is a setting to bring it back if needed.
As a side note, the _type mapping can also be set to index : no, with almost all functionality retained (with a bit slower type filtering) and a new type filter, though this does not improve memory consumption by any noticeable measure.
Though, to add on that, there is a setting to set to make sure it is still indexed when upgrading. And, if starting fresh, you can mark it as indexed. I plan to also add a special sort option for id, that will be less memory heavy.
On Sunday, April 24, 2011 at 9:35 AM, Shay Banon wrote:
Yes.
On Sunday, April 24, 2011 at 12:58 AM, Grant Rodgers wrote:
In order to improve memory usage per shard, the _id field is not longer indexed by default. Note, no capability is lost except for the ability to use search queries using the _id field. For that, a new ids query / filter was introduced which does not require the _id field to be indexed (and is actually faster). There is a setting to bring it back if needed.
As a side note, the _type mapping can also be set to index : no, with almost all functionality retained (with a bit slower type filtering) and a new type filter, though this does not improve memory consumption by any noticeable measure.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.