You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2015/04/29 16:37:05 UTC

[jira] [Created] (OAK-2825) better diagnostics for invalid BlobIds

Julian Reschke created OAK-2825:
-----------------------------------

             Summary: better diagnostics for invalid BlobIds
                 Key: OAK-2825
                 URL: https://issues.apache.org/jira/browse/OAK-2825
             Project: Jackrabbit Oak
          Issue Type: Improvement
          Components: blob
            Reporter: Julian Reschke
            Assignee: Julian Reschke


When systems are migrated from Jackrabbit 2 to Oak, it can happen that there's a mismatch between the config used by the migration tool and the one running the actual application.

One scenario is that during migration, the old data store was preserved, while when the migrated system is started, an instance of AbstractBlobStore is used.

When this happens, AbstractBlobStore.readBlob will be invoked with a blobId it can't parse, leading to an IllegalArgumentException reported by StringUtils.convertHexToBytes.

When this happens, it would be good to augment the exception text with a hint of the likely reason (such as "maybe this is a blobId assigned by a different and incompatible BlobStore implementation?)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)