Terms Aggregation KeyAsString is always null

NEST/Elasticsearch.Net version:2.4.6

Elasticsearch version: “version” : { “number” : “2.4.1”, “build_hash” : “c67dc32e24162035d18d6fe1e952c4cbcbe79d16”, “build_timestamp” : “2016-09-27T18:57:55Z”, “build_snapshot” : false, “lucene_version” : “5.5.2” },

Description of the problem including expected versus actual behavior:

Steps to reproduce:

1. run Search with Terms aggregation on one of the object properties of type Guid
   for example object like : {name: ‘SOME NAME’ guidVal: ‘034a7b09-9fee-4f63-a87f-4592edd9560d’}

var aggResponse =  client.Search<TestClass>(s=>            
s.Aggregations(a => a.Terms("distinc_bus", ad => ad.Field(t => t.guidVal))));

List<Guid> listOfGuids = aggResponse.Aggs.Terms("distinc_bus").Buckets.Select(b => Guid.Parse(b.Key)).ToList(); //this line will throw as key is not returned as valid Guid

1. expected result : you get bucket that the bucket key ,or at least the KeyAsString is the same as the guidVal (i.e. ‘034a7b09-9fee-4f63-a87f-4592edd9560d’).
2. actual result : the bucket key is only the last token of the Guid : “4592edd9560d”, and the KeyAsString is null (the value returned fine when reading a single document with Get() or multiple with Search() with no aggregations , so it is saved fine on the Elastic search itself)

[djnelson9715]

if look at the mapping for this type,

yourindex/_mapping

        "properties": {
           "Id": {
              "type": "string",
              "index": "not_analyzed"
           },

you need to add the index setting. This is very good practice to use non-analyzed fields for terms aggregations.

On Sat, Nov 19, 2016 at 11:15 AM, Amir Sasson [e-mail] wrote:

How can the analyzer be disabled for this aggregation only?

On Nov 19, 2016 19:07, “djnelson9715” [e-mail] wrote:

Amir,

I think the issue you are having is because your guidVal property is being analyzed which results in the quid fragments being used by the terms aggregation.

On Sat, Nov 19, 2016 at 9:34 AM, Amir Sasson [e-mail] wrote:

NEST/Elasticsearch.Net version:2.4.6

Elasticsearch version: “version” : { “number” : “2.4.1”, “build_hash” : “c67dc32e24162035d18d6fe1e952c4cbcbe79d16”, “build_timestamp” : “2016-09-27T18:57:55Z”, “build_snapshot” : false, “lucene_version” : “5.5.2” },

Description of the problem including expected versus actual behavior:

Steps to reproduce:

1. run Search with Terms aggregation on one of the object properties of type Guid for example object like : {name: ‘SOME NAME’ guidVal: ‘034a7b09-9fee-4f63-a87f-4592edd9560d’}

var aggResponse = client.Search(s=> s.Aggregations(a => a.Terms(“distinc_bus”, ad => ad.Field(t => t.guidVal))));

aggResponse .Aggs.Terms(“distinc_bus”).Buckets.Select(b => Guid.Parse(b.Key)).ToList(); //this line will throw as key is not returned as valid Guid

1. expected result : you get bucket that the bucket key ,or at least the KeyAsString is the same as the guidVal (i.e. ‘034a7b09-9fee-4f63-a87f- 4592edd9560d’).
2. actual result : the bucket is only the last token of the Guid : “4592edd9560d”, and the KeyAsString is null

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/elastic/elasticsearch-net/issues/2393, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABy19V- A4zX6WeEQVNVbktXf32hHX_1Hks5q_xcTgaJpZM4K3SD0> .

Doug Nelson

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/elastic/elasticsearch-net/issues/2393# issuecomment-261725829>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKxwHKo5Q1cS9Q- PNBojPbTUCya9VNaMks5q_yztgaJpZM4K3SD0> .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/elastic/elasticsearch-net/issues/2393#issuecomment-261726326, or mute the thread https://github.com/notifications/unsubscribe-auth/ABy19WpTr9LpAKUMDji4152o-T1Fr_Neks5q_y7MgaJpZM4K3SD0 .

Doug Nelson

[russcam]

Meant to add that .KeyAsString maps to the value returned by Elasticsearch in the "key_as_string" property of a bucket; for some keys such as dates, Elasticsearch returns a "key_as_string" property as well as the numerical epoch time as the key. In NEST, we always read the "key" as a string, but #2336 is an issue to look at supporting any returned json value.