Assign or Move UserID
$client->assignUserId(string userID, string clusterName)
About this method # A
You’re currently reading the JavaScript API client v4 documentation. Check the migration guide to learn how to upgrade from v3 to v4. You can still access the v3 documentation.
You’re currently reading the Ruby API client v2 documentation. Check the migration guide to learn how to upgrade from v1 to v2. You can still access the v1 documentation.
Assign or Move a userID to a cluster.
The time it takes to migrate (move) a user is proportional to the amount of data linked to the userID.
Examples # A
Assign a user to a cluster#
1
$client->assignUserId('myUserID1', 'c1-test');
Parameters # A
userID
# |
type: string
Required
userID to assign. If userID is unknown, we will assign the userID to the cluster, otherwise the operation will move the userID and its associated data from its current cluster to the new one specified in parameter 2. If you have already called this method, and it is still running, you will not be able to run this method again for the same userID, until the first has finished. Any attempt will be rejected. it will be rejected. The userID can contain:
|
clusterName
# |
type: string
Required
Cluster name. |
Response # A
This section shows the JSON response returned by the API. Since each language encapsulates this response inside objects specific to that language and/or implementation, the actual type in your language might differ from what’s written here. You can view the response in the logs (using the getLogs
method).
JSON format#
1
2
3
{
"createdAt": "2013-01-18T15:33:13.556Z"
}
createdAt
# |
string
Date at which the indexing job has been created. |