qbe | A Quick Backend - QBE - Backend Compiler http : //c9x

Short answer: QBE cannot match any exact document structure including an array structure.

Context: QBE executes against the MarkLogic universal index and range indexes.

On JSON documents, the MarkLogic universal index contains property names and atomic values:

• each object provides a bag of indexed names
• each array contributes to a bag of multiple values
• each atomic value is indexed

Matching against indexes is important for performance and scale.

To put it the other way, inspecting the actual structure of every document instead of the indexes projected from the documents would be impractical for almost any production database.

Some alternatives:

• Inspect the matched documents to eliminate the false positives (preferably in SJS on the enode)
• Materialize the concatenation of the array items with a _ separator character in the document as a property used only in queries.
• Solve the problem with TDE and the Optic API.

Expanding on the last alternative:

• TDE could concatenate the array items as a value in a single-column view.
• Or, TDE could project each array item as a separate row and the query could group on the document fragment id, sample the row, filter out groups where the count is > 1, and join the documents

Hoping that's useful,

The spring document states that this only works with SingularAttribute.

Currently, only SingularAttribute properties can be used for property matching. https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#query-by-example.running

You want to search by a property that is a Set (genreList), which is a PluralAttribute. It is not possible to search by this field.

It will be ignored when building a query, as can be seen here: https://github.com/spring-projects/spring-data-jpa/blob/master/src/main/java/org/springframework/data/jpa/convert/QueryByExamplePredicateBuilder.java#L127

Advanced Spring Data JPA - Specifications and Querydsl. https://spring.io/blog/2011/04/26/advanced-spring-data-jpa-specifications-and-querydsl/

For this you need to extend from interface JpaSpecificationExecutor:

FunCoder, This should allow you to get the Last Login Date and Time from the DC. It will convert the user found to an authenticated principle which contains a number of different properties that might help with other information you might be looking for in the future.

The problem can occur in case you are passing your elements to dao funciton public Collection findFilesByFolder(Collection ids) using Arrays.asList() function.

In that case the object instance will not be of class ArrayList. It will be of type Arrays$ArrayList. I am guessing this based on the error message pasted by you.

Your code flow goes to else part in your loop which calls setParameter instead of setParameterList. When you pass Array$ArrayList object to setParameter function, it tries to cast list object, but fails for obvious reasons, hence the error.

If you pass an ArrayList object which you have created using new ArrayList() function. It should work fine.

You are missing an #include directive:

You can try this: