Parent child query

[aash dhariya]

Here are my two elastictastic models

Post:

class Post

include Elastictastic::Document

field :content, type: 'string'

has_many comments, class_name: 'Comment'

end

Comment:

class Comment

include Elastictastic::Document

belongs_to :post, class_name: 'Post'

field :content, type: 'string'

end

Next, this is how I save my documents:

p = Post.new

p.content = 'aash'

c = p.comments.new

c.content = 'hello'

c.save

p.save

Now, on querying 

Post.query(has_child: {type: 'comments', query: {term: {content: 'hello'}}})

I get the following error: 

Elastictastic::ServerError::QueryParsingException: [[development_posts] [has_child] No mapping for for type [comments]]; }]

Is there something wrong that I am doing here? If yes, then please give me directions on how to make parent child relationships using elastictastic documents and how to query them

-- 

Thanks, 

Aash

[Matthew A. Brown]

I notice that "comments" is not quoted as a string or symbol in your Post definition. Does that reflect what's in your code?

Anywho, Elastictastic uses the singularized, underscored class name for the "type". Thus what you're looking for is {type: 'comment', ...}

Mat

--
 
 

[aash dhariya]

1. About  the quotes, it was a typo when I wrote the code in the email

2. Even if I query this:

Post.query(has_child: {type: 'comment', query: {term: {content: 'hello'}}})

I get the same type of error:

Elastictastic::ServerError::QueryParsingException: [[development_posts] [has_child] No mapping for for type [comment]]; }]

--
 
 

--
Thanks, 

Aash

[Mat Brown]

Have you run:

    Post.sync_mapping

    Comment.sync_mapping

?

--
 
 

[aash dhariya]

Ok, I found the problem. When I execute

Comment.sync_mapping

it throws me the following error:

Elastictastic::ServerError::IndexMissingException: [[development_comments] missing]

As parent and child have the same index, I changed the index name of Comment model same as parent. Now its working correct. 

The elastictastic gem that I use is customized such that depending on the rails environment, the term development, staging or production is appended to the index_name. I suspect, in doing these changes I would have broken the parent child index name creation. I will soon look into the code and fix it

Thanks a lot for your help

 

--
 
 

--
Thanks, 

Aash