Documentation

experimental.addDuration() function

experimental.addDuration() is subject to change at any time.

experimental.addDuration() adds a duration to a time value and returns the resulting time value.

Deprecated

experimental.addDuration() is deprecated in favor of date.add().

Function type signature
(d: duration, to: A, ?location: {zone: string, offset: duration}) => time where A: Timeable
For more information, see Function type signatures.

Parameters

d

(Required) Duration to add.

to

(Required) Time to add the duration to.

location

Location to use for the time value.

Use an absolute time or a relative duration. Durations are relative to now().

Examples

Add six hours to a timestamp

import "experimental"

experimental.addDuration(d: 6h, to: 2019-09-16T12:00:00Z)// Returns 2019-09-16T18:00:00.000000000Z

Add one month to yesterday

A time may be represented as either an explicit timestamp or as a relative time from the current now time. addDuration can support either type of value.

import "experimental"

option now = () => 2021-12-10T16:27:40Z

experimental.addDuration(d: 1mo, to: -1d)// Returns 2022-01-09T16:27:40Z

Add six hours to a relative duration

import "experimental"

option now = () => 2022-01-01T12:00:00Z

experimental.addDuration(d: 6h, to: 3h)// Returns 2022-01-01T21:00:00.000000000Z

Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: