Skip to content
#

distributed-database

Here are 275 public repositories matching this topic...

mortehu
mortehu commented Mar 3, 2022

What happened?

If you don't pass a --name argument to your etcd processes, they will all have the name default and the cluster will operate normally. However, when you add a member, the generated ETCD_INITIAL_CLUSTER variable will have multiple entries with the name "default". When this environment variable is used, etcd will parse these into a mapping under a single key ("defau

cockroach
mgartner
mgartner commented Apr 19, 2022

There are several optimization the execution engine can perform when evaluating LIKE patterns with %, which matches zero or any number of any character. For example, see #80073.

Sequential %s can prevent these optimizations, but they are semantically equivalent to a single %, so the optimizer should normalize them to a single %.

For example:

-- The following expressions 
C-enhancement good first issue T-sql-queries
sfc-gh-ajbeamon
sfc-gh-ajbeamon commented Aug 9, 2021

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

yugabyte-db
chrisckchang
chrisckchang commented Mar 16, 2022

Description

source: https://docs.yugabyte.com/latest/architecture/transactions/isolation-levels/#root

We begin the section by listing out 4 transaction isolation levels in decreasing order of strictness. Where possible, subsequent sections should follow this order to make it easier for readers to follow. For example, rewrite the second paragraph to read:

YugabyteDB supports three transa

good first issue area/documentation
risingwave
yezizp2012
yezizp2012 commented May 25, 2022

Requirements
We want to support the owner field for database / schema / table / source objects. The implementation should be based on the user account management design recorded in #2193 , and should work as an addition to the feature chunk for supporting the concepts of and operations related to database, schema, and users (tracked in #2150 )
References
Please use #2150 as the main ref

type/enhancement good first issue help wanted component/meta
dengn
dengn commented May 3, 2022

Is there an existing issue for the same feature request?

  • I have checked the existing issues.

Is your feature request related to a problem?

Several showcase SQL requires the support of this function:


select DATE_FORMAT(b.measurement_time,'%Y-%m-%d') 

select DATE_FORMAT(FROM_UNIXTIME(tm.create_time), %Y%m%d)

Describe the feature you'd like

good first issue kind/feature MatrixCamp Challenging
IceFireDB

IceFireDB is a database built for web3 and web2. It strives to fill the gap between web2 and web3 with a friendly database experience, making web3 application data storage more convenient, and making it easier for web2 applications to achieve decentralization and data immutability.

  • Updated Jun 1, 2022
  • Go
jakekgrog
jakekgrog commented Jul 16, 2020

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

enhancement good first issue

Improve this page

Add a description, image, and links to the distributed-database topic page so that developers can more easily learn about it.

Curate this topic

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."

Learn more