Hi Aliaksandr This sounds like a bug to me - I can't think of any reason why this would be intentional behavior. Maybe I'm missing something and this is "expected", but if so someone will come along and correct me.
Can you file a JIRA ticket with this information in it? Jason On Wed, Jun 24, 2020 at 10:03 AM Aliaksandr Asiptsou <aliaksandr_asipt...@epam.com.invalid> wrote: > > Sorry I forgot to mention: we use Solr 8.3.1 > > Best regards, > Aliaksandr Asiptsou > From: Aliaksandr Asiptsou > Sent: Wednesday, June 24, 2020 12:44 AM > To: solr-user@lucene.apache.org > Subject: Restored collection cluster status rendering some values as Long (as > opposed to String for other collections) > > Hello Solr experts, > > Our team noticed the below behavior: > > 1. A collection is restored from a backup, and a replication factor is > specified within the restore command: > > /solr/admin/collections?action=RESTORE&name=backup_name&location=/backups/solr&collection=collection_name&collection.configName=config_name&replicationFactor=1&maxShardsPerNode=1 > > 2. Collection restored successfully, but looking into cluster status we see > several values are rendered as Long for this particular collection: > > /solr/admin/collections?action=clusterstatus&wt=xml > > <long name="pullReplicas">0</long> > <long name="replicationFactor">1</long> > <str name="maxShardsPerNode">1</str> > <str name="autoAddReplicas">false</str> > <long name="nrtReplicas">1</long> > <long name="tlogReplicas">0</long> > <int name="znodeVersion">138</int> > > Whereas for all the other collections pullReplicas, replicationFactor, > nrtReplicas and tlogReplicas are Strings. > > Please advise whether it is known and expected or it needs to be fixed (if > so, is there a Jira ticket already for this or should we create one)? > > Best regards, > Aliaksandr Asiptsou
