Done, also added a component for Documentation. On Thu, Oct 8, 2015 at 11:00 AM, Lirong Jian <[email protected]> wrote:
> Please add one more component: *Dispatcher. * > > We already have found some bugs closely related to the Dispatcher > component. > > Thanks, > Lirong > > 2015-10-05 23:41 GMT+08:00 Caleb Welton <[email protected]>: > > > 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 <[email protected]> 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 <[email protected]> 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 > > > > > > > > > >
