Specific fields and routing on Get and Multi Get

[elastic]

Specific fields and routing on Get and Multi Get

[Mpdreamz]

It does when you do a search. In the case of get and multiget it doesn't.

Moving this to the top of my todo list.

On Aug 21, 2012, at 3:24 AM, danielduartef [email protected] wrote:

Hi,
Does NEST allow me to specify the fields to be retrieved in cases that I only need one or two fields in documents with a lot of other information?
In elasticsearch you can do something like:

curl -XGET 'http://localhost:9200/twitter/tweet/1?fields=title,content'

and

curl 'localhost:9200/_mget' -d '{
"docs" : [
{
"_index" : "test",
"_type" : "type",
"_id" : "1",
"fields" : ["field1", "field2"]
}
]
}'

It would be also good to allow me to provide the routing value:

curl -XGET 'http://localhost:9200/twitter/tweet/1?routing=kimchy'

—
Reply to this email directly or view it on GitHub.

[Mpdreamz]

Implemented this for Get

ef2ca4d

var obj = elasticClient.Get<MyClass>(g=>g
    .Index("newindex")
    .Refresh()
    .Routing("routing")
    .ExecuteOnPrimary()
    .Id(1)
);

Leaving issue open since this still needs some integration tests and MultiGet needs to get support for this too.

[danielduartef]

I am testing it, but it returns null every time if I specify the fields.

This will return an User object, not null:

User user = GetClient().Get<User>(g => g
            .Index(UserIndexName)
            .Type("user")
            .Id(userId)
        );

But this will return null every time:

User user = GetClient().Get<User>(g => g
            .Index(UserIndexName)
            .Type("user")
            .Id(userId)
            .Fields(u => u.Id, u => u.FacebookUID)
        );

[Mpdreamz]

Thanks you for getting back to me, i was on holiday and then under the weather for a couple a days.

See i know i could not close this without some integration test :)

[Mpdreamz]

@danielduartef sorry it took a while.

Get<T>(g=>g.Fields()) now no longer returns null.

Selecting a propery in an array i.e f=>f.Followers.First().FirstName will return data like this on elasticsearch'es side:

{
    "followers.firstName" : ["a", "b"]
}

instead of

{
    "followers" : [ { " firstName" : "a" }, { " firstName" : "a" } ]
}

this cannot be parsed back into the orginal object. Therefor a second method GetFieldSelection<T>(g=>g.Fields())) has been added that retuns FieldSelection<T> this has the following properties and methods:

• Document the attempted parsed document, for most properties (not in arrays) this is sufficient
• FieldValue(field) this will get the field data and cast it to K.

i.e fieldSelection.FieldValue<List<string>>(f=>f.Followers.First().FirstName)

See https://github.com/Mpdreamz/NEST/blob/d6ccb9118950b000b8fe9aaeb66adb36ed5bedca/src/Nest.Tests.Integration/Get/GetTests.cs#L45 For more info.

[james1ewis]

Just to confirm - routing isn't supported in multiget is it?