I have not tested routing but I did put that functionality in so it should work fine. Let me know if you have any issues!
Thanks, Matt Weber On Thu, Jun 26, 2014 at 7:20 PM, Drew Kutcharian <d...@venarc.com> wrote: > Thanks Matt, that feature is exactly what we need. One thing I couldn’t > figure out was that I would be able to pass a routing key so only relevant > shards would be queried, right? > > > > On Jun 26, 2014, at 8:14 AM, Matt Weber <matt.we...@gmail.com> wrote: > > See PR #3278. Hopefully it will get merged into one of the next releases. > > https://github.com/elasticsearch/elasticsearch/pull/3278 > > Thanks, > Matt Weber > > > > On Thu, Jun 26, 2014 at 12:10 AM, Thomas <thomas.bo...@gmail.com> wrote: > >> Hi, >> >> Unfortunately this is not supported by elasticsearch, the parent document >> and the child document must be under the same index or else the rounting >> will not be established. You can either try coping the parent document if >> they are not many or you can use an other way to split your data like with >> a hash function and to ensure that both parent and child document will be >> indexed into the same index. >> >> Hope it helps >> Thomas >> >> On Wednesday, 25 June 2014 04:48:48 UTC+3, Drew wrote: >>> >>> Hi! >>> >>> Does ES support cross-index parent/child relationship? More >>> specifically, can I have all the parents in one index (say users) and the >>> children (say events) in a multiple time series style (managed by curator) >>> indices? If so, how is this done? If not, what’s the alternative? >>> >>> Thanks, >>> >>> Drew >> >> >> -- >> 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 elasticsearch+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/d1d73ca5-8d7f-4515-83bb-87f956f5fd83%40googlegroups.com >> <https://groups.google.com/d/msgid/elasticsearch/d1d73ca5-8d7f-4515-83bb-87f956f5fd83%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > 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 elasticsearch+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/CAJ3KEoDq74hQ-OSByFs2HotMtb7aAUfM1zfHwTaMBpQ542o0EA%40mail.gmail.com > <https://groups.google.com/d/msgid/elasticsearch/CAJ3KEoDq74hQ-OSByFs2HotMtb7aAUfM1zfHwTaMBpQ542o0EA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- > 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 elasticsearch+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/0E6751DE-2040-4F12-829E-2F729E7DE053%40venarc.com > <https://groups.google.com/d/msgid/elasticsearch/0E6751DE-2040-4F12-829E-2F729E7DE053%40venarc.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAJ3KEoCpxwUw9510Cp7SWpQNA0Zs8kTY7bUcKWYDpW9mEgHYpw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
