Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

The mechanism of publishing assets from Author

shintarok596176
Level 1
Level 1

Hi

Could someone tell me the mechanism of publishing assets?

When published asserts is changed in local author then it is published, How does publishing perfome?

Doss It peform as full,incremental or differential?

If changing asset is metadata only, does that mechanism perfome in the same way? 

I am using MongoMk and binary data is stored in MongoDB.

regards.

1 Accepted Solution
mvance
Correct answer by
Employee
Employee

Hi,

In a normal setup, files are activated and published out in full. The system just knows a node is changed, and activates it accordingly, without the context of what has changed.

So when using Tar storage, this is an ideal scenario for a shared datastore, so that author and publish access the same file, so there is no copying.once you turn on binary less replication,

As you are using Mongo, then the file is shared in author only, and must be replicated out to the publish servers. This is fine unless you deal with very large files.

I think this would be good to qualify with Customer Care or post in the sticky above for a feature request

Mark

View solution in original post

1 Reply
mvance
Correct answer by
Employee
Employee

Hi,

In a normal setup, files are activated and published out in full. The system just knows a node is changed, and activates it accordingly, without the context of what has changed.

So when using Tar storage, this is an ideal scenario for a shared datastore, so that author and publish access the same file, so there is no copying.once you turn on binary less replication,

As you are using Mongo, then the file is shared in author only, and must be replicated out to the publish servers. This is fine unless you deal with very large files.

I think this would be good to qualify with Customer Care or post in the sticky above for a feature request

Mark

View solution in original post