jean-claude created DRILL-4278:
--
Summary: Memory leak when using LIMIT
Key: DRILL-4278
URL: https://issues.apache.org/jira/browse/DRILL-4278
Project: Apache Drill
Issue Type: Bug
Compo
GitHub user jacques-n opened a pull request:
https://github.com/apache/drill/pull/327
DRILL-4131: Move RPC allocators under Drill's root allocator & accounting
- Allow settings to be set to ensure RPC reservation and maximums
(currently unset by default). Defaults set in drill-modul
Github user hnfgns commented on the pull request:
https://github.com/apache/drill/pull/325#issuecomment-172126518
I took the API somewhat Drill internal but you are right about discussing
this in the public list first. This patch -as the numbers above check out- is
more of a clean-up
Github user hnfgns commented on a diff in the pull request:
https://github.com/apache/drill/pull/325#discussion_r49916936
--- Diff:
contrib/storage-mongo/src/main/java/org/apache/drill/exec/store/mongo/MongoGroupScan.java
---
@@ -180,39 +179,39 @@ private void init() throws IOExce
Github user asfgit closed the pull request at:
https://github.com/apache/drill/pull/319
---
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 jaltekruse commented on the pull request:
https://github.com/apache/drill/pull/326#issuecomment-172110734
+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 a
GitHub user jacques-n opened a pull request:
https://github.com/apache/drill/pull/326
DRILL-4277: Fix issue with JdbcPrel serialization
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jacques-n/drill DRILL-4277
Alternatively you
Github user jacques-n commented on the pull request:
https://github.com/apache/drill/pull/325#issuecomment-172106187
I don't think we should change the PStore API without some level of
discussion since it was designed as a public API. Can you share the driving
requirements that pushed
Github user jacques-n commented on a diff in the pull request:
https://github.com/apache/drill/pull/325#discussion_r49909762
--- Diff:
contrib/storage-mongo/src/main/java/org/apache/drill/exec/store/mongo/MongoGroupScan.java
---
@@ -180,39 +179,39 @@ private void init() throws IOE
Github user jacques-n commented on the pull request:
https://github.com/apache/drill/pull/319#issuecomment-172103488
Looks reasonable. +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
GitHub user hnfgns opened a pull request:
https://github.com/apache/drill/pull/325
DRILL-4275: Refactor e/pstore interfaces and their factories to provide a
unified mechanism to access stores
The main changes are the following:
Remove EStore and EStoreProvider interfaces.
Re
Jacques Nadeau created DRILL-4277:
-
Summary: Jdbc Storage Plugin doesn't correctly add metadata for
physical serialization
Key: DRILL-4277
URL: https://issues.apache.org/jira/browse/DRILL-4277
Project
Github user parthchandra commented on a diff in the pull request:
https://github.com/apache/drill/pull/323#discussion_r49890071
--- Diff:
exec/memory/base/src/main/java/org/apache/drill/exec/memory/AllocationManager.java
---
@@ -168,20 +213,26 @@ private BufferLedger(BaseAllocator
Github user parthchandra commented on the pull request:
https://github.com/apache/drill/pull/323#issuecomment-172053123
LGTM. +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
e
Victoria Markman created DRILL-4276:
---
Summary: Need a way to check on status of drillbits
Key: DRILL-4276
URL: https://issues.apache.org/jira/browse/DRILL-4276
Project: Apache Drill
Issue T
Github user adeneche commented on the pull request:
https://github.com/apache/drill/pull/322#issuecomment-172040219
According to the SQL specification you can have a FRAME clause with
FIRST_VALUE, LAST_VALUE or aggregate functions. Custom frame template will be
used for those function
Github user amansinha100 commented on the pull request:
https://github.com/apache/drill/pull/322#issuecomment-172038682
Overall refactoring looks ok. One thing that needs some clarity: Is the
definition of default frame 'between unbounded preceding and current row' ? If
the user exp
Hanifi Gunes created DRILL-4275:
---
Summary: Refactor e/pstore interfaces and their factories to
provide a unified mechanism to access stores
Key: DRILL-4275
URL: https://issues.apache.org/jira/browse/DRILL-4275
Github user krishahn commented on the pull request:
https://github.com/apache/drill/commit/84fe034e2644ce9164e1cee93843edd196f1c68b#commitcomment-15476398
In
_docs/develop-custom-functions/010-develop-custom-functions-introduction.md:
In
_docs/develop-custom-functions/010-develop
GitHub user acmeguy opened a pull request:
https://github.com/apache/drill/pull/324
Minor Reporting for Schema Changes
Hi,
Here is proposed improvement for error reporting for schema changes when
working with hash joins.
This is my first PR so please advise if this
Hi,
I would be more than happy to pay for this support if someone renders
professional services in this area and is willing to assist us in getting
this going.
What Drill reader/plugins currently support joins based on filters/indexes
that I can study?
Regards,
-Stefan
On Thu, Jan 14, 2016 a
21 matches
Mail list logo
