On 4 January 2018 at 17:42, Will Norris <w...@willnorris.com> wrote: > I'm using perkeep in production with MySQL, though I'm not using dbNames, > just dbname.
Cool, thanks. > You mentioned migrating the index database... wouldn't it be sufficient to > simply rebuild the index and not worry about migrating? Or are you > specifically trying to avoid users having to do that? Yeah, migrating in a vague sense for now. i.e. in your case, making sure the index gets rebuilt. and also probably that the old database(s) get wiped, so as not to needlessly waste space? I assume people running their own instance with MySQL know how to deal with that, so the priority is to at least alert them about it. The main priority is to make it as automatic as possible for GCE users, who are not supposed to touch their MySQL manually. > On Thu, Jan 4, 2018 at 8:36 AM, Mathieu Lonjaret > <mathieu.lonja...@gmail.com> wrote: >> >> yeah, will do. >> >> >> On 4 January 2018 at 17:34, Brad Fitzpatrick <b...@danga.com> wrote: >> > We should at least fix the launcher case, which should be easy. We can >> > special-case that, detecting we're a launcher config and changing the >> > automatic config it builds at startup to use the old db names. >> > >> > >> > On Thu, Jan 4, 2018 at 7:47 AM, Mathieu Lonjaret >> > <mathieu.lonja...@gmail.com> wrote: >> >> >> >> Hi, >> >> >> >> as of rev 7eda9fd5027fda88166d6c03b6490cffbf2de5fb >> >> >> >> >> >> (https://github.com/camlistore/camlistore/commit/7eda9fd5027fda88166d6c03b6490cffbf2de5fb), >> >> the default names of the various databases used by Perkeep change. >> >> That basically means: >> >> >> >> 1) if you were using dbNames (not dbname), to set your "index" >> >> database name, then it concerns you. >> >> 2) if you were using dbNames for the other "secondary" indexes and >> >> queues then your are affected, but it's maybe not as important. >> >> 3) If you are running a Camli/Perkeep instance on GCE, deployed with >> >> the launcher, you fall into case 1) (and case 2) as well). >> >> >> >> We probably need to think about a transition patch to help users >> >> migrate at least their index database, or at the very least warn them. >> >> >> >> But to figure out how much effort we have to put into this, it would >> >> help to know how many among you are affected. >> >> >> >> So, if you are either running Perkeep in production with a DBMS >> >> (MySQL, PostgreSQL, MongoDB), or running an instance from the GCE >> >> launcher, could you please let us know? >> >> >> >> Feel free to forward this to friends who are not on the mailing-list >> >> too. >> >> >> >> Thanks. >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> >> Groups >> >> "Camlistore" group. >> >> To unsubscribe from this group and stop receiving emails from it, send >> >> an >> >> email to camlistore+unsubscr...@googlegroups.com. >> >> For more options, visit https://groups.google.com/d/optout. >> > >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "Camlistore" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> > an >> > email to camlistore+unsubscr...@googlegroups.com. >> > For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Camlistore" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to camlistore+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Camlistore" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to camlistore+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Camlistore" group. To unsubscribe from this group and stop receiving emails from it, send an email to camlistore+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
