Skip to main content

Multi-tiered storage in Assets Server

Comments

Do you have corrections or additional information about this article? Leave a comment!

Do you have a question about what is described in this article? Please contact support here.


3 comments

  • Craig Cardillo

    This page specifically says that storage engine patterns are case-insensitive ("These will match on the assetPath of your asset, ignoring case"). But it appears that they ARE case sensitive (discovered a problem today because of this so decided to test to confirm). This is in Assets 6.56

    If I define a non-default storage engine like:
    {
    name = "test"
    type = "s3"
    pattern = "/Foo/**"
    region = "us-east-1"
    bucket = "test-bucket"
    }

    Then create a folder /Foo/ and upload an asset then check the storage location like this:
    https://devassets.company.com/services/search?q=id:Eco0hhol4r88gD93YdWZ0m&expand=originalStoragePath
    In the response I see: "originalStoragePath":"s3://test-bucket/Eco0/Eco0hhol4r88gD93YdWZ0m/asset/2.jpg"

    But if I create a folder /FOO/ and upload an asset then check the storage location like this:
    https://devassets.company.com/services/search?q=id:8k_rLXIVaGw8y_zbAeHFvk&expand=originalStoragePath
    In the response I see: "default:///491/0966/0402/8k_rLXIVaGw8y_zbAeHFvk_2.jpeg"

    So because the case is different the pattern for the storage engine did not match and the object was stored using the default storage engine.

    Though when you search in the UI assetPath is case-insensitive (i.e. assetPath:/FOO/* == assetPath:/Foo/*)

    0
  • Maarten van Kleinwee

    Hi Craig Cardillo,

    Apologies for this late response.

    I have turned your question into a ticket for our Support team so that they can verify the exact behavior with the developers. They will reply to you via that ticket.

    Best regards,

    Maarten van Kleinwee
    Senior Technical Writer, WoodWing Software

    0
  • Maarten van Kleinwee

    Note to all: Turns out this issue was a bug in the software which has been fixed in Assets Server 6.64.

    Best regards,

    Maarten van Kleinwee

    Senior Technical Writer, WoodWing Software

    0

Please sign in to leave a comment.