Multiple facets error

I'm trying to query with multiple facets in a query. I've posted the query
and subsequent error
here: https://gist.github.com/alebsack/fc8f0b377c1ca1e780fd

The query works if I remove one of the facets. Is the format correct? Is
it possible to use more than one facet? I'm using tire to form the query,
and it seems to be creating the query correctly per the documentation. Is
this a bug, or am I in fact doing something wrong?

ES version: 0.20.6
OS: OS X Lion 10.8.3

Regards,
Adam

--
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.

There is no problem creating as much facets as you want.

Try removing the second facet called 'inactive_2w' (on which you get the
error) and see if you still get the same error..

BTW why do you have an 'and' filter in the query section when you only have
1 condition?

On Thursday, April 25, 2013 3:15:34 PM UTC+3, Adam Lebsack wrote:

I'm trying to query with multiple facets in a query. I've posted the
query and subsequent error here:
https://gist.github.com/alebsack/fc8f0b377c1ca1e780fd

The query works if I remove one of the facets. Is the format correct? Is
it possible to use more than one facet? I'm using tire to form the query,
and it seems to be creating the query correctly per the documentation. Is
this a bug, or am I in fact doing something wrong?

ES version: 0.20.6
OS: OS X Lion 10.8.3

Regards,
Adam

--
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.

Like I mentioned, the query works properly if I remove one of the facets,
so I've tried removing the 'inactive_2w' already.

As for the query, the "and" is put there by tire when I do:

  query do
    filtered do
      query { all }
      filter :term,  :customer_id => customer_id
    end
  end

... but I think that should be unrelated, right?

On Thursday, April 25, 2013 1:38:55 PM UTC+1, Yehuda Zargarov wrote:

There is no problem creating as much facets as you want.

Try removing the second facet called 'inactive_2w' (on which you get the
error) and see if you still get the same error..

BTW why do you have an 'and' filter in the query section when you only
have 1 condition?

On Thursday, April 25, 2013 3:15:34 PM UTC+3, Adam Lebsack wrote:

I'm trying to query with multiple facets in a query. I've posted the
query and subsequent error here:
https://gist.github.com/alebsack/fc8f0b377c1ca1e780fd

The query works if I remove one of the facets. Is the format correct?
Is it possible to use more than one facet? I'm using tire to form the
query, and it seems to be creating the query correctly per the
documentation. Is this a bug, or am I in fact doing something wrong?

ES version: 0.20.6
OS: OS X Lion 10.8.3

Regards,
Adam

--
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.

It is obviously not the reason for the error.. just didn't make sense to me.

Did you try removing the first facet and leaving only the "inactive_2w"?

On Thursday, April 25, 2013 3:50:52 PM UTC+3, Adam Lebsack wrote:

Like I mentioned, the query works properly if I remove one of the facets,
so I've tried removing the 'inactive_2w' already.

As for the query, the "and" is put there by tire when I do:

  query do
    filtered do
      query { all }
      filter :term,  :customer_id => customer_id
    end
  end

... but I think that should be unrelated, right?

On Thursday, April 25, 2013 1:38:55 PM UTC+1, Yehuda Zargarov wrote:

There is no problem creating as much facets as you want.

Try removing the second facet called 'inactive_2w' (on which you get the
error) and see if you still get the same error..

BTW why do you have an 'and' filter in the query section when you only
have 1 condition?

On Thursday, April 25, 2013 3:15:34 PM UTC+3, Adam Lebsack wrote:

I'm trying to query with multiple facets in a query. I've posted the
query and subsequent error here:
https://gist.github.com/alebsack/fc8f0b377c1ca1e780fd

The query works if I remove one of the facets. Is the format correct?
Is it possible to use more than one facet? I'm using tire to form the
query, and it seems to be creating the query correctly per the
documentation. Is this a bug, or am I in fact doing something wrong?

ES version: 0.20.6
OS: OS X Lion 10.8.3

Regards,
Adam

--
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.

Yes, I've tried both... each facet works on its own. The interesting part
of the error is at the bottom:

Parse Failure [No parser for element [inactive_2w]]

Why would an (almost) identical sibling of inactive_1w not have a parser
defined?

On Thursday, April 25, 2013 2:07:44 PM UTC+1, Yehuda Zargarov wrote:

It is obviously not the reason for the error.. just didn't make sense to
me.

Did you try removing the first facet and leaving only the "inactive_2w"?

On Thursday, April 25, 2013 3:50:52 PM UTC+3, Adam Lebsack wrote:

Like I mentioned, the query works properly if I remove one of the facets,
so I've tried removing the 'inactive_2w' already.

As for the query, the "and" is put there by tire when I do:

  query do
    filtered do
      query { all }
      filter :term,  :customer_id => customer_id
    end
  end

... but I think that should be unrelated, right?

On Thursday, April 25, 2013 1:38:55 PM UTC+1, Yehuda Zargarov wrote:

There is no problem creating as much facets as you want.

Try removing the second facet called 'inactive_2w' (on which you get
the error) and see if you still get the same error..

BTW why do you have an 'and' filter in the query section when you only
have 1 condition?

On Thursday, April 25, 2013 3:15:34 PM UTC+3, Adam Lebsack wrote:

I'm trying to query with multiple facets in a query. I've posted the
query and subsequent error here:
https://gist.github.com/alebsack/fc8f0b377c1ca1e780fd

The query works if I remove one of the facets. Is the format correct?
Is it possible to use more than one facet? I'm using tire to form the
query, and it seems to be creating the query correctly per the
documentation. Is this a bug, or am I in fact doing something wrong?

ES version: 0.20.6
OS: OS X Lion 10.8.3

Regards,
Adam

--
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.

can you please pass your full *tire *code?

On Thursday, April 25, 2013 4:19:25 PM UTC+3, Adam Lebsack wrote:

Yes, I've tried both... each facet works on its own. The interesting
part of the error is at the bottom:

Parse Failure [No parser for element [inactive_2w]]

Why would an (almost) identical sibling of inactive_1w not have a parser
defined?

On Thursday, April 25, 2013 2:07:44 PM UTC+1, Yehuda Zargarov wrote:

It is obviously not the reason for the error.. just didn't make sense to
me.

Did you try removing the first facet and leaving only the "inactive_2w"?

On Thursday, April 25, 2013 3:50:52 PM UTC+3, Adam Lebsack wrote:

Like I mentioned, the query works properly if I remove one of the
facets, so I've tried removing the 'inactive_2w' already.

As for the query, the "and" is put there by tire when I do:

  query do
    filtered do
      query { all }
      filter :term,  :customer_id => customer_id
    end
  end

... but I think that should be unrelated, right?

On Thursday, April 25, 2013 1:38:55 PM UTC+1, Yehuda Zargarov wrote:

There is no problem creating as much facets as you want.

Try removing the second facet called 'inactive_2w' (on which you get
the error) and see if you still get the same error..

BTW why do you have an 'and' filter in the query section when you only
have 1 condition?

On Thursday, April 25, 2013 3:15:34 PM UTC+3, Adam Lebsack wrote:

I'm trying to query with multiple facets in a query. I've posted the
query and subsequent error here:
https://gist.github.com/alebsack/fc8f0b377c1ca1e780fd

The query works if I remove one of the facets. Is the format correct?
Is it possible to use more than one facet? I'm using tire to form the
query, and it seems to be creating the query correctly per the
documentation. Is this a bug, or am I in fact doing something wrong?

ES version: 0.20.6
OS: OS X Lion 10.8.3

Regards,
Adam

--
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.

On Thursday, April 25, 2013 2:22:17 PM UTC+1, Yehuda Zargarov wrote:

can you please pass your full *tire *code?

On Thursday, April 25, 2013 4:19:25 PM UTC+3, Adam Lebsack wrote:

Yes, I've tried both... each facet works on its own. The interesting
part of the error is at the bottom:

Parse Failure [No parser for element [inactive_2w]]

Why would an (almost) identical sibling of inactive_1w not have a parser
defined?

On Thursday, April 25, 2013 2:07:44 PM UTC+1, Yehuda Zargarov wrote:

It is obviously not the reason for the error.. just didn't make sense to
me.

Did you try removing the first facet and leaving only the "inactive_2w"?

On Thursday, April 25, 2013 3:50:52 PM UTC+3, Adam Lebsack wrote:

Like I mentioned, the query works properly if I remove one of the
facets, so I've tried removing the 'inactive_2w' already.

As for the query, the "and" is put there by tire when I do:

  query do
    filtered do
      query { all }
      filter :term,  :customer_id => customer_id
    end
  end

... but I think that should be unrelated, right?

On Thursday, April 25, 2013 1:38:55 PM UTC+1, Yehuda Zargarov wrote:

There is no problem creating as much facets as you want.

Try removing the second facet called 'inactive_2w' (on which you get
the error) and see if you still get the same error..

BTW why do you have an 'and' filter in the query section when you only
have 1 condition?

On Thursday, April 25, 2013 3:15:34 PM UTC+3, Adam Lebsack wrote:

I'm trying to query with multiple facets in a query. I've posted the
query and subsequent error here:
https://gist.github.com/alebsack/fc8f0b377c1ca1e780fd

The query works if I remove one of the facets. Is the format
correct? Is it possible to use more than one facet? I'm using tire to
form the query, and it seems to be creating the query correctly per the
documentation. Is this a bug, or am I in fact doing something wrong?

ES version: 0.20.6
OS: OS X Lion 10.8.3

Regards,
Adam

--
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 found an (exactly) similar problem on stack overflow.. there is even a
reply from karmi (the author of tire) in which he says he has no idea..
The funny thing is that he also has 2 facets, both with range, and it also
works when he removes 1 of the facets..

On Thursday, April 25, 2013 4:24:44 PM UTC+3, Adam Lebsack wrote:

https://gist.github.com/alebsack/fc8f0b377c1ca1e780fd#file-tire-query

On Thursday, April 25, 2013 2:22:17 PM UTC+1, Yehuda Zargarov wrote:

can you please pass your full *tire *code?

On Thursday, April 25, 2013 4:19:25 PM UTC+3, Adam Lebsack wrote:

Yes, I've tried both... each facet works on its own. The interesting
part of the error is at the bottom:

Parse Failure [No parser for element [inactive_2w]]

Why would an (almost) identical sibling of inactive_1w not have a parser
defined?

On Thursday, April 25, 2013 2:07:44 PM UTC+1, Yehuda Zargarov wrote:

It is obviously not the reason for the error.. just didn't make sense
to me.

Did you try removing the first facet and leaving only the
"inactive_2w"?

On Thursday, April 25, 2013 3:50:52 PM UTC+3, Adam Lebsack wrote:

Like I mentioned, the query works properly if I remove one of the
facets, so I've tried removing the 'inactive_2w' already.

As for the query, the "and" is put there by tire when I do:

  query do
    filtered do
      query { all }
      filter :term,  :customer_id => customer_id
    end
  end

... but I think that should be unrelated, right?

On Thursday, April 25, 2013 1:38:55 PM UTC+1, Yehuda Zargarov wrote:

There is no problem creating as much facets as you want.

Try removing the second facet called 'inactive_2w' (on which you get
the error) and see if you still get the same error..

BTW why do you have an 'and' filter in the query section when you
only have 1 condition?

On Thursday, April 25, 2013 3:15:34 PM UTC+3, Adam Lebsack wrote:

I'm trying to query with multiple facets in a query. I've posted
the query and subsequent error here:
https://gist.github.com/alebsack/fc8f0b377c1ca1e780fd

The query works if I remove one of the facets. Is the format
correct? Is it possible to use more than one facet? I'm using tire to
form the query, and it seems to be creating the query correctly per the
documentation. Is this a bug, or am I in fact doing something wrong?

ES version: 0.20.6
OS: OS X Lion 10.8.3

Regards,
Adam

--
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.