{
  "fess_config.related_query" : {
    "aliases" : { },
    "mappings" : {
      "related_query" : {
        "properties" : {
          "createdBy" : {
            "type" : "keyword"
          },
          "createdTime" : {
            "type" : "long"
          },
          "queries" : {
            "type" : "keyword"
          },
          "term" : {
            "type" : "keyword"
          },
          "updatedBy" : {

{
  "fess_config.related_content" : {
    "aliases" : { },
    "mappings" : {
      "related_content" : {
        "properties" : {
          "content" : {
            "type" : "keyword"
          },
          "createdBy" : {
            "type" : "keyword"
          },
          "createdTime" : {
            "type" : "long"
          },
          "sortOrder" : {
            "type" : "integer"
          },
          "term" : {

Shinsuke Sugaya <******@****.***> 1638450896 +0900

Shinsuke Sugaya <******@****.***> 1638450896 +0900

Shinsuke Sugaya <******@****.***> 1638450896 +0900

Shinsuke Sugaya <******@****.***> 1638450896 +0900

     */
    @Nonnull
    <T> Optional<T> lookupOptional(Class<T> type, String name);

    /**
     * Performs a collection lookup for given typed components.
     *
     * @param type The component type.
     * @return The list of components. The list may be empty if no components found.
     * @param <T> The component type.
     * @throws LookupException if there is some provisioning related issue.
     */

    T item = itemInfo.value;
    T related = relatedInfo.value;
    assertWithTemplate(
        "$ITEM must be $RELATIONSHIP to $OTHER",
        itemInfo,
        relatedInfo,
        equivalence.equivalent(item, related));

    int itemHash = equivalence.hash(item);
    int relatedHash = equivalence.hash(related);
    assertWithTemplate(
        "the $HASH ("
            + itemHash

# Extra Models

Continuing with the previous example, it will be common to have more than one related model.

This is especially the case for user models, because:

* The **input model** needs to be able to have a password.
* The **output model** should not have a password.
* The **database model** would probably need to have a hashed password.

!!! danger
    Never store user's plaintext passwords. Always store a "secure hash" that you can then verify.

                                                key="labels.related_query_term"/></th>
                                        <td>${f:h(term)}<la:hidden property="term"/></td>
                                    </tr>
                                    <tr>
                                        <th><la:message
                                                key="labels.related_query_queries"/></th>