[GitHub] sohami commented on issue #1459: DRILL-6731: Move the BFs aggregating work from the Foreman to the RuntimeFi…

sohami commented on issue #1459: DRILL-6731: Move the BFs aggregating work from the Foreman to the RuntimeFi… URL: https://github.com/apache/drill/pull/1459#issuecomment-426521845 @weijietong - Thanks! I ran the pre-commit tests and few JPPD tests are failing due to some issues related to

Re: Possible way to specify column types in query

I made some progress. I looked at the parquet format plugin because it looked the closest to what I want to do. I thus now have a custom BasicFormatMatcher which overrides isReadable(). IsReadable() returns a DrillTable which hard codes a schema for now. If I select a column not in the hard coded

Re: Possible way to specify column types in query

The Drill table looks like the way to integrate schema into the planner. As you noted, pcap is hardcoded. You'd want to load your schema from a file. Because pcap is hard coded, that planner does not need to pass the schema to the reader, but you would need to do so to know the type of missing c

[jira] [Created] (DRILL-6767) Simplify transfer of information from the planner to the operators

Boaz Ben-Zvi created DRILL-6767: --- Summary: Simplify transfer of information from the planner to the operators Key: DRILL-6767 URL: https://issues.apache.org/jira/browse/DRILL-6767 Project: Apache Drill

Re: Possible way to specify column types in query

I've been looking at the pcap reader https://github.com/apache/drill/tree/master/exec/java-exec/src/main/java/org/apache/drill/exec/store/pcap it has a simple PcapDrillTable (hard coded). I though of using it as inspiration but I wonder if the way it is implemented would the DESCRIBE functionality

[GitHub] Agirish commented on issue #1307: DRILL-6473: Update MapR Hive, MapR release version and ojai version

Agirish commented on issue #1307: DRILL-6473: Update MapR Hive, MapR release version and ojai version URL: https://github.com/apache/drill/pull/1307#issuecomment-426476958 @KazydubB, can we get this in soon? This is an autom

[GitHub] Agirish commented on a change in pull request #1307: DRILL-6473: Update MapR Hive, MapR release version and ojai version

Agirish commented on a change in pull request #1307: DRILL-6473: Update MapR Hive, MapR release version and ojai version URL: https://github.com/apache/drill/pull/1307#discussion_r222154373 ## File path: pom.xml ## @@ -2439,7 +2439,7 @@ mapr true

[GitHub] Agirish commented on a change in pull request #1307: DRILL-6473: Update MapR Hive, MapR release version and ojai version

Agirish commented on a change in pull request #1307: DRILL-6473: Update MapR Hive, MapR release version and ojai version URL: https://github.com/apache/drill/pull/1307#discussion_r222154293 ## File path: pom.xml ## @@ -2439,7 +2439,7 @@ mapr true

[GitHub] Agirish commented on a change in pull request #1307: DRILL-6473: Update MapR Hive, MapR release version and ojai version

Agirish commented on a change in pull request #1307: DRILL-6473: Update MapR Hive, MapR release version and ojai version URL: https://github.com/apache/drill/pull/1307#discussion_r222154231 ## File path: pom.xml ## @@ -2439,7 +2439,7 @@ mapr true

[GitHub] Agirish commented on a change in pull request #1307: DRILL-6473: Update MapR Hive, MapR release version and ojai version

Agirish commented on a change in pull request #1307: DRILL-6473: Update MapR Hive, MapR release version and ojai version URL: https://github.com/apache/drill/pull/1307#discussion_r222154084 ## File path: pom.xml ## @@ -53,8 +53,8 @@ 2.9.5 2.9.5 3.4.12 -5

[GitHub] Agirish commented on a change in pull request #1307: DRILL-6473: Update MapR Hive, MapR release version and ojai version

Agirish commented on a change in pull request #1307: DRILL-6473: Update MapR Hive, MapR release version and ojai version URL: https://github.com/apache/drill/pull/1307#discussion_r222153910 ## File path: pom.xml ## @@ -53,8 +53,8 @@ 2.9.5 2.9.5 3.4.12 -5

Re: Possible way to specify column types in query

Hi JC, Now that you have a working reader, sounds like your next task is to pass column schema to the reader. There are two ways to do that. There are sketchy examples of both. First, the reader itself can obtain the schema (as is done in Parquet.) Second, the planner can pass the schema to the

[GitHub] arina-ielchiieva opened a new pull request #1485: DRILL-6759: Make columns array name for csv data case insensitive

arina-ielchiieva opened a new pull request #1485: DRILL-6759: Make columns array name for csv data case insensitive URL: https://github.com/apache/drill/pull/1485 Details in [DRILL-6759](https://issues.apache.org/jira/browse/DRILL-6759).

[GitHub] weijietong commented on issue #1459: DRILL-6731: Move the BFs aggregating work from the Foreman to the RuntimeFi…

weijietong commented on issue #1459: DRILL-6731: Move the BFs aggregating work from the Foreman to the RuntimeFi… URL: https://github.com/apache/drill/pull/1459#issuecomment-426259756 @sohami done, really appreciate the effort you made. -