## Return Type and Data Filtering { #return-type-and-data-filtering }

Let's continue from the previous example. We wanted to **annotate the function with one type**, but we wanted to be able to return from the function something that actually includes **more data**.

   styles.willChange = `${sideA}, ${sideB}`;\n  }\n\n  // Attributes\n  const attributes = {\n    'x-placement': data.placement,\n  };\n\n  // Update `data` attributes, styles and arrowStyles\n  data.attributes = { ...attributes, ...data.attributes };\n  data.styles = { ...styles, ...data.styles };\n  data.arrowStyles = { ...data.offsets.arrow, ...data.arrowStyles };\n\n  return data;\n}\n","import getOppositePlacement from '../utils/getOppositePlacement';\nimport getOppositeVariation from '../u...

    void testGetSize() throws SMBProtocolDecodingException {
        // Prepare test data
        byte[] buffer = new byte[22];
        long expectedAllocationSize = 1024L;
        long expectedEndOfFile = 512L;
        int expectedNumberOfLinks = 3;
        boolean expectedDeletePending = true;
        boolean expectedDirectory = false;

        // Encode test data
        int offset = 0;

        byte[] data = new byte[8];
        long low = filetime.longValue();
        long high = filetime.shiftRight(32).longValue();

        // write little-endian
        data[0] = (byte) (low);
        data[1] = (byte) (low >> 8);
        data[2] = (byte) (low >> 16);
        data[3] = (byte) (low >> 24);
        data[4] = (byte) (high);
        data[5] = (byte) (high >> 8);

```JSON
{"item_id":"foo"}
```

## Parameter path dengan tipe data

Tipe data parameter path bisa didefinisikan di dalam fungsi, menggunakan anotasi tipe data standar Python:

{* ../../docs_src/path_params/tutorial002.py hl[7] *}

Dalam hal ini `item_id` didefinisikan sebagai `int`.

/// check | Periksa

            searchPaging(data, form);
        });
    }

    /**
     * Set up pagination data for search results.
     *
     * @param data the render data to populate
     * @param form the search form containing pagination parameters
     */
    protected void searchPaging(final RenderData data, final SearchForm form) {
        // page navi

e=function(t){return this.each((function(){var a=n.default(this).data(B),i=n.default.extend({},W,n.default(this).data());a||(a=new e(n.default(this),i),n.default(this).data(B,a)),"toggleSubmenu"!==t&&"fixPosition"!==t||a[t]()}))},e}();n.default('.dropdown-menu [data-toggle="dropdown"]').on("click",(function(e){e.preventDefault(),e.stopPropagation(),V._jQueryInterface.call(n.default(this),"toggleSubmenu")})),n.default('.navbar [data-toggle="dropdown"]').on("click",(function(e){e.preventDefault(),...

    }

    /**
     * Processes the result data through all available ingesters.
     * Each ingester can transform and enrich the data before it is indexed.
     *
     * @param responseData the response data from the crawled resource
     * @param resultData the result data to be processed
     * @return the processed result data after all ingesters have been applied
     */

     *
     * @return the read data
     */
    public final byte[] getData() {
        return this.data;
    }

    /**
     * Gets the offset in the data buffer.
     *
     * @return the offset
     */
    public final int getOffset() {
        return this.offset;
    }

    /**
     * Adjusts the offset by the specified amount.
     *
     * @param n the amount to adjust the offset

To get an idea of how various combinations of data and parity drives affect the storage usage, let’s take an example of a 100 MiB file stored
on 16 drive MinIO deployment. If you use eight data and eight parity drives, the file space usage will be approximately twice, i.e. 100 MiB
file will take 200 MiB space. But, if you use ten data and six parity drives, same 100 MiB file takes around 160 MiB. If you use 14 data and