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.
If I put something in /_all/tweet/_mapping will it affect all existing
and future automatically-created indexes such as /foo/tweet/ and /bar/
tweet/?
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'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.
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).
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.
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).
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.
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).
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.