please check with SP 6.4.4.0. If the issue still exists, file a daycare ticket with the package of the rollout config.On the other hand, make sure to follow MSM Best Practices

If I understand correctly, you are trying to fetch some information from postgresql for some transaction in AEM and not trying to replace  tarMK with RDBMS. Couple of options to look at - Are you able to successfully install the driver specific to postgreSQL? Make sure you have wrapped the driver ja...

IMO, AEM doesn’t support containers currently for on-prem instances, could be an option in the future for AMS(Adobe managed services)

As far as I understand, there isn't a pre-release notes until the SP is released. If you are looking for anything specific that you are expecting as part of the SP, you could check by creating a ticket in daycare.

Nice workaround Ravi Pampana

You could use tools like exiftool or ffmpeg to view metadata of an asset. Below are few commandsRead all metadataexiftool abc.mp4 Read XMP metadata (metadata from creative cloud tools like PS, AE ..)exiftool -xmp -b -m -scanForXMP abc.mp4 > out.xmpReferencehttps://owl.phy.queensu.ca/~phil/exiftool/e...

Did you try adding the osgi wrapped bundle to your apps install folder (through code package, with the help of filter.xml) and use the maven-bundle-plugin or content-package-maven-plugin. Please refer [0] & [1] option #4[0]cq5 - How to use third party JAR into AEM? - Stack Overflow[1]Adobe CQ/Adobe ...

In this case AEM 6.4 should auto populate these custom metadata fields if you match the schema to the the image metadata value. If you have a namespace which is custom, one needs to create custom namespaces as wellScreenshot 1Screenshot 2

deepakt84913413, Do you want to auto populate these metadata fields when and asset is uploaded? Or do you want to programmatically read the stored metadata?

On the 6.2 instance, goto /content/rep:policy/allow50 and get the value of rep:principalName and run the below query(depending on allow or deny) to check if there are any duplicate ACLs under /content/rep:policy. Delete ACL and proceed with the upgrade.If you are not able to delete the rep:policy no...