Clarification on Parent data hierarchy in "spy_category_node_storage"

Sakelarios

Hello everyone!

I have a question about the expected behaviour of the "spy_category_node_storage" table regarding parent hierarchy data.

For example if I have:
Category ID 1 (parent of Category ID 2)
Category ID 2 (parent of Category ID 3)

After running publish & sync, the "data" column in "spy_category_node_storage" includes all parent categories in the hierarchy (e.g., for Category ID 3, it shows both Category ID 2 and Category ID 1)

This results in a large amount of extra data for extensive category trees. In my testing, it seems unnecessary to include all parent levels in the "data". The first-level parent and child categories appear sufficient for functionality.

Is this behavior (storing all parent levels in the "data" column) expected, and if so, what is its purpose? Would it be safe to optimize the data to only include first-level parents and children?

Thank you in advance for any input you could provide!

profuel

I'm not sure what you are trying to achieve, thus asking for more details.

In general, we store in storage all entries we may use in the frontend, see this method:

https://github.com/spryker/category-storage/blob/master/src/Spryker/Client/CategoryStorage/CategoryStorageClient.php#L50

Anther option (although not adressing the table) is removal of the sync queues, which comes with the latest release: https://docs.spryker.com/docs/about/all/releases/release-notes-202410.0.html#publish-and-synchronize-configuration-and-optimization-span-classinline-imgimg-srchttpssprykers3eu-central-1amazonawscomdocsscosuserintro-to-sprykerreleasesrelease-notesimprovementpng-altimprovement-span