Input formats

Pinot offers support for various popular input formats during ingestion. By changing the input format, you can reduce the time that goes in serialization-deserialization and speed up the ingestion.
The input format can be changed using the recordReaderSpec config in the ingestion job spec.
1
recordReaderSpec:
2
  dataFormat: 'csv'
3
  className: 'org.apache.pinot.plugin.inputformat.csv.CSVRecordReader'
4
  configClassName: 'org.apache.pinot.plugin.inputformat.csv.CSVRecordReaderConfig'
5
  configs: 
6
			key1 : 'value1'
7
			key2 : 'value2'
Copied!
The config consists of the following keys -
dataFormat - Name of the data format to consume.
className - name of the class that implements the RecordReader interface. This class is used for parsing the data.
configClassName - name of the class that implements the RecordReaderConfig interface. This class is used the parse the values mentioned in configs
configs - Key value pair for format specific configs. This field can be left out.
Pinot supports the multiple input formats out of the box. You just need to specify the corresponding readers and the associated custom configs to switch between the formats.
CSV
1
dataFormat: 'csv'
2
className: 'org.apache.pinot.plugin.inputformat.csv.CSVRecordReader'
3
configClassName: 'org.apache.pinot.plugin.inputformat.csv.CSVRecordReaderConfig'
4
configs:
5
	fileFormat: 'default' #should be one of default, rfc4180, excel, tdf, mysql
6
	header: 'columnName seperated by delimiter'
7
  delimiter: ','
8
  multiValueDelimiter: '-'
Copied!
CSV Record Reader supports the following configs -
fileFormat - can be one of default, rfc4180, excel, tdf, mysql
header - header of the file. The columnNames should be seperated by the delimiter mentioned in the config
delimiter - The character seperating the columns
multiValueDelimiter - The character seperating multiple values in a single column. This can be used to split a column into a list.
Your CSV file may have raw text fields that cannot be reliably delimited using any character. In this case, explicitly set the multiValueDelimeter field to empty in the ingestion config. 

multiValueDelimiter: '' 
AVRO
1
dataFormat: 'avro'
2
className: 'org.apache.pinot.plugin.inputformat.avro.AvroRecordReader'
Copied!
The Avro record reader converts the data in file to a GenericRecord. A java class or .avro file is not required.
JSON
1
dataFormat: 'json'
2
className: 'org.apache.pinot.plugin.inputformat.json.JSONRecordReader'
Copied!
Thrift
1
dataFormat: 'thrift'
2
className: 'org.apache.pinot.plugin.inputformat.thrift.ThriftRecordReader'
3
configs:
4
	thriftClass: 'ParserClassName'
Copied!
Note: Thrift requires the generated class using .thrift file to parse the data. The .class file should be available in the Pinot's classpath. You can put the files in the lib/ folder of pinot distribution directory.
Parquet
1
dataFormat: 'parquet'
2
className: 'org.apache.pinot.plugin.inputformat.parquet.ParquetRecordReader'
Copied!
The above class doesn't read the Parquet INT96 and Decimaltype.
Please use the below class to handle  INT96 and Decimaltype.
1
dataFormat: 'parquet'
2
className: 'org.apache.pinot.plugin.inputformat.parquet.ParquetNativeRecordReader'
Copied!
Parquet Data Type
Java Data Type
Comment
INT96
INT64
ParquetINT96 type converts nanoseconds
 to Pinot INT64 type of milliseconds
DECIMAL
DOUBLE
​
ORC
1
dataFormat: 'orc'
2
className: 'org.apache.pinot.plugin.inputformat.orc.ORCRecordReader'
Copied!
ORC record reader supports the following data types -
ORC Data Type
Java Data Type
BOOLEAN
String
SHORT
Integer
INT
Integer
LONG
Integer
FLOAT
Float
DOUBLE
Double
STRING
String
VARCHAR
String
CHAR
String
LIST
Object[]
MAP
Map<Object, Object>
DATE
Long
TIMESTAMP
Long
BINARY
byte[]
BYTE
Integer
In LIST and MAP types, the object should only belong to one of the data types supported by Pinot.
Protocol Buffers
1
dataFormat: 'proto'
2
className: 'org.apache.pinot.plugin.inputformat.protobuf.ProtoBufRecordReader'
3
configs:
4
	descriptorFile: 'file:///path/to/sample.desc'
Copied!
The reader requires a descriptor file to deserialize the data present in the files. You can generate the descriptor file (.desc) from the .proto file using the command -
1
protoc --include_imports --descriptor_set_out=/absolute/path/to/output.desc /absolute/path/to/input.proto
Copied!

Google Cloud Storage

Complex Type (Array, Map) Handling

Last modified 2mo ago

Copy link