The HDFS2 sink connector pulls the messages from Pulsar topics and persists the messages to HDFS files.
The configuration of the HDFS2 sink connector has the following properties.
|String||true||None||A file or a comma-separated list containing the Hadoop file system configuration.|
|String||true||None||The HDFS directory where files read from or written to.|
|String||false||None||The character encoding for the files.|
|Compression||false||None||The compression code used to compress or de-compress the files on HDFS. |
Below are the available options:
|String||false||None||The principal account of Kerberos user used for authentication.|
|String||false||None||The full pathname of the Kerberos keytab file used for authentication.|
|String||true, if ||None||The prefix of the files created inside the HDFS directory.|
The value of topicA result in files named topicA-.
|String||true||None||The extension added to the files written to HDFS.|
|char||false||None||The character used to separate records in a text file. |
If no value is provided, the contents from all records are concatenated together in one continuous byte array.
|long||false||0||The interval between calls to flush data to HDFS disk in milliseconds.|
|int||false||Integer.MAX_VALUE||The maximum number of records that hold in memory before acking. |
Setting this property to 1 makes every record send to disk before the record is acked.
Setting this property to a higher value allows buffering records before flushing them to disk.
|String||false||None||A subdirectory associated with the created time of the sink.|
The pattern is the formatted pattern of
See DateTimeFormatter for pattern's syntax.
Before using the HDFS2 sink connector, you need to create a configuration file through one of the following methods.