Helix Core is now P4. Product user interfaces will be updated soon. Learn more >>

P4 Server Administration Documentation | 2026.1

# What’s new in P4 Server administration in 2024.1

For a complete list of what’s new in this release, see the Release notes and What’s new in the Helix Core Command-Line (P4) Reference.

## S3 Support

The S3 storage feature supports depots of all types, except remote depots. See Set a depot location in Amazon S3 storage.(In 2023.2, this feature was limited to S3 storage for archive depots.

## Sparse streams

Two stream types, `sparsedev` and `sparserel`, avoid delays due to long population operations on new streams. See Sparse streams in the P4 CLI Documentation.

## Structured logging

Missing archive files can be recorded in structured logs when the commit server is running `p4 verify -t` to pull any missing archives from downstream replicas or edge servers. See `CommitVerifyResults` for `f_integrityEvent` in Event Type 15 Integrity under Using structured logging.

## Additional enhancements

- The `partitioned-jnl` client type has been added to the Client workspace types. Like the `readonly` and `partitioned` client types, `partitioned-jnl` uses an independent `db.have` table to reduce contention on the server's central `db.have` table. However, in addition, `partitioned-jnl` clients support checkpoints, recovery, and replication. See partitioned-jnl client recovery.

- The `p4d -jd` command works with partitioned `db.have` tables. See Journal dump and restore filtering. For the configurables that support this feature, see 2024.1 release in What’s new in the Helix Core Command-Line (P4) Reference.

- The `P4V.Behavior.DisallowDragReparenting` property, if set to `On`, overwrites the P4V preference named "Don't allow streams to be reparented with drag and drop in the stream graph". See Miscellaneous P4V properties.

Your search for returned results