A Cluster configuration of FeatureBase nodes where data is evenly distributed and any node can respond to queries. Also defines how data is replicated and inter-node communication.
Concurrency
SQL/PQL Queries
Number of concurrent users running queries on data and how this may affect query latency
FeatureBase Community Row fields and database shards
A fragment typically corresponds to a file on disk which represents an intersection of: * field and shard, or * field, shard and time data type time quantum constraint
Freshness
Data import/ingest
How much time elapses from when a data point is “sensed” by the system, until that data point will affect the results of a query.
A FeatureBase field type similar to the Set type, in which only a single value can be set at any time. Conceptually similar to an enum type, but implemented on top of Set fields, with a performance cost from the single-value constraint. Not to be confused with the mutex synchronization primitive.
N
Term
Context
Additional information
Node
FeatureBase Community Cluster
An individual running instance of FeatureBase server which belongs to a cluster.
Normalizing
The act of identifying the cardinality of your data in order to design the relationships between different tables.
Equivalent to RDBMS table row. FeatureBase uses “Record” to avoid confusion
Replica cluster.replicas parameter
FeatureBase Community Clusters
Replica of shard within a cluster. cluster.replicas configuration parameter determines the number of shard replicas within a cluster where replicas=1 indicates no copies have been made.
Rows are the fundamental vertical data axis within FeatureBase. Rows are namespaced by field so the same row ID in a different field refers to a different row.