distributed-database

I apologize if this is the wrong venue for this. I can't tell if this behavior is buggy or just not what I expected.

Describe the problem

The disable_full_table_scans option seems so close to what I'm looking for, but not quite right.

My team is building an application atop CockroachDB with the intent of scaling horizontally. Naturally, we want to avoid using queries that require

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

Hello Philip!
I think there is an issue with this part of the code of rqlite (store/store.go).

func (s *Store) Database(leader bool) ([]byte, error) {
	if leader && s.raft.State() != raft.Leader {
		return nil, ErrNotLeader
	}
	// Ensure only one snapshot can take place at once, and block all queries.
	s.mu.Lock()
	defer s.mu.Unlock()

	f, err := ioutil.TempFile("", "rqlilte-snap-

Currently, the list_snapshots yb-admin command only prints the snapshot id and the state of the snapshot. It should also print more information such as the time of the snapshot. This is already tracked and filled for every snapshot in its state structure [see snapshot_state.cc]. We just need to expose it.

With Hive connector

trino:default> CREATE TABLE one (a varchar);
            -> CREATE VIEW two AS SELECT * FROM one;
CREATE TABLE
CREATE VIEW

DROP TABLE is rejected on a view:

trino:default> DROP TABLE two;
Query 20210906_150832_00015_id3y3 failed: line 1:1: Table 'hive.default.two' does not exist, but a view with that name exists. Did you mean DROP VIEW hive.default.t

Required by DataGrip. See crate/crate#11726

The full query is

select L.transactionid::varchar::bigint as transaction_id
from pg_catalog.pg_locks L                                                                               
where L.transactionid is not null                                                                        
order by pg_catalog.age(L

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