Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-7850

Move user customization out of solr.in.* scripts

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 5.2.1
    • 6.3
    • scripts and tools
    • None

    Description

      I've seen a fair number of users customizing solr.in.* scripts to make changes to their Solr installs. I think the documentation suggests this, though I haven't confirmed.

      One possible problem with this is that we might make changes in those scripts which such a user would want in their setup, but if they replace the script with the one in the new version, they will lose their customizations.

      I propose instead that we have the startup script look for and utilize a user customization script, in a similar manner to linux init scripts that look for /etc/default/packagename, but are able to function without it. I'm not entirely sure where the script should live or what it should be called. One idea is server/etc/userconfig.{sh,cmd} ... but I haven't put a lot of thought into it yet.

      If the internal behavior of our scripts is largely replaced by a small java app as detailed in SOLR-7043, then the same thing should apply there – have a config file for a user to specify settings, but work perfectly if that config file is absent.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            dsmiley David Smiley
            elyograg Shawn Heisey
            Votes:
            2 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment