[GitHub] drill pull request #918: Drill-5734: exclude commons-codes dependency confli...

Github user weijietong closed the pull request at: https://github.com/apache/drill/pull/918 --- 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 #917: Drill-5734: exclude the conflicted dependency commons-code...

Github user paul-rogers commented on the issue: https://github.com/apache/drill/pull/917 Same as #903? --- 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

Re: Discuss about Drill's schedule policy

Hi Weijie, Great analysis. Let’s look at a few more data points. Drill has no central scheduler (this is a feature: it makes the cluster much easier to manage and has no single point of failure. It was probably the easiest possible solution while Drill was being built.) Instead of central

Re: Discuss about Drill's schedule policy

If control RPC is down to a drillbit i.e if a drillbit is not responding, zookeeper should detect that and notify other drillbits to remove the dead drillbit from their active list. Once that happens, the next query that comes in should not even see that drillbit. We need a way to differentiate

Discuss about Drill's schedule policy

HI all: Drill's current schedule policy seems a little simple. The SimpleParallelizer assigns endpoints in round robin model which ignores the system's load and other factors. To critical scenario, some drillbits are suffering frequent full GCs which will let their control RPC blocked. Current

[GitHub] drill issue #889: DRILL-5691: enhance scalar sub queries checking for the ca...

Github user weijietong commented on the issue: https://github.com/apache/drill/pull/889 @arina-ielchiieva other tests have passed separately and time zone related test cases have been corrected in PR 5717 --- If your project is set up for it, you can reply to this email and have

[GitHub] drill pull request #918: Drill-5734: exclude commons-codes dependency confli...

GitHub user weijietong opened a pull request: https://github.com/apache/drill/pull/918 Drill-5734: exclude commons-codes dependency confliction exclude commons-codes from pom files: contrib/format-maprdb/pom.xml , contrib/storage-hive/hive-exec-shade/pom.xml You can merge this

[GitHub] drill pull request #917: Drill-5734: exclude the conflicted dependency commo...

Github user weijietong closed the pull request at: https://github.com/apache/drill/pull/917 --- 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 pull request #917: Drill-5734: exclude the conflicted dependency commo...

GitHub user weijietong opened a pull request: https://github.com/apache/drill/pull/917 Drill-5734: exclude the conflicted dependency commons-codec exclude commons-codes from pom files: contrib/format-maprdb/pom.xml , contrib/storage-hive/hive-exec-shade/pom.xml You can merge this

[GitHub] drill issue #904: DRILL-5717: let some date time test cases be Local indepen...

Github user weijietong commented on the issue: https://github.com/apache/drill/pull/904 @vvysotskyi sorry for the late update as have passed a busy week. update points: * move out the pom update * recover the date related templates and update the related test cases by

[jira] [Created] (DRILL-5734) exclude commons-codec dependency conflict

weijie.tong created DRILL-5734: -- Summary: exclude commons-codec dependency conflict Key: DRILL-5734 URL: https://issues.apache.org/jira/browse/DRILL-5734 Project: Apache Drill Issue Type: Bug