},
      "french_stop": {
        "type":       "stop",
        "stopwords":  "_french_"
      },
      "french_keywords": {
        "type":       "keyword_marker",
        "keywords": ["Bonjour", "monde", "recherche"]
      },
      "french_stemmer": {
        "type":       "stemmer",
        "language":   "light_french"
      },
      "german_stop": {
        "type":       "stop",

// elsewhere), the AssumeRole case (because the parent user is real and their
// policy is associated via policy-set API) and the AssumeRoleWithLDAP case
// (because the policy association is made via policy-set API).
func (sys *IAMSys) SetTempUser(ctx context.Context, accessKey string, cred auth.Credentials, policyName string) (time.Time, error) {
	if !sys.Initialized() {
		return time.Time{}, errServerNotInitialized

     * changing any bin. The operations must not take any action that could even momentarily
     * cause a concurrent read operation to see inconsistent data. This is made easier by the
     * nature of the read operations in Map. For example, no operation can reveal that the table
     * has grown but the threshold has not yet been updated, so there are no atomicity requirements