[
https://issues.apache.org/jira/browse/JCLOUDS-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897765#comment-17897765
]
Matthew Bellew edited comment on JCLOUDS-1504 at 11/13/24 12:03 AM:
--------------------------------------------------------------------
(amended comment) I tracked this down more specifically
The endpoint actually get create correctly in the initial parameter
substitition. It gets messed up right at the end in
BindAsHostPrefix.bindToRequest(). This code does
URI newEndpoint =
uriBuilder(request.getEndpoint()).host(name.toString()).build();
That build() call calls expand() again, even though the endpoint has been
calculated and there are no variables to substitute.
return new URI(expand(variables, true));
So you can see the endpoint go from
request.endpoint = .../container2/Test_{_test.txt
to
newEndpoint.endpont = .../container2/Test_
was (Author: mbellew):
>From what I can tell this has something to do with the "{" in the file name
>messing up the argument substitution code in
>RestAnnotationProcessor.getEndpointInParametersOrNull()
> BlobStore.list(container, ListContainerOptions) returns collection containing
> null elements
> --------------------------------------------------------------------------------------------
>
> Key: JCLOUDS-1504
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1504
> Project: jclouds
> Issue Type: Bug
> Reporter: Енчо Белезирев
> Priority: Blocker
> Attachments: jclouds-wire.log, jclouds.log
>
>
> Hello,
> I am SAP developer and we are using jclouds for the communication with our
> blob stores.
> We have issue with the querying of the StorageMetadata for some blobs. We are
> using the method from the BlobStore -
> {code:java}
> PageSet<? extends StorageMetadata> list(String container,
> ListContainerOptions options);{code}
> However, when we are using the method, we are providing
> ListContainerOptions.Builder.withDetails() because we want to take directly
> the userMetadata field from the StorageMetadata object and to use it later
> on. Here comes the problem, sometimes, when the method is being executed, the
> list that is being returned contains null objects. This is a problem because
> we want each StorageMetadata to be non-null.
> I have validated our entries in the container and it seemed that there are no
> suspicious entries in it(which might cause the issue).
> Could you share some information what could have caused the issue and
> eventually, is there a way to workaround this?
>
> We are using aws-s3 implementation of the blob store.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
