Location in filedatastore doesn't match with dam:sha1 value | Community
Skip to main content
siddhartha252
Level 2
Jun 14, 2019 8:26 PM UTC
Solved

Location in filedatastore doesn't match with dam:sha1 value

Dear Experts,

When a bunch of images are uploaded to AEM instance with 6.3.3 version having separated datastore, all images are uploaded successfully and proper jcr content fields are allocated. But, when I tried to locate the image(file) specified in dam:sha1 field in filedatastore, I neither found the image nor folder taxonomy.

Could you please point me in the right direction?

Kind regards

Sid

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
siddhartha252
siddhartha252Accepted solution
Level 2
Jul 1, 2019 6:47 PM UTC

Had a session with Daycare support, content saved in jcr is with sha1 value and format with which folder taxonomy/ file saved in datastore is with sha256 value. Unfortunately, we can't track it unless we make any additional customizations out of adobe's scope.

Thanks

Sid

12 replies

joerghoh
Employee
Jul 1, 2019 7:18 PM UTC

Anyway, this information is an implementation detail of AEME (or Oak, to be more precise). It may change without further announcement. Do not rely on it.

(and I am quite sure, that the presenter mentioned it at some point, but did not refer to it as feature which can be used at will.)

Jörg

Translate
siddhartha252
siddhartha252AuthorAccepted solution
Level 2
Jul 1, 2019 6:47 PM UTC

Had a session with Daycare support, content saved in jcr is with sha1 value and format with which folder taxonomy/ file saved in datastore is with sha256 value. Unfortunately, we can't track it unless we make any additional customizations out of adobe's scope.

Thanks

Sid

Translate
siddhartha252
Level 2
Jun 27, 2019 8:17 PM UTC

Opened an Adobe ticket for this. WIll update the thread accordingly.

Thanks

Sid

Translate
joerghoh
Employee
Jun 18, 2019 9:33 PM UTC

Ok, might be good to follow up on this. Can you start an conversation with the presenter (or the AEM gems team), point out your problem and also give the link to this forum thread. Would be good to have this resolved.

Thanks,

Jörg

Translate
siddhartha252
Level 2
Jun 17, 2019 8:59 PM UTC

This is for validations. In the AEM Gems presentation, the presenter mentioned that filedatastore follows the pattern of folder names extracted from the sha value of the blob.

Translate
joerghoh
Employee
Jun 17, 2019 7:05 PM UTC

There is no documented way to do that. But why do you want to bypass all abstractions and access the blob directly?

Jörg

Translate
siddhartha252
Level 2
Jun 17, 2019 6:47 PM UTC

@husams51669576

Calculating sha256 and validating for path in filedatastore didn't help, but thanks

Translate
siddhartha252
Level 2
Jun 17, 2019 6:44 PM UTC

Is there a way to identify the location of asset uploaded in UI to track in Filedatastore?

Thanks

Sid

Translate
joerghoh
Employee
Jun 16, 2019 11:09 AM UTC

It has never been guaranteed that the name of the blob in the datastore is the same as the dam:sha1 hash.

Jörg

Translate
Employee
Jun 15, 2019 5:17 PM UTC

Try calculating sha256 and look up that path. I am not sure if this applies to file datastore, but for S3 it now uses sha256 instead of sha1

Translate