Re: Bulk JIRA email, or how to find good newbie tasks

Please don't add that comment. :) What's currently labelled ramp-up is often not a good newbie task (and maybe not even a good ramp-up task). The best way to identify newbie tasks is for a few senior engineers to sift through the ramp-up tasks and pick out maybe a few dozen that truly qualify as

Re: Bulk JIRA email, or how to find good newbie tasks

Cool, it seems very helpful to me to have such a list of easy tasks. I think that watchers of these issues could often be interested in a fix, but might not necessarily know how much effort these issues are. Would it be an alternative to ask people familiar with various parts of the codebase for

[Toolchain-CR] Versioning of build artifacts

Matthew Jacobs has posted comments on this change. Change subject: Versioning of build artifacts .. Patch Set 1: (1 comment) http://gerrit.cloudera.org:8080/#/c/4742/1/functions.sh File functions.sh: PS1, Line 425: git

[Toolchain-CR] Versioning of build artifacts

Matthew Jacobs has posted comments on this change. Change subject: Versioning of build artifacts .. Patch Set 1: Oh, nm the jenkins build # does give it the right ordering. -- To view, visit

[Toolchain-CR] Versioning of build artifacts

Matthew Jacobs has posted comments on this change. Change subject: Versioning of build artifacts .. Patch Set 1: > My feeling was that we generally be referencing a fixed version of > the toolchain artifacts in most cases

[Toolchain-CR] Versioning of build artifacts

Tim Armstrong has posted comments on this change. Change subject: Versioning of build artifacts .. Patch Set 1: My feeling was that we generally be referencing a fixed version of the toolchain artifacts in most cases (rather

[Toolchain-CR] Versioning of build artifacts

Matthew Jacobs has posted comments on this change. Change subject: Versioning of build artifacts .. Patch Set 1: Nice! I think we'll need a good way to find/download the latest builds as well, since it'll be hard or

[Toolchain-CR] Versioning of build artifacts

Tim Armstrong has posted comments on this change. Change subject: Versioning of build artifacts .. Patch Set 1: This solves a couple of pressing issues around build times and reproducibility of builds. Hoping this can start a

[Toolchain-CR] Versioning of build artifacts

Tim Armstrong has uploaded a new change for review. http://gerrit.cloudera.org:8080/4742 Change subject: Versioning of build artifacts .. Versioning of build artifacts Previously publishing a new version of toolchain

Re: Impala build error with libgflags-dev installed

Thanks! Can you file a bug for this? On Mon, Oct 17, 2016 at 12:01 PM, Yonghyun Hwang wrote: > Impala build sees an error if "libgflags-dev" package is already installed > in a machine. Here is the error. > > $ source bin/impala-config.sh && buildall.sh -skiptests

Impala build error with libgflags-dev installed

Impala build sees an error if "libgflags-dev" package is already installed in a machine. Here is the error. $ source bin/impala-config.sh && buildall.sh -skiptests -notests ... ... *Linking CXX shared library* ../../build/debug/gutil/libgutil.so

Re: Bootstrapping an Impala Development Environment From Scratch

I think this takes at least 80GB of disk space and 16GB of RAM. On Mon, Oct 17, 2016 at 11:50 AM, Laszlo Gaal wrote: > Running in a VM is good idea. Do you have a recommendation on how much > memory the VM should be configured with? > > On Mon, Oct 17, 2016 at 7:58 PM,

Re: Bootstrapping an Impala Development Environment From Scratch

Running in a VM is good idea. Do you have a recommendation on how much memory the VM should be configured with? On Mon, Oct 17, 2016 at 7:58 PM, Jim Apple wrote: > If you are running Ubuntu 14.04, you can bootstrap a development > environment using the script

Re: problems for the debuging the frontend in Eclipse IDE

1. You need to generate en Eclipse project via "mvn eclipse:eclipse" from the "fe" directory, 2. Before starting Eclipse, you need to "source bin/impala-config.sh" and "source bin/set-classpath.sh". If that still does not work, do you have a stack? On Mon, Oct 17, 2016 at 10:41 AM, Jim Apple

Bootstrapping an Impala Development Environment From Scratch

If you are running Ubuntu 14.04, you can bootstrap a development environment using the script bin/bootstrap_development.sh[0]. It will alter your environment, including ~/.ssh/config and /etc/hosts, so consider running it in a VM or container. It takes 6-7 hours in total to load all of the

Re: problems for the debuging the frontend in Eclipse IDE

Do the planner tests pass when you run them outside of the Eclipse IDE? On Sun, Oct 16, 2016 at 6:47 PM, Zhangjun (Jerry) wrote: > Hi， > I download the source code from master branch. And build it and run all > service with testdata successfully. But when I debug the

problems for the debuging the frontend in Eclipse IDE

Hi， I download the source code from master branch. And build it and run all service with testdata successfully. But when I debug the planner test case(PlannerTest.java) for frontend in Eclipse IDE, the application shutdown and no any exception print( I have modified the log level to “all” level

Bulk JIRA email, or how to find good newbie tasks

The Impala JIRA has 129 tasks that have no assignee, are still open, and are labelled ramp* (i.e. ramp-up, ramp-up-introductory, etc.). I'd like to find which of those tasks are good tasks for someone who is making their first Impala patch. I intend to promote those on one or more of : the blog,