distributed-database
Here are 269 public repositories matching this topic...
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:

 the datestyle used by the database. It seems like there is already some implementation for that.
Feature description:
As a db tool engineer I want to be able to fetch the set datestyle of a database to be know how to interpret dates in my tool.
extra: ability
I thought the size of std::bitset<16> is 2 bytes, but it turns out it's 8 bytes
#include <bitset>
#include <iostram>
int main() {
std::cout << sizeof(std::bitset<2>) << std::endl;
std::cout << sizeof(std::bitset<8>) << std::endl;
std::cout << sizeof(std::bitset<16>) << std::endl;
std::cout << sizeof(std::bitset<32>) << std::endl;
std::cout << sizeof(std::bitset
-
Updated
Mar 8, 2022 - Go
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
-
Updated
Aug 6, 2021 - Go
-
Updated
Mar 7, 2022 - C++
-
Updated
Jul 17, 2020 - C++
-
Updated
May 6, 2017 - C++
-
Updated
Mar 8, 2022 - Java
-
Updated
Mar 8, 2022 - Go
-
Updated
Sep 27, 2021 - C++
-
Updated
Mar 8, 2022 - Rust
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
Improve this page
Add a description, image, and links to the distributed-database topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the distributed-database topic, visit your repo's landing page and select "manage topics."
What happened?
If you don't pass a
--nameargument to youretcdprocesses, they will all have the namedefaultand the cluster will operate normally. However, when you add a member, the generatedETCD_INITIAL_CLUSTERvariable will have multiple entries with the name "default". When this environment variable is used,etcdwill parse these into a mapping under a single key ("defau