Can't delete index (3.5 RC 3)

[Johan]

I am having a problem with an incorrect index definition which I can't seem to remove.

I migrated to 3.5 and one of my indexes has an incorrect definition. For some reason the index used to work, though it truly has an unterminated string constant in the definition.

When I start 3.5 I get a message about this.

Index '32-(MyIndex)' removed because it is not found or invalid

I correct my index definition and perform PutIndex with the overwrite option set to true. This creates the correct index.

I clear my alerts on the DB and restart the DB.

I get the same error message that index 32 is incorrect and removed. I do however have my newly created index (with the same name), but this now has a different index ID.

How do I get rid of this incorrect index definition?

Or how should I have corrected this index definition as it seems to have created a new definition instead of overwriting the existing one.

- Johan

[Oren Eini (Ayende Rahien)]

Can you check the IndexDefinitions folder? Do you have 32 there?

Hibernating Rhinos Ltd  

Oren Eini l CEO l Mobile: + 972-52-548-6969

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811

 

--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Johan]

Yes the IndexDefinition folder has a definition for index 32. It is the original definition with the error in there.

The Index folder also has a subfolder 32.

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.

[Johan]

Turns out the database I sent as part of RavenDB-5160 should have this issue as well. In this test DB it is index 29 that has the problem (same index). I can send you a test case if needed as well.

I am fine that it removes the index (as it is incorrect), as long as it truly deletes it.

[Oren Eini (Ayende Rahien)]

Yes, this is by design, if for some reason we can't create the index, we will avoid doing so, but we'll not delete the index.

Typically, index init failure after it is created is because you are missing an analyzer, and it is expected the admin will correct it

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.

[Johan]

Ok, but how do I correct it.

I correct my index definition and perform PutIndex with the overwrite option set to true. This creates a new correct index, but it still didn't delete the old incorrect index. Everything is working, but I always get this error about this old index.

[Oren Eini (Ayende Rahien)]

Manually go to the directory and delete the old index directory

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.

[Johan]

Even removing the .index file from the IndexDefinitions and the index folder from Indexes doesn't clear the error in I see in the alerts (I delete all alerts, save, then restart the db and the alert is back with the starting time of the new start of the db).

The error message has changed slightly.

Index '32-(Unknown Name)' removed because it is not found or invalid

Before the removal of the .index file it still knew the name of the index in question, but now it mentions "Unknown Name".

Deleting the index from my old data directory before the migration does seem to get rid of this.

[ar...@ayende.com]

Hi Johan,

we have found the issue and fixed it (http://issues.hibernatingrhinos.com/issue/RavenDB-5491). Thanks for the report.

Regards,
Arek

[Johan]

Awesome!

Thanks,

Johan