tsdb

Bug Description
fix issues found by Coverity Scan in taosdump.c

To Reproduce
Steps to reproduce the behavior:
N/A

Expected Behavior
fix following issues found by Coverity Scan in taosdump.c

1. String not null terminated High TDengine/src/kit/taos-tools/src/benchUtil.c postProceSql
2. Resource leak High TDengine/src/kit/taos-tools/src/taosdump.c parse_json_to_recordschema
   3

Scenario

A user is ingesting some data (~300M rows) into a table with 270K distinct symbol values. For each of these 270K symbols we end up with at least one posix_fallocate() necessary to add a new value block. See the below flamegraph - it's quite illustrative.

An important part of the scenario is non-default index block capacity which is set to 2048. With the default capacity (w

示例

• 企业或者组织: 夜莺
• 地点：北京
• 联系方式：contact-us at xxx.com
• 使用场景和经验分享：你们最看重夜莺的哪些功能，解决一个什么样的问题，以及使用规模和范围，使用夜莺监控构建企业级监控体系的过程中，有哪些好的经验分享。
• 需求建议：希望哪些点上夜莺监控能做的更好，更契合您的使用场景。

Describe the bug

Not all resources declare their namespaces. Because of this running helm template --namespace foo .. | kubectl apply -f - creates the resources in the current namespace, not in foo

To Reproduce

Steps to reproduce the behavior:

1. Checkout any version of the chart. cd operations/helm/charts/mimir-distributed
2. Have a kubernetes cluster where the foo na

Describe the requested changes:
This page could be simplified. The most impactful change: Do not start with the "Any (No JVM)" version. It forces us to bother users with the Java version, JAVA_HOME env. variable, etc. That's scary, especially for non-Java folks. If we start with the OS-specific versions and leave the "No JVM" version in some "f