TF_DeleteTensor(fetchValues[0]);
  TF_DeleteTensor(fetchValues[1]);
}

// REGISTER_OP for CApiAttributesTest test cases.
// Registers two ops, each with a single attribute called 'v'.
// The attribute in one op will have a type 'type', the other
// will have list(type).
#define ATTR_TEST_REGISTER_OP(type)                           \
  REGISTER_OP("CApiAttributesTestOp" #type)                   \

		// GetObjectAttributes
		router.Methods(http.MethodGet).Path("/{object:.+}").
			HandlerFunc(s3APIMiddleware(api.GetObjectAttributesHandler, traceHdrsS3HFlag)).
			Queries("attributes", "")

		// CopyObjectPart
		router.Methods(http.MethodPut).Path("/{object:.+}").
			HeadersRegexp(xhttp.AmzCopySource, ".*?(\\/|%2F).*?").
			HandlerFunc(s3APIMiddleware(api.CopyObjectPartHandler)).

    // ===================================================================================
    //                                                                           Attribute
    //

    /**
     * Search engine client for performing maintenance operations on indices.
     */
    @Resource
    protected SearchEngineClient searchEngineClient;

The `security_scopes` object (of class `SecurityScopes`) also provides a `scope_str` attribute with a single string, containing those scopes separated by spaces (we are going to use it).

We create an `HTTPException` that we can reuse (`raise`) later at several points.

#### Daten-„Schema“ { #data-schema }

Der Begriff „Schema“ kann sich auch auf die Form von Daten beziehen, wie z. B. einen JSON-Inhalt.

In diesem Fall sind die JSON-Attribute und deren Datentypen, usw. gemeint.

#### OpenAPI und JSON Schema { #openapi-and-json-schema }

	UserDefined         map[string]string   // only set in case of POST/PUT operations
	ObjectAttributes    map[string]struct{} // Attribute tags defined by the users for the GetObjectAttributes request
	MaxParts            int                 // used in GetObjectAttributes. Signals how many parts we should return

labels.oic_default_groups=Default Groups
labels.oic_default_roles=Default Roles
labels.general_menu_saml=SAML
labels.saml_sp_base_url=SP Base URL
labels.saml_attribute_group_name=Group Attribute Name
labels.saml_attribute_role_name=Role Attribute Name
labels.saml_default_groups=Default Groups
labels.saml_default_roles=Default Roles
labels.general_menu_spnego=SPNEGO
labels.spnego_krb5_conf=Krb5 Config

labels.oic_default_groups=Default Groups
labels.oic_default_roles=Default Roles
labels.general_menu_saml=SAML
labels.saml_sp_base_url=SP Base URL
labels.saml_attribute_group_name=Group Attribute Name
labels.saml_attribute_role_name=Role Attribute Name
labels.saml_default_groups=Default Groups
labels.saml_default_roles=Default Roles
labels.general_menu_spnego=SPNEGO
labels.spnego_krb5_conf=Krb5 Config

labels.oic_default_groups=Default Groups
labels.oic_default_roles=Default Roles
labels.general_menu_saml=SAML
labels.saml_sp_base_url=SP Base URL
labels.saml_attribute_group_name=Group Attribute Name
labels.saml_attribute_role_name=Role Attribute Name
labels.saml_default_groups=Default Groups
labels.saml_default_roles=Default Roles
labels.general_menu_spnego=SPNEGO
labels.spnego_krb5_conf=Krb5 Config

    *   `Estimator.export_savedmodel` has been renamed to `export_saved_model`.
    *   When saving to SavedModel, Estimators will strip default op attributes.
        This is almost always the correct behavior, as it is more forwards
        compatible, but if you require that default attributes to be saved with
        the model, please use `tf.compat.v1.Estimator`.
    *   Feature Columns have been upgraded to be more Eager-friendly and to work