| Problem mongodb query/find by id [message #1031352] |
Mon, 01 April 2013 12:07  |
Eclipse User |
|
|
|
Using Eclipselink version 2.4.2-RC1 because of Bug 392174. Mongodb version is 2.4.0.
I am having a problem searching for a document by the mongo generated OID.
I have a simple mongo entity, Exercise, mapped to a collection called 'exercises. The id is mapped to _id as @GeneratedValue.
The document already exists in the collection.
db.exercises.findOne()
{
"_id" : ObjectId("5155ccb4f4b5a31e95000334"),
"name" : "Unicycling",
"description" : "unicycling"
}
Searching by id using:
String exerciseId = "5155ccb4f4b5a31e95000334";
Exercise testExercise = em.find(Exercise.class,exerciseId);
returns no results:
[EL Fine]: sql: 2013-04-01 10:25:20.203--ServerSession(529858968)--Connection(102824579)--Thread(Thread[main,5,main])--Executing MappedInteraction()
spec => null
properties => {mongo.collection=exercises, mongo.operation=FIND}
input => [5155ccb4f4b5a31e95000334]
[EL Finest]: query: 2013-04-01 10:25:20.394--ServerSession(529858968)--Thread(Thread[main,5,main])--Adapter result: null
[EL Finest]: query: 2013-04-01 10:25:20.394--ServerSession(529858968)--Thread(Thread[main,5,main])--Data access result: null
I have also tried JPQL:
[code]
String id = "5155ccb4f4b5a31e95000334";
Query query = getEntityManager().createQuery("SELECT e FROM Exercise e WHERE e.id = :id");
query.setParameter("id", id);
List<Exercise> exercises = query.getResultList();
[\code]
Also with no results.
I am however able to query by one of the other fields:
String description = "unicycling";
Query query = getEntityManager().createQuery("SELECT e FROM Exercise e WHERE e.description = :description");
query.setParameter("description", description);
List<Exercise> exercises = query.getResultList();
[EL Fine]: sql: 2013-04-01 10:52:20.868--ServerSession(305297482)--Connection(70630159)--Thread(Thread[main,5,main])--Executing MappedInteraction()
spec => null
properties => {mongo.collection=exercises, mongo.operation=FIND}
input => [DatabaseRecord(
exercises.description => unicycling)]
[EL Finest]: query: 2013-04-01 10:52:21.772--ServerSession(305297482)--Thread(Thread[main,5,main])--Adapter result: [{_id=5155ccb4f4b5a31e95000334, description=unicycling, name=Unicycling}]
Once the record has been found by another search (or by a findAll()), the JPQL method of finding by id will return a record (I am assuming from the EntityManager cache). The EntityManager.find() method however still does not return results.
Has anyone else seen this behavior or have a workaround?
Thanks,
Jason
|
|
|
|
|
|
|
|
|
| Re: Problem mongodb query/find by id [message #1052646 is a reply to message #1042464] |
Tue, 30 April 2013 06:49  |
| Eclipse User |
|
|
|
I've got the same problem. My eclipselink version : 2.4.1.
My class :
@Entity
@NoSql(dataFormat=DataFormatType.MAPPED, dataType="collecte")
public class Collecte {
@Id
@GeneratedValue
//@Field(name="_id")
private String id;
....
I've tried with or without @Field annotation, same results.
The test :
EntityManagerFactory emf = Persistence
.createEntityManagerFactory("mongoPU");
EntityManager em = emf.createEntityManager();
Collecte c = em.find(Collecte.class, "517f9d50559a541e63011fe0");
//Query q = em.createQuery("select c from Collecte c where c.id =:id");
// Query q = em.createNativeQuery("db.collecte.findOne({\"_id\": ObjectId(" +"517f9d50559a541e63011fe0"+ ") \"})", Collecte.class);
//q.setParameter("id", "517f9d50559a541e63011fe0");
// Collecte c = (Collecte) q.getSingleResult();
assertThat(c.getEan()).isEqualTo("3251248033108");
None of the methods find(), createQuery, createNativeQuery() works.
The logs :
[EL Finest]: jpa: End deploying Persistence Unit mongoPU; session file:/home/david/git/servicescrowdsourcing/target/scala-2.10/classes/_mongoPU; state Deployed; factoryCount 1
[EL Finer]: connection: client acquired: 148643588
[EL Finer]: transaction: acquire unit of work: 1188706162
[EL Finest]: query: Execute query ReadObjectQuery(name="readObject" referenceClass=Collecte )
[EL Finest]: connection: Connection(1634151355)--Connection acquired from connection pool [default].
[EL Fine]: sql: Connection(1634151355)--Executing MappedInteraction()
spec => null
properties => {mongo.collection=collecte, mongo.operation=FIND}
input => [517f9d50559a541e63011fe0]
[EL Finest]: query: Adapter result: null
[EL Finest]: query: Data access result: null
[EL Finest]: connection: Connection(1634151355)--Connection released to connection pool [default].
The data have been inserted in MongoDB also with EclipseLink.
Any advice ?
Thanks,
David
|
|
|
|
| Re: Problem mongodb query/find by id [message #1052803 is a reply to message #1052720] |
Tue, 30 April 2013 10:50 |
| Eclipse User |
|
|
|
Yes insertion in database work find but I think find the cause :
1/ if you add the annotation @Field(name="_id"), the id java field is record as a capitalise string in the _id database field, not as an ObjectId.
2/ if you suppress this annotation, you hava two UUID record in the database, first in ID column and the UUID string is capitalise, and second UUID in _id column, not capitalized and it's type is ObjectId !
In first case, you can find the produit with the ID, but tools like MonjaDb and Genghis can't be used to maintain database.
In second case, you can find the product with the capitalize id, but record twice an UUID is strange...
|
|
|
|
| Re: Problem mongodb query/find by id [message #1053771 is a reply to message #1053070] |
Tue, 07 May 2013 10:28 |
| Eclipse User |
|
|
|
MongoDB requires an "_id" key field. If your data does not contain one, Mongo will generate one as an ObjectId.
The application is free to use whatever value it wants for "_id", it is odd your tools are requiring this to be an ObjectId.
In EclipseLink, you can use whatever type you want for the "_id", but this will be the value passed to Mongo. So if you map it as String, then it will be a String.
@GeneratedValue will initialize this field with a new ObjectId converted to your field's type (in your case String).
Your converter is probably the best way to ensure the type is an ObjectId in the database.
You might also be able to declare the type as ObjectId to avoid the String conversion. If this does not work, please log a bug to have ObjectId support corrected.
|
|
|
Powered by
FUDForum. Page generated in 0.28558 seconds
Home