We will continue to build upon a forked Elasticsearch and Kibana 7. Open Distro for Elasticsearch is an Elasticsearch-compatible stack that is made up of several projects. Each of these projects can be built and installed independently of Open Distro for Elasticsearch on the corresponding version of open source Elasticsearch.
They have not been tested with the default download from Elastic, which includes proprietary software, but we welcome the community to test and enhance individual plugins for compatibility with the Elastic Stack. Open Distro for Elasticsearch is powered by the Apache 2. All clients and tools that are compatible with this underlying version of Elasticsearch should work without modification.
We are just getting started. You are invited to join us in creating innovative new features. Try the Logstash Helm Chart beta. This default distribution is governed by the Elastic License, and includes the full set of free features. A pure Apache 2. Elastic's documentation helps you with all things implementation — from installation to solution components and workflow. Download Logstash. GA Release. Preview Release. Download and unzip Logstash. Choose platform:.
Package managers:. Configure Logstash. Run Logstash. Dive in. We have dropped support for Java 7 and removed the previously deprecated Scala producer and consumer. Kafka Connect includes a number of improvements and features. KIP enables you to control how errors in connectors, transformations and converters are handled by enabling automatic retries and controlling the number of errors that are tolerated before the connector is stopped.
More contextual information can be included in the logs to help diagnose problems and problematic messages consumed by sink connectors can be sent to a dead letter queue rather than forcing the connector to stop.
KIP adds a new extension point to move secrets out of connector configurations and integrate with any external key management system. The placeholders in connector configurations are only resolved before sending the configuration to the connector, ensuring that secrets are stored and managed securely in your preferred key management system and not exposed over the REST APIs or in log files.
Scala users can have less boilerplate in their code, notably regarding Serdes with new implicit Serdes. Message headers are now supported in the Kafka Streams Processor API, allowing users to add and manipulate headers read from the source topics and propagate them to the sink topics.
Windowed aggregations performance in Kafka Streams has been largely improved sometimes by an order of magnitude thanks to the new single-key-fetch API. We have further improved unit testibility of Kafka Streams with the kafka-streams-testutil artifact. Here is a summary of some notable changes: Kafka 1. ZooKeeper session expiration edge cases have also been fixed as part of this effort.
Controller improvements also enable more partitions to be supported on a single cluster. KIP introduced incremental fetch requests, providing more efficient replication when the number of partitions is large.
Some of the broker configuration options like SSL keystores can now be updated dynamically without restarting the broker. See KIP for details and the full list of dynamic configs. Delegation token based authentication KIP has been added to Kafka brokers to support large number of clients without overloading Kerberos KDCs or other authentication servers. Additionally, the default maximum heap size for Connect workers was increased to 2GB. Several improvements have been added to the Kafka Streams API, including reducing repartition topic partitions footprint, customizable error handling for produce failures and enhanced resilience to broker unavailability.
See KIPs , , , and for details. Here is a summary of a few of them: Since its introduction in version 0. For more on streams, check out the Apache Kafka Streams documentation, including some helpful new tutorial videos.
These are too many to summarize without becoming tedious, but Connect metrics have been significantly improved KIP , a litany of new health check metrics are now exposed KIP , and we now have a global topic and partition count KIP Over-the-wire encryption will be faster now, which will keep Kafka fast and compute costs low when encryption is enabled.
Previously, some authentication error conditions were indistinguishable from broker failures and were not logged in a clear way. This is cleaner now.
0コメント