How many properties can be set at node level - AEM 6.4 | Community
Skip to main content
Level 2
June 27, 2018
Solved

How many properties can be set at node level - AEM 6.4

  • June 27, 2018
  • 5 replies
  • 3373 views

Is there any limitation about number of properties to be stored at one node. I have 1 node at it can have 1700 - 2000 properties. Is this possible. If yes then what could be performance drawback of this.

Thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Lokesh_Shivalingaiah

Hi,

I dont think there is any restrictions on the number of properties for a given node in Jackrabbit Oak. However, the number of nodes would contribute to the performance impact but the number of properties might not if its indexed.

Thanks,

Lokesh

5 replies

Lokesh_Shivalingaiah
Lokesh_ShivalingaiahAccepted solution
Level 10
June 27, 2018

Hi,

I dont think there is any restrictions on the number of properties for a given node in Jackrabbit Oak. However, the number of nodes would contribute to the performance impact but the number of properties might not if its indexed.

Thanks,

Lokesh

Lokesh_Shivalingaiah
Level 10
June 27, 2018

Also, we should think of real need to have so many properties for a node!

A right balance could be made between hierarchical and properties. If you can give more details of your usecase, we can suggest better!

ad6Author
Level 2
June 29, 2018

Thanks for your input.

My use case is, we are migerating from legacy system to AEM. We have around 10 K constans wiht values(like message, alt text etc.) We need to take these constatn as it is and put it into jcr repository. Also the catch is these key / value can be mulitlingual also. So we are thinking about various approach to design this in AEM.

peterp18579053
June 29, 2018

Theoretically, you can import any number of properties.

The only problem is maintenance. It would be near impossible to CRX/De 10K properties.

Concurrent modifications to properties would be fun with OAK as well.

Better migrate to a normal JCR structure.

Regards,

Peter

peterp18579053
June 29, 2018

Multilingual properties are handled in AEM by i18n system.

Which is exactly build for key value pairs.

Regards,

Peter