Boaz Ben-Zvi created DRILL-6479:
---
Summary: Support for EMIT outcome in Hash Aggregate
Key: DRILL-6479
URL: https://issues.apache.org/jira/browse/DRILL-6479
Project: Apache Drill
Issue Type:
Padma Penumarthy created DRILL-6478:
---
Summary: enhance debug logs for batch sizing
Key: DRILL-6478
URL: https://issues.apache.org/jira/browse/DRILL-6478
Project: Apache Drill
Issue Type:
Thanks for the feedback Dave / Robert.
So here is revised proposal that does not automatically close a PR, but does
include some automation to alleviate some of the leg work:
1. Auto reply with information about how to help the contributor to be
successful and about the PR process.
2. Use
Makes sense, Aman. The fact that such PR's exist should cause us to regard
automatic removal of PR's as a risky proposition. There is no way (currently)
for a machine to reliably determine which PR's have these kinds of qualities.
Regarding my experience, it is not just the fact that the PR
I haven't looked at Tim's survey yet but just wanted to respond to Dave
about his experience. I can assure you that Drill committers would welcome
quality contributions from you or anyone else. In the case of your PR,
the reason for it getting stuck was basically what you already
mentioned:
Kunal Khatua created DRILL-6477:
---
Summary: Drillbit hangs/crashes with OOME Java Heap Space for a
large query through WebUI
Key: DRILL-6477
URL: https://issues.apache.org/jira/browse/DRILL-6477
The Exchange PR was under active development, but there were some issues that
could not be resolved at the time. So it was shelved until someone could get
some time to resolve those issues.
Thanks.
--Robert
From: Robert Hou
Sent: Thursday, June 7, 2018
On a related note, someone created a PR to resolve some Exchange issues a year
ago. It has been dormant since then, and the original author is probably not
going to push it forward. However, a second person has picked it up now
because we need to resolve the issue. There is a lot of good
Hi Tim,
Everyone's time is constrained, so I doubt that it will always be possible to
give "timely" reviews to PR's, especially complex ones, or ones regarding
problems that are not regarded as high priority. I suggest these changes to
your scheme:
1) Once a PR reaches the 3 months point,
Hi Dave,
I'm sorry you had a bad experience. We should do better giving timely reviews
moving forward. I think there are some ways we can protect PRs from
unresponsive committers while still closing PRs from unresponsive contributors.
Here are some ideas.
1. Have an auto responder comment on
Hanumath Rao Maduri created DRILL-6476:
--
Summary: Generate explain plan which shows relation between
Lateral and the corresponding Unnest.
Key: DRILL-6476
URL:
11 matches
Mail list logo
