[
https://issues.apache.org/jira/browse/METAMODEL-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028568#comment-15028568
]
ASF GitHub Bot commented on METAMODEL-211:
------------------------------------------
GitHub user mishadoff opened a pull request:
https://github.com/apache/metamodel/pull/73
METAMODEL-211 Mongo autogenerated _id handled properly in where clause
This fix processes each value in filter clauses and if it is a valid Mongo
bson id, converts it into ObjectId. Tests are included and cover select by id
and delete by id queries.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Zoomdata/metamodel METAMODEL-211
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/metamodel/pull/73.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #73
----
commit 5d737b832c86fba9cb0df131c92789eebc629628
Author: Mykhailo Kozik <[email protected]>
Date: 2015-11-26T10:52:44Z
METAMODEL-211 Mongo autogenerated _id handled properly in where clause
----
> Primary key query in MongoDB does not find the record
> -----------------------------------------------------
>
> Key: METAMODEL-211
> URL: https://issues.apache.org/jira/browse/METAMODEL-211
> Project: Apache MetaModel
> Issue Type: Bug
> Affects Versions: 4.4.1
> Reporter: Tomasz Guzialek
>
> Primary key query in MongoDbDataContext does not return the record despite it
> being there. Example query:
> {code:java}
> DataSet ds = dc.query()
> .from("users")
> .selectAll()
> .where("_id").eq("56334c6fb38cfec169db2ccb")
> .execute();
> {code}
> My suspition is that in the query we have the _id in a form of a String while
> the _id field in Mongo is actually a new ObjectId("56334c6fb38cfec169db2ccb")
> and therefore it does not match.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
