Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
MODE-2684 Removes the compile time dependency of modeshape-core towards Apache Tika The mime type extraction functionality will still function as-is if Tika is present, but now there is also an independent extension-based default which will be used if Tika is not present in the CP at runtime

    • -1
    • +1
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 23 more files in changeset.
MODE-2594 Adds better query handling by the REST service for multi-valued properties

    • -0
    • +15
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 3 more files in changeset.
MODE-2590 Adds the 'batchSize' attribute to the REST service's backup and restore methods

    • -2
    • +2
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 1 more file in changeset.
MODE-2516 Updates JDK to 1.8 and jboss-parent to the latest version (19) This is the first significant commit of the 5.x series and contains a number of significant changes: - the naming of Maven version properties changed to adopt the standard pattern: 'version.<groupId>.<artifactId>' - build system and dependency updates so that the latest Maven plugin versions function correctly - updating source code to avoid compiler and javadoc warnings

    • -16
    • +18
    ./jcr/rest/AbstractRestTest.java
  1. … 154 more files in changeset.
MODE-2109 Updates some unit tests which fail whenever built-in node types are added.

    • -4
    • +18
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 5 more files in changeset.
MODE-2452 Implemented backup/restore methods for the REST service.

    • -0
    • +78
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 9 more files in changeset.
MODE-2297 Minor correction to previous change on pseudocolumns.

  1. … 2 more files in changeset.
MODE-2299 Suppressed several compiler warnings about use of deprecated APIs from the recently-updated Apache HttpClient library.

  1. … 2 more files in changeset.
MODE-2185 Fixed JavaDoc error and Java compiler warnings

    • -109
    • +85
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 10 more files in changeset.
MODE-2185 Removed the old REST service (/v1) and retrofitted the existing tests to reflect this change.

    • -0
    • +497
    ./jcr/rest/AbstractRestTest.java
    • -962
    • +0
    ./jcr/rest/JcrResourcesTest.java
    • -238
    • +270
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 186 more files in changeset.
MODE-2261 Fixed the REST service to handle multiple query selectors and in addition fixed the query engine's handling of the [jcr:score] property when this appears in multiple selectors.

    • -1
    • +9
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 3 more files in changeset.
MODE-2261 Fixed the REST service to handle multiple query selectors and in addition fixed the query engine's handling of the [jcr:score] property when this appears in multiple selectors.

    • -1
    • +9
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 3 more files in changeset.
MODE-2261 Fixed the handling of multiple selectors for the REST service queries.

    • -0
    • +9
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 1 more file in changeset.
MODE-2250 Fixed the handling of negative (-1) depths for the REST service when retrieving items.

    • -0
    • +21
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 2 more files in changeset.
MODE-2250 Fixed the handling of negative (-1) depths for the REST service when retrieving items.

Conflicts:

web/modeshape-web-jcr-rest-war/src/test/java/org/modeshape/web/jcr/rest/ModeShapeRestServiceTest.java

    • -0
    • +22
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 2 more files in changeset.
MODE-2250 Fixed the handling of negative (-1) depths for the REST service when retrieving items.

Conflicts:

web/modeshape-web-jcr-rest-war/src/test/java/org/modeshape/web/jcr/rest/ModeShapeRestServiceTest.java

    • -0
    • +22
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 2 more files in changeset.
MODE-2182 Added 2 methods to the REST service which allow uploading binaries under a [nt:folder]/[nt:file] hierarchy, creating the hierarchy if it doesn't exist.

    • -18
    • +108
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 6 more files in changeset.
MODE-2188 Added management of index providers and index definitions

ModeShape now can manage index providers and index definitions via a programmatic API

that allows registering new/updated providers and adding/updating/removing index definitions.

Index definitions are stored as nodes in the system area using a structure such as

"/jcr:system/mode:indexes/{providerName}/{indexDefinition}/{indexColumnDefinition}".

Changes on one process in the cluster will be persisted to the cace store, and events

on all processes in the cluster will signal a refreshing of a snapshot of the index

definitions used by the query system. Additionally, when changes are made to

an index definition, the provider that owns that definition will be notified of the

new/changed or removed index definition.

Index provider information is not stored in the system area, but rather is used to

instantiate the providers in the same way as sequencers and connectors. Thus,

the repository configuration for each process in the cluster needs to define the

index providers; no information is shared across processes. Notice that all process-specific

information about indexes must be defined on the provider. For example, a notional

provider that stores indexes on the file system would likely require as a configuration

setting the directory in which those files are stored, and this could vary in each

process' configuration. BTW, this maintains ModeShape's convention of using the same

repository configuration file on each process in the cluster, albeit with variables

for any configuration parameters that must vary for the different processes.

Every index definition explicitly states the name of the provider that owns it.

If there is no such provider, ModeShape will mark the index definition as 'disabled'

and it will not be used on that process.

At this time it is not yet possible to define index providers or index definitions

in the repository configuration JSON file or the Wildfly subsystem. This will be

done with a future commit.

However, it is possible with this commit to programmatically register a provider

and define multiple indexes. Testing will also be done in a future commit as a

practical and usable provider is available.

The package and most of the interfaces in the index SPI introduced in 4.0.0.Alpha1

(e.g., formerly 'org.modeshape.jcr.spi.query') were renamed to be shorter and

more appropriate for their current & planned scope. For example, the "QueryIndexProvider"

interface is now simply "IndexProvider".

  1. … 72 more files in changeset.
Corrected compiler and JavaDoc warnings

    • -19
    • +14
    ./jcr/rest/JcrResourcesTest.java
  1. … 25 more files in changeset.
MODE-2018 Implemented new query engine.

Refactored the query functionality to now use several new service provider interfaces (SPI),

and implemented a new query engine that can take advantage of administrator-defined indexes.

When no such indexes are defined, the query engine is able to still answer the queries

by "scanning" all nodes in the repository. This is like a regular relational database:

all query functionality works (albeith slowly) even when no indexes are defined, though

to improve performance simply define an appropriate index based upon the query or queries

that are being used.

All of ModeShape's query parsing, planning, and optimization steps are basically unchanged

from the previous query system. There is one addition to the rule-based optimizer: a new

rule looks at query plans and adds the potential indexes that might be of use in each

access query portion of a query plan. Then, the query execution process (see below)

chooses one of the identified indexes based upon the selectivity and cardinality. If no index

is available for that portion of the query plan, then the query engine simply iterates

over all queryable nodes in the repository.

A new kind of component, called a "query index provider", allows the query engine to delegate

various responsibilities around indexes to these providers. For example, a provider must

provide an index planner that can examine the constraints that apply to an access query

and determine if any of the provider's indexes can be used. When they are, ModeShape

adds those indexes to the query plan. If the query engine uses one of those indexes,

then provider must be able to return all of those nodes that satisfy the criteria

as described earlier by its index planner. Finally, as ModeShape content changes, ModeShape

will notify the index providers' of the changes so that they can ensure their indexes

are kept up-to-date with the content.

This means that a provider can implement the functionality using any kind of technology,

and consequently, that ModeShape can begin to leverage multiple kinds of search and index

technology within its query system. The ModeShape community anticipates having providers

that use Lucene, Solr, and ElasticSearch. ModeShape will also likely come with a provider

that maintains file-system based indexes. Additionally, providers can optionally support

indexes on one or more properties. Thus, it will be possible to mix and match

these providers, selecting the best technology for the specific kind of index.

The new query engine does the execution in a very different way than the previous engine,

which used Lucene to determine the tuples (that is, the values in each row) for each access

query and that were then further processed and combined to form the tuples that were returned

in the result set. The new engine instead uses a new concept of a "stream of node keys"

for each access query: what actually implements that stream depends on many factors.

A node sequence is an abstraction of a stream of "rows" containing one or more node keys.

The interfaces are designed to make it possibly to lazily implement a stream in a very

efficient manner. Specifically, a node stream is actually comprised of multiple "batches"

of rows, and batches can be of any size.

Consider when the engine findes no indexes are available for a certain access query. The

engine simply uses a "node sequence" (or NodeSequence) implementation that returns in batches

a row for each node in the repository.

But if an access query involves a criteria on the path of a node, such as

"... WHERE ISSAMENODE('/foo/bar') ...", then ModeShape knows that this query (or portion of

a query) will have only one result, namely the node at "/foo/bar". ModeShape doesn't need

an index to quickly find this node; it merely has to navigate to that path to find the one

node that satisfies this query. ModeShape has several other optimizations, too: it knows

when a query involves all children or descendants of a node at a given path, and can take

this into account when optimizing and executing the query. All of these are handled with

special NodeSequence implementations optimized for each case.

For many access queries (i.e., part of a larger query), the engine will use one of the

indexes identified by one of the providers. When this happens, ModeShape uses other

NodeSequence implementations that utilize the underlying indexes to find the nodes that satisfy

some of the criteria.

The above describes how the engine uses a single NodeSequence instance for each each access

query in a larger query. But how does the engine combine these to determine the ultimate

query results? Basically, the engine constructs a series of functions that process one or more

NodeSequence instances to filter and combine into other NodeSequences.

For example, a custom index might be used to find all nodes that have a 'jcr:lastModified'

timestamp within some range. Presumably this index is used because it has a higher selectivity,

meaning that it will filter out more nodes and return fewer nodes than other indexes.

Other criteria that are also applied to this access query might then be applied by a filter

that processes the actual nodes' property values.

While the result of this commit is a functioning query engine that is shown to work in most

of the query-related unit and integration tests, there still are a few areas that are not complete.

Specifically:

* The new engine does not support full-text search, and currently throws an exception

* No index providers are implemented. Therefore, all queries involve "scanning" the repository.

This can be time consuming, especially for federated repositories. Consequently, all such

tests that query federated content have been disabled/ignored.

  1. … 231 more files in changeset.
MODE-2181 Changed the REST service tests to use Apache HttpClient. This allowed some previously disabled tests to be re-enabled.

    • -169
    • +190
    ./jcr/rest/JcrResourcesTest.java
    • -31
    • +32
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 4 more files in changeset.
MODE-2181 Added supported for SNS to the REST service via support of JSON arrays.

    • -18
    • +63
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 6 more files in changeset.
MODE-2181 Added supported for SNS to the REST service via support of JSON arrays.

    • -0
    • +46
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 5 more files in changeset.
MODE-2170 Fixed the handling of multi-valued properties in the REST service and converted the deprecated API (interceptors) to use the current RestEASY API (filters).

    • -0
    • +10
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 6 more files in changeset.
MODE-2170 Fixed the handling of multi-valued properties in the REST service and converted the deprecated API (interceptors) to use the current RestEASY API (filters).

    • -0
    • +10
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 11 more files in changeset.
MODE-2065 Ported the EAP kit to Wildfly 8.0.0.CR1. This exposed a number of issues that had to be addressed: - using Servlet 3.1 compliant containers meant upgrading Cargo & Jetty to 9.x - WebDAV mock tests together with dependencies were removed because they added no value - upgraded to the latest EE BOM which meant changing the Arquillian tests

    • -1
    • +1
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 124 more files in changeset.
MODE-2065 Updated the main ModeShape dependencies which overlap with those from Wildfly. Some notable changes include: - RestEASY upgraded to 3.0.6 (includes ModeShape code update) - Servlet API upgraded to 3.1 (includes ModeShape code update) - org.jboss.as dependencies replaced with org.wildfly dependencies

    • -61
    • +32
    ./jcr/rest/JcrResourcesTest.java
  1. … 42 more files in changeset.
MODE-2041 Corrected numerous compiler warninings, JavaDoc errors and warnings, and removed quite a few JavaDoc comments that are inherited via @Override.

  1. … 79 more files in changeset.
MODE-2081 Changed the license for ModeShape code to ASL 2.0.

    • -17
    • +9
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 558 more files in changeset.
MODE-2056 Updated the REST service so that any session used for servicing a request is always logged out at the end, either in the happy or the exceptional cases. To support this, a couple of other changes were made: - the modeshape-api/Repository interface was updated to expose the current active sessions - the modeshap-api/Logger interface was updated and the standard "isEnabled" methods added - a Logging interceptor was added which, in DEBUG mode, can output various information about the incoming requests.

    • -1
    • +15
    ./jcr/rest/ModeShapeRestServiceTest.java
  1. … 22 more files in changeset.