I posted this over the holidays, so I figured I'd bump it. Anyone else ever
seen this behavior?
On Monday, January 5, 2015 at 11:30:36 AM UTC-6, Randy McCluer wrote:
>
> I have some sensitive data that I want excluded from source, but indexed.
> I am using "_source"
I have some sensitive data that I want excluded from source, but indexed. I
am using "_source": { "excludes": ["field1"] }, and everything seems to be
working just as expected with the source docs coming back without field1.
If I update the mapping to not exclude field1, the docs still return
w
I'm trying to track down an issue where 2 simple documents I'm testing are
being ranked quite a bit differently.
For testing purposes, I'm only searching against one field, "keywords". The
only word in that field for both documents is "jefferson". However, when I
search for the word "jefferson"
I need to be able to do an exact search against two fields, Program Heading
and Subheading each with it's own search term.
For example, I might need to search for Health Professions -> Medical. So
the Program Area field would be "Health Professions" and the Subheading
field would be "Medical".
Probably low on disc on at least one machine. Monitor disc usage. Also look in
the logs and find out what error you are getting. Report back.
Sent from my iPhone
> On Feb 25, 2014, at 7:25 AM, Umutcan wrote:
>
> Hi,
>
> I created a Elasticsearch cluster with 4 instance. Elasticsearch 0.90.1
#2. Its a hash so youll be fine and get is always faster than search. A lot.
Sent from my iPhone
> On Feb 10, 2014, at 10:26 PM, Arinto Murdopo wrote:
>
> Hi all,
>
> Is there any best practice in generating document ID in ElasticSearch? Let's
> say we want to evenly distribute the data in
