If we are trying to optimise some properties in a class with lot many instances. Which approach is ideal out of the two ? (without running into issues like util node going down)
I have the following questions :
Are we directly hitting the database through PRRestService ?
Is there a timeout incase the number of instances are huge ?
And is there a way to selectively populate the columns ?
Will this get recorded in the audit ?
***Edited by Moderator: Pooja Gadige to add capability tags***
I could be wrong but here is my understanding of different expose property options -
Optimize for reporting is available only in non-production environments. This helps to modify the table to optimize a property (and auto-populate the new exposed column with data from BLOB), and move this table change easily via migrating Data-Admin-Db-Table instance. If you are planning to use it directly in production, it won't work.
For any change to be made directly in production, you need to create that column on table either via PRPC (Modify Schema) or from DB console. After that you either can follow one of these two approaches -