Object Store

Code example

1
2
// Object ID here corresponds to the object ID in the Forge Object Store.
OsParameters osParameters = new OsParametersBuilder("your-object-id").build();
try (OutputStream osStream = gateway.createOsData(osParameters)) {
    osStream.write("Your Forge Object Store bytes here".getBytes());
} catch (IOException e) {
    ...
}

That's it, your data will be uploaded to the Forge Object Store and can be retrieved once the migration completes.

You may combine this with other data planes to keep track of which objects were migrated as well.

1
2
KeyValueParameters parameters = new KeyValueParameters("file-mapping", true);
Map<String, String> fileMapping = new HashMap<>();
fileMapping.put("your-object-id", "some object metadata");

gateway.sendKeyValuePair(fileMapping, parameters);

Limits

Maximum object size is 5 GiB—if you need larger objects, we recommend splitting your data into multiple objects. This is calculated at OutputStream.close(), and if the object size exceeds the limit, the request will fail.

objectId must be between 1 and 128 characters, and only contain letters, numbers, colons, periods, underscores, spaces, hyphens, or hash symbols.

Code considerations

You can invoke the method write() as many times as you need, and we recommend doing this regularly to avoid handling large in-memory objects.

The migration platform will chunk data into 25 MiB chunks.

Error handling and remediation

If an unexpected error occurs, the migration will be marked as FAILED and can be safely retried.

Have your say

We want to make the most out of the EAP and would love to hear your feedback on this feature.