hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Caleb Welton <cwel...@pivotal.io>
Subject Re: HAWQ JIRA components
Date Mon, 05 Oct 2015 15:41:28 GMT
I have created components for:
- Ambari
- Build
- Catalog
- Command Line Tools
- Core
- DDL
- External tables & PXF
- libyarn
- libhdfs
- Optimizer
- Parser
- Query Execution
- Resource Manager
- Storage
- Tests

With this list all existing jira's have been assigned a reasonable
component.  We can add more as needed.



On Sun, Oct 4, 2015 at 7:43 PM, Jimmy Da <jd462@cornell.edu> wrote:

> I agree with Noa. We can and should use components in combination with
> "Labels" to further categorize the Jiras considering the scale of the code
> base.
>
> Potentially, every module in src/backend could be its own component, but
> let's brain storm first:
>
> Optimizer
> Query Execution
> PXF
> catalog
> dispatch
> storage
> interconnect
> resource manager
> hadoop/yarn/ecosystem integration
> master/segment process
> utility tools
>
> Perhaps product can use the list to seed some components in Jiras.
>
> Jimmy Da
> Electrical and Computer Engineering
> Cornell University 2011
>
> On Fri, Oct 2, 2015 at 2:14 PM, Noa Horn <nhorn@pivotal.io> wrote:
>
> > Since HAWQ is such a big project, it makes sense to have different
> > components assigned to the JIRAs.
> >
> > Let's create a list of all required components. Please add your
> suggestions
> > below.
> >
> > 1. Optimizer
> > 2. Query Execution
> > 3. PXF
> >
>

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