Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
This page group contains simple recipes for managing your arrays. You can find the contents below:
To create an array you will need to use TileDB Open Source. After you create the array, if you would like to make it "visible" to TileDB Cloud, you need to register the array in a subsequent step. However, TileDB Open Source allows you to create and register the array in a single step, with a very simple change in the way you would otherwise create the array:
Instead of using <array-uri>
as you would typically in TileDB Open Source, you must use tiledb://<username>/<array-uri>
. For example, if you wish to create an array at s3://my_bucket/my_array
, you need to set the array URI to tiledb://my_username/s3://my_bucket/my_array
and TileDB Open Source will instruct TileDB Cloud to automatically register the array as tiledb://my_username/my_array
.
You can register a TileDB array that is already created in a cloud bucket under your control, either via the TileDB Cloud API, or in the TileDB Cloud console as follows. Make sure that you have already set up your AWS credentials, which are needed to access the array you are registering, as those will have to be selected in the drop down list in the pop up, after you click on the "add array" button in Assets -> Arrays
. You can also choose who will be the owner of the array (you or an organization you belong to). Your array will be accessible by tiledb://<namespace>/<array-name>
after it is registered, where namespace
is the owner of the array and <array-name>
is the name of the array that you can select during this registration process in the pop up.
There is absolutely no data movement upon registering an array with TileDB Cloud. Your data continues to remain in your bucket and you are the full owner of this data. TileDB Cloud just records the path and the AWS keys that can access it, so that it can govern access when you or the users you share this array with need to access it.
This page is currently under development and will be updated soon.
You can access the array details programmatically via the TileDB Cloud API (e.g., see Utilities), or on the console as follows. You can see the array overview, which includes the physical path of the array, permissions, a description, etc. Moreover, you can see the array schema, activity logs, metadata, sharing properties, monetization and settings.
Deleting (deregistering) an array (in Settings
) does not physically delete your array from the physical cloud storage. It simply deregisters the array from TileDB Cloud. Your data will still be accessible by you outside of TileDB Cloud if you own the appropriate AWS access keys.
Renaming an array (in Settings
) is under the danger zone, because from that point onwards you (and all the users you shared the array with) will have to change your code to add the new array name. The array will still be shared and accessible by the other users, but they will need to add the new name to their code. In other words, TileDB Cloud does not currently support automatic redirection of array URIs upon renaming.
This page is currently under development and will be updated soon.
You can explore public arrays, adding a variety of filters, from the Explore
page.
This page is currently under development and will be updated soon.
You can share a registered array with any other user on TileDB Cloud. Currently, you can specify array-wide policies, such as read, write and read/write. We plan to add finer-grained access policies soon. To share an array, find it on Assets -> Arrays
and either click on the sharing button located on the right end of the array card in the list, or click on the array card and navigate to the Sharing
tab. The added member will appear in the array members list, where you will be able to change the access policy or revoke access from the user. Users get notified by email when someone shares an array with them.
When sharing an array with other users, you do not get charged for the accesses that those users make. You only get charged for the accesses that you make on your arrays.
When sharing with a member, TileDB Cloud uses auto-complete to facilitate finding a username you are looking for. Similar to GitHub/GitLab, the usernames are considered public information (in contrast to full names and emails that are protected). Please email us at privacy@tiledb.com
if you wish your username to be excluded from auto-complete.
Note that the array URL when you are viewing its Overview
is shareable, and another user can view it on their browser if they have access to it. URLs of public arrays can be viewed by users, even if they are not logged in.
This page is currently under development and will be updated soon.
You can also make an array public, effectively sharing it with every user on TileDB Cloud. This can make your array discoverable by other users that wish to explore public arrays, or you can discover useful datasets that others wish to share with the world.
To make an array public, you just need to navigate to the Settings
of that array and click on Make public
as shown below. Similarly, you can always switch the array back to private mode at any time.
When making an array public, you do not get charged for the accesses that other users make on this array. You only get charged for the accesses that you make on public arrays.
This page is currently under development and will be updated soon.
TileDB Cloud allows you to extract monetary value from your arrays, by setting a dollar amount for egress (per GB of data read by another user) and CPU (per hour of compute spent when another user reads your array).
Before you start monetizing your arrays, you need to create an account with Stripe and connect it with your TileDB Cloud account:
Now you are ready to add pricing to your array from the array's Pricing
tag: