Hp StoreAll Storage User Manual download pdf (Page 189)

curl -g "http://99.226.50.92/ibrix_share1/lab/images/?attributes=

custom::*&query=physician~'^S.*'&recurse"

This example queries all files that have a custom metadata attribute of physician with a value

that starts with S in the lab/images subdirectory of the ibrix_share1 HTTP share, in addition

to the files in all subdirectories, recursively walking the directory tree. A JSON document is returned

containing all custom metadata attribute values, for all files and subdirectories in the lab/images

directory tree that matches the custom metadata criterion.

Get all files that match a name pattern

The following is one command line:

curl -g "http://99.226.50.92/ibrix_share1/lab/images?query=

system::path~'.*\.(gif|jpg)$'"

This example returns a JSON document that contains all files in the lab/images directory that

end in .gif or .jpg.

Get all activity-related times for files with recent activity

The following is one command line:

curl -g "http://99.226.50.92/ibrix_share1/lab/?query=system::

createTime,system::lastChangedTime,system::lastModifiedTime,system::deleteTime&query=system::

lastActivityTime>1334642962"

This example returns a JSON document that contains all files in the lab/images directory that have

experienced activity since April 17, 2012, 06:09:22 UTC/GMT. For live files, the following

attributes are returned: system::createTime,system::lastChangedTime and

system::lastModifiedTime. For live files, system::deleteTime is returned.

Retention properties assignment

Retention and WORM support was initially implemented in 9000/IBRIX v6.0 following an

atime-based retention date interface, to be compatible with existing products that implement

retention this way. This feature is independent of the StoreAll REST API.

Briefly, without the API, the sequence of events is:

1. A user creates or uploads a file to an IBRIX file system.

2. If the autocommit feature is enabled, the file becomes WORM after a certain period of inactivity.

If a non-zero default retention period is defined for the file system, then the file is also set to

the retained state for that period of time, at the same time it becomes WORM.

3. If no autocommit, the user sets the last access time (atime) to the desired retention expiration

date/time (or skips this step if a non-zero default retention period is defined for the file system

and the user does not want to override that period).

4. If no autocommit, after setting the atime, the user turns off all write permission bits on the file.

This triggers the file’s state transition to WORM, and also to retained if the atime is in the

future or if there is a non-zero default retention period.

5. Later, the user can change the atime to change the expiration time, subject to the file system’s

retention policy settings.

The StoreAll REST API commands provide the same ability to perform these actions, but in fewer

steps.

HTTP syntax

The commands provided in this section should be entered on one line.

The HTTP request line format is the following on one line:

StoreAll REST API 189

1 2 ... 184 185 186 187 188 189 190 191 192 193 194 ... 253 254

Comments to this Manuals

No comments

Hp StoreAll Storage User Manual Page 189

Comments to this Manuals

Related products and manuals for Storage Hp StoreAll Storage