kafka

package module
v0.14.2 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Sep 13, 2022 License: Apache-2.0 Imports: 28 Imported by: 0

README

xk6-kafka logo xk6-kafka

GitHub Workflow Status Docker Pulls Coverage Status Go Reference

The xk6-kafka project is a k6 extension that enables k6 users to load test Apache Kafka using a producer and possibly a consumer for debugging.

The real purpose of this extension is to test the system you meticulously designed to use Apache Kafka. So, you can test your consumers, hence your system, by auto-generating messages and sending them to your system via Apache Kafka.

You can send many messages with each connection to Kafka. These messages are arrays of objects containing a key and a value in various serialization formats, passed via configuration objects. Various serialization formats are supported, including strings, JSON, binary, Avro, and JSON Schema. Avro and JSON Schema can either be fetched from Schema Registry or hard-code directly in the script. SASL PLAIN/SCRAM authentication and message compression are also supported.

For debugging and testing purposes, a consumer is available to make sure you send the correct data to Kafka.

If you want to learn more about the extension, see the article explaining how to load test your Kafka producers and consumers using k6 on the k6 blog.

Supported Features

Download Binaries

The Official Docker Image

The official Docker image is available on Docker Hub. Before running your script, make the script available to the container by mounting a volume (a directory) or passing it via stdin.

docker run --rm -i mostafamoradian/xk6-kafka:latest run - <scripts/test_json.js
The Official Binaries

The binaries are generated by the build process and published on the releases page. Currently, binaries for the GNU/Linux, macOS, and Windows on amd64 (x86_64) machines are available.

Note: If you want to see an official build for your machine, please build and test xk6-kafka from source and then create an issue with details. I'll add the specific binary to the build pipeline and publish them on the next release.

Build from Source

You can build the k6 binary on various platforms, each with its requirements. The following shows how to build k6 binary with this extension on GNU/Linux distributions.

Prerequisites

You must have the latest Go version installed to build the k6 binary. The latest version should match k6 and xk6. I recommend gvm because it eases version management.

  • gvm for easier installation and management of Go versions on your machine
  • Git for cloning the project
  • xk6 for building k6 binary with extensions
Install and build the latest tagged version

Feel free to skip the first two steps if you already have Go installed.

  1. Install gvm by following its installation guide.

  2. Install the latest version of Go using gvm. You need Go 1.4 installed for bootstrapping into higher Go versions, as explained here.

  3. Install xk6:

    go install go.k6.io/xk6/cmd/xk6@latest
    
  4. Build the binary:

    xk6 build --with github.com/mostafa/xk6-kafka@latest
    

Note You can always use the latest version of k6 to build the extension, but the earliest version of k6 that supports extensions via xk6 is v0.32.0. The xk6 is constantly evolving, so some APIs may not be backward compatible.

Build for development

If you want to add a feature or make a fix, clone the project and build it using the following commands. The xk6 will force the build to use the local clone instead of fetching the latest version from the repository. This process enables you to update the code and test it locally.

git clone git@github.com:mostafa/xk6-kafka.git && cd xk6-kafka
xk6 build --with github.com/mostafa/xk6-kafka@latest=.

Example scripts

There are many examples in the script directory that show how to use various features of the extension.

How to Test You Kafka Setup

You can start testing your setup immediately, but it takes some time to develop the script, so it would be better to test your script against a development environment and then start testing your environment.

Development environment

I recommend the fast-data-dev Docker image by Lenses.io, a Kafka setup for development that includes Kafka, Zookeeper, Schema Registry, Kafka-Connect, Landoop Tools, 20+ connectors. It is relatively easy to set up if you have Docker installed. Just monitor Docker logs to have a working setup before attempting to test because the initial setup, leader election, and test data ingestion take time.

  1. Run the Kafka environment and expose the ports:

    sudo docker run \
        --detach --rm \
        --name lensesio \
        -p 2181:2181 \
        -p 3030:3030 \
        -p 8081-8083:8081-8083 \
        -p 9581-9585:9581-9585 \
        -p 9092:9092 \
        -e ADV_HOST=127.0.0.1 \
        -e RUN_TESTS=0 \
        lensesio/fast-data-dev:latest
    
  2. After running the command, visit localhost:3030 to get into the fast-data-dev environment.

  3. You can run the command to see the container logs:

    sudo docker logs -f -t lensesio
    

Note: If you have errors running the Kafka development environment, refer to the fast-data-dev documentation.

The xk6-kafka API

All the exported functions are available by importing the module object from k6/x/kafka. The exported objects, constants and other data structures are available in the index.d.ts file, and they always reflect the latest changes on the main branch. You can access the generated documentation at api-docs/docs/README.md.

⚠️ Warning: The Javascript API is subject to change in future versions unless a new major version is released.

k6 Test Scripts

The example scripts are available as test_<format/feature>.js with more code and commented sections in the scripts directory. Since this project extends the functionality of k6, it has four stages in the test life cycle.

  1. To use the extension, you need to import it in your script, like any other JS module:

    // Either import the module object
    import * as kafka from "k6/x/kafka";
    
    // Or individual classes and constants
    import { Writer, Reader, Connection, SchemaRegistry, SCHEMA_TYPE_STRING } from "k6/x/kafka";
    
  2. You need to instantiate the classes in the init context. All the k6 options are also configured here:

    // Creates a new Writer object to produce messages to Kafka
    const writer = new Writer({
        // WriterConfig object
        brokers: ["localhost:9092"],
        topic: "my-topic",
    });
    
    const reader = new Reader({
        // ReaderConfig object
        brokers: ["localhost:9092"],
        topic: "my-topic",
    });
    
    const connection = new Connection({
        // ConnectionConfig object
        address: "localhost:9092",
    });
    
    const schemaRegistry = new SchemaRegistry(
        // Can accept a SchemaRegistryConfig object
    )
    
    if (__VU == 0) {
        // Create a topic on initialization (before producing messages)
        connection.createTopic({
            // TopicConfig object
            topic: "my-topic",
        });
    }
    
  3. In the VU code, you can produce messages to Kafka or consume messages from it:

    export default function() {
        // Fetch the list of all topics
        const topics = connection.listTopics();
        console.log(topics); // list of topics
    
        // Produces message to Kafka
        writer.produce({
            // ProduceConfig object
            messages: [
                // Message object(s)
                {
                    key: schemaRegistry.serialize({
                        data: "my-key",
                        schemaType: SCHEMA_TYPE_STRING,
                    }),
                    value: schemaRegistry.serialize({
                        data: "my-value",
                        schemaType: SCHEMA_TYPE_STRING,
                    }),
                },
            ],
        });
    
        // Consume messages from Kafka
        let messages = reader.consume({
            // ConsumeConfig object
            limit: 10
        });
    
        // your messages
        console.log(messages);
    
        // You can use checks to verify the contents,
        // length and other properties of the message(s)
    
        // To serialize the data back into a string, you should use
        // the deserialize method of the Schema Registry client. You
        // can use it inside a check, as shown in the example scripts.
        let deserializedValue = schemaRegistry.deserialize({
            data: messages[0].value,
            schemaType: SCHEMA_TYPE_STRING,
        })
    }
    
  4. In the teardown function, close all the connections and possibly delete the topic:

    export function teardown(data) {
        // Delete the topic
        connection.deleteTopic("my-topic");
    
        // Close all connections
        writer.close();
        reader.close();
        connection.close();
    }
    
  5. You can now run k6 with the extension using the following command:

    ./k6 run --vus 50 --duration 60s scripts/test_json.js
    
  6. And here's the test result output:

    
            /\      |‾‾| /‾‾/   /‾‾/
       /\  /  \     |  |/  /   /  /
      /  \/    \    |     (   /   ‾‾\
     /          \   |  |\  \ |  (‾)  |
    / __________ \  |__| \__\ \_____/ .io
    
    execution: local
        script: scripts/test_json.js
        output: -
    
    scenarios: (100.00%) 1 scenario, 50 max VUs, 1m30s max duration (incl. graceful stop):
            * default: 50 looping VUs for 1m0s (gracefulStop: 30s)
    
    
    running (1m04.4s), 00/50 VUs, 20170 complete and 0 interrupted iterations
    default ✓ [======================================] 50 VUs  1m0s
    
        ✓ 10 messages are received
        ✓ Topic equals to xk6_kafka_json_topic
        ✓ Key contains key/value and is JSON
        ✓ Value contains key/value and is JSON
        ✓ Header equals {'mykey': 'myvalue'}
        ✓ Time is past
        ✓ Partition is zero
        ✓ Offset is gte zero
        ✓ High watermark is gte zero
    
        █ teardown
    
        checks.........................: 100.00% ✓ 181530       ✗ 0
        data_received..................: 0 B     0 B/s
        data_sent......................: 0 B     0 B/s
        iteration_duration.............: avg=153.45ms min=6.01ms med=26.8ms  max=8.14s   p(90)=156.3ms p(95)=206.4ms
        iterations.....................: 20170   313.068545/s
        kafka.reader.dial.count........: 50      0.776075/s
        kafka.reader.dial.seconds......: avg=171.22µs min=0s     med=0s      max=1.09s   p(90)=0s      p(95)=0s
     ✓ kafka.reader.error.count.......: 0       0/s
        kafka.reader.fetch_bytes.max...: 1000000 min=1000000    max=1000000
        kafka.reader.fetch_bytes.min...: 1       min=1          max=1
        kafka.reader.fetch_wait.max....: 200ms   min=200ms      max=200ms
        kafka.reader.fetch.bytes.......: 58 MB   897 kB/s
        kafka.reader.fetch.size........: 147167  2284.25179/s
        kafka.reader.fetches.count.....: 107     1.6608/s
        kafka.reader.lag...............: 1519055 min=0          max=2436190
        kafka.reader.message.bytes.....: 40 MB   615 kB/s
        kafka.reader.message.count.....: 201749  3131.446006/s
        kafka.reader.offset............: 4130    min=11         max=5130
        kafka.reader.queue.capacity....: 1       min=1          max=1
        kafka.reader.queue.length......: 1       min=0          max=1
        kafka.reader.read.seconds......: avg=96.5ms   min=0s     med=0s      max=59.37s  p(90)=0s      p(95)=0s
        kafka.reader.rebalance.count...: 0       0/s
        kafka.reader.timeouts.count....: 57      0.884725/s
        kafka.reader.wait.seconds......: avg=102.71µs min=0s     med=0s      max=85.71ms p(90)=0s      p(95)=0s
        kafka.writer.acks.required.....: 0       min=0          max=0
        kafka.writer.async.............: 0.00%   ✓ 0            ✗ 2017000
        kafka.writer.attempts.max......: 0       min=0          max=0
        kafka.writer.batch.bytes.......: 441 MB  6.8 MB/s
        kafka.writer.batch.max.........: 1       min=1          max=1
        kafka.writer.batch.size........: 2017000 31306.854525/s
        kafka.writer.batch.timeout.....: 0s      min=0s         max=0s
      ✓ kafka.writer.error.count.......: 0       0/s
        kafka.writer.message.bytes.....: 883 MB  14 MB/s
        kafka.writer.message.count.....: 4034000 62613.709051/s
        kafka.writer.read.timeout......: 0s      min=0s         max=0s
        kafka.writer.retries.count.....: 0       0/s
        kafka.writer.wait.seconds......: avg=0s       min=0s     med=0s      max=0s      p(90)=0s      p(95)=0s
        kafka.writer.write.count.......: 4034000 62613.709051/s
        kafka.writer.write.seconds.....: avg=523.21µs min=4.84µs med=14.48µs max=4.05s   p(90)=33.85µs p(95)=42.68µs
        kafka.writer.write.timeout.....: 0s      min=0s         max=0s
        vus............................: 7       min=7          max=50
        vus_max........................: 50      min=50         max=50
    
FAQ
  1. Why do I receive Error writing messages?

    There are a few reasons why this might happen. The most prominent one is that the topic might not exist, which causes the producer to fail to send messages to a non-existent topic. You can use Connection.createTopic method to create the topic in Kafka, as shown in scripts/test_topics.js. You can also set the autoCreateTopic on the WriterConfig. You can also create a topic using the kafka-topics command:

    $ docker exec -it lensesio bash
    (inside container)$ kafka-topics --create --topic xk6_kafka_avro_topic --bootstrap-server localhost:9092
    (inside container)$ kafka-topics --create --topic xk6_kafka_json_topic --bootstrap-server localhost:9092
    
  2. Why does the reader.consume keeps hanging?

    If the reader.consume keeps hanging, it might be because the topic doesn't exist or is empty.

  3. I want to test SASL authentication. How should I do that?

    If you want to test SASL authentication, look at this commit message, in which I describe how to run a test environment to test SASL authentication.

  4. Why doesn't the consumer group consuming messages from the topic?

    As explained in issue #37, multiple inits by k6 causes multiple consumer group instances to be created in the init context, which sometimes causes the random partitions to be selected by each instance. This, in turn, causes confusion when consuming messages from different partitions. This can be solved by using a UUID when naming the consumer group, thereby guaranteeing that the consumer group object was assigned to all partitions in a topic.

Contributions, Issues and Feedback

I'd be thrilled to receive contributions and feedback on this project. You're always welcome to create an issue if you find one (or many). I would do my best to address the issues. Also, feel free to contribute by opening a PR with changes, and I'll do my best to review and merge it as soon as I can.

Backward Compatibility Notice

If you want to keep up to date with the latest changes, please follow the project board. Also, since v0.9.0, the main branch is the development branch and usually has the latest changes and might be unstable. If you want to use the latest features, you might need to build your binary by following the build from source instructions. In turn, the tagged releases and the Docker images are more stable.

I make no guarantee to keep the API stable, as this project is in active development unless I release a major version. The best way to keep up with the changes is to follow the xk6-kafka API and look at the scripts directory.

The Release Process

The main branch is the development branch, and the pull requests will be squashed and merged into the main branch. When a commit is tagged with a version, for example, v0.10.0, the build pipeline will build the main branch on that commit. The build process creates the binaries and the Docker image. If you want to test the latest unreleased features, you can clone the main branch and instruct the xk6 to use the locally cloned repository instead of using the @latest, which refers to the latest tagged version, as explained in the build for development section.

The CycloneDX SBOM

CycloneDX SBOMs in JSON format are generated for go.mod (as of v0.9.0) and the Docker image (as of v0.14.0) and they can be accessed from the the release assets.

Disclaimer

This project was a proof of concept but seems to be used by some companies nowadays. However, it isn't supported by the k6 team, but rather by me personally, and the APIs may change in the future. USE AT YOUR OWN RISK!

This project was AGPL3-licensed up until 7 October 2021, and then we relicensed it under the Apache License 2.0.

Documentation

Index

Constants

View Source
const (
	Key                Element = "key"
	Value              Element = "value"
	MagicPrefixSize    int     = 5
	ConcurrentRequests int     = 16
)
View Source
const (
	TopicNameStrategy       string = "TopicNameStrategy"
	RecordNameStrategy      string = "RecordNameStrategy"
	TopicRecordNameStrategy string = "TopicRecordNameStrategy"
)
View Source
const (
	Bytes srclient.SchemaType = "BYTES"
)
View Source
const (
	String srclient.SchemaType = "STRING"
)
View Source
const (
	Timeout = time.Second * 10
)

Variables

View Source
var (
	// ErrUnsupported is the error returned when the operation is not supported.
	ErrUnsupportedOperation = NewXk6KafkaError(unsupportedOperation, "Operation not supported", nil)

	// ErrForbiddenInInitContext is used when a Kafka producer was used in the init context.
	ErrForbiddenInInitContext = NewXk6KafkaError(
		kafkaForbiddenInInitContext,
		"Producing Kafka messages in the init context is not supported",
		nil)

	// ErrInvalidDataType is used when a data type is not supported.
	ErrInvalidDataType = NewXk6KafkaError(
		invalidDataType,
		"Invalid data type provided for serializer/deserializer",
		nil)

	// ErrInvalidSchema is used when a schema is not supported or is malformed.
	ErrInvalidSchema = NewXk6KafkaError(failedUnmarshalSchema, "Failed to unmarshal schema", nil)

	// ErrFailedTypeCast is used when a type cast failed.
	ErrFailedTypeCast = NewXk6KafkaError(failedTypeCast, "Failed to cast type", nil)

	// ErrUnknownSerdesType is used when a serdes type is not supported.
	ErrUnknownSerdesType = NewXk6KafkaError(invalidSerdeType, "Unknown serdes type", nil)

	// ErrNotEnoughArguments is used when a function is called with too few arguments.
	ErrNotEnoughArguments = errors.New("not enough arguments")

	// ErrNoSchemaRegistryClient is used when a schema registry client is not configured correctly.
	ErrNoSchemaRegistryClient = NewXk6KafkaError(
		failedConfigureSchemaRegistryClient,
		"Failed to configure the schema registry client",
		nil)

	ErrInvalidPEMData = errors.New("tls: failed to find any PEM data in certificate input")
)
View Source
var (
	GroupBalancers map[string]kafkago.GroupBalancer

	IsolationLevels map[string]kafkago.IsolationLevel

	MaxWait          = time.Millisecond * 200
	RebalanceTimeout = time.Second * 5
)
View Source
var (

	// CompressionCodecs is a map of compression codec names to their respective codecs.
	CompressionCodecs map[string]compress.Compression

	// Balancers is a map of balancer names to their respective balancers.
	Balancers map[string]kafkago.Balancer
)
View Source
var TLSVersions map[string]uint16

TLSVersions is a map of TLS versions to their numeric values.

View Source
var TypesRegistry map[string]Serdes = map[string]Serdes{
	String.String():        &StringSerde{},
	Bytes.String():         &ByteArraySerde{},
	srclient.Json.String(): &JSONSerde{},
	srclient.Avro.String(): &AvroSerde{},
}

Functions

func GetSerdes

func GetSerdes(schemaType string) (Serdes, *Xk6KafkaError)

Types

type AvroSerde

type AvroSerde struct {
	Serdes
}

func (*AvroSerde) Deserialize

func (*AvroSerde) Deserialize(data []byte, schema *Schema) (interface{}, *Xk6KafkaError)

Deserialize deserializes a Avro binary into a JSON object.

func (*AvroSerde) Serialize

func (*AvroSerde) Serialize(data interface{}, schema *Schema) ([]byte, *Xk6KafkaError)

Serialize serializes a JSON object into Avro binary.

type BasicAuth

type BasicAuth struct {
	Username string `json:"username"`
	Password string `json:"password"`
}

type ByteArraySerde

type ByteArraySerde struct {
	Serdes
}

func (*ByteArraySerde) Deserialize

func (*ByteArraySerde) Deserialize(data []byte, schema *Schema) (interface{}, *Xk6KafkaError)

DeserializeByteArray returns the data as-is, because it is already a byte array.

func (*ByteArraySerde) Serialize

func (*ByteArraySerde) Serialize(data interface{}, schema *Schema) ([]byte, *Xk6KafkaError)

Serialize serializes the given data into a byte array.

type ConnectionConfig

type ConnectionConfig struct {
	Address string     `json:"address"`
	SASL    SASLConfig `json:"sasl"`
	TLS     TLSConfig  `json:"tls"`
}

type ConsumeConfig

type ConsumeConfig struct {
	Limit int64 `json:"limit"`
}

type Container

type Container struct {
	Data       interface{} `json:"data"`
	Schema     *Schema     `json:"schema"`
	SchemaType string      `json:"schemaType"`
}

type Element

type Element string

type JSONSerde

type JSONSerde struct {
	Serdes
}

func (*JSONSerde) Deserialize

func (*JSONSerde) Deserialize(data []byte, schema *Schema) (interface{}, *Xk6KafkaError)

Deserialize deserializes a map from bytes to be exported as object to JS.

func (*JSONSerde) Serialize

func (*JSONSerde) Serialize(data interface{}, schema *Schema) ([]byte, *Xk6KafkaError)

Serialize serializes a JSON object as map to bytes.

type Kafka

type Kafka struct {
	// contains filtered or unexported fields
}

type Message

type Message struct {
	Topic string `json:"topic"`

	// Setting Partition has no effect when writing messages.
	Partition     int                    `json:"partition"`
	Offset        int64                  `json:"offset"`
	HighWaterMark int64                  `json:"highWaterMark"`
	Key           []byte                 `json:"key"`
	Value         []byte                 `json:"value"`
	Headers       map[string]interface{} `json:"headers"`

	// If not set at the creation, Time will be automatically set when
	// writing the message.
	Time time.Time `json:"time"`
}

type Module

type Module struct {
	*Kafka
}

func (*Module) Exports

func (m *Module) Exports() modules.Exports

Exports returns the exports of the Kafka module, which are the functions that can be called from the JS code.

type ProduceConfig

type ProduceConfig struct {
	Messages []Message `json:"messages"`
}

type ReaderConfig

type ReaderConfig struct {
	WatchPartitionChanges  bool          `json:"watchPartitionChanges"`
	ConnectLogger          bool          `json:"connectLogger"`
	Partition              int           `json:"partition"`
	QueueCapacity          int           `json:"queueCapacity"`
	MinBytes               int           `json:"minBytes"`
	MaxBytes               int           `json:"maxBytes"`
	MaxAttempts            int           `json:"maxAttempts"`
	GroupID                string        `json:"groupId"`
	Topic                  string        `json:"topic"`
	IsolationLevel         string        `json:"isolationLevel"`
	StartOffset            int64         `json:"startOffset"`
	Offset                 int64         `json:"offset"`
	Brokers                []string      `json:"brokers"`
	GroupTopics            []string      `json:"groupTopics"`
	GroupBalancers         []string      `json:"groupBalancers"`
	MaxWait                time.Duration `json:"maxWait"`
	ReadLagInterval        time.Duration `json:"readLagInterval"`
	HeartbeatInterval      time.Duration `json:"heartbeatInterval"`
	CommitInterval         time.Duration `json:"commitInterval"`
	PartitionWatchInterval time.Duration `json:"partitionWatchInterval"`
	SessionTimeout         time.Duration `json:"sessionTimeout"`
	RebalanceTimeout       time.Duration `json:"rebalanceTimeout"`
	JoinGroupBackoff       time.Duration `json:"joinGroupBackoff"`
	RetentionTime          time.Duration `json:"retentionTime"`
	ReadBackoffMin         time.Duration `json:"readBackoffMin"`
	ReadBackoffMax         time.Duration `json:"readBackoffMax"`
	SASL                   SASLConfig    `json:"sasl"`
	TLS                    TLSConfig     `json:"tls"`
}

type RootModule

type RootModule struct{}

func New

func New() *RootModule

New creates a new instance of the root module.

func (*RootModule) NewModuleInstance

func (*RootModule) NewModuleInstance(virtualUser modules.VU) modules.Instance

NewModuleInstance creates a new instance of the Kafka module.

type SASLConfig

type SASLConfig struct {
	Username  string `json:"username"`
	Password  string `json:"password"`
	Algorithm string `json:"algorithm"`
}

type Schema

type Schema struct {
	EnableCaching bool                 `json:"enableCaching"`
	ID            int                  `json:"id"`
	Schema        string               `json:"schema"`
	SchemaType    *srclient.SchemaType `json:"schemaType"`
	Version       int                  `json:"version"`
	References    []srclient.Reference `json:"references"`
	Subject       string               `json:"subject"`
	// contains filtered or unexported fields
}

Schema is a wrapper around the schema registry schema. The Codec() and JsonSchema() methods will return the respective codecs (duck-typing).

func (*Schema) Codec

func (s *Schema) Codec() *goavro.Codec

Codec ensures access to Codec Will try to initialize a new one if it hasn't been initialized before Will return nil if it can't initialize a codec from the schema

func (*Schema) JsonSchema

func (s *Schema) JsonSchema() *jsonschema.Schema

JsonSchema ensures access to JsonSchema Will try to initialize a new one if it hasn't been initialized before Will return nil if it can't initialize a json schema from the schema

type SchemaRegistryConfig

type SchemaRegistryConfig struct {
	EnableCaching bool      `json:"enableCaching"`
	URL           string    `json:"url"`
	BasicAuth     BasicAuth `json:"basicAuth"`
	TLS           TLSConfig `json:"tls"`
}

type Serdes

type Serdes interface {
	Serialize(data interface{}, schema *Schema) ([]byte, *Xk6KafkaError)
	Deserialize(data []byte, schema *Schema) (interface{}, *Xk6KafkaError)
}

type StringSerde

type StringSerde struct {
	Serdes
}

func (*StringSerde) Deserialize

func (*StringSerde) Deserialize(data []byte, schema *Schema) (interface{}, *Xk6KafkaError)

Deserialize deserializes a string from bytes.

func (*StringSerde) Serialize

func (*StringSerde) Serialize(data interface{}, schema *Schema) ([]byte, *Xk6KafkaError)

Serialize serializes a string to bytes.

type SubjectNameConfig

type SubjectNameConfig struct {
	Schema              string  `json:"schema"`
	Topic               string  `json:"topic"`
	Element             Element `json:"element"`
	SubjectNameStrategy string  `json:"subjectNameStrategy"`
}

type TLSConfig

type TLSConfig struct {
	EnableTLS             bool   `json:"enableTls"`
	InsecureSkipTLSVerify bool   `json:"insecureSkipTlsVerify"`
	MinVersion            string `json:"minVersion"`
	ClientCertPem         string `json:"clientCertPem"`
	ClientKeyPem          string `json:"clientKeyPem"`
	ServerCaPem           string `json:"serverCaPem"`
}

type WireFormat

type WireFormat struct {
	SchemaID int    `json:"schemaId"`
	Data     []byte `json:"data"`
}

type WriterConfig

type WriterConfig struct {
	AutoCreateTopic bool          `json:"autoCreateTopic"`
	ConnectLogger   bool          `json:"connectLogger"`
	MaxAttempts     int           `json:"maxAttempts"`
	BatchSize       int           `json:"batchSize"`
	BatchBytes      int           `json:"batchBytes"`
	RequiredAcks    int           `json:"requiredAcks"`
	Topic           string        `json:"topic"`
	Balancer        string        `json:"balancer"`
	Compression     string        `json:"compression"`
	Brokers         []string      `json:"brokers"`
	BatchTimeout    time.Duration `json:"batchTimeout"`
	ReadTimeout     time.Duration `json:"readTimeout"`
	WriteTimeout    time.Duration `json:"writeTimeout"`
	SASL            SASLConfig    `json:"sasl"`
	TLS             TLSConfig     `json:"tls"`
}

type Xk6KafkaError

type Xk6KafkaError struct {
	Code          errCode
	Message       string
	OriginalError error
}

func GetDialer

func GetDialer(saslConfig SASLConfig, tlsConfig TLSConfig) (*kafkago.Dialer, *Xk6KafkaError)

GetDialer creates a kafka dialer from the given auth string or an unauthenticated dialer if the auth string is empty.

func GetSASLMechanism

func GetSASLMechanism(saslConfig SASLConfig) (sasl.Mechanism, *Xk6KafkaError)

GetSASLMechanism returns a kafka SASL config from the given credentials.

func GetTLSConfig

func GetTLSConfig(tlsConfig TLSConfig) (*tls.Config, *Xk6KafkaError)

GetTLSConfig creates a TLS config from the given TLS config struct and checks for errors. nolint: funlen

func NewXk6KafkaError

func NewXk6KafkaError(code errCode, msg string, originalErr error) *Xk6KafkaError

NewXk6KafkaError is the constructor for Xk6KafkaError.

func (Xk6KafkaError) Error

func (e Xk6KafkaError) Error() string

Error implements the `error` interface, so Xk6KafkaError are normal Go errors.

func (Xk6KafkaError) Unwrap

func (e Xk6KafkaError) Unwrap() error

Unwrap implements the `xerrors.Wrapper` interface, so Xk6KafkaError are a bit future-proof Go 2 errors.

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL