Cleaning BTG Segment Evaluation Results

[pratik_a_soni]

Hello,

In our project we are using BTG and would like to clean the unwanted session scope results from the DB which makes our Admin tab useless due to high volume of data. To make this possible we need to go with 2 steps:

1. Clean existing results via cron job. (Done, we are able to do this).

2. Do not allow hybris to store the results in database. (Not done, facing issues as mentioned below).

I went through the Wiki link where the cleaning of BTG segment results is explained. https://wiki.hybris.com/display/release5/Cleaning+BTG+Segment+Evaluation+Results

I was able to:

• create the cron job which removes the results from all the users.

I'm not able to:

• use the btg.session.scope.result.not.stored.in.database property, even if I set it to true/false. Results will always be created.

• tried searching for de.hybris.platform.btg.dao.impl.DefaultResultDataCachingBTGDao class, but couldn't find any class file which I can use in the spring file.

• couldn't find de.hybris.platform.btg.dao.impl.SessionResultAwareBTGDaoSelector class as well.

If I try to put the spring configurations the server startup fails. Which confirms that these classes are not available OOTB.

We need your guidance on this to implement the btg.session.scope.result.not.stored.in.database=true logic.

I would really appreciate your help/guidance on this.

Thanks Pratik

[pratik_a_soni]

Any update on this? Anyone?

[Former Member]

what hybris version are you using? Fix for not storing session results in DB was introduced with Commerce Suite 5.7.0.11.

See https://jira.hybris.com/browse/PATCH-2478 https://jira.hybris.com/browse/ECP-1019

Hope that helps, Best regards, Norbert

[pratik_a_soni]

We are using hybris 6.0.

[Former Member]

5.7.0.11 was released after 6.0.0.0 afaik. Having a look at https://jira.hybris.com/browse/ECP-1019 it seems the fix will be available in 6.1.

[Former Member]

...and it's also backported to 6.0.0.1, so give this version a try. FYI: we are using the fix already in production, and it works fine for us.

[pratik_a_soni]

Thanks Norbert for your valuable input, we will check on this.