[
https://issues.apache.org/jira/browse/DRILL-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114343#comment-15114343
]
Jacques Nadeau commented on DRILL-4307:
---------------------------------------
This isn't really a bug as much as a change in behavior.
1.3 ObjectId => map
1.4 ObjectId => binary value
Can you explain your use case and why you want ObjectId types (basically uuids)
to translate to a drill map? In general, exposing the value as single scalar
actually seems more useful since it can be used in group bys, used in where
clauses easily, etc.
> new MongoDB BSON record reader breaks _id SELECT-ion
> ----------------------------------------------------
>
> Key: DRILL-4307
> URL: https://issues.apache.org/jira/browse/DRILL-4307
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - MongoDB
> Affects Versions: 1.5.0
> Reporter: Michael Gokhman
>
> in Drill 1.4, SELECT-ing an _id results in:
> {code}
> {"$oid":"567ff2697f2310849fea0666"}
> {code}
> as expected.
> however, when working with the master branch, SELECT-ing an _id results in a
> something that looks like a pointer:
> {code}
> [B@3149a…]
> {code}
> This is caused by DRILL-3478, and can be avoided by disabling the new BSON
> record reder:
> {code:sql}
> ALTER SESSION SET store.mongo.bson.record.reader = false
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
