On Fri, Apr 2, 2010 at 3:49 AM, Dobes firstname.lastname@example.org wrote:
I'd like to make a search system such that each "user" of the system
has their own set of indexes, but all the user share a common set of
schemas and field settings.
There was actually a thread similar to this which resulted in this
issue: http://github.com/elasticsearch/elasticsearch/issues/86. This means
you can define mappings in advance, and they will automatically be applied
to all indices created.
If I put something in /_all/tweet/_mapping will it affect all existing
and future automatically-created indexes such as /foo/tweet/ and /bar/
Thats another option that was discussed, there is an issue for this, and I
plan to support this notion as well.
Or, do I have to configure the indexes each time a new user is added,
and then reconfigure all existing users when a schema is updated?
I notice that the docs say that types can be automatically detected
like numbers, strings. The example (in
includes a date, are those detected automatically as well?
Dates (strings) are automatically detected using the following logic: They
much have either '-' or ':' in the string, and the date parser manages to
parse them. If both happen, then they are treated as dates. Note, there was
a problem with this in 0.5.1, and its fixed in master (upcoming 0.6.0).