I'd like to know how dspace manage indexing in both the database and solr while supporting concurrency. In other words, if 2 individuals try to write at the same time, on the same item (e.g. changing metadata), how do dspace ensure that the index will not be desynchronized with the database.
This can happen if USER1 write concurrently with USER 2 on the same metadata value, and the write to the database of USER 1 first happen, but then the Write to the database and the Index of USER2 happen, and then the write to the index of USER1 Happen. In other words USER1 "write" will be in the index while User2 write will be in the database = inconsistency !!! I wonder how this case can be avoid in dspace, which is a typical dual write problem. With the Event system of dspace, i don't know how this can be avoided. Does anyone knows? -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
