Oscar Morante created DRILL-4869:
Summary: Some queries sent via JDBC get executed twice.
Key: DRILL-4869
URL: https://issues.apache.org/jira/browse/DRILL-4869
Project: Apache Drill
Issue Typ
Krystal, Sékine, thanks for your help. Pease find more informations :
*$dpkg -s unixodbc*
Package: unixodbc
Status: install ok installed
Priority: optional
Section: database
Installed-Size: 111
Maintainer: Ubuntu Developers
Architecture: amd64
Multi-Arch: foreign
Version: 2.2.14p2-5ubuntu5
Depend
Github user jcmcote commented on the issue:
https://github.com/apache/drill/pull/573
Please review
---
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 th
On behalf of the Apache Drill community, I am happy to announce the
release of Apache Drill 1.8.0.
This release of Drill fixes 47 JIRA issues and introduces a number of
enhancements, including metadata cache pruning, DESCRIBE SCHEMA
command, multi-byte delimiter support, and launch script changes.
Paul Rogers created DRILL-4870:
--
Summary: drill-config.sh sets JAVA_HOME incorrectly for the Mac
Key: DRILL-4870
URL: https://issues.apache.org/jira/browse/DRILL-4870
Project: Apache Drill
Issue
Congratulations everyone!
On Wed, Aug 31, 2016 at 10:33 AM, Jinfeng Ni wrote:
> On behalf of the Apache Drill community, I am happy to announce the
> release of Apache Drill 1.8.0.
>
> This release of Drill fixes 47 JIRA issues and introduces a number of
> enhancements, including metadata cache
GitHub user sudheeshkatkam opened a pull request:
https://github.com/apache/drill/pull/578
DRILL-4280: Kerberos Authentication
I am posting these changes from review. There are four commits in this pull
request. All changes squashed are in [this
branch](https://github.com/sudheeshk
Chun Chang created DRILL-4871:
-
Summary: random JsonParseException: Illegal character ((CTRL-CHAR,
code 0)): only regular white space (\r, \n, \t) is allowed between tokens
Key: DRILL-4871
URL: https://issues.apache.o
Should be confirmed but yes, dDrillExplorer most likely makes use of iodbc
only and not unixODBC.
Regarding the unixODBC stuff, my guess is that libodbcinst.so is not in
your LD_LIBRARY_PATH. But you most likely have libodbcinst.so.1.
So, please give it a try changing your .mapr.drillodbc.ini :
#
Github user parthchandra commented on the issue:
https://github.com/apache/drill/pull/567
Per my understanding User Exception was meant for errors on the server side
that are to bet sent back to the user. Are you extending that definition?
---
If your project is set up for it, you ca
Github user jacques-n commented on the issue:
https://github.com/apache/drill/pull/567
This also breaks client/wire compatibility. In previous discussions, we
said that we would avoid breaking compatibility. If you proceed with this,
you'll need to add a compatibility layer in the ser
Github user sudheeshkatkam commented on the issue:
https://github.com/apache/drill/pull/567
Per [Hakkim's
comment](https://github.com/apache/drill/pull/460/files#diff-158c887d198393117d3a1bbc42114a8bR344),
SYSTEM type is meant for unexpected errors that do not have a "nice" error
mes
Github user jacques-n commented on the issue:
https://github.com/apache/drill/pull/567
It seems error-prone/dangerous to change the wire protocol for something
that will never be sent on the wire.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user sudheeshkatkam commented on the issue:
https://github.com/apache/drill/pull/567
For now, I am not sure how else to fix this; will punt until compatibility
later is introduced.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user jacques-n commented on the issue:
https://github.com/apache/drill/pull/567
Since it is all on the client/in the same jvm, why not just throw an
exception and catch it? No need to jump through all the hoops that
UserException goes through since you're never trying to propag
Can someone help or point me to where I can maybe get some help?
I am trying to figure out why I am getting a ClassCastException when I do the
following query. If I change the "FROM" clause to just "FROM (VALUES(0))" it
works just fine, but whenever I have "FROM" to an HBase table, I get the er
Github user sudheeshkatkam commented on the issue:
https://github.com/apache/drill/pull/567
I am confused here. The patch enhances the catch clauses of thrown
exceptions and, in a way, "corrects" what was being reported to the user as a
SYSTEM (server) error to CLIENT error since thes
17 matches
Mail list logo
