[GitHub] drill pull request #865: DRILL-5634 - Add Crypto and Hash Functions

Github user cgivre commented on a diff in the pull request: https://github.com/apache/drill/pull/865#discussion_r127132444 --- Diff: exec/java-exec/src/main/java/org/apache/drill/exec/expr/fn/impl/CryptoFunctions.java --- @@ -0,0 +1,389 @@ +/* + * Licensed to the Apache

[jira] [Created] (DRILL-5671) Set a secure ACL (Access Control List) for Drill ZK nodes in a secure cluster

Karthikeyan Manivannan created DRILL-5671: - Summary: Set a secure ACL (Access Control List) for Drill ZK nodes in a secure cluster Key: DRILL-5671 URL: https://issues.apache.org/jira/browse/DRILL-5671

[GitHub] drill pull request #874: DRILL-5663: Drillbit fails to start when only keyst...

GitHub user sindhurirayavaram opened a pull request: https://github.com/apache/drill/pull/874 DRILL-5663: Drillbit fails to start when only keystore path is provided without keystore password. When we configure keystore path without keystore password inside drill-override.conf for

Re: [DISCUSS] Drill 1.11.0 release

I withdraw my suggestion to fix DRILL-5660. Was a big hassle for us to track down the incompatibility the issue internally, but production users probably don’t attempt to use one build of Drill with metadata files created from another. We can worry about the issue later only if a user actually

Re: [DISCUSS] Drill 1.11.0 release

Upgrade from 1.10 to 1.11 is irreversible only when parquet metadata cache file is involved. I might be wrong, but I thought that if someone is running on 1.10.0, and he wants to go back to 1.0.0, where the first version of parquet meatadata cache was introduced, can we guarantee that Drillbit

Re: [DISCUSS] Drill 1.11.0 release

If we don’t do DRILL-5660 for 1.11 then we don’t need to do it at all, so that is a time savings. We could handle this via a release note item that simply states that an upgrade from 1.10 to 1.11 is irreversible: we do not support the ability to fall back to the old version. Everyone OK with

[jira] [Created] (DRILL-5670) Varchar vector throws an assertion error when allocation a new verctor

Rahul Challapalli created DRILL-5670: Summary: Varchar vector throws an assertion error when allocation a new verctor Key: DRILL-5670 URL: https://issues.apache.org/jira/browse/DRILL-5670

[jira] [Created] (DRILL-5669) Multiple TPCH queries failed due to OOM

Dechang Gu created DRILL-5669: - Summary: Multiple TPCH queries failed due to OOM Key: DRILL-5669 URL: https://issues.apache.org/jira/browse/DRILL-5669 Project: Apache Drill Issue Type: Bug

Re: [DISCUSS] Drill 1.11.0 release

I put some analysis in DRILL-5468. Also, IMHO, DRILL-5660 is not a release blocker. On Tue, Jul 11, 2017 at 11:27 AM, Parth Chandra wrote: > Re DRILL-5634: > From the Apache commons web page [1] - > > Please note that Apache Commons Crypto doesn't implement the

[GitHub] drill pull request #873: DRILL-5668: Fix C++ connector crash on error

Github user asfgit closed the pull request at: https://github.com/apache/drill/pull/873 --- 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

[GitHub] drill issue #873: DRILL-5668: Fix C++ connector crash on error

Github user parthchandra commented on the issue: https://github.com/apache/drill/pull/873 +1. LGTM. --- 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

[GitHub] drill pull request #865: DRILL-5634 - Add Crypto and Hash Functions

Github user arina-ielchiieva commented on a diff in the pull request: https://github.com/apache/drill/pull/865#discussion_r127004765 --- Diff: exec/java-exec/src/main/java/org/apache/drill/exec/expr/fn/impl/CryptoFunctions.java --- @@ -0,0 +1,389 @@ +/* + * Licensed to

[GitHub] drill issue #873: DRILL-5668: Fix C++ connector crash on error

Github user laurentgo commented on the issue: https://github.com/apache/drill/pull/873 @parthchandra @sudheeshkatkam look good to you? --- 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