Expand description
Structs§
BinaryViewType
for string arrays- A boolean datatype
- 32-bit date type: the elapsed time since UNIX epoch in days (32 bits).
- 64-bit date type: the elapsed time since UNIX epoch in milliseconds (64 bits). Values must be divisible by
86_400_000
. SeeDataType::Date64
for more details. - The decimal type for a Decimal128Array
- The decimal type for a Decimal256Array
- Elapsed time type: microseconds.
- Elapsed time type: milliseconds.
- Elapsed time type: nanoseconds.
- Elapsed time type: seconds.
- Describes a single column in a
Schema
. - A cheaply cloneable, owned slice of
FieldRef
- 16-bit floating point number type.
- 32-bit floating point number type.
- 64-bit floating point number type.
ByteArrayType
for binary arraysByteArrayType
for string arrays- A signed 8-bit integer type.
- Signed 16-bit integer type.
- Signed 32-bit integer type.
- Signed 64-bit integer type.
- Value of an IntervalDayTime array
- “Calendar” interval type: days and milliseconds. See
IntervalDayTime
for more details. - Value of an IntervalMonthDayNano array
- “Calendar” interval type: months, days, and nanoseconds. See
IntervalMonthDayNano
for more details. - 32-bit “calendar” interval type: the number of whole months.
- Describes the meta-data of an ordered sequence of relative types.
ByteViewType
for string arrays- 32-bit time type: the elapsed time since midnight in milliseconds.
- 32-bit time type: the elapsed time since midnight in seconds.
- 64-bit time type: the elapsed time since midnight in microseconds.
- 64-bit time type: the elapsed time since midnight in nanoseconds.
- Timestamp microsecond type with an optional timezone.
- Timestamp millisecond type with an optional timezone.
- Timestamp nanosecond type with an optional timezone.
- Timestamp second type with an optional timezone.
- Unsigned 8-bit integer type.
- Unsigned 16-bit integer type.
- Unsigned 32-bit integer type.
- Unsigned 64-bit integer type.
- A cheaply cloneable, owned collection of
FieldRef
and their corresponding type ids - A signed 256-bit integer
Enums§
- Datatypes supported by this implementation of Apache Arrow.
- YEAR_MONTH, DAY_TIME, MONTH_DAY_NANO interval in SQL style.
- An absolute length of time in seconds, milliseconds, microseconds or nanoseconds.
- Sparse or Dense union layouts
Constants§
- The maximum precision for DataType::Decimal128 values
- The maximum scale for DataType::Decimal128 values
- The maximum precision for DataType::Decimal256 values
- The maximum scale for DataType::Decimal256 values
- The default scale for DataType::Decimal128 and DataType::Decimal256 values
MAX_DECIMAL_FOR_EACH_PRECISION[p-1]
holds the maximumi128
value that can be stored in arrow_schema::DataType::Decimal128 value of precisionp
MIN_DECIMAL_FOR_EACH_PRECISION[p-1]
holds the minimumi128
value that can be stored in a arrow_schema::DataType::Decimal128 value of precisionp
Traits§
- A subtype of primitive type that represents legal dictionary keys. See https://arrow.apache.org/docs/format/Columnar.html
- Trait expressing a Rust type that has the same in-memory representation as Arrow.
- Trait for
ArrowNativeType
that adds checked and unchecked arithmetic operations, and totally ordered comparison operations - A subtype of primitive type that represents numeric values.
- Trait for primitive values.
- A subtype of primitive type that represents temporal values.
- A timestamp type allows us to create array builders that take a timestamp.
- A trait over the variable-size byte array types
- A trait over the variable length bytes view array types
- A trait over the decimal types, used by
PrimitiveArray
to provide a generic implementation across the various decimal types - A subtype of primitive type that is used as run-ends index in
RunArray
. See https://arrow.apache.org/docs/format/Columnar.html - Allows conversion from supported Arrow types to a byte slice.
Functions§
- Determines whether the specified
i256
value can be properly interpreted as a Decimal256 number with precisionprecision
- Determines whether the specified
i128
value can be properly interpreted as a Decimal number with precisionprecision
- Validates that the specified
i256
of value can be properly interpreted as a Decimal256 number with precisionprecision
- Validates that the specified
i128
value can be properly interpreted as a Decimal number with precisionprecision
- Validate that
precision
andscale
are valid forT