Uploaded image for project: 'CloverDX'
  1. CloverDX
  2. CLO-10567

Warn from using Derby DB on production

    XMLWordPrintable

    Details

    • Story Points:
      2
    • QA Testing:
      UNDECIDED
    • Epic Link:
    • Sprint:
      Blue Sprint 98, Blue Sprint 99

      Description

      What usually happens is, people after trial go with CloverETL server live with the same configuration they used. Which may cause nightmare to support on a long run. Upgrade from Derby DB is almost impossible without data loss and tends to be sluggish when grows big.

      My recommendation would be, doing the same thing as was done with OpenJDK use warning, let people know somewhere on plain sight - the thing they do have installed is not a production-grade configuration.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              horskyt Tomas Horsky
              Reporter:
              svecp Pavel Svec
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: