distributed-database

lightning v5.3.0

After the content in parquet may be written by spark, the definition of bool is true or false. Regenerating the parquet file takes time, In tidb, bool behaves as tinyint, so proper type conversion will help improve the success rate of lightning import

parquet file：
![image](https://user-images.githubusercontent.com/21033020/147809823-214dcb34-0e10-4566-aa75-2109c0525144

Currently, the ulid_to_uuid builtin passes raw parsing errors back to the user, which get turned into internal errors. These should be returned with parsing error codes of some sort.

Our CMake build process produces tarball packages using the cpack TGZ target. This produces a server and client package with a file layout meant to match where the various artifacts go.

Meanwhile, the packages we include on the download page are a flat archive of various binaries produced by the build process. This include one regular package and one debug package with debug symbols for a few

Description

Currently, the table "write_read_test" in keySpace "system_platform" is counted towards user tables, so even when the user has only one table, the portal shows the user has two tables.

![image](https://user-images.githubusercontent.com/23063104/152056332-f32dc60a-d9ce-

The current test TestCassandraConnectorTest has some issues:

• Unrelated types in a table
  • It reduces maintainability when we want to add test cases to a type
• The definition and data are managed in the different class
  • We need to look for the different class when we want to check the expected values
• Less coverage in a type
  • Should test min, max, null
  • Should test DST, juli

Use case:
Add the ability to search for an element in an array and retrieve back the array index.
As per the PostgreSQL documentation:

array_position ( anycompatiblearray, anycompatible [, integer ] ) → integer

Returns the subscript of the first occurrence of the second argument in the array, or NULL if it's not present

StarRocks is compiled using c++17, so instead of relying on boost::variant, we can use std::variant.

This is a very simple issue, you can try this modification

Currently we don't have any mechanism to limit the maximum number of clients that could be handled simultaneously.

This feature should be designed properly. Here is some clue: https://redis.io/topics/clients#maximum-number-of-clients

Now that we support more than 1 data type, we should include the values data type in cache nodes. This give us a way of easily identifying what type of data a key points to e.g. string, queue (and more types in the future)

Currently a cache node object consists of a Key, a Value and a TTL. We should also add a field specifying the type of the Value