RoutingMissingException[routing is required for [search]/[images]/[86]]

[pdrosos]

Hello,

I am using this library for persisting Doctrine entities in Elasticsearch using Doctrine life cycle events. I have two types: images and photographers. Photographers are set as parent of images. Here are their mappings:

{
    "my_search" : {
        "mappings" : {
            "photographers" : {
                "properties" : {
                    "fullName" : {
                        "type" : "string",
                        "include_in_all" : true
                    }
                }
            },
            "images" : {
                "_parent" : {
                    "type" : "photographers"
                },
                "_routing" : {
                    "required" : true
                },
                "properties" : {
                    "description" : {
                        "type" : "string",
                        "include_in_all" : true
                    },
                    "headline" : {
                        "type" : "string",
                        "include_in_all" : true
                    }
                }
            }
        }
    }
}

On image postPersist/postUpdate this exception is thrown:

Elastica\Exception\ResponseException
File:
    /var/www/search/vendor/ruflin/elastica/lib/Elastica/Transport/Http.php:146
Message:
    RoutingMissingException[routing is required for [my_search]/[images]/[86]]

I use the same annotations like the entities in the demo folder of the library. The demo works fine, but my code doesn't.

Can someone give me a hint what could be the problem? Any help will be appreciated!
Thanks in advance.

[MrHash]

Are you setting the parent value on the images? In the demo it uses $this->setParent($user->getId())

[MrHash]

The other thing to watch out for is that if the parent object does not have an id value the routing will fail.

[pdrosos]

Thank you for you reply!

It works now, it seems that the field, which contains the parent id in the Images entity must have exactly the name $_parent. it was $photographer before and it didn't work.

[MrHash]

OK there is a way you can use the annotation attribute as @MAP\Parameter(name="_parent") if you want and then you should be able to use any member name.