Are you using the _all field in your mapping? I think that could work. That
will make all data searchable, without having to worry about particular
fields.
Logstash does this for an example.
https://github.com/elasticsearch/logstash/blob/master/lib/logstash/outputs/elasticsearch/elasticsearch-template.json
On Friday, September 19, 2014 8:14:57 PM UTC-7, [email protected] wrote:
>
> Hi,
>
> Actually, search need go over all fields, every field has special
> definition, the number of fields is too big to remember,
> I need search all fields for any keywords, return matched docs and field
> name to request.
>
> Why so many fields, cause the data come from tables of database.
> Client want a system to search any data conveniently.
>
> There are other problems like, search results from two tables need do
> a join-like operation.
>
> These requirements exceed ES capcacity, I am not sure.
>
> Thanks.
>
>
>
>> A search is independent from the number of fields as long as you do not
>> search over this number of fields.
>>
>> You can create as much fields as your memory und resources will let you
>> do so.
>>
>> Jörg
>>
>>
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/f502ad18-2c3c-46f6-bda4-dc30d0b79564%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
