[
https://issues.apache.org/jira/browse/DRILL-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bhallamudi Venkata Siva Kamesh updated DRILL-2879:
--------------------------------------------------
Attachment: DRILL-2879_1.patch
Hi Jacques,
Thanks for the detailed explanation.
Basically I wanted like to add support to parse $oid. From the documentation
of Mongo, $oid is represented as hexadecimal string and hence I tried to write
it to VarChar. As you mentioned above, not parsing $oid. But any suggestions to
represent this
As of now, value of $date is assumed to be in string representation. But if
$date is represented in long (Mongo strict mode) it fails to parse it and hence
I extended it support parsing even when it is represented in long. But I think,
while exporting from drill, it is exported in string representation.
While storing $binary in mongo, it stores $type as well. Current behaviour of
$binary (only parses $binary) fails to parse it. So, added support for parsing
binary data, which has type info (Mongo extended Json in strict json mode).
Also, without this patch, queries on Mongo will fail when the collection
contains $binary (which has $type) field.
This patch keeps the default behaviour as it is, however, enhances to parse
$binary and $date.
Go through the attach patch provide any comments
> Drill extended json's support $oid
> ----------------------------------
>
> Key: DRILL-2879
> URL: https://issues.apache.org/jira/browse/DRILL-2879
> Project: Apache Drill
> Issue Type: Improvement
> Components: Storage - JSON
> Reporter: Bhallamudi Venkata Siva Kamesh
> Assignee: Steven Phillips
> Attachments: DRILL-2879_1.patch, extended.json, extendedjson.patch
>
>
> Enhancing JSON reader to parse $oid (from mongo).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
