Table of Contents |
---|
Version 0.5 (Clementine)
Feature | Description | Notes |
---|---|---|
Concourse Criteria Language (CCL) | ||
Query Optimization | ||
User Attribution |
...
Conquest | ||
JSON Dumping | ||
CaSH Improvements | ||
Extended Permissions | ||
Aggregation Support |
Version 0.4 (Boysenberry)
...
Feature | Description | Plan | Notes |
---|---|---|---|
Distributed Concourse | Support the ability to distribute Concourse over many different commodity nodes while maintaining consistency and ACID transactions. | Distributed Concourse | |
Graph Queries | Give users the ability to query the relationships among records using graph algorithms (i.e. find the shortest path between two records on a given key). | ||
Geo Support | Automatically index geo data and allow users to perform geo queries/searches. | ||
SSL | Support secure connections between client and server and also between nodes in a cluster. | http://chamibuddhika.wordpress.com/2011/10/03/securing-a-thrift-service/ | |
Block Compression | Improve space efficiency by compressing blocks on disk. | Requires an upgrade task | |
Natural Language Processing | Improve fulltext indexing and search to conform more to natural language (i.e. don't just return results that match a keyword or phrase, but return results that match a certain semantic meaning) | ||
S3 Based Storage | Support the option to store data in a remote cloud service like S3 directly. | ||
Export Framework | Give users the ability to export data from Concourse to a file in an exchangeable format. | ||
Purge History | Give users the ability to purge all historical revisions before a certain timestamp. | ||
Nuke Data | Give users the ability to hard delete an entire record or an entire key in a record. Nuking data does not record a remove revision and purges all history associated with the key/record. | ||
Concourse Action Language (CAL) | Give users the ability to interact with Concourse using a language (e.g. SQL). | ||
Optional Indexing | Give users the ability to opt-out of secondary or fulltext indexing for a particular write. | ||
Web Admin UI | Give users the ability to manage Concourse from the Web. Think PhpMyAdmin but much more attractive. | ||
REST API | Expose the public api via REST. | ||
Search Result Ordering | Order results returned from search in a meaningful way (i.e. give the results a relevancy score) | ||
- Verify Cache
- Record snapshotting (along with block compression)
- Record directory
- Statistics gathering