OpenIO

OpenIO SDS APIOpenIO SDS API is a java remote API for OpenIO Software Defined Storage. It is designedto be as simple and fast as possible. Getting startedOioUrl objectEach methods of the api will ask you for an OioUrl instance. This class simplify methods signatures and make code cleaner.You will build it simply by calling OioUrl#url(String, String) for container url, i.e. to perform operations on container,and by calling OioUrl#url(String, String, String) for object url.The first parameter is called "ACCOUNT". It define a storage space inside your SDS namespace. It could be usedfor a dedicated application space for example. If you don't care about that, just choose an account name and keep the same all the time.The second parameter is the container name. It is the space in which your future objects will be created directly.Its name is unique by account.And the last parameter is the object name, which is the identifier of your object inside a container, so, like container in account,an object name is unique inside a container.Container url example:OioUrl url = OioUrl.url("MY_ACCOUNT", "MY_CONTAINER_NAME");Object url example:OioUrl url = OioUrl.url("MY_ACCOUNT", "MY_CONTAINER_NAME", "MY_OBJECT_NAME");Storage client usageOpenIO SDS API entry point is the Client implementations classes. Instances of these implementationsare built with ClientBuilder class. You could create a basic client by callingClientBuilder#newClient(String, String)} method, specifying the OpenIO namespace and proxydservice url as argument. If you don't know what is proxyd service, please refer to OpenIO SDS documentation here.Clients built from ClientBuilder are ready to be used. Let's see some basics examples.Basic client instantiationClient client = ClientBuilder.newClient("OPENIO", " client configurationSettings settings = new Settings(); settings.proxy() .ns("OPENIO") .url(" .ecd(" //setup an ecd url for Erasure cogin management client = ClientBuilder.newClient(settings);Container creation exampleAs simple as it could be:OioUrl url = OioUrl.url("MY_ACCOUNT", "MY_CONTAINER_NAME");client.createContainer(url);Upload an object from an InputStreamOioUrl url = OioUrl.url("MY_ACCOUNT", "MY_CONTAINER_NAME", "MY_OBJECT_NAME");File file = new File("MY_SAMPLE_FILE.txt");FileInputStream fis

= new FileInputStream(file);client.putObject(url, 1024L, fis);Retrieve and download an objectOioUrl url = OioUrl.url("MY_ACCOUNT", "MY_CONTAINER_NAME", "MY_OBJECT_NAME");ObjectInfo oinf = client.getObjectInfo(url);InputStream data = client.downloadObject(oinf);List objects inside a containerOioUrl url = OioUrl.url("MY_ACCOUNT", "MY_CONTAINER_NAME");ObjectList list = client.listContainer(url, new ListOptions());Delete a contentOioUrl url = OioUrl.url("MY_ACCOUNT", "MY_CONTAINER_NAME", "MY_OBJECT_NAME");client.deleteObject(url);Delete a containerAn empty container (it should be explicitly empty) could be deleted from your SDS namespace, as follow.OioUrl url = OioUrl.url("MY_ACCOUNT", "MY_CONTAINER_NAME");client.deleteContainer(url);Exception managementOpenIO choose to make all possible exceptions as RuntimeException extensions. By this way, we allow cleaner codewhen you decide to not check exceptions because you can't deal with unexpected behaviour (IOException etc...).So our client throws only OioException : OioSystemException which indicates server error (connection issues, hardware issues,...),and others OioException extension for all use case errors. See io.openio.sds.exceptions package for exceptions detail.Usage exceptions are detailed just belowNameDescriptionAccountNotFoundExceptionThe account you try to deal with does not existBadRequestExceptionSome parameter is wrong in your requestContainerExistExceptionThe container you try to create is already createdContainerNotFoundExceptionThe container you want to reach does not existObjectExistExceptionThe object you try to created is alreay createdObjectNotFoundExceptionThe object you try to reach does not existOioExceptionMain OpenIO exception classOioSystemExceptionA system error occurred during your requestReferenceAlreadyExistExceptionThe reference you try to create is alreayd createdReferenceNotFoundExceptionthe reference you try to reach does not existContributingThis project was originally indented with tabulations but should from now onbe indented with 4 spaces.

The Direct Download feature works for the following storage connectors:Amazon S3 (without Customer-Provided Encryption Keys (SSE-C); not for files stored in Glacier or Glacier Deep Archive)Microsoft Azure Blob Storage (without shared access signature (SAS))DropboxGoogle StorageRackSpaceOpenS3Minio Object StorageScalityOpenStack Swift (v1 and v2) (with the option 'Swift supports temporary URL')OpenStack Swift v3 (with the option 'Swift supports temporary URL')OpenIO (with the option 'Swift supports temporary URL')Memset Memstore (with the option 'Swift supports temporary URL')Direct Download can be used with the public cloud storage services on this list by all Access Anywhere customers. For private storage services, for example an on-premises Cloudian installation, it is up to the administrator or user who adds the provider to determine whether or not Direct Download should be enabled. Direct Downloads will not work if the storage on which the file to be downloaded is stored is not accessible from the browser or client program that is requesting the download.When Direct Download is activated, a file download is streamed to the user directly from the storage using a secure hand-off with the storage platform. Direct Download activates in a number of scenarios including file download and accessing files from secure shared links. Access to files via Direct Download is logged in the Audit Logs with an indication that the download was direct. Configuring the Direct DownloadTo configure Direct Download, navigate to the settings of a provider that uses one of the supported connectors. You will observe a Direct Download control as outlined below. This can be enabled or disabled depending on your choice of behaviour.