Github user sudheeshkatkam commented on the issue:
https://github.com/apache/drill/pull/769
Built, and sanity tested using querySubmitter test application.
---
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 d
Github user sudheeshkatkam commented on the issue:
https://github.com/apache/drill/pull/769
+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 fe
Github user sudheeshkatkam commented on the issue:
https://github.com/apache/drill/pull/770
+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 fe
Looks like the C++ client is not able to built successfully [1], after
the change of DRILL-5301 / DRILL-5167.
This seems to be a blocking issue for 1.10.0, and I'll merge the patch
once it's verified/reviewed.
1. https://issues.apache.org/jira/browse/DRILL-5313
On Thu, Mar 2, 2017 at 5:37 PM, Ji
GitHub user laurentgo opened a pull request:
https://github.com/apache/drill/pull/770
DRILL-5311: Check handshake result in C++ connector
In C++ client connector, DrillClientImpl::recvHandshake always
return success, even in case of connection error (like a tcp
timeout issue)
Github user sohami commented on the issue:
https://github.com/apache/drill/pull/768
Thanks for the actual fix. I will close this pull request.
---
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
GitHub user laurentgo opened a pull request:
https://github.com/apache/drill/pull/769
DRILL-5313: Fix compilation issue in C++ connector
DRILL-5301 and DRILL-5167 have conflicting changes, which causes
the C++ connector to not compile: the static symbol for the search
escape
Github user laurentgo commented on a diff in the pull request:
https://github.com/apache/drill/pull/768#discussion_r104085400
--- Diff: contrib/native/client/src/clientlib/drillClientImpl.cpp ---
@@ -662,8 +662,9 @@ DrillClientQueryResult*
DrillClientImpl::ExecuteQuery(const Prepar
GitHub user sohami opened a pull request:
https://github.com/apache/drill/pull/768
DRILL-5313: Fix build failure in C++ client
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sohami/drill DRILL-5313
Alternatively you can review
Sorabh Hamirwasia created DRILL-5313:
Summary: C++ client build failure on linux
Key: DRILL-5313
URL: https://issues.apache.org/jira/browse/DRILL-5313
Project: Apache Drill
Issue Type: Bu
I missed 5208, because it did not show up in Paul's list when he replied to
this thread.
On Thu, Mar 2, 2017 at 2:58 PM Zelaine Fong wrote:
> Jinfeng,
>
> I notice the following Jira has the ready-to-commit label but isn’t on
> your list:
>
> DRILL-5208
>
> Was this one overlooked?
>
> -- Zelain
GitHub user paul-rogers opened a pull request:
https://github.com/apache/drill/pull/767
DRILL-5226: Managed external sort fixes
* Memory leak in managed sort if OOM during sv2 allocation
* "Record batch sizer" does not include overhead for variable-sized
vectors
* Paranoi
[
https://issues.apache.org/jira/browse/DRILL-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Rogers resolved DRILL-4301.
Resolution: Fixed
Fix Version/s: 1.10.0
> OOM : Unable to allocate sv2 for 1000 records, and
[
https://issues.apache.org/jira/browse/DRILL-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Rogers resolved DRILL-5294.
Resolution: Fixed
> Managed External Sort throws an OOM during the merge and spill phase
> -
[
https://issues.apache.org/jira/browse/DRILL-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Rogers resolved DRILL-5210.
Resolution: Fixed
Fix Version/s: 1.10.0
> External Sort BatchGroup leaks memory if an OOM occ
[
https://issues.apache.org/jira/browse/DRILL-5262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Rogers resolved DRILL-5262.
Resolution: Fixed
> NPE in managed external sort while spilling to disk
> --
[
https://issues.apache.org/jira/browse/DRILL-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Rogers resolved DRILL-5062.
Resolution: Fixed
> External sort refers to the deprecated HDFS fs.default.name param
>
[
https://issues.apache.org/jira/browse/DRILL-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Rogers resolved DRILL-5264.
Resolution: Fixed
> Managed External Sort fails with OOM
>
>
>
[
https://issues.apache.org/jira/browse/DRILL-5017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Rogers resolved DRILL-5017.
Resolution: Fixed
> Config param drill.exec.sort.external.batch.size is not used
> -
[
https://issues.apache.org/jira/browse/DRILL-5285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Rogers resolved DRILL-5285.
Resolution: Fixed
> Provide detailed, accurate estimate of size consumed by a record batch
> ---
[
https://issues.apache.org/jira/browse/DRILL-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Rogers resolved DRILL-5267.
Resolution: Fixed
Fix Version/s: (was: 1.10)
1.10.0
> Managed external
Paul Rogers created DRILL-5312:
--
Summary: "Record batch sizer" does not include overhead for
variable-sized vectors
Key: DRILL-5312
URL: https://issues.apache.org/jira/browse/DRILL-5312
Project: Apache D
Jinfeng,
I notice the following Jira has the ready-to-commit label but isn’t on your
list:
DRILL-5208
Was this one overlooked?
-- Zelaine
On 3/2/17, 1:04 PM, "Jinfeng Ni" wrote:
The following PRs have been merged to Apache master.
DRILL-4994
DRILL-4730
DRILL-5301
D
Github user StevenMPhillips commented on the issue:
https://github.com/apache/drill/pull/456
There was a brief discussion on the drill-dev mailing list a few days after
this PR was posted. Unfortunately the discussion did not culminate in any
decision. The discussion was mainly around
[
https://issues.apache.org/jira/browse/DRILL-5290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zelaine Fong resolved DRILL-5290.
-
Resolution: Fixed
> Provide an option to build operator table once for built-in static functions
[
https://issues.apache.org/jira/browse/DRILL-5287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zelaine Fong resolved DRILL-5287.
-
Resolution: Fixed
> Provide option to skip updates of ephemeral state changes in Zookeeper
> -
[
https://issues.apache.org/jira/browse/DRILL-5252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zelaine Fong resolved DRILL-5252.
-
Resolution: Fixed
Fix Version/s: 1.10.0
> A condition returns always true
> ---
Laurent Goujon created DRILL-5311:
-
Summary: C++ connector connect doesn't wait for handshake to
complete
Key: DRILL-5311
URL: https://issues.apache.org/jira/browse/DRILL-5311
Project: Apache Drill
Paul Rogers created DRILL-5310:
--
Summary: Memory leak in managed sort if OOM during sv2 allocation
Key: DRILL-5310
URL: https://issues.apache.org/jira/browse/DRILL-5310
Project: Apache Drill
Iss
The following PRs have been merged to Apache master.
DRILL-4994
DRILL-4730
DRILL-5301
DRILL-5167
DRILL-5221
DRILL-5258
DRILL-5034
DRILL-4963
DRILL-5252
DRILL-5266
DRILL-5284
DRILL-5304
DRILL-5290
DRILL-5287
QA folks will run tests. If no issue found, I'll build a RC0 candidate
for 1.10 and start
Github user asfgit closed the pull request at:
https://github.com/apache/drill/pull/752
---
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/701
---
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/766
---
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/712
---
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/761
---
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/749
---
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/745
---
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/733
---
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/758
---
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/656
---
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/764
---
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/613
---
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/757
---
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 paul-rogers commented on the issue:
https://github.com/apache/drill/pull/701
@jinfengni ,
As it turns out, we do have a comprehensive design for the original feature
and the MVCC revision. The key goals are that a function, once registered, is
guaranteed to be av
I'm building a merge branch, and hopefully push to master branch today
if things go smoothly.
On Wed, Mar 1, 2017 at 7:13 PM, Padma Penumarthy wrote:
> Hi Jinfeng,
>
> Please include DRILL-5287, DRILL-5290 and DRILL-5304.
>
> Thanks,
> Padma
>
>
>> On Feb 22, 2017, at 11:16 PM, Jinfeng Ni wrote
Github user ko3ak commented on the issue:
https://github.com/apache/drill/pull/456
Any idea when this pull request will be implemented in mainstream release
1.10?
---
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 p
Github user jinfengni commented on the issue:
https://github.com/apache/drill/pull/701
@arina-ielchiieva ,
Regarding your 3rd comment, we probably can discuss further once you have
the design. I would think we may process "refresh function registry" command as
a query (or mor
Nikolaos Tsipas created DRILL-5309:
--
Summary: Error: Protocol message was too large. May be malicious.
Key: DRILL-5309
URL: https://issues.apache.org/jira/browse/DRILL-5309
Project: Apache Drill
Hi Jinfeng,
Please include DRILL-5287, DRILL-5290 and DRILL-5304.
Thanks,
Padma
> On Feb 22, 2017, at 11:16 PM, Jinfeng Ni wrote:
>
> Hi Drillers,
>
> It has been almost 3 months since we release Drill 1.9. We have
> resolved plenty of fixes and improvements (closed around 88 JIRAs
> [1]). I
Github user arina-ielchiieva commented on the issue:
https://github.com/apache/drill/pull/701
@jinfengni
1. Depending on how often udfs are added, we don't expect it to happen
often though. But you are correct about the overhead for the queries that do
not use dynamic UDFs.
50 matches
Mail list logo
