Joins on weekly rotated indexes

I need to perform joins on indexes that are rotated per week, is that
possible? By 'rotated per week' I mean that I only want to perform indexing
on this week's indexes and not past ones. Every week I create a new index,
optimize the past ones and stop writing on hem. Thus, i wanted to have 2
aliases, one for searching (including all weeks' indexes) and one for
indexing (pointing to this week's index).
The problem is that nested documents, parent-child solutions all need to
exist on the same index(shard).

Is there any better solution that 2-step-query?

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

I think the terms lookup (which is part of the terms filter) can to do join
you need:
http://www.elasticsearch.org/guide/reference/query-dsl/terms-filter/

On 30 July 2013 11:04, Harris dimitriou.xar@gmail.com wrote:

I need to perform joins on indexes that are rotated per week, is that
possible? By 'rotated per week' I mean that I only want to perform indexing
on this week's indexes and not past ones. Every week I create a new index,
optimize the past ones and stop writing on hem. Thus, i wanted to have 2
aliases, one for searching (including all weeks' indexes) and one for
indexing (pointing to this week's index).
The problem is that nested documents, parent-child solutions all need to
exist on the same index(shard).

Is there any better solution that 2-step-query?

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Met vriendelijke groet,

Martijn van Groningen

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hmm I am not sure this is what I wanted. I am more like into "bring me all
the users who have tweeted from 23:00 to 24:00", or "bring me all the
tweets of the users who have at least once tweeted from 23:00-24:00"

Thus, it's not that i do the query only for a given id, i want to do it for
all ids. In addition i expect the tweets to exist on multiple indexes
(let's say one index per week).

On Tue, Jul 30, 2013 at 2:12 PM, Martijn v Groningen <
martijn.v.groningen@gmail.com> wrote:

I think the terms lookup (which is part of the terms filter) can to do
join you need:
http://www.elasticsearch.org/guide/reference/query-dsl/terms-filter/

On 30 July 2013 11:04, Harris dimitriou.xar@gmail.com wrote:

I need to perform joins on indexes that are rotated per week, is that
possible? By 'rotated per week' I mean that I only want to perform indexing
on this week's indexes and not past ones. Every week I create a new index,
optimize the past ones and stop writing on hem. Thus, i wanted to have 2
aliases, one for searching (including all weeks' indexes) and one for
indexing (pointing to this week's index).
The problem is that nested documents, parent-child solutions all need to
exist on the same index(shard).

Is there any better solution that 2-step-query?

--
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+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
Met vriendelijke groet,

Martijn van Groningen

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/1OlWcrEXcbY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

What would you be joining? Just searching across indices works just fine.
Now if you have an index of users and an index for tweets that need to be
"joined", you will need something like the terms lookup by query which is
not supported by ES yet.

Thanks,
Matt Weber

On Tuesday, July 30, 2013, Harris Dimitriou wrote:

Hmm I am not sure this is what I wanted. I am more like into "bring me all
the users who have tweeted from 23:00 to 24:00", or "bring me all the
tweets of the users who have at least once tweeted from 23:00-24:00"

Thus, it's not that i do the query only for a given id, i want to do it
for all ids. In addition i expect the tweets to exist on multiple indexes
(let's say one index per week).

On Tue, Jul 30, 2013 at 2:12 PM, Martijn v Groningen <
martijn.v.groningen@gmail.com <javascript:_e({}, 'cvml',
'martijn.v.groningen@gmail.com');>> wrote:

I think the terms lookup (which is part of the terms filter) can to do
join you need:
http://www.elasticsearch.org/guide/reference/query-dsl/terms-filter/

On 30 July 2013 11:04, Harris <dimitriou.xar@gmail.com<javascript:_e({}, 'cvml', 'dimitriou.xar@gmail.com');>

wrote:

I need to perform joins on indexes that are rotated per week, is that
possible? By 'rotated per week' I mean that I only want to perform indexing
on this week's indexes and not past ones. Every week I create a new index,
optimize the past ones and stop writing on hem. Thus, i wanted to have 2
aliases, one for searching (including all weeks' indexes) and one for
indexing (pointing to this week's index).
The problem is that nested documents, parent-child solutions all need to
exist on the same index(shard).

Is there any better solution that 2-step-query?

--
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+unsubscribe@googlegroups.com<javascript:_e({}, 'cvml', 'elasticsearch%2Bunsubscribe@googlegroups.com');>
.

For more options, visit https://groups.google.com/groups/opt_out.

--
Met vriendelijke groet,

Martijn van Groningen

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/1OlWcrEXcbY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com <javascript:_e({}, 'cvml',
'elasticsearch%2Bunsubscribe@googlegroups.com');>.
For more options, visit https://groups.google.com/groups/opt_out.

--
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+unsubscribe@googlegroups.com <javascript:_e({},
'cvml', 'elasticsearch%2Bunsubscribe@googlegroups.com');>.
For more options, visit https://groups.google.com/groups/opt_out.

--
Thanks,
Matt Weber

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.