If I query from parent type using hasChild filter, there are no problems.
Everything works as expected.
But if I do a count request with the same hasChild filter, then there is a
problem:
Type [myChildType] does not have parent mapping.
There is a workaround for this: use query instead of count and use total
count returned, but this isn't optimal solution of course:)
If I query from parent type using hasChild filter, there are no problems.
Everything works as expected.
But if I do a count request with the same hasChild filter, then there is a
problem:
Type [myChildType] does not have parent mapping.
There is a workaround for this: use query instead of count and use total
count returned, but this isn't optimal solution of course:)
Could you please explain why the count would be just as fast as a query? Is
that because count is implemented as a query and is just a convenience
operation?
Thanks
On Sunday, 13 November 2011 02:09:25 UTC-5, kimchy wrote:
Yes, its not supported. Use search_type=count and do a regular search, it
is as fast as the count endpoint.
If I query from parent type using hasChild filter, there are no problems.
Everything works as expected.
But if I do a count request with the same hasChild filter, then there is
a problem:
Type [myChildType] does not have parent mapping.
There is a workaround for this: use query instead of count and use total
count returned, but this isn't optimal solution of course:)
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.