Version 0.5 (Clementine)
- User Attribution
- Environment Permissions
- Query Optimization
- Block Compression
- Upgrade Framework
Version 0.4 (Boysenberry)
This version focuses on new features that make it easier to bring data into the system and query it in complex ways. We hope that these features will increase user adoption and allow us to create more compelling demos and representative test cases. Additionally, we will also make changes to incrementally improve performance, where possible.
| Feature | Description | Notes |
|---|---|---|
| Import Framework | Give users the ability to bulk import raw data from a single CSV file into Concourse. | CON-33 - Getting issue details... STATUS |
| Performance Improvements | Tackle any obvious low hanging fruit that will incrementally improve write/read performance that users experience. | CON-38 - Getting issue details... STATUS |
| Environments | Allow users to store different data sets in different namespaces that are all managed by the same Concourse server. | CON-37 - Getting issue details... STATUS |
| Criteria Builder | Allow users to programmatically build complex find queries (e.g. conjunctive, disjunctive, combination, etc). | CON-39 - Getting issue details... STATUS |
| Bulk Insert | Allow the client to efficiently insert many key/value pairs into one or more records by reducing network overhead and farming work from the the client to the server. | CON-40 - Getting issue details... STATUS |
Schedule
| Release | Date | Notes |
|---|---|---|
| General Availability | TBD |
Version 0.3 (Avocado)
This version focuses on improving the database storage model and adding new features related to security, usability and data consistency.
Schedule
| Release | Date | Notes |
|---|---|---|
| General Availability | 2/1/14 | https://github.com/cinchapi/concourse/releases/tag/v0.3.0 |
| Update 1 | 3/9/14 | https://github.com/cinchapi/concourse/releases/tag/v0.3.1 |
| Update 2 | 3/16/14 | https://github.com/cinchapi/concourse/releases/tag/v0.3.2 |
| Update 3 | 3/25/14 | https://github.com/cinchapi/concourse/releases/tag/v0.3.3 |
| Update 4 | 4/13/14 | https://github.com/cinchapi/concourse/releases/tag/v0.3.4 |
| Update 5 | 5/26/14 | https://github.com/cinchapi/concourse/releases/tag/v0.3.5 |
Backlog
These features may be added in a future release.
| 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) |