图片服务器minio分片

图片服务器minio分片上传时需要注意的问题

1.在日常的开发中我们会用到图片上传的工具，大多数情况下会在网上找到一些现成的demo来进行调整，但是这样就会出现一些未知的问题，这里我遇见的问题是来自于上传的文件过大导致超时以及上传速度慢。

/**
     * 创建分片上传
     *
     * @param createRequest
     * @return
     */
    public MultipartUploadCreateResponse createMultipartUpload(MultipartUploadCreateRequest createRequest) {
        System.out.println("创建分片上传开始, createRequest: [{}]");
        MultipartUploadCreateResponse response = new MultipartUploadCreateResponse();
        response.setChunks(new LinkedList<>());
        final MultipartUploadCreate uploadCreate = MultipartUploadCreate.builder()
                .bucketName(minioConfig.getBucketName())
                .objectName(createRequest.getFileName())
                .build();
        final CreateMultipartUploadResponse uploadId = minioUtil.uploadId(uploadCreate);
        uploadCreate.setUploadId(uploadId.result().uploadId());
        response.setUploadId(uploadCreate.getUploadId());
        Map<String, String> reqParams = new HashMap<>();
        reqParams.put("uploadId", uploadId.result().uploadId());
        for (int i = 0; i < createRequest.getChunkSize(); i++) {
            reqParams.put("partNumber", String.valueOf(i));
            String presignedObjectUrl = minioUtil.getPresignedObjectUrl(uploadCreate.getBucketName(), uploadCreate.getObjectName(), reqParams);
            if (StringUtils.isNotBlank(minioConfig.getEndpoint())) {//如果线上环境配置了域名解析，可以进行替换
                presignedObjectUrl = presignedObjectUrl.replace(minioConfig.getEndpoint(), minioConfig.getEndpoint());
            }
            MultipartUploadCreateResponse.UploadCreateItem item = new MultipartUploadCreateResponse.UploadCreateItem();
            item.setPartNumber(i);
            item.setUploadUrl(presignedObjectUrl);
            response.getChunks().add(item);
        }
        System.out.println("创建分片上传结束, createRequest: [{}]");
        return response;
    }

/**
     * 分片合并
     *
     * @param uploadRequest
     */
    public FileUploadResponse completeMultipartUpload(CompleteMultipartUploadRequest uploadRequest) {
        System.out.println("文件合并开始, uploadRequest: [{}]");
        try {
            final ListPartsResponse listMultipart = minioUtil.listMultipart(MultipartUploadCreate.builder()
                    .bucketName(minioConfig.getBucketName())
                    .objectName(uploadRequest.getFileName())
                    .maxParts(uploadRequest.getChunkSize() + 10)
                    .uploadId(uploadRequest.getUploadId())
                    .partNumberMarker(0)
                    .build());
            final ObjectWriteResponse objectWriteResponse = minioUtil.completeMultipartUpload(MultipartUploadCreate.builder()
                    .bucketName(minioConfig.getBucketName())
                    .uploadId(uploadRequest.getUploadId())
                    .objectName(uploadRequest.getFileName())
                    .parts(listMultipart.result().partList().toArray(new Part[]{}))
                    .build());

            return FileUploadResponse.builder()
                    .url(minioConfig.getEndpoint() + "/" + minioConfig.getBucketName() + "/" + uploadRequest.getFileName())
                    .build();
        } catch (Exception e) {
            System.out.println("合并分片失败");
        }
        System.out.println("文件合并结束, uploadRequest: [{}]");
        return null;
    }

在上述代码的执行过程中有一段代码称为分片上传，一段代码成为合并分片，在依照demo的执行过程会发现在分片的合并时会出现未找到分片，并合并失败，存在这样的原因时在第一个demo执行完毕之后他会通过掉调用返回的一个PUT方法来根据分片的大小进行上传文件，但是在此demo中并为执行此上传操作，只是返回了对应的id以及上传时所需的url但是并未执行上传的功能所以，再执行分片上传的时候需要注意demo中的分片上传是否调用上传接口

##实际上你也可以在代码中手动调用
主要的参数 分片的大小:通过分片的大小取到对应位置的byte[] 作为参数通过分片上传返回的url 作为参数进行传递即可