Sorting using a nested dictionary field

[RobloxSai-zz]

I am indexing a nested dictionary using NEST. This is the Document Class that I send up to ES:

public class Document
{
    public class Foo
    {
        public Dictionary<int, Bar> BarDict { get; set; }
    }
    public class Bar
    {
        public long Data1 { get; set; }
        public long Data2 { get; set; }
    }
    public Dictionary<int, Foo> FooDict { get; set; }
}

The data gets indexed as expected.

"fooDict" : {
    "1": {
        "barDict": {
            "1": {
                "data1": 10,
                "data2": 4
            },
            "2": {
                "data1": 16,
                "data2": 8
            }
        }
    },
    "2": {
        "barDict": {
            "4": {
                "data1": 11,
                "data2": 3
            },
            "5": {
                "data1": 2,
                "data2": 17
            }
        }
    }
}

I can sort using the following query and it returns the required output on ElasticSearch server.

"sort": {
    "fooDict.2.barDict.5.data2": {
      "order": "desc"
    }
}

However, when I use the NEST Client to generate a similar query, the "Keys" are ignored. Eg:
C# Code:
SearchDescriptor searcher;
searcher.SortDescending(s => s.FooDict[2].BarDict[5].Data2)

generates the following query:
"fooDict.barDict.data2"
which is missing the values of the Keys ("fooDict.2.barDict.5.data2").

Is there a different way to implement the Sort Function in this particular context?

[Mpdreamz]

For now you can specify the string directly using the other overload for SortDescending(string fieldName), i'll look into supporting Dictionary index lookups using the expression overload.

[Mpdreamz]

Just a heads up that dictionary lookup expressions are now supported in the master and will make it into the next release.

[RobloxSai-zz]

Thanks for the update. I ended up using the SortDescending(string fieldName) as a workaround.

[RobloxSai-zz]

I don't think this is fixed. If you tried passing in the Key as a parameter, it uses the name of the Parameter instead of the value.

Eg:

int someInt = 13;
searcher.SortDescending(s => s.FooDict[someInt].SomeData)

Converts this to someInt.FooDict.SomeData instead of FooDict.13.SomeData

[Mpdreamz]

Yeah nest does not actually execute the code inside the lambda but takes it as an expression and then translates the expression to a string. It won't/can't substitute variables like someInt, you will have to use string overload.