AsProjection not returning values that are nested in map statement

[Chris Marisic]

I have an index as such:

public class ContactIndex : AbstractIndexCreationTask<Contact>
{
    public ContactIndex()
    {
        Map = contacts => from contact in contacts
                        select new
                                   {
                                       contact.Name,
                                       PrimaryEmail_EmailAddress = contact.PrimaryEmail.EmailAddress,
                                       PrimaryPhone_PhoneNumber = contact.PrimaryPhone.PhoneNumber,
                                   };       
    }   

    public class IndexResult
    {
        public string Id { get; set; }
        public string Name { get; set; }           
        public string EmailAddress { get; set; }
        public string PrimaryPhone_PhoneNumber { get; set; }
    }
}

Note, on my IndexResult I have conflicting usages of Email & Phone for illustration.

When querying:

_session.Query<Contact, ContactIndex>().AsProjection<ContactIndex.IndexResult>().ToList()

My result set has Id, Name set fine, however neither EmailAddress, PrimaryEmail_EmailAddress, PhoneNumber, PrimaryPhone_PhoneNumber have any values.

When opening the index in the management studio I correctly see in the terms view the correct terms inside of PrimaryEmail_EmailAddress and PrimaryPhone_PhoneNumber

[Matt Warren]

I wonder if the "_" (underscore) characters in the property names are confusing RavenDB, is has some conventions that use this.

What happens if you remove all the "_" characters from your property names inside the Select part of your Map statement?

[Chris Marisic]

If i would remove those underscores I would no longer be able to query against the full documents like:

_session.Query<Contact, ContactIndex>().Where(x=> x.PrimaryEmail.EmailAddress == "em...@site.com").ToList()

[Chris Marisic]

Although I suppose I could keep duplicate fields for the different names, but that seems silly.

[Itamar Syn-Hershko]

You need to have those fields marked as stored

[Chris Marisic]

Itamar could you please explain when things need stored vs when they do not.

When I view the terms in the management studio, is that actually doing like a fake query to show me what terms would be there? as opposed to showing me whats directly in the index because it's not stored?

[Oren Eini (Ayende Rahien)]

Chris,

Terms is taken without relation to a document.

When you want to do a projection, and it is not on the root of the object, you need to store it.

When it is on the root of the object, we can pull it from the doc, but not when it is nested.

[Chris Marisic]

On Thursday, February 23, 2012 8:58:04 AM UTC-5, Ayende Rahien wrote:

Chris,

Terms is taken without relation to a document.

When you want to do a projection, and it is not on the root of the object, you need to store it.

When it is on the root of the object, we can pull it from the doc, but not when it is nested.

I think this information would be very relevant for the site documentation. I did a search on google for site:old.ravendb.net asprojection and site:ravendb.net asprojection and it doesn't seem to even have AsProjection, especially about how it's reading from the doc's top level fields otherwise it needs stored fields.

[Chris Marisic]

Updated index to be:

    public ContactIndex()
    {
        Map = contacts => from contact in contacts
                        select new
                                   {
                                       contact.Name,
                                       PrimaryEmail_EmailAddress = contact.PrimaryEmail.EmailAddress,

                                       PrimaryPhone_PhoneNumber = contact.PrimaryPhone.PhoneNumber,
                                   };       

            Store(x => x.PrimaryEmail.EmailAddress, FieldStorage.Yes);
            Store(x => x.PrimaryPhone.PhoneNumber, FieldStorage.Yes);
    }   

_session.Query<Contact, ContactIndex>().AsProjection<ContactIndex.IndexResult>().ToList()

Still none of EmailAddress, PrimaryEmail_EmailAddress, PhoneNumber, PrimaryPhone_PhoneNumber have any values.

On Thursday, February 23, 2012 8:58:04 AM UTC-5, Ayende Rahien wrote:

[Chris Marisic]

Further strangeness with AsProjection, in my domain Contact is a Person ( class  Contract : Person ). All of those properties are properties of the person object, except for Id which are on Contact being an aggregate root.

If I change

    public class IndexResult
    {
        public string Id { get; set; }
        public string Name { get; set; }           
        public string EmailAddress { get; set; }
        public string PrimaryPhone_PhoneNumber { get; set; }
    }

To be

    public class IndexResult : Person

    {
        public string Id { get; set; }
    }

When I query

_session.Query<Contact, ContactIndex>().AsProjection<ContactIndex.IndexResult>().ToList()

The IndexResult objects are fully hydrated with all of the Person data which contains many other fields and sub objects. The only store settings I have are on the fields for  x.PrimaryEmail.EmailAddress, x.PrimaryPhone.PhoneNumber,

[Oren Eini (Ayende Rahien)]

The fields names are " PrimaryPhone_PhoneNumber  ", but you are using this:

            Store(x => x.PrimaryPhone.PhoneNumber, FieldStorage.Yes);

This tries to store a field named PhoneNumber.

[Oren Eini (Ayende Rahien)]

For simple props, we can load it from the document, but for nested props, we can't.

[Chris Marisic]

That's extremely nonobvious when you factor in the magic of PrimaryPhone_PhoneNumber matching Where(x=>x.PrimaryPhone.PhoneNumber == "123") and that Store only supports strongly typed registrations.

[Oren Eini (Ayende Rahien)]

I agree, can you open an issue for this?

[Chris Marisic]

Should I open the issue that   Store(x => x.PrimaryPhone.PhoneNumber, FieldStorage.Yes) should match PrimaryPhone_PhoneNumber = contact.PrimaryPhone.PhoneNumb

er,

or that I should be able to do

Store("PrimaryPhone_PhoneNumber", FieldStorage.Yes)

or should i open 2 issues to cover both of these?

[Oren Eini (Ayende Rahien)]

Both

[Chris Marisic]

Issues 80 & 81 opened

[Oren Eini (Ayende Rahien)]

Thanks, we will look them over on Sunday