I saw the default sharding scheme for Secondary Indexes is HASH for the first column. (https://docs.yugabyte.com/preview/explore/indexes-constraints/secondary-indexes-ysql/)
My DDL is generated mostly via ORM (hibernate: create index IDXname on tbl_name (date_column_name)).

We are performing tests for an aggregator application, and are observing some differences on how data is being displayed for certain datatypes (double and decimal so far) between Cassandra and YugabyteDB.

Can you shard based on a key that has duplicate values, or does it need to be unique like a primary key? I have a table where data, including a Date, is added daily. The table’s structure is:

Issue: Compilation Failed
I have attached the CMakeError.log file.
Yugabyte Version: 2.14.11
System Info:
OS – Ubuntu22.04
Architecture: x86_64

I’m trying to create a fresh installation with one master and tserver. My first order of business was to modify the default password and I keep getting the following error:

Lets assume I have a 3 nodes setup, and a replication factor of 3 and a database of around 150GB.

I have a problem when using yugabyte with persistence volume in docker.
On first run everything work fine, but when re-create container with existing volume, it fail to start:
master.err :

Newbie user here, starting to use yugabyteDB with some transactional queries.
Regarding optimistic and pessimistic locks, could somebody please clarify what is supported by yugabyte?

Is there’s a way to auto-discover the current leader of YB-master machine? Or can we proxy the ysql requests from follower to leader?

Is there’s a way to auto-discover the current leader of YB-master machine? Or can we proxy the ysql requests from follower to leader?