Each SwarmNFS lets export you specify each view (export) from all of the content object types stored within Swarm: unnamed mutable (alias), unnamed immutable, and named objects. Here is the essential difference between object types:
- Unnamed objects - SwarmNFS lets you read, update, and delete both mutable (alias) and immutable unnamed objects, but not create new ones.
- Named objects - SwarmNFS provides full create, read, update, and delete support for named objects.
presents the named objects that are stored within a Swarm bucket. For manageability, the exact objects that a client sees when connected to SwarmNFS is filtered by type or other subset. Hierarchies are presented to the degree possible. There are two types of hierarchy available in Swarm:
- Bucket level, for named objects
- Domain level, for unnamed objects
, and virtual hierarchies are presented as much as possible.
| Info | ||
|---|---|---|
| ||
Objects created outside of a SwarmNFS server take longer in Swarm natively (not via SwarmNFS) can take up to 5 minutes plus the Search Feed's Batch Timeout to appear in SwarmNFS listings. The delay is up to twice the value of the Batch Timeout for the Search Feed, because they must be indexed by Elasticsearch. For best listing performance, lower the search feed's Batch Timeout to 1 or 0 (recommended). |
Named Object Listings
To present named object listings as if they were in a traditional file system, SwarmNFS creates a simulation: it translates each forward slash (/) in any object name into a traditional directory delimiter. SwarmNFS then presents a view of objects at the simulated directory level. For example, suppose these named objects exist in the bucket “AcmeBucket”:
...