[
https://issues.apache.org/jira/browse/JCLOUDS-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16906885#comment-16906885
]
Енчо Белезирев commented on JCLOUDS-1504:
-----------------------------------------
Hi [~gaul],
I have explained above, the nulls are produced for the 404 Not Found HTTP
Statuses returned when querying the blobs. For me this is not OK, to return
null as blobMetadata. I agree that we need to find the root cause but all my
questions have been left unanswered in this issue and the github PR was closed
without my questions been answered there, as well.
Also, could you explain to me what is that "eventual consistency"? If this is
really the way I agree to put null filtering for the blobs.
For now, I do not understand your statement "the blobMetadata could be null ->
this could rise NullPointerException but it is okay".
Thanks,
Encho
> 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
(v7.6.14#76016)
