impala-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Todd Lipcon <>
Subject Re: February podling report
Date Mon, 29 Feb 2016 23:16:08 GMT
Looks good to me. Only feedback is that I think I'd move the gerrit thing
to the bottom of the priority list, over the near term higher priority
moving of infrastructure. On Kudu we followed the example of AsterixDB and
I believe the general consensus is that this is an acceptable way to use
gerrit (no need to block on asf infra running a gerrit server).


On Mon, Feb 29, 2016 at 2:45 PM, Henry Robinson <> wrote:

> Hi all -
> It's report season again. Here is my draft for this month's report (we
> missed last month's). Do let me know what you think we should add.
> I'll move to the report wiki in the next day or so.
> Best,
> Henry
> --------------------
> Impala
> Impala is a high-performance C++ and Java SQL query engine for data stored
> in
> Apache Hadoop-based clusters.
> Impala has been incubating since 2015-12-03.
> Three most important issues to address in the move towards graduation:
>   1. Resolve any issues around use of Gerrit as code-review tool.
>   2. Movement of existing JIRA / Git / wiki resources to Apache
> equivalents
>   3. Initial release as incubating project.
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
> None.
> How has the community developed since the last report?
> There have been no additions to the committer or PMC lists since incubation
> began. However, we have seen an uptick in external contributions, both
> through code, and in discussion on the mailing list. One contributor
> has been attempting to port Impala to PPC, and has reported some
> success after asking many questions.
> How has the project developed since the last report?
> We have made some slow progress with our initial infrastructure tasks.
> Code review traffic is now copied to,
> which means that developer discussions are now happening on the
> mailing lists.
> We have a number of infrastructure tasks ahead of us which are blocked
> on the current Impala team at Cloudera being very busy with an
> internal release (this is one reason we look forward to a more diverse
> community!). For example:
> 1. We would like to move our Git repository to in short
> order, but as it stands the existing repo is 10GB large and
> historically contains many binary artifacts that, while acceptably
> licensed, have no useful place in Impala's repository. We need to
> strip these artifacts from the Git history, and then adjust Gerrit to
> commit to the new branch in the new repo. This is not hard but takes
> some time.
> 2. We would also like to move our JIRA tickets from
> to Experience in a sister
> podling has shown that this isn't straightforward if we wish to
> preserve existing release labels, user assignments and so on, so
> requires some time.
> We anticipate having much more time to work on these basic issues
> after the end of February. We look forward to getting Impala into a
> position where it is easier for the larger community to collaborate on
> these kinds of project management issues.

Todd Lipcon
Software Engineer, Cloudera

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message