[
https://issues.apache.org/jira/browse/SOLR-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13699158#comment-13699158
]
Shalin Shekhar Mangar commented on SOLR-4997:
---------------------------------------------
There is no way to match the last commit point on the parent exactly. The best
we can do is to commit right before we switch states. So users must still call
a commit after splitshard but at least they will get more up to date results.
> The splitshard api doesn't call commit on new sub shards
> --------------------------------------------------------
>
> Key: SOLR-4997
> URL: https://issues.apache.org/jira/browse/SOLR-4997
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.3, 4.3.1
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Fix For: 4.4
>
>
> The splitshard api doesn't call commit on new sub shards but it happily sets
> them to active state which means on a successful split, the documents are not
> visible to searchers unless an explicit commit is called on the cluster.
> The coreadmin split api will still not call commit on targetCores. That is by
> design and we're not going to change that.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
