Allow some loader properties to be set per job instead of global

XMLWordPrintable

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor
    • None
    • Affects Version/s: 2.4.0
    • Component/s: grouperLoader
    • None

      Certain loader job properties take effect on a global level, and can't be configured differently per job. So if different jobs have a different need, there is currently no option except to decide on a compromise at the enterprise level. E.g., these are some options that would be useful to set per job:

      • loader.sqlTable.likeString.removeGroupIfNotUsed = true
      • loader.sqlTable.likeString.removeGroupIfMemberOfAnotherGroup = false
      • loader.ldap.requireTopStemAsStemFromConfigGroup = true
      • loader.allowBlankGroupDescriptions = false
      • loader.deleteGroupsNoLongerInSource = false
      • loader.ldap.requireTopStemAsStemFromConfigGroup = true
      • loader.ldap.resultsTransformationDelimitedValueExampleDelimiter = -
      • ...

            Assignee:
            Chris Hyzer (upenn.edu)
            Reporter:
            Chad Redman (unc.edu) (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: