skip to main content
Close Icon We use cookies to improve your website experience.  To learn about our use of cookies and how you can manage your cookie settings, please see our Cookie Policy.  By continuing to use the website, you consent to our use of cookies.
Global Search Configuration

Introduction

Roughly 18 months after its unveiling, the Kudu analytics storage engine is now becoming an officially supported part of the Cloudera Enterprise Hadoop platform.

Highlights

  • This note analyzes where Kudu fits in with the Hadoop platform.

Features and Benefits

  • Discusses how Kudu picks up where other Hadoop technologies, such as HDFS, HBase, and Parquet, leave off.
  • Drills down on the trade-offs involved with Kudu.
  • Analyzes the synergies with Impala.

Key questions answered

  • What gaps does Kudu fill?
  • Why use Kudu instead of Parquet?
  • How does Kudu work with Impala, or other Hadoop data access methods?

Table of contents

Ovum view

  • Summary
  • Filling a gap in the Hadoop stack
  • Why was Kudu necessary?
  • Why use Kudu?
  • How does Kudu stack up to the alternatives?

Appendix

  • Further reading
  • Author

Recommended Articles

;

Have any questions? Speak to a Specialist

Europe, Middle East & Africa team - +44 (0) 207 017 7700


Asia-Pacific team - +61 (0)3 960 16700

US team - +1 646 957 8878

Email us at ClientServices@ovum.com

You can also contact your named/allocated Client Services Executive using their direct dial.
PR enquiries - Call us at +44 788 597 5160 or email us at pr@ovum.com

Contact marketing - 
marketingdepartment@ovum.com

Already an Ovum client? Login to the Knowledge Center now