eXo-JCR-jcr

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates

Changeset {id} does not exist.

TASK-35691: Create FB ma and update projects versions/dependencies

Use parent pom of projects instead of addons (#67)

Currently, the jcr is an addon ans should use addons parent pom as any other eXo addon. Since there is a big change to do in Nexus and Jenkins to consider this new change, we will make as workaround this modification to be able to release on time the M08 version

Restore foundation-parent

Use parent pom of projects instead of addons

Currently, the jcr is an addon ans should use addons parent pom as any other eXo addon. Since there is a big change to do in Nexus and Jenkins to consider this new change, we will make as workaround this modification to be able to release on time the M08 version

Use parent pom of projects instead of addons

Currently, the jcr is an addon ans should use addons parent pom as any other eXo addon. Since there is a big change to do in Nexus and Jenkins to consider this new change, we will make as workaround this modification to be able to release on time the M08 version

Use parent pom of projects instead of addons

Currently, the jcr is an addon ans should use addons parent pom as any other eXo addon. Since there is a big change to do in Nexus and Jenkins to consider this new change, we will make as workaround this modification to be able to release on time the M08 version

TASK-28034: Update addons-parent-pom to 13-M01

TASK-35704: Create FB maintenance and update projects versions/dependencies

TASK-35704: Create FB maintenance and update projects versions/dependencies

TASK-35704: Create FB maintenance and update projects versions/dependencies

TASK-35363: Create FB clustering and update projects versions/dependencies

TASK-35363: Create FB clustering and update projects versions/dependencies

TASK-35691: Create FB minarm and update projects versions/dependencies

Fix random fail in Unit tests (#66)

This random fail is due to the fact that Unit Test methods execution order could be different. In fact, when a 'node creation' only is added in queue, the count of queue elements equals to the last executed operation. When a 'delete or update' operation is made, the size of queue should be less than the last executed queue operation id because in case of 'delete' or 'update', some queue elements are purged, thus the count will be always less than the last ID of the queue.

Fix random fail in Unit tests This random fail is due to the fact that Unit Test methods execution order could be different. In fact, when a 'node creation' only is added in queue, the count of queue elements equals to the last executed operation. When a 'delete or update' operation is made, the size of queue should be less than the last executed queue operation id because in case of 'delete' or 'update', some queue elements are purged, thus the count will be always less than the last ID of the queue.

Fix random fail in Unit tests This random fail is due to the fact that Unit Test methods execution order could be different. In fact, when a 'node creation' only is added in queue, the count of queue elements equals to the last executed operation. When a 'delete or update' operation is made, the size of queue should be less than the last executed queue operation id because in case of 'delete' or 'update', some queue elements are purged, thus the count will be always less than the last ID of the queue.

TASK-28401: Create FB microservices and update projects versions/dependencies

TASK-28401: Create FB microservices and update projects versions/dependencies

JCR Index Clustering : implement Persistent Changelog Strategy (#65)

* Switch default Cluster configuration to use TCP instead of UDP

* Copy implementation of Persistent changelog made in PR https://github.com/exodev/commons/pull/133

* Enhance code readability

* Move Persistent changelog API to an appropriate package

* Add Unit Tests and enhance code with Java 8

* Use old version of JUnit for backward compatibility

* Inherit version of maven plugin instead of declaring it explicitely

* Include Test file

* Store file content in Test before doing assertions

* Enhance last operation identifier storage and fix DB sequence definition

* Avoid executing Index recovery on startup

* Avoid useless blocking indexing synchronization with persistent index strategy

* Enhance Fault tolerance for JCR reading operations when reindexing

When reindexing JCR content, we may encounter sometimes some inconsistent Data. Knowing that the JCR will not be correctly accessible at all when not having a minimal index information, this improvement ensures to not stop indexation even when encountering some inconsistent data and still continue indexing other consistent data.

In addition, in clustering, the Suspend/resume of containers when stopping servers aren't mandatory since we will have a unique data storage and no multiple databases (Deprecated and not used at all). Thus it has been disabled by default to allow :

1/ Restart servers without affecting state (Online/Offline) status of other nodes in the cluster

2/ Starting a fresh node

3/ Reindexing on one single node

* Compress all index folder before sending it back to cluster member

* Retrieve Last operation ID File from coordinator before retrieving indexes

* Optimize code by deleting useless parts

  1. … 18 more files in changeset.
JCR Index Clustering : implement Persistent Changelog Strategy (#65)

* Switch default Cluster configuration to use TCP instead of UDP

* Copy implementation of Persistent changelog made in PR https://github.com/exodev/commons/pull/133

* Enhance code readability

* Move Persistent changelog API to an appropriate package

* Add Unit Tests and enhance code with Java 8

* Use old version of JUnit for backward compatibility

* Inherit version of maven plugin instead of declaring it explicitely

* Include Test file

* Store file content in Test before doing assertions

* Enhance last operation identifier storage and fix DB sequence definition

* Avoid executing Index recovery on startup

* Avoid useless blocking indexing synchronization with persistent index strategy

* Enhance Fault tolerance for JCR reading operations when reindexing

When reindexing JCR content, we may encounter sometimes some inconsistent Data. Knowing that the JCR will not be correctly accessible at all when not having a minimal index information, this improvement ensures to not stop indexation even when encountering some inconsistent data and still continue indexing other consistent data.

In addition, in clustering, the Suspend/resume of containers when stopping servers aren't mandatory since we will have a unique data storage and no multiple databases (Deprecated and not used at all). Thus it has been disabled by default to allow :

1/ Restart servers without affecting state (Online/Offline) status of other nodes in the cluster

2/ Starting a fresh node

3/ Reindexing on one single node

* Compress all index folder before sending it back to cluster member

* Retrieve Last operation ID File from coordinator before retrieving indexes

* Optimize code by deleting useless parts

  1. … 18 more files in changeset.
Optimize code by deleting useless parts

Retrieve Last operation ID File from coordinator before retrieving indexes

Retrieve Last operation ID File from coordinator before retrieving indexes

Compress all index folder before sending it back to cluster member

Enhance Fault tolerance for JCR reading operations when reindexing When reindexing JCR content, we may encounter sometimes some inconsistent Data. Knowing that the JCR will not be correctly accessible at all when not having a minimal index information, this improvement ensures to not stop indexation even when encountering some inconsistent data and still continue indexing other consistent data. In addition, in clustering, the Suspend/resume of containers when stopping servers aren't mandatory since we will have a unique data storage and no multiple databases (Deprecated and not used at all). Thus it has been disabled by default to allow : 1/ Restart servers without affecting state (Online/Offline) status of other nodes in the cluster 2/ Starting a fresh node 3/ Reindexing on one single node

Avoid useless blocking indexing synchronization with persistent index strategy

Avoid executing Index recovery on startup

Fix prefix of variables to avoid using gatein

Enhance last operation identifier storage and fix DB sequence definition

Store file content in Test before doing assertions