On 1/10/2018 11:00 PM, manish tanger wrote:
As we are connecting through zookeeper my understanding was routing will
done by a zookeeper, Thanks for the clarification.
CloudSolrClient doesn't actually connect through ZK. When you create
the client using ZK info, the client reads information about the cloud
from ZK, and discovers where the Solr servers are. All the actual work
that the client does is sent to those Solr servers that were discovered
by reading the ZK database.
*What was the precise commands or API calls that you used to create the
collection? What is the definition of the dateandhour field?*
*
*Collection Creation Through UI:
Inline image 3
Attachments rarely make it to the list. Your image showing the
collection creation did not make it, so I can't that information. If
you want to use an image for that, you're going to need to find some
kind of website for sharing images and provide us with a link. But as
you'll read below, sharing that may not be required.
*dateandhour field defination:
*<fieldname="dateandhour"type="string"indexed="false"stored="true"/>*
I have discovered a problem in the admin UI on version 7.2, which may
affect other versions. Whatever you enter into the "routerField" box
gets sent as a "routerField" parameter -- *not* as the "router.field"
parameter that is actually required. So the collection's state.json
file does not have a router field defined.
I opened an issue for that problem:
https://issues.apache.org/jira/browse/SOLR-11843
Can you try creating a collection with the API directly, rather than
with the admin UI, and using the correct "router.field" parameter?
https://lucene.apache.org/solr/guide/7_2/collections-api.html#CollectionsAPI-Input
Thanks,
Shawn
