Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Sun, 24 Jan 2016 17:03:39 +0000 (UTC)
From: "Michael Gokhman (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12933661.1453629496000.195318.1453655019915@Atlassian.JIRA>
In-Reply-To: <JIRA.12933661.1453629496000@Atlassian.JIRA>
References: <JIRA.12933661.1453629496000@Atlassian.JIRA>
 <JIRA.12933661.1453629496548@arcas>
Subject: [jira] [Commented] (DRILL-4307) new MongoDB BSON record reader
 breaks _id SELECT-ion
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/DRILL-4307?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1511=
4380#comment-15114380 ]=20

Michael Gokhman commented on DRILL-4307:
----------------------------------------

ok thanks, I indeed managed to select using:

{code}
SELECT * from mongo.db.collection WHERE _id=3DBINARY_STRING('V)x\x84H0\x8F\=
x11\x94\x11\x1Eq') limit 1;
{code}

And I also see that the binary value is a hex-decoding of the original $oid=
. in python:
{code}
'V)x\x84H0\x8F\x11\x94\x11\x1Eq'.encode('hex') =3D '5629788448308f1194111e7=
1'
{code}

I think it will be much more intuitive if instead of the pointer-thing, the=
 SELECT will simply return the original $oid string, i.e.=20
"5629788448308f1194111e71" in the case above (as returned by mongo cli)

Thanks


> 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"}=20
> {code}
> as expected.
> however, when working with the master branch, SELECT-ing an _id results i=
n a something that looks like a pointer:
> {code}
> [B@3149a=E2=80=A6]
> {code}
> This is caused by DRILL-3478, and can be avoided by disabling the new BSO=
N record reder:
> {code:sql}
> ALTER SESSION SET store.mongo.bson.record.reader =3D false
> {code}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)