<executions>
          <execution>
            <id>unpack-jline-native</id>
            <goals>
              <goal>unpack-dependencies</goal>
            </goals>
            <configuration>
              <includeArtifactIds>jline-native</includeArtifactIds>
              <includes>org/jline/nativ/**</includes>
            </configuration>
          </execution>
        </executions>

```JSON
{
  "detail": "Not authenticated"
}
```

### Inactive user { #inactive-user }

Now try with an inactive user, authenticate with:

User: `alice`

Password: `secret2`

And try to use the operation `GET` with the path `/users/me`.

You will get an "Inactive user" error, like:

```JSON
{
  "detail": "Inactive user"
}
```

## Recap { #recap }

## Why is MinIO cloud-native?

        super(config, andx);
    }

    /**
     * Returns the native LAN Manager string reported by the server.
     *
     * @return the nativeLanMan
     */
    public final String getNativeLanMan() {
        return this.nativeLanMan;
    }

    /**
     * Returns the native operating system string reported by the server.
     *
     * @return the nativeOs
     */

MinIO is a high performance distributed object storage server, designed for large-scale private cloud infrastructure. MinIO is designed in a cloud-native manner to scale sustainably in multi-tenant environments. Orchestration platforms like Kubernetes provide perfect cloud-native environment to deploy and scale MinIO.

## MinIO Deployment on Kubernetes

There are multiple options to deploy MinIO on Kubernetes:

     *
     * @return remote key
     */
    protected abstract int generateRemoteKey();

    /**
     * Get native memory address of the buffer
     *
     * @param buffer buffer to get address for
     * @return native memory address
     */
    protected abstract long getBufferAddress(ByteBuffer buffer);

    @Override
    public void close() {
        invalidate();

            // - Testing basic RDMA operations
            // - Checking for required native libraries

            return true;
        } catch (ClassNotFoundException e) {
            log.debug("DiSNI not available: {}", e.getMessage());
            return false;
        } catch (UnsatisfiedLinkError e) {
            log.debug("DiSNI native libraries not available: {}", e.getMessage());
            return false;
        }
    }

# **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.

    }

    @Override
    protected long getBufferAddress(ByteBuffer buffer) {
        // Return a fake address for TCP
        // In real RDMA implementations, this would be the native memory address
        return buffer.hashCode();
    }

And to communicate using WebSockets with your backend you would probably use your frontend's utilities.

Or you might have a native mobile application that communicates with your WebSocket backend directly, in native code.

Or you might have any other way to communicate with the WebSocket endpoint.

---