Motivation
...
- Newly created index is in offline state
- offline index cannot be read, only modified (in scope of index rebuild or regular updates)
- index becomes online after index rebuild
- Index may be created on cache start, by DDL command or by API call (direct call to IndexManager)
- on index create an Index instance is created using provided factory, this way we may introduce geospatial indexes or prefix trees in future just providing specific factory.
- sorted index represents a database index in terms of SQL and requires hash index created first (if not exists).
- hash index is just a proxy to cache partitions and always online, it represents a table in terms of SQL. This way SQL queries may be executed before index is fully built
...
On index create
...
:
- index created - all indexes and definitions registered on all nodes, all indexes starts applying current updates
- onIndexCreate() callback executes - index is registered in a query execution engine
- index rebuild started - index is filling up with existing data
- index rebuild finished - index is ready to use
- onIndexStateChange() callback executes - index becomes available for a query execution engine.
...
New indexes should be binary compatible with current H2 indexes
Dev list discussion
will be added later
JIRA tickets
http://apache-ignite-developers.2346864.n4.nabble.com/Basic-index-infrastructure-as-a-part-of-core-APIs-td47638.html
JIRA tickets
Jira |
---|
server | ASF JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
maximumIssues | 20 |
---|
jqlQuery | labels = IEP-49 |
---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
---|
|
will be added later