Dear all,
is there anyone who knows if the issue 2705 has been fixed on the latest
stable
or it's still open as GitHub says?
Is there a plan to fix it in the next release or maybe is there someone
that could suggest an elegant workaround solution?
all the best,
--
Davide Palmisano
http://twitter.com/dpalmisano
--
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 .
mvg
(Martijn Van Groningen)
September 10, 2013, 7:59pm
2
That is issue is still open. There is as far as I know no effort to fix
this in the near future. I think right now the best way to delete all
children belonging to a parent is to do a scan search and bulk the found
ids in the a bulk request with deletes.
On 10 September 2013 15:56, Davide Palmisano dpalmisano@gmail.com wrote:
Dear all,
is there anyone who knows if the issue 2705 has been fixed on the latest
stable
or it's still open as GitHub says?
Is there a plan to fix it in the next release or maybe is there someone
that could suggest an elegant workaround solution?
all the best,
--
Davide Palmisano
http://davidepalmisano.com
http://twitter.com/dpalmisano
--
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 .
Dear all,
is it possible that the CountQuery is affected by issue 2705 as well?
all the best,
On Tue, Sep 10, 2013 at 2:56 PM, Davide Palmisano dpalmisano@gmail.com wrote:
Dear all,
is there anyone who knows if the issue 2705 has been fixed on the latest
stable
or it's still open as GitHub says?
Is there a plan to fix it in the next release or maybe is there someone
that could suggest an elegant workaround solution?
all the best,
--
Davide Palmisano
http://davidepalmisano.com
http://twitter.com/dpalmisano
--
Davide Palmisano
http://twitter.com/dpalmisano
--
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 .
mvg
(Martijn Van Groningen)
September 16, 2013, 7:29pm
4
Yes, the count api is affected as well. Both apis don't execute context
rewrites, which all the parent/child queries rely on. For the search api
this is done in the QueryPhase class. For the count api this would be a
trivial fix. On the other hand you could also just use the count search
type over the count api, which besides the total count also can compute
facet counts:
Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.
On 16 September 2013 18:15, Davide Palmisano dpalmisano@gmail.com wrote:
Dear all,
is it possible that the CountQuery is affected by issue 2705 as well?
all the best,
On Tue, Sep 10, 2013 at 2:56 PM, Davide Palmisano dpalmisano@gmail.com wrote:
Dear all,
is there anyone who knows if the issue 2705 has been fixed on the latest
stable
or it's still open as GitHub says?
Is there a plan to fix it in the next release or maybe is there someone
that could suggest an elegant workaround solution?
all the best,
--
Davide Palmisano
http://davidepalmisano.com
http://twitter.com/dpalmisano
--
Davide Palmisano
http://davidepalmisano.com
http://twitter.com/dpalmisano
--
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 .