eXo-JCR-jcr

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
JCR-2350 : JCR_SVALUE and JCR_SITEM on delete cascade

  1. … 11 more files in changeset.
JCR-2353: The method SharedFieldCache.getValueIndex needs to be optimized

JCR-2352: The method SharedFieldCache.getValueIndex needs to be optimized

JCR-2311: Implement a value storage based on Amazon S3

    • -0
    • +834
    /exo.jcr.component.core.impl.amazonaws.v1/pom.xml
  1. … 21 more files in changeset.
Added support of the GridFS

    • -0
    • +12
    /exo.jcr.component.core.impl.tokumx.v1/pom.xml
  1. … 4 more files in changeset.
Merge branch 'master' of github.com:exodev/jcr into TokuMX-POC

Ask to spool content for performances reason

JCR-2347: Allow to Spool content if required

JCR-2347: Allow to Spool content if required

Reduce the total amount of queries

Add max-connections to avoid connection reset

JCR-2347: Fix TestCacheableWorkspaceDataManager.java

JCR-2347: Fix TestCacheableWorkspaceDataManager.java

Upgraded to AWS 1.9.0, fixed the connection leak issue and added some unit tests

    • -3
    • +8
    /exo.jcr.component.core.impl.amazonaws.v1/pom.xml
Merge branch 'stable/1.15.x' of github.com:exoplatform/jcr into S3

JCR-2347: Allow to implement a Value Storage non File System based

Integrarted changes from JCR-2347

Merge branch 'TokuMX-POC' of github.com:exodev/jcr into TokuMX-POC

Upgrade to the latest version of eXo JCR 1.16.x

KER-292: Add some doc about the example project

KER-292: SessionScoped and RequestScoped beans are not accessible from the rest webapp in portal mode (jcr part)

JCR-2346: Simultaneous startup of the nodes results in failure of initialization of almost all nodes

JCR-2345: Simultaneous startup of the nodes results in failure of initialization of almost all nodes

Problem analysis

- Deep investigations show that the requested RemoteCommand _org.exoplatform.services.jcr.impl.core.query.lucene.DocNumberRecoveryFilter-getDocNum-portal-repository-portal-system-false_ cannot be invoked because it has been removed from the commands map under the RPCService.

- The timestamp in which command was removed from the coordinator coincides with the timestamp where the same command get removed from the nodes being shut down using the org.exoplatform.services.rpc.impl.AbstractRPCService#unregisterCommand.

Fix description

- When the SearchIndex has been suspended, the getDocsNumCommand command waits until SearchIndex is resumed

JCR-2345: Simultaneous startup of the nodes results in failure of initialization of almost all nodes

JCR-2345: Simultaneous startup of the nodes results in failure of initialization of almost all nodes

JCR-2226 :Performance Issues when working with a large Database

  1. … 90 more files in changeset.
Merge branch 'fix/1.16.x/JCR-2322'

JCR-2344: Parsing error appeared when export PDF file

JCR-2343: Parsing error appeared when export PDF file and import it again

* Problem analysis:

An invalid character in a PDF file is stored in XML file when exporting it.

XML parser cannot then parse this character when importing again.

* Fix description:

- Validate all characters when exporting to System View.

If a string has invalid character, it uses Base64 encoding instead of unicode (default) for that string.

- When importing, it checks and sets appropriate encoding value per string.

- Nothing changes in case of Document View.

ECMS-6597 will provide a comprehensible message so that the user who imports such file can remove that character manually.

JCR-2343: Parsing error appeared when export PDF file