Yes, I already have kept user's fields as data's fields in datas. On Thursday, August 14, 2014 6:26:20 PM UTC+3, Ramy wrote: > > You can try to save the user _id in each post!!! maybe it solves your > problem > > Am Donnerstag, 14. August 2014 15:34:39 UTC+2 schrieb ali koyuncu: >> >> I have an index named DataIndex. It has two types: posts and users. >> The posts have an user which has small info like just id, name but it has >> more. And I regulary update users some fields like followers count,age etc >> . So I must do below jobs: >> >> - When I run on posts type, I want to join users. >> - I want to join user's posts. So I can retrieval that the user has 1000 >> data etc. >> >> You can suggest using Nested Objects or Parent/Child object. But I >> regulerly update users therefore I can't use nested objects. Parent-Child >> has >> a cost in terms of performance and memory used. >> I want to know is there any method doing this jobs with high performance. >> >> >> >> >> >> >>
-- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/ab1bd531-c480-44df-8a12-6f76d94d8958%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
