Skip to Content
author's profile photo Former Member
Former Member

Issue when searching for value having dontOptimize="true"

Dear experts,

I have the following issue: Env: Hybris v5.7 and Hybris v6.5 Database MySQL Server v5.7

Issue: CMSParagraphComponent.content has dontOptimize="true". This causes the CMSParagraphComponent.content value to be kept in two columns in a separate table:

  • props.valueString1 having type Text (max length 2 pow 16 - 1 = 65535 bytes).

  • props.value1 having type longBlob.

The full value of CMSParagraphComponent.content is kept in props.value1. The first 8888 chars of the CMSParagraphComponent.content are kept in props.valueString1.

When I perform flexible search filtered by CMSParagraphComponent.content, Hybris searches in props.valueString1 column.

This causes issues if I search for a String value that is beyond the first 8888 chars (the scenario when this value is not written in props.valueString1, but it exists in props.value1 and I can see it in HMC/BackOffice content of the paragraph).

  1. Could you please explain the functional meaning of this implementation? Why do we keep the content in two separate columns?

  2. Could you please suggest a workaround for that, e.g. is there an option to keep in props.valueString1 the max value allowed by the db type? The final goal is to be able to do a flexible search on the full value of CMSParagraphComponent.content, not only on the first 8888 chars of it.


Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Feb 15, 2018 at 10:32 AM

    If 'true' the attribute value will be stored in the 'global' property table, this is in general a bad idea. when flag is true hybris will dump such properties in the props table and this will grow very rapidly and next thing you know, if you are not careful how you design your solution, is performance headaches.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.