[FRG-312] create index on existing data should not hold catalog lock during execution

LucidDB / luciddb

DEFUNCT: See README

https://github.com/LucidDB/luciddb

Apache License 2.0

53 stars 24 forks source link

[FRG-312] create index on existing data should not hold catalog lock during execution #560

Open dynamobi-build opened 12 years ago

dynamobi-build commented 12 years ago

[reporter="jvs", created="Tue, 4 Mar 2008 16:43:53 -0500 (GMT-05:00)"] Should take lock at beginning to update catalog, store index definition, and mark it as build-pending, then drop lock; then after execution, update state to reflect completion. Optimizer has to avoid trying to use index while build-pending, and if a crash occurs, need to figure out how to deal with the bad index.

dynamobi-build commented 12 years ago

[author="jvs", created="Thu, 6 Mar 2008 23:12:57 -0500 (GMT-05:00)"] DROP INDEX has a similar issue, although it should run much faster.