Thanks Shawn for your clarifications, I think showing a confirmation message saying that "The whole index will be cleaned" when the clean option is checked will be good.
I always remove the check from the file /opt/solr/server/solr-webapp/webapp/tpl/dataimport.html after installing solr but when I upgraded it this time forget to do that and press Execute with the check and the whole index cleaned. And for the dataimport I always use the old UI cause the new UI doesn't show the live update and sometimes doesn't show the configuration. I think there are many bugs on the new UI. Thanks, Mahmoud On Mon, May 1, 2017 at 4:30 PM, Shawn Heisey <apa...@elyograg.org> wrote: > On 4/28/2017 9:01 AM, Mahmoud Almokadem wrote: > > We already using a shell scripts to do our import and using fullimport > > command to do our delta import and everything is doing well several > > years ago. But default of the UI is full import with clean and commit. > > If I press the Execute button by mistake the whole index is cleaned > > without any notification. > > I understand your frustration. What I'm worried about is the fallout if > we change the default to be unchecked, from people who didn't verify the > setting and expected full-import to wipe their index before it started > importing, just like it has always done for the last few years. > > The default value for the clean parameter when NOT using the admin UI is > true for full-import, and false for delta-import. That's not going to > change. I firmly believe that the admin UI should have the same > defaults as the API itself. The very nature of a full-import carries > the implication that you want to start over with an empty index. > > What if there were some bright red text in the UI near the execute > button that urged you to double-check that the "clean" box has the > setting you want? An alternate idea would be to pop up a yes/no > verification dialog on execute when the clean box is checked. > > Thanks, > Shawn > >
