* Search term for the related query.
     */
    public String term;

    /**
     * Related queries string containing associated search queries.
     */
    public String queries;

    /**
     * User who created the related query entry.
     */
    public String createdBy;

    /**
     * Timestamp when the related query was created.
     */
    public String createdTime;

    /**

* **Document** the API using OpenAPI:
    * which is then used by the automatic interactive documentation user interfaces.

This might all sound abstract. Don't worry. You'll see all this in action in the [Tutorial - User Guide](tutorial/index.md){.internal-link target=_blank}.

        this.guidToHandle = new ConcurrentHashMap<>();
        this.scheduler = Executors.newScheduledThreadPool(1);
        
        // Create state directory for persistent storage
        String homeDir = System.getProperty("user.home");
        this.stateDirectory = Paths.get(homeDir, ".jcifs", "handles");
        try {
            Files.createDirectories(stateDirectory);
        } catch (IOException e) {

   * {@code ClassCastException} for any elements {@code e1} and {@code e2} in the multiset. If the
   * user attempts to add an element to the multiset that violates this constraint (for example, the
   * user attempts to add a string element to a set whose elements are integers), the {@code
   * add(Object)} call will throw a {@code ClassCastException}.
   *

		</postConstruct>
		<postConstruct name="addIndexConfig">
			<arg>"fess_config.web_config/web_config"</arg>
		</postConstruct>
		<!-- fess_user index -->
		<postConstruct name="addIndexConfig">
			<arg>"fess_user.user/user"</arg>
		</postConstruct>
		<postConstruct name="addIndexConfig">
			<arg>"fess_user.role/role"</arg>
		</postConstruct>
		<postConstruct name="addIndexConfig">
			<arg>"fess_user.group/group"</arg>

	// and must use forward slashes instead of back slashes. A trailing slash
	// indicates that this file is a directory and should have no data.
	Name string

	// Comment is any arbitrary user-defined string shorter than 64KiB.
	Comment string

	// NonUTF8 indicates that Name and Comment are not encoded in UTF-8.
	//
	// By specification, the only other encoding permitted should be CP-437,

        final OptionalThing<FessUserBean> userBean = ComponentUtil.getComponent(FessLoginAssist.class).getSavedUserBean();
        final String permissionKey = userBean.map(user -> StreamUtil.stream(user.getPermissions())
                .get(stream -> stream.sorted().distinct().collect(Collectors.joining("\n")))).orElse(StringUtil.EMPTY);

        try {

OkHttp may add headers that are absent from the original request, including `Content-Length`, `Transfer-Encoding`, `User-Agent`, `Host`, `Connection`, and `Content-Type`. It will add an `Accept-Encoding` header for transparent response compression unless the header is already present. If you’ve got cookies, OkHttp will add a `Cookie` header with them.

 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND,
 * either express or implied. See the License for the specific language
 * governing permissions and limitations under the License.
 */
package org.codelibs.fess.opensearch.user.allcommon;

import java.io.Serializable;
import java.util.Map;
import java.util.Set;

import org.dbflute.Entity;
import org.dbflute.FunCustodial;
import org.dbflute.dbmeta.accessory.EntityModifiedProperties;

{* ../../docs_src/dataclasses/tutorial002.py hl[1,7:13,19] *}

The dataclass will be automatically converted to a Pydantic dataclass.

This way, its schema will show up in the API docs user interface:

<img src="/img/tutorial/dataclasses/image01.png">

## Dataclasses in Nested Data Structures { #dataclasses-in-nested-data-structures }