spring-projects / spring-data-mongodb Goto Github PK

Mark Pollack opened DATAMONGO-9 and commented

This is based off the functionality now in Spring Data Commons that came from the Hades project

Issue Links:

• DATAMONGO-17 Add generic repository implementation for MongoDB
  ("duplicates")

Mark Pollack opened DATAMONGO-26 and commented

Affects: 1.0 M1

2 votes, 0 watchers

Mark Pollack opened DATAMONGO-18 and commented

Issue Links:

• DATAMONGO-25 Extract MongoOperations from MongoTemplate
  ("is duplicated by")

Mark Pollack opened DATAMONGO-2 and commented

No further details from DATAMONGO-2

Mark Pollack opened DATAMONGO-16 and commented

No further details from DATAMONGO-16

Oliver Drotbohm opened DATAMONGO-17 and commented

We should add a repository implementation to execute criteria queries that are derived from query methods

Issue Links:

• DATAMONGO-9 Automatic implementation of interface query method nameds on repositories
  ("is duplicated by")

Thomas Risberg opened DATAMONGO-42 and commented

We should provide a way to specify replica sets in the Mongo namespace

Affects: 1.0 M2

Mark Pollack opened DATAMONGO-28 and commented

Docbook style reference guide

No further details from DATAMONGO-28

Mark Pollack opened DATAMONGO-39 and commented

Affects: 1.0 M1

Oliver Drotbohm opened DATAMONGO-20 and commented

We should create a namespace to allow automatic detection of MongoRepository interfaces and bean creation

No further details from DATAMONGO-20

Oliver Drotbohm opened DATAMONGO-49 and commented

When triggering queries like

List<Person> findByLastnameLikeAndAgeBetween(String lastname, int from, int);

only the last criteria will be issued against Mongo

Affects: 1.0 M1

Attachments:

• mylyn-context.zip (8.74 kB)

Mark Pollack opened DATAMONGO-5 and commented

The first pass at exception translation just converts most everything to InvalidDataAccessApiUsageException. Need to dig deeper into the WriteResult values and other errors to provide a more accurate translation to the DAO exception hierarchy

This issue is a sub-task of DATAMONGO-4

Mark Pollack opened DATAMONGO-7 and commented

The use of MapReduce via the driver is cumbersome, provide a layer that exposes map reduce operations with type-safe helper objects.

Investigate: http://cookbook.mongodb.org/ lists a few common cases where one would use map-reduce, typically to sort/count document array elements. See how this might be better packaged up so as to avoid Java users from having to write JavaScript/MapReduce for common tasks

Issue Links:

• DATAMONGO-182 add 'group' and 'mapreduce' to the MongoOps
  ("Cloned from")

1 votes, 1 watchers

Oliver Drotbohm opened DATAMONGO-41 and commented

QueryDsl just introduced an abstraction of the actual API used for Mongo access. Thus we can provide a MongoTemplate based implementation and offer integration to execute predicates similar to the functionality in the JPA module.

https://bugs.launchpad.net/querydsl/+bug/713025

Affects: 1.0 M1

Issue Links:

• DATAJPA-8 Integration of QueryDsl library

Jon Brisbin opened DATAMONGO-50 and commented

We should incorporate code from the spring-data-mapping project (formerly Grails' inconsequential) to support rich mapping in the MongoDB support.

Things we'll need to address include:

• Implementing the right MappingContext and MappingConfigurationStrategy objects to read an object's annotations and configure the mapper appropriately.
• Saving and reading child collections in case of relationships.
• Implementing a special MongoConverter class to handle reading and writing objects

Affects: 1.0 M1

Sub-tasks:

• DATAMONGO-52 Add further mapping integration tests

• DATAMONGO-53 Annotation refactoring

• DATAMONGO-54 Move model package into commons

• DATAMONGO-55 Refactoring to break up MongoIntrospector

Mark Pollack opened DATAMONGO-4 and commented

Sub-tasks:

• DATAMONGO-5 Provide detailed mapping of Mongo errors onto Spring DAO exception

Oliver Drotbohm opened DATAMONGO-30 and commented

We should create some basic reference documentation:

• configuration
  both Java @Configuration and XML style
• using the MongoTemplate
  inserting, querying, saving, updating etc.
• using the repositories
  how the repository approach works, what keywords for query creation are currently supported and so on

No further details from DATAMONGO-30

Mark Pollack opened DATAMONGO-6 and commented

Provide Spring Resource abstraction for GridFS.
Helper class around common use cases.

File upload servlet?

Referenced from: commits 572c4bb

8 votes, 9 watchers

Oliver Drotbohm opened DATAMONGO-43 and commented

Affects: 1.0 M2

Mark Pollack opened DATAMONGO-27 and commented

Review MongoTemplate API

Affects: 1.0 M1

Mark Pollack opened DATAMONGO-10 and commented

This allows for the DB getConnection() method to be DB getDB() which is more natural

No further details from DATAMONGO-10

Oliver Drotbohm opened DATAMONGO-34 and commented

Suppose we have a repository as follows:

public interface UserRepository extends MongoRepository<User, ObjectId> {

  List<User> findByUsername(String username);
}

On repository instance creation we could check for and index being available for User.username and create one if not existent

Affects: 1.0 M1

Attachments:

• mylyn-context.zip (6.13 kB)

Oliver Drotbohm opened DATAMONGO-22 and commented

We should add sorting and pagination behaviour to the base repository implementation as well as to the execution of query methods

Attachments:

• mylyn-context.zip (2.76 kB)

Mark Pollack opened DATAMONGO-15 and commented

Consider just not doing this as it leads to many overloads... TBD

No further details from DATAMONGO-15

Mark Serrano opened DATAMONGO-44 and commented

When creating a simple POJO with an id property and persisting this object to MongoDB, the id property is overridden by Spring Data. It merges the "id" with "_id".

For example:
{ "_id" : "69133244-fcc0-42b2-aa59-308f00c75860", "firstName" : "John", "money" : 1000, "lastName" : "Smith" }

{ "_id" : "45d236ff-6a38-4767-a973-6f3d70ff2448", "firstName" : "Jane", "money" : 2000, "lastName" : "Adams" }

{ "_id" : "9dcba269-9ed5-45c6-887e-a2de8fec334d", "firstName" : "Jeff", "money" : 3000, "lastName" : "Mayer" }

The native MongoDB preserves both the "id" and "_id", while Spring Data combines both as "_id". As a workaround, I have to rename my POJO's id property as "pid" (any other name will work).

For example:
{ "_id" : ObjectId("4d5e7b3bfdece02281f253a4"), "id" : "f1e6b8b2-9d68-495c-9d6e-b81cc35cf9bc", "firstName" : "John", "lastName" : "Smith", "money" : 1000 }

{ "_id" : ObjectId("4d5e7b3bfdece02282f253a4"), "id" : "39f6ebfb-10cf-4702-a5b8-8bc2489cebcc", "firstName" : "Jane", "lastName" : "Adams", "money" : 2000 }

{ "_id" : ObjectId("4d5e7b3bfdece02283f253a4"), "id" : "f4932004-c320-47e4-b4b3-7d07f3aaabb9", "firstName" : "Jeff", "lastName" : "Mayer", "money" : 3000

See the following tutorial that shows this "pid" workaround: http://krams915.blogspot.com/2011/02/spring-data-mongodb-tutorial.html

See the following tutorial that uses native MongoDB which correctly preserves both "id" and "_id": http://krams915.blogspot.com/2011/01/spring-mvc-3-using-document-oriented.html

Reference URL: http://forum.springsource.org/showthread.php?p=346693&posted=1#post346693

Issue Links:

• DATAMONGO-56 Document id conversion rules and assumptions

Mark Pollack opened DATAMONGO-38 and commented

Affects: 1.0 M1

Issue Links:

• DATAMONGO-56 Document id conversion rules and assumptions

2 votes, 2 watchers

Oliver Drotbohm opened DATAMONGO-33 and commented

Currently we expect the id field of a domain class to be named id. We could get rid of this constraint by allowing any field to be annotated

Affects: 1.0 M1

Oliver Drotbohm opened DATAMONGO-25 and commented

We should introduce a MongoOperations interface for the functionality provided in MongoTemplate to decrease the coupling of potential clients (e.g. the repository abstraction) and align to all other Spring templates that follow that guideline.

It's probably a good idea to do this while polishing the JavaDoc as well

Affects: 1.0 M1

Issue Links:

• DATAMONGO-18 Extract common MongoTemplate methods into MongoOperations interface
  ("duplicates")

Mark Pollack opened DATAMONGO-19 and commented

No further details from DATAMONGO-19

Mark Pollack opened DATAMONGO-36 and commented

Spring 3.0 supports JSR-303. If

<bean id="validator" class="org.springframework.validation.beanvalidation.LocalValidatorFactoryBean"/>
is defined, we can ask the container for the validator (is there an Aware interface?) and then perform validation within MongoTemplate methods that take a POJO for Create, update, or delete operations.

Affects: 1.0 M2

Attachments:

• mylyn-context.zip (6.70 kB)

Referenced from: commits 5b13307

1 votes, 3 watchers

Mark Pollack opened DATAMONGO-35 and commented

No further details from DATAMONGO-35

Oliver Drotbohm opened DATAMONGO-46 and commented

As of issue DATACMNS-16 the query infrastructure detects In and NotIn keywords. We should add implementations for this for Mongo

Affects: 1.0 M1

Attachments:

• mylyn-context.zip (3.31 kB)

Oruganti Shanker opened DATAMONGO-40 and commented

Need to be able to specify the collection name for each repository. The collection name used for each entity should be specifiable as an annotation, e.g., the Table annotation.

Another important enabler for using spring-data-mongo in production code is to add a few annotations which have similar functionality to the @Reference, @Embedded etc. in Morphia, and for naming the fieldnames in the persistence store differently from the fieldnames used in the Java Entity. Of course these annotations should be consistent with JPA annotations, and should be a superset of JPA annotations.

See the thread http://forum.springsource.org/showthread.php?t=102127 in the Forum

Attachments:

• mylyn-context.zip (14.78 kB)

1 votes, 2 watchers

Oliver Drotbohm opened DATAMONGO-31 and commented

Currently one cannot use Between as keyword inside query method names. It would be cool if we allowed something like this:

List<Person> findByAgeBetween(int from, int to);

This should logically result in:

find({"age" : {"$gte" : from, "$lte" : to}})

No further details from DATAMONGO-31

Mark Pollack opened DATAMONGO-48 and commented

Support @Document (or similar annotation) on a field of a JPA manged entity to allow the entity state to be stored/loaded form a relationaldb + mongo.

Affects: 1.0 M1

Mark Pollack opened DATAMONGO-8 and commented

Make it very easy to build up an update document with various operations

No further details from DATAMONGO-8

Mark Pollack opened DATAMONGO-13 and commented

No further details from DATAMONGO-13

Thomas Risberg opened DATAMONGO-23 and commented

No further details from DATAMONGO-23

Mark Pollack opened DATAMONGO-37 and commented

if (!conversionService.canConvert(ObjectId.class, String.class)) {

always returns true, picks ObjectToObjectConverter as satisfying the conversion

Affects: 1.0 M1

Mark Pollack opened DATAMONGO-1 and commented

No further details from DATAMONGO-1

Oliver Drotbohm opened DATAMONGO-47 and commented

Attachments:

• mylyn-context.zip (18.21 kB)

Issue Links:

• DATACMNS-17 Introduce value object for domain class and repository metadata
  ("depends on")

Mark Pollack opened DATAMONGO-11 and commented

No further details from DATAMONGO-11

Mark Pollack opened DATAMONGO-12 and commented

queryForCollection -> getCollection
queryForList -> query

No further details from DATAMONGO-12

Oliver Drotbohm opened DATAMONGO-24 and commented

As queries a defined using a JSON syntax in MongoDB we could allow usage of Query annotation on query methods

Attachments:

• mylyn-context.zip (2.57 kB)

Mark Pollack opened DATAMONGO-21 and commented

Instead of using MongoFactoryBean and MongoOptionsFactoryBean

No further details from DATAMONGO-21

Mark Pollack opened DATAMONGO-3 and commented

The work done on CouchDB for SpringOne was done inside the http://git.springsource.org/spring-data/datastore-document-examples and needs to be moved

No further details from DATAMONGO-3

Oliver Drotbohm opened DATAMONGO-32 and commented

Besides plain JSON array hierarchies the SimpleMongoConverter could support Spring EL expressions for keys such as:

{"parameters.p1" : "1" , "count" : 5.0}

Need to discuss, how to detect Spring EL in this case. We could simply forbid dots in plain keys and treat every key containing a dot as Spring EL or enforce concrete EL delimter usage #{...}

No further details from DATAMONGO-32

Mark Pollack opened DATAMONGO-45 and commented

Affects: 1.0 M1

Mark Pollack opened DATAMONGO-29 and commented

Sample applications sit in a separate repository but should be sync'd with the M1 release.
Two types of examples are important to show

1. Generic Repository data access (CRUD) on some domain object
2. Specific features of MongoTemplate that highlight typical MongoDB use cases, such as partial update.

Existing apps show

1. Spring MVC analytics
2. Collection of file system information

Could look into music play-list style application or use of Restaurants domain from Chris Richardson's POJOs in action as much has been done in neo and couchdb to support that domain

No further details from DATAMONGO-29

Mark Pollack opened DATAMONGO-14 and commented

No further details from DATAMONGO-14