The dictionary indices are constrained to be non-negative integers. If this field is null, the indices must be signed int32. To maximize cross-language compatibility and performance, implementations are recommended to prefer signed integer types over unsigned integer types and to avoid uint64 indices unless they are required by an application.
| 1974 | /// recommended to prefer signed integer types over unsigned integer types |
| 1975 | /// and to avoid uint64 indices unless they are required by an application. |
| 1976 | const org::apache::arrow::flatbuf::Int *indexType() const { |
| 1977 | return GetPointer<const org::apache::arrow::flatbuf::Int *>(VT_INDEXTYPE); |
| 1978 | } |
| 1979 | /// By default, dictionaries are not ordered, or the order does not have |
| 1980 | /// semantic meaning. In some statistical, applications, dictionary-encoding |
| 1981 | /// is used to represent ordered categorical data, and we provide a way to |