[
https://issues.apache.org/jira/browse/DRILL-7313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16877726#comment-16877726
]
ASF GitHub Bot commented on DRILL-7313:
---------------------------------------
arina-ielchiieva commented on pull request #1819: DRILL-7313: Use Hive schema
for MaprDB native reader when field was empty
URL: https://github.com/apache/drill/pull/1819#discussion_r299879561
##########
File path:
contrib/format-maprdb/src/main/java/org/apache/drill/exec/store/mapr/db/MapRDBSubScan.java
##########
@@ -57,34 +59,37 @@ public MapRDBSubScan(@JacksonInject StoragePluginRegistry
engineRegistry,
@JsonProperty("regionScanSpecList")
List<MapRDBSubScanSpec> regionScanSpecList,
@JsonProperty("columns") List<SchemaPath> columns,
@JsonProperty("maxRecordsToRead") int maxRecordsToRead,
- @JsonProperty("tableType") String tableType) throws
ExecutionSetupException {
+ @JsonProperty("tableType") String tableType,
+ @JsonProperty("schema") TupleSchema schema) throws
ExecutionSetupException {
Review comment:
Ideally we should use `TupleMetadata` instance not conrete implementation,
DRILL-7272 will add such support, could you please add todo with Jira number in
all places where `TupleSchema` is used so it could be easily tracked.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Use Hive schema for MaprDB native reader when field was empty
> -------------------------------------------------------------
>
> Key: DRILL-7313
> URL: https://issues.apache.org/jira/browse/DRILL-7313
> Project: Apache Drill
> Issue Type: Task
> Affects Versions: 1.16.0
> Reporter: Volodymyr Vysotskyi
> Assignee: Volodymyr Vysotskyi
> Priority: Major
> Fix For: 1.17.0
>
>
> Currently, when an external Hive MaprDB table is queried using hive plugin
> with enabled {{store.hive.maprdb_json.optimize_scan_with_native_reader}},
> some queries may fail due to soft schema change, though Hive knows actual
> data types.
> For example, when we have a table with several fields, and one of them has
> only several non-null values, queries with grouping by such field will fail
> due to schema change.
> The goal of this Jira is to allow using types from Hive when a non-existing
> field is created, so it will allow avoiding such issues.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
