}

    @Override
    public Nature getNature() {
        if (metadata instanceof RepositoryMetadata repositoryMetadata) {
            return switch (repositoryMetadata.getNature()) {
                case RepositoryMetadata.RELEASE_OR_SNAPSHOT -> Nature.RELEASE_OR_SNAPSHOT;
                case RepositoryMetadata.SNAPSHOT -> Nature.SNAPSHOT;
                default -> Nature.RELEASE;
            };
        } else {

        /**
         * Sets the nature of repositories to query when resolving the version range.
         * If {@code null} is provided, defaults to {@link Nature#RELEASE_OR_SNAPSHOT}.
         *
         * @param nature the repository nature, or {@code null} to use the default
         * @return this builder, never {@code null}
         */
        public VersionResolverRequestBuilder nature(Nature nature) {

                        wantedNature = Metadata.Nature.RELEASE_OR_SNAPSHOT;
                    } else {
                        wantedNature = Metadata.Nature.RELEASE;
                    }
                } else {
                    wantedNature = Metadata.Nature.valueOf(natureString.toUpperCase(Locale.ROOT));
                }

        int nature = getNature();
        if ((nature & RepositoryMetadata.RELEASE_OR_SNAPSHOT) == RepositoryMetadata.RELEASE_OR_SNAPSHOT) {
            ArtifactRepositoryPolicy policy = new ArtifactRepositoryPolicy(repository.getReleases());
            policy.merge(repository.getSnapshots());
            return policy;
        } else if ((nature & RepositoryMetadata.SNAPSHOT) != 0) {

carefully. Because of this, if you're interested in seeing a new feature in
Guava, the best approach is to create an [issue][] (or comment on an existing
issue if there is one) requesting the feature and describing specific use cases
for it.

If we decide to pursue a feature request, it will go through a thorough process
of API design and review. Any code should come after this.

 */
package org.codelibs.fess.exception;

/**
 * Exception thrown when web API operations encounter errors.
 * This exception includes an HTTP status code to indicate the nature of the error.
 */
public class WebApiException extends FessSystemException {

    private static final long serialVersionUID = 1L;

    /**
     * The HTTP status code associated with this exception.
     */

   * {@code ExecutorService} imposes a small locking overhead on each task submission in order to
   * implement shutdown and termination behavior.
   *
   * <p>Because of the nature of single-thread execution, the methods {@code scheduleAtFixedRate}
   * and {@code scheduleWithFixedDelay} are not supported by this class and will throw an
   * UnsupportedOperationException.
   *

        String[] emptyArray = crawlerContext.removeSitemaps();
        assertNotNull(emptyArray);
        assertEquals(0, emptyArray.length);
    }

    /**
     * Test thread-local nature of sitemaps
     */
    public void test_sitemaps_threadLocal() throws Exception {
        final String[] thread1Sitemaps = new String[] { "http://thread1.com/sitemap.xml" };

        for (String pluginGroup : candidates.keySet()) {
            org.eclipse.aether.metadata.Metadata metadata =
                    new DefaultMetadata(pluginGroup, "maven-metadata.xml", DefaultMetadata.Nature.RELEASE_OR_SNAPSHOT);

            requests.add(new MetadataRequest(metadata, null, REPOSITORY_CONTEXT).setTrace(trace));

            for (RemoteRepository repository : request.getRepositories()) {

# **Disaggregated HDP Spark and Hive with MinIO**

## **1. Cloud-native Architecture**

![cloud-native](https://github.com/minio/minio/blob/master/docs/bigdata/images/image1.png?raw=true "cloud native architecture")

Kubernetes manages stateless Spark and Hive containers elastically on the compute nodes. Spark has native scheduler integration with Kubernetes. Hive, for legacy reasons, uses YARN scheduler on top of Kubernetes.