Get desktop application:
View/edit binary Protocol Buffers messages
* This interface contains file system master service endpoints for Alluxio clients.
* Checks access to path.
(message has no fields)
* Checks the consistency of the files and directores with the path as the root of the subtree
* the root of the subtree to check
* Checks the existence of the file or directory.
* Marks a file as completed.
* the path of the file
(message has no fields)
* Creates a directory.
* the path of the directory
(message has no fields)
* Creates a file.
* the path of the file
* Frees the given file or directory from Alluxio.
* the path of the file or directory
(message has no fields)
* Returns the file path of a file id
* Returns a map from each Alluxio path to information of corresponding mount point
* Returns a list of paths that are being actively synced by Alluxio
(message has no fields)
* Generates a new block id for the given file.
* the path of the file
* Returns the status of the file or directory.
* the path of the file or directory
* If the path points to a file, the method returns a singleton with its file information. If the path points to a directory, the method returns a list with file information for the directory contents.
* the path of the file or directory
* If the path points to a file, the method returns a singleton with its file information. If the path points to a directory, the method returns a list with file information for the directory contents. This operation takes additional options for partial listing of files.
* the path of the file or directory
True if the partial listing was truncated.
The total number of files in the listing directory, (i.e. the size of the result if partial listing was not used) or -1 if the listing was recursive.
* Creates a new "mount point", mounts the given UFS path in the Alluxio namespace at the given path. The path should not exist and should not be nested under any existing mount point.
* the path of alluxio mount point
* the path of the under file system
(message has no fields)
* Deletes a file or a directory and returns whether the remove operation succeeded.
* the path of the file or directory
(message has no fields)
* Renames a file or a directory.
* the source path of the file or directory
* the destination path
(message has no fields)
* Reverse resolve a ufs path.
* Schedules async persistence.
* the path of the file
(message has no fields)
* Sets ACL for the path.
* the path of the file or directory
* the set action to perform
* the list of ACL entries
* the method options
(message has no fields)
* Sets file or directory attributes.
* the path of the file
(message has no fields)
* Start the active syncing of the directory or file
(message has no fields)
* Start the active syncing of the directory or file
(message has no fields)
* Deletes an existing "mount point", voiding the Alluxio namespace at the given path. The path should correspond to an existing mount point. Any files in its subtree that are backed by UFS will be persisted before they are removed from the Alluxio namespace.
* the path of the alluxio mount point
(message has no fields)
* Updates an existing "mount point", changing its mount properties
* the path of alluxio mount point
(message has no fields)
* Updates the ufs mode for a ufs path under one or more mount points.
* the ufs path
(message has no fields)
(message has no fields)
* Load a directory into Alluxio.
* Load metadata from up into Alluxio.
* This interface contains file system master service endpoints for Alluxio workers.
Returns the file information for a file or directory identified by the given file id.
* Returns the UFS information for the given mount point identified by its id.
* This interface contains file system master service endpoints for Alluxio workers.
* Periodic file system worker heartbeat. Returns the command for persisting the blocks of a file.
* the id of the worker
* the list of persisted files
Returns the file information for a file or directory identified by the given file id.
* Returns the set of pinned file ids.
TODO(adit): set replacement?
* Returns the UFS information for the given mount point identified by its id.
Used in:
Used in:
Used in:
Used in:
Used in:
If specified, the data will be written to the certain worker
Used in:
Used in:
* Contains the information of a block in a file. In addition to the BlockInfo, it includes the offset in the file, and the under file system locations of the block replicas.
Used in:
deprecated since 1.1 will be removed in 2.0 (replaced by ufsStringLocations)
Used in:
, , , ,Used in:
Used in:
Used in:
Used in:
, , , , , , , , , , , , , , , , , , , ,Used in:
* Unique operation id.
Used in:
Used in:
(message has no fields)
Used as request type in: FileSystemMasterJobService.GetFileInfo, FileSystemMasterWorkerService.GetFileInfo
* the id of the file
Used as response type in: FileSystemMasterJobService.GetFileInfo, FileSystemMasterWorkerService.GetFileInfo
Used in:
Used in:
(message has no fields)
Used in:
(message has no fields)
Used in:
Used in:
(message has no fields)
Used as request type in: FileSystemMasterJobService.GetUfsInfo, FileSystemMasterWorkerService.GetUfsInfo
* the id of the ufs
Used as response type in: FileSystemMasterJobService.GetUfsInfo, FileSystemMasterWorkerService.GetUfsInfo
Used in:
,Used in:
Used in:
,Used in:
,This is deprecated since 1.1.1 and will be removed in 2.0. Use loadMetadataType.
No data will be transferred.
Setting this to true will disable checking during metadata sync to see if the children of a directory has been loaded. This will avoid a costly full traversal of the file system during recursive listings, but may result in the children of directories not being loaded. It is recommended to set this to true after the first call of a recursive partial listing.
Mount info will be excluded from the list status response if this field is set to true. Resolving a path and obtain the mount info is an expensive operation. For clients that do not need this information such as hadoop-compatible clients, excluding mount info improves the endpoint performance.
Used in:
An offset type can be chosen as from where to start the listing. If none are set the listing will start from the beginning.
Start listing after the given FileId, the FileId can be calculated from the result of a previous listing's FileInfo or URIStatus results using the getFileId method. If the file with the given ID has been moved or deleted then the call will return an error.
Start the listing after this path. If startAfter starts with "/", then it is expected that the path given in the ListStatusPartialPRequest is a prefix of startAfter (e.g. if listing "/dir", then startAfter could be "/dir/next"). Otherwise if start after does not start with "/", then startAfter is appended to the path given in the ListStatusPartialPRequest (e.g. if the listing path is "/dir" and startAfter is "after" then files that start after "/dir/after" in lexicographic order will be listed). The full path itself does not need to exist. This offset type is recommended to use if POSIX compatible listings are needed.
Only start listing items after this many items have been processed. This will count from the start of the listing up to offsetCont before listing items. This can be useful for example to show individual pages in a UI. Note that this listing type may be more expensive than the others as it must traverse offsetCount items, while the others reach the listing point by querying a skip list.
Batch size for partial listings.
Only match files with a given prefix. The prefix starts after the given listing path (e.g. if "/dir" is being listed and prefix is "/pre", then any file with path having a prefix of "/dir/pre" will be listed).
* whether to load metadata recursively
Used in:
, , ,Never load metadata.
Load metadata only once.
Always load metadata.
Used in:
, ,Used in:
If specified and the blocks are not cached in any worker, the data will be read and cached to the certain worker. If the blocks have been cached in some alluxio workers, this field will be ignored.
Used in:
Used in:
Used in:
,Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
,Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used as request type in: FileSystemMasterClientService.SyncMetadata, FileSystemMasterClientService.SyncMetadataAsync
Used in:
Used in:
,Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
,XAttrPropagationStrategy controls the behaviour for assigning xAttr on Inodes within nested directories - NEW_PATHS: Assign xAttr for any missing nodes along the filepath - LEAF_NODE: Only assign xAttr on the leaf node of the filepath
Used in:
,