You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Paul Rogers (JIRA)" <ji...@apache.org> on 2018/05/08 22:05:00 UTC
[jira] [Commented] (DRILL-6390) UnsupportedOperationException:
Unable to get holder type for minor type [LATE] and mode [OPTIONAL]
[ https://issues.apache.org/jira/browse/DRILL-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16468023#comment-16468023 ]
Paul Rogers commented on DRILL-6390:
------------------------------------
This is, unfortunately, a known limitation of Drill's JSON support. If your fields were at the top level, you could work around this by using a CAST. But, the trick does not work in nested structures (without also re-projecting the column to the top level.) There is another ticket open with the gory details.
> UnsupportedOperationException: Unable to get holder type for minor type [LATE] and mode [OPTIONAL]
> --------------------------------------------------------------------------------------------------
>
> Key: DRILL-6390
> URL: https://issues.apache.org/jira/browse/DRILL-6390
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Data Types, Storage - JSON
> Affects Versions: 1.11.0
> Reporter: Trung Ta
> Priority: Major
>
> I tried this query on some of our JSON files that are stored in a S3 Bucket, in which I tried to convert JSON objects (application, application_fee) into varchar:
> {code:java}
> SELECT
> CONCAT(
> '"', CONVERT_TO(_stg.data.application_fee, 'JSON'), '"'
> , ',', '"', CONVERT_TO(_stg.data.application_fee, 'JSON'), '"'
> ) as JSONs
> FROM (
> SELECT
> flatten(js.data) AS data
> FROM
> s3_bucket.`<PATH_TO_FILE_IN_S3>` AS js
> ) _stg
> {code}
> On some of the datasets the query failed and I got this error message
> {quote}org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR: UnsupportedOperationException: Unable to get holder type for minor type [LATE] and mode [OPTIONAL] Fragment 0:0 [Error Id: 5e74e125-de22-46fa-8d31-233d0fc40140
> {quote}
> The dataset, on which the query failed looks like following:
> {code:java}
> {
> "data":
> [
> {
> "application": null,
> "application_fee": null,
> "amount": 1
> },
> {
> "application":
> {
> "id": "some_id",
> "name": "Some App",
> "object": "application"
> },
> "application_fee": null,
> "amount": 5
> }
> ],
> "has_more": false,
> "object": "list",
> "url": "/v1/charges"
> }
> {code}
> I ran some further tests on the query and found out that the query only fails at object "application_fee", which is null in both arrays of object "data". Which might explain why I never ran into this error in the other datasets (no object arrays there are null).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)