As I understand, the current algorithm is next:
to use any function in drill we must find the best match for this function
via get cast rules and precedence map.
To implement count function for complex datatypes we just need availability
of map and list in precedenceMap and cast rules.
Kind regard
Alexey Minakov created DRILL-4705:
-
Summary: Simple TSV file with quotes causes read error
Key: DRILL-4705
URL: https://issues.apache.org/jira/browse/DRILL-4705
Project: Apache Drill
Issue Ty
Kunal Khatua created DRILL-4706:
---
Summary: Fragment planning causes Drillbits to read remote chunks
when local copies are available
Key: DRILL-4706
URL: https://issues.apache.org/jira/browse/DRILL-4706
Jinfeng Ni created DRILL-4707:
-
Summary: Conflicting columns names under case-insensitive policy
lead to either memory leak or incorrect result
Key: DRILL-4707
URL: https://issues.apache.org/jira/browse/DRILL-4707
Chun Chang created DRILL-4708:
-
Summary: connection closed unexpectedly
Key: DRILL-4708
URL: https://issues.apache.org/jira/browse/DRILL-4708
Project: Apache Drill
Issue Type: Bug
Compo
GitHub user parthchandra opened a pull request:
https://github.com/apache/drill/pull/513
DRILL-4607: - Fix unittest failure. Janino cannot compile a function â¦
â¦that uses generics; so replaced the implementation of
StringFunctions.Split to not use any.
You can merge this pull r
Github user sudheeshkatkam commented on the issue:
https://github.com/apache/drill/pull/513
+1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the fe
Github user asfgit closed the pull request at:
https://github.com/apache/drill/pull/513
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
GitHub user parthchandra opened a pull request:
https://github.com/apache/drill/pull/514
DRILL-4694: CTAS in JSON format produces extraneous NULL fields
Changed behavior of JSON CTAS to skip fields if the value is null. Added
an option "store.json.writer.skip_null_fields" to enab
Github user amansinha100 commented on a diff in the pull request:
https://github.com/apache/drill/pull/514#discussion_r65795019
--- Diff:
exec/java-exec/src/main/codegen/templates/JsonOutputRecordWriter.java ---
@@ -61,7 +62,13 @@
@Override
public void start
Github user amansinha100 commented on a diff in the pull request:
https://github.com/apache/drill/pull/514#discussion_r65795030
--- Diff:
exec/java-exec/src/main/codegen/templates/JsonOutputRecordWriter.java ---
@@ -120,7 +127,13 @@ public void writeField() throws IOException {
Github user amansinha100 commented on a diff in the pull request:
https://github.com/apache/drill/pull/514#discussion_r65795093
--- Diff: exec/java-exec/src/test/resources/json/ctas_alltypes_map_out.json
---
@@ -0,0 +1,41 @@
+{
--- End diff --
minor point: in TestJ
Github user amansinha100 commented on a diff in the pull request:
https://github.com/apache/drill/pull/514#discussion_r65795257
--- Diff: exec/java-exec/src/test/java/org/apache/drill/TestCTASJson.java
---
@@ -0,0 +1,129 @@
+/**
+ * Licensed to the Apache Software Foundatio
13 matches
Mail list logo
