Non-atomic option for buildwatson

[dustinrb]

Although having buildwatson add SearchEntries entries atomically is preferable, adding batches of SearchEntries to the database can help the index build successfully complete for large indexes (>1 GB).

This PR adds two flags to buildwatson:

• --non_atomic: Submits each batch in a non-atomic transaction. It will create and incomplete index if buildwatson fails but may help with make large indexing jobs more stable.

• --batch_size=100: Changes the batch size buildwatson uses to add entries to the database.

[amureki]

@dustinrb @etianen wiki/docs update would be good for this one. :)

[dustinrb]

I'm happy to write some brief documentation. I can expand the "Manually updating the search indexes" subsection of the Registering Models section on the wiki. Let me know if you can think of a better place to put this information.

[etianen]

Maybe a new wiki page dedicated to management commands would be good?

…

On 11 December 2017 at 23:19, Dustin Broderick ***@***.***> wrote: I'm happy to write some brief documentation. I can expand the "Manually updating the search indexes" subsection of the *Registering Models* section on the wiki. Let me know if you can think of a better place to put this information. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#229 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAJFCI9p76wSt5NqFFRvCEeEjhrSuzMgks5s_biUgaJpZM4Q4Yic> .