Skip to content

Altinity/ClickHouse

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Website Apache 2.0 License

Altinity company logo

Altinity Stable Builds®

Altinity Stable Builds are releases of ClickHouse® that undergo rigorous testing to verify they are secure and ready for production use. Among other things, they are:

  • Supported for three years
  • Validated against client libraries and visualization tools
  • Tested for cloud use, including Kubernetes
  • 100% open source and 100% compatible with ClickHouse upstream builds
  • Available in FIPS-compatible versions

We encourage you to use Altinity Stable Builds whether you're an Altinity Support customer or not.

Acknowledgement

We at Altinity, Inc. are thoroughly grateful to the worldwide ClickHouse community, including the core committers who make ClickHouse the world's best analytics database.

What should I do if I find a bug in an Altinity Stable Build?

ClickHouse’s thousands of core features are all well-tested and stable. To maintain that stability, Altinity Stable Builds are built with a CI system that runs tens of thousands of tests against every commit. But of course, things can always go wrong. If that happens, let us know! We stand behind our work.

If you're an Altinity customer:

  1. Contact Altinity support to file an issue.

If you're not an Altinity customer:

  1. Try to upgrade to the latest bugfix release. If you’re using v23.8.8 but you know that v23.8.11.29 exists, start by upgrading to the bugfix. Upgrades to the latest maintenance releases are smooth and safe.
  2. Look for similar issues in the Altinity/ClickHouse or ClickHouse/ClickHouse repos; it's possible the problem has been logged and a fix is on the way.
  3. If you can reproduce the bug, try to isolate it. For example, remove pieces of a failing query one by one, creating the simplest scenario where the error still occurs. Creating a minimal reproducible example is a huge step towards a solution.
  4. File an issue in the Altinity/ClickHouse repo.

Useful Links


©2024 Altinity Inc. All rights reserved. Altinity®, Altinity.Cloud®, and Altinity Stable Builds® are registered trademarks of Altinity, Inc. ClickHouse® is a registered trademark of ClickHouse, Inc.

Languages

  • C++ 81.1%
  • Python 8.4%
  • Shell 4.2%
  • C 3.7%
  • CMake 1.3%
  • Jinja 0.6%
  • Other 0.7%