searchisko/elasticsearch-river-jira

Can't specify parent if no parent field has been configured

Opened this issue · 4 comments

Chadwiki commented

Receiving this error from recent config: Can't specify parent if no parent field has been configured

I switched from changelog/comment -> embedded mode to child.

I added both field type names, in change log and comment element.
"index": {
"index": "jira",

"type": "proj1_issue", .......

"changelog_mode": "child",
"changelog_type": "proj1_change",

"comment_mode": "child",
"comment_type": "proj1_comment",
  1. Second attempt, removed above river. I then tried to add into the opi_changelog/_mapping

followed in:
{
"proj1_changelog" : {
"_timestamp" : { "enabled" : true },
"_parent" : { "type" : "proj_issue" },
"properties" : {
"project_key" : {"type" : "string", "analyzer" : "keyword"},
"source" : {"type" : "string", "analyzer" : "keyword"}
}
}
}

velias commented

Hi, I never changes type on existing data so I'm not sure how to do it correctly. You definitely have to correctly define _parent in the mapping for comments and change log types, but I'm not sure if it is possible to do it for existing data. Maybe you should completely remove old river and old index with jira data, then recreate index with new correct mappings (for all three types - issues, comments and changelog) and then add river again to index jira data from scratch.

velias commented

BTW examples of correct basic mappings used during tests are available in https://github.com/searchisko/elasticsearch-river-jira/tree/master/src/test/resources/mappings

Chadwiki commented

Thanks for response.

I did re-index but, I found my issues.
It was a config problem, used and older config and then a simple typo.

FYI: I saw a huge Indexing performance increase, moving from embedded to Child

I would also like to see this feature extended for the IssueLinks. :-)

velias commented

Nice, create new issue for your feature request please and close this one