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

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

  • June 14, 2019
  • 12 replies
  • 6406 views

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.
Best answer by siddhartha252

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

A
Anonymous
June 14, 2019

Please reference the documentation you are following so we can try to reproduce

siddhartha252
siddhartha252Author
Level 2
June 14, 2019

Sure,

Configurations for "org.apache.jackrabbit.oak.plugins.blob.datastore.FileDataStore.config", file we specified are as below:

path="/app/datastore/current_datastore"

service.pid="org.apache.jackrabbit.oak.plugins.blob.datastore.FileDataStore"

minRecordLength="1024"

Now when the image is uploaded jcr content says: f17de40d1a85c8b822f81cd87b3dd04f1d31f394

dam:sha1

String

f17de40d1a85c8b822f81cd87b3dd04f1d31f394

As per sha value "f17de40d1a85c8b822f81cd87b3dd04f1d31f394", when I navigate to filedatastore, I should see folders

f1--> 7d-->e4-->f17de40d1a85c8b822f81cd87b3dd04f1d31f394. But, I could only see folder f1 there is no 7d sub-folder.

Thanks

Sid

S
Adobe Employee
sssfaffaaaAdobe Employee
Adobe Employee
June 15, 2019

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

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
June 16, 2019

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

Jörg

siddhartha252
siddhartha252Author
Level 2
June 17, 2019

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

Thanks

Sid

siddhartha252
siddhartha252Author
Level 2
June 17, 2019

@husams51669576

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

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
June 17, 2019

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

Jörg

siddhartha252
siddhartha252Author
Level 2
June 17, 2019

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.

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
June 18, 2019

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

siddhartha252
siddhartha252Author
Level 2
June 27, 2019

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

Thanks

Sid

Show more replies
Terms & ConditionsAccessibility statement

Loading footer...