Khurram Faraaz created DRILL-4941:
-
Summary: UnsupportedOperationException : CASE WHEN true or null
then 1 else 0 end
Key: DRILL-4941
URL: https://issues.apache.org/jira/browse/DRILL-4941
Project: Apa
GitHub user arina-ielchiieva opened a pull request:
https://github.com/apache/drill/pull/610
DRILL-4674: Allow casting to boolean the same literals as in Postgre
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/arina-ielchiieva/dr
Khurram Faraaz created DRILL-4942:
-
Summary: incorrect result - case when (not null is null) then
true else false end
Key: DRILL-4942
URL: https://issues.apache.org/jira/browse/DRILL-4942
Project: Ap
Github user asfgit closed the pull request at:
https://github.com/apache/drill/pull/603
---
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
Hi Drill devs,
Since I recently worked on a bug fix for which I need to test with a query
and that query triggered a mysterious error:
org.objectweb.asm.tree.analysis.AnalyzerException: Expected an object
reference, but found .
The error stack was printed during drillbit running, meanwhile correc
Khurram Faraaz created DRILL-4943:
-
Summary: need better error message - DrillRuntimeException:
Failure while materializing expression in constant expression evaluator
Key: DRILL-4943
URL: https://issues.apache.o
Github user vkorukanti commented on a diff in the pull request:
https://github.com/apache/drill/pull/395#discussion_r83089376
--- Diff: exec/jdbc/pom.xml ---
@@ -21,9 +21,9 @@
- net.hydromatic
- optiq-avatica
- 0.9-drill-r20
+
GitHub user parthchandra opened a pull request:
https://github.com/apache/drill/pull/611
Drill-4800: Improve parquet reader performance
Added a Buffering input stream
Updated parquet reader to optionally use the buffering input stream
Added optional asynchronous reading of pa
Github user vkorukanti commented on the issue:
https://github.com/apache/drill/pull/596
+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 featur
Github user asfgit closed the pull request at:
https://github.com/apache/drill/pull/395
---
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 asfgit closed the pull request at:
https://github.com/apache/drill/pull/596
---
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
[
https://issues.apache.org/jira/browse/DRILL-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venki Korukanti resolved DRILL-4452.
Resolution: Fixed
Fix Version/s: 1.9.0
Fixed in
[a888ce6|https://github.com/apache/d
[
https://issues.apache.org/jira/browse/DRILL-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venki Korukanti resolved DRILL-4880.
Resolution: Fixed
Fixed in
[09abcc3|https://github.com/apache/drill/commit/09abcc32cc9d6e3d
GitHub user laurentgo opened a pull request:
https://github.com/apache/drill/pull/612
DRILL-4925: Add tableType filter to GetTables metadata query
- Adding tableType filter to GetTablesReq query (needed for JDBC and ODBC
drivers).
- Fix table type returned by sys and INFORMAT
GitHub user laurentgo opened a pull request:
https://github.com/apache/drill/pull/613
DRILL-4730: Update JDBC DatabaseMetaData implementation to use new Metadata
APIs
Update JDBC driver to use Metadata APIs instead of executing SQL queries
You can merge this pull request into a Git
GitHub user laurentgo opened a pull request:
https://github.com/apache/drill/pull/614
DRILL-4930: Fix Metadata results ordering
Change MetadataProvider to return metadata results ordered (following
convention used by ODBC and JDBC specs).
You can merge this pull request into a G
Github user vkorukanti commented on a diff in the pull request:
https://github.com/apache/drill/pull/612#discussion_r83124391
--- Diff:
exec/java-exec/src/main/java/org/apache/drill/exec/work/metadata/MetadataProvider.java
---
@@ -347,9 +351,9 @@ protected Response runInternal(fin
Github user vkorukanti commented on the issue:
https://github.com/apache/drill/pull/614
+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 featur
Hi,
We finally got rid of this error. We have tried many, many things (like
modifying drill to ignore the error!), it ultimately came down to this
change:
from default
planner.affinity_factor=1.2
to
planner.affinity_factor=100
Basically this encourages fragment to only care about locally s
Github user parthchandra commented on the issue:
https://github.com/apache/drill/pull/602
@laurentgo I have been trying, unsuccessfully, to build on Windows and Mac.
Is there a cppunit build available for Windows? I am unable to get past that
and my effort to build cppunit from source
GitHub user lvxin1986 opened a pull request:
https://github.com/apache/drill/pull/615
Update 035-plugin-configuration-basics.md
Fix the errors in the content
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lvxin1986/drill patch-2
Github user laurentgo commented on the issue:
https://github.com/apache/drill/pull/602
I have built it successfully on Mac and Linux (centos 5). On Mac, I used
homebrew to install cppunit locally on Mac, but I didn't try to build it from
source. You can send me your output, and I will
Github user cgivre commented on the issue:
https://github.com/apache/drill/pull/607
@chunhui-shi
I've actually been thinking about writing a generic log parser for Drill in
which the user would provide a regex with groups and a list of fields. For
instance consider the following
23 matches
Mail list logo