On Wed, Nov 25, 2015, at 05:09 PM, Alexandre Rafalovitch wrote: > I am testing 5.4 branch and was enjoying new UI for adding/removing > fields in the schema. > > So, for a test of an error message, I decided to delete the ID field. > And it let me. And then I indexed some files and the ID got recreated > as a generic field. > > Should this be allowed or should delete field API check that we are > not deleting the uniqueKey? I can kind of see it both ways.
There's much damage can be done with the "delete field" button :-) I think it makes sense to add a "are you sure you want to delete your unique key?" warning to the UI, in 5.5. We could actually add a check to see if the field has content, and warn them before deleting a field with content. Those would both make lots of sense. Upayavira --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
