corona.schema — corona 0.1.16

add-field! clj

(add-field! client-config field-map)

The add-field command adds a new field definition to your schema. If a field with the same name exists an error is thrown.

All of the properties available when defining a field with manual schema.xml edits can be passed via the API. These request attributes are described in detail in the section Defining Fields.

Usage:

(add-field! {:type :http :core :tmdb} {:name "id" :type "pint" :stored true :indexed true})

;; add multiple fields at once

(add-field! {:type :http :core :tmdb} [{:name "id" :type "pint" :stored true :indexed true} {:name "pid" :type "pint" :stored true :indexed true}])

add-field-type! clj

(add-field-type! client-config field-map)

Add a New Field Type The add-field-type command adds a new field type to your schema.

All of the field type properties available when editing schema.xml by hand are available for use in a POST request. The structure of the command is a json mapping of the standard field type definition, including the name, class, index and query analyzer definitions, etc. Details of all of the available options are described in the section Solr Field Types.

Usage:

delete-field! clj

(delete-field! client-config field-map)

Delete a Field The delete-field command removes a field definition from your schema. If the field does not exist in the schema, or if the field is the source or destination of a copy field rule, an error is thrown.

Usage:

(delete-field! {:type :http :core :tmdb} {:name "id"})

delete-field-type! clj

(delete-field-type! client-config field-map)

Delete a Field The delete-field command removes a field definition from your schema. If the field does not exist in the schema, or if the field is the source or destination of a copy field rule, an error is thrown.

Usage:

(delete-field-type! {:type :http :core :tmdb} {:name "id"})

get-field-types clj

(get-field-types client-config)

get-fields clj

(get-fields client-config)

make-schema-url clj

(make-schema-url client-config & [trailing-uri])

replace-field! clj

(replace-field! client-config field-map)

Replace a Field The replace-field command replaces a field’s definition. Note that you must supply the full definition for a field - this command will not partially modify a field’s definition. If the field does not exist in the schema an error is thrown.

Usage: (replace-field! {:type :http :core :tmdb} {:name "id" :type "string" :stored true :indexed true})

update-field! clj

(update-field! client-config body)

Updates fields in schema. Update body has at least one keyword that represents the method and the param as value. Available methods: :add-field add a new field with parameters you provide. :delete-field delete a field. :replace-field replace an existing field with one that is differently configured. :add-dynamic-field add a new dynamic field rule with parameters you provide. :delete-dynamic-field delete a dynamic field rule. :replace-dynamic-field replace an existing dynamic field rule with one that is differently configured. :add-field-type add a new field type with parameters you provide. :delete-field-type delete a field type. :replace-field-type replace an existing field type with one that is differently configured. :add-copy-field add a new copy field rule. :delete-copy-field delete a copy field rule.

Usage:

(update-field! {:type :http :core :tmdb} {:add-field {:name "id" :type "pint" :stored true :indexed true}})

(update-field! {:type :http :core :tmdb} {:delete-field {:name "id"}})

NOTE: only supported with :http config type.