Even though it's a minority, I think it should be disabled by default. That's a cleaner approach. Accidentally running it in prod without unchecking 'clean' can be disastrous.
On Apr 28, 2017, at 8:01AM, Mahmoud Almokadem <prog.mahm...@gmail.com> wrote: > > Thanks Shawn, > > 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. > > Thanks, > Mahmoud > > > > > On Fri, Apr 28, 2017 at 2:51 PM, Shawn Heisey <apa...@elyograg.org> wrote: > > On 4/28/2017 5:11 AM, Mahmoud Almokadem wrote: >> >>> I'd like to request to uncheck the "Clean" checkbox by default on DIH >>> >> page, >> >>> cause it cleaned the whole index about 2TB when I click Execute button by >>> wrong. Or show a confirmation message that the whole index will be >>> >> cleaned!! >> >> When somebody is doing a full-import, clean is what almost all users are >> going to want. If you're wanting to do full-import without cleaning, >> then you are in the minority. It is perhaps a fairly large minority, >> but still not the majority. >> >> Also, once you move into production, you should not be using the admin >> UI for this. You should be calling the DIH handler directly with HTTP >> from another source, which might be a shell script using curl, or a >> full-blown program in another language. >> >> Thanks, >> Shawn > > > >
