Documentation

Work with bytes types

A bytes type represents a sequence of byte values.

Type name: bytes

Bytes syntax

Flux does not provide a bytes literal syntax. Use the bytes() function to convert a string into bytes.

bytes(v: "hello")
// Returns [104 101 108 108 111]

Only string types can be converted to bytes.

Convert strings to bytes

Use bytes() or hex.bytes() to convert strings to bytes.

  • bytes(): Convert a string to bytes
  • hex.bytes(): Decode hexadecimal value and convert it to bytes.

Convert a hexadecimal string to bytes

import "contrib/bonitoo-io/hex"

hex.bytes(v: "FF5733")
// Returns [255 87 51] (bytes)

Include the string representation of bytes in a table

Use display() to return the string representation of bytes and include it as a column value. display() represents bytes types as a string of lowercase hexadecimal characters prefixed with 0x.

import "sampledata"

sampledata.string()
    |> map(fn: (r) => ({r with _value: display(v: bytes(v: r._value))}))

Output

tag _time _value (string)
t1 2021-01-01T00:00:00Z 0x736d706c5f673971637a73
t1 2021-01-01T00:00:10Z 0x736d706c5f306d6776396e
t1 2021-01-01T00:00:20Z 0x736d706c5f706877363634
t1 2021-01-01T00:00:30Z 0x736d706c5f6775767a7934
t1 2021-01-01T00:00:40Z 0x736d706c5f357633636365
t1 2021-01-01T00:00:50Z 0x736d706c5f7339666d6779
tag _time _value (string)
t2 2021-01-01T00:00:00Z 0x736d706c5f623565696461
t2 2021-01-01T00:00:10Z 0x736d706c5f6575346f7870
t2 2021-01-01T00:00:20Z 0x736d706c5f356737747a34
t2 2021-01-01T00:00:30Z 0x736d706c5f736f78317574
t2 2021-01-01T00:00:40Z 0x736d706c5f77666d373537
t2 2021-01-01T00:00:50Z 0x736d706c5f64746e326276

Was this page helpful?

Thank you for your feedback!


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: