Hi Garvit,
We have some documentation on how to contribute (
http://fluo.apache.org/how-to-contribute/) on our website. Also, if you
don't find an issue that you want work on, one way to contribute is to
build a example Fluo application (see
http://fluo.apache.org/related-projects/ for examples)
I was able to build fluo-recipes using fluo-parent 1-incubating & fluo
1.0.0-incubating from the staging repo. I am ready to vote.
On Tue, Jul 26, 2016 at 11:19 AM Keith Turner wrote:
> I was able to build fluo-quickstart, fluo-recipes, phrasecount,
> fluo-stress, and
The dev list would be nice if only one email was sent for a new pull
request. However, I think emails are sent every time someone comments on
the PR. Therefore, I prefer them being sent to the notifications list.
On Wed, Aug 3, 2016 at 11:00 AM Christopher wrote:
> For
We do have a 'how to contribute' page (
https://fluo.apache.org/how-to-contribute/) but it needs to be updated with
how we are working around problems with GH issues.
On Tue, Jun 28, 2016 at 3:44 PM Keith Turner wrote:
> On Tue, Jun 28, 2016 at 3:35 PM, Josh Elser
+1
* Verified sha1 & md5 hashes for fluo-parent & build-resoures
* Verified signatures for fluo-parent & build-resources
* Built Fluo and Fluo recipes using staging repo and new fluo-parent
On Fri, Aug 5, 2016 at 11:11 AM Keith Turner wrote:
> +1
>
> * sigs and hashes are
Hi Caleb,
I wouldn't try to follow our Twill code too closely. We have a lot of
abstraction in the code that I don't think you need. We do use TwillRunner
and TwillController. One major tip is that you should consider whether or
not you want to pull in all of Twill dependencies (which may
Looks great. Thanks Keith!
On Wed, Feb 1, 2017 at 10:48 AM Keith Turner wrote:
> I updated the Fluo report on the wiki. Does anyone have any suggested
> changes?
>
> https://wiki.apache.org/incubator/February2017
>
> On Tue, Jan 31, 2017 at 10:02 PM,
This is a great idea. How would users configure their UserObserversFactory
in fluo.properties? Would there still be observer properties in
fluo.properties or just application properties?
On Thu, Feb 23, 2017 at 5:36 PM Keith Turner wrote:
> The current way observers are set
I checked over rc0 and didn't find any issues. While rc1 needs to be
latest commit, the release artifacts look good.
On Mon, Sep 19, 2016 at 5:32 PM Christopher wrote:
> My plan is to submit an RC1 for a vote tomorrow.
>
> On Fri, Sep 16, 2016 at 4:39 PM Christopher
the property
'fluo.observer.*'
-Mike
On Tue, Nov 1, 2016 at 3:33 PM Meier, Caleb <caleb.me...@parsons.com> wrote:
> Do you have any tips for how to make Observers log to the log files found
> in the directory specified by 'yarn.nodemanager.log-dirs'?
>
> -Original Message
Hi Caleb,
The logs for a Fluo application can be found in YARN but they are tricky to
find. Fluo should have better documentation on this which I will add now.
The easiest way to view the logs for a Fluo application is to use the web
interface for the YARN resource manager
worker
> >
> > yielded nothing. Any ideas as to why these don't exist? I'm not sure
> > that my fluo.log.dir system property is successfully being set by the
> LogbackUtil class.
> > Maybe this has something to do with it?
> >
> >
> >
> >
> >
> >
Yes. Keith, you are right. Logging config changes need to be made to
/path/to/fluo/apps/$APPNAME/conf/logback.xml
On Tue, Nov 1, 2016 at 4:21 PM Keith Turner <ke...@deenlo.com> wrote:
> On Tue, Nov 1, 2016 at 4:02 PM, Mike Walch <mwa...@apache.org> wrote:
> > Were you a
I am working on changes to how Fluo launches applications in YARN.
However, my changes are not close to being ready for a PR. I am OK with
1.1.0 being released and this getting into 1.2.0.
On Fri, Apr 21, 2017 at 12:46 PM Keith Turner wrote:
> I am thinking of initiating a
I would like to create new repo (called 'fluo-yarn') using Gitbox to hold
code for launching Fluo applications in YARN. This is related to my recent
pull request [1]. Does anyone have any objections to this?
[1]: https://github.com/apache/incubator-fluo/pull/883
Christopher <ctubb...@apache.org> wrote:
> Is the idea to have fluo-yarn on a different release cycle?
>
>
> On Mon, Jul 17, 2017 at 3:52 PM Mike Walch <mwa...@apache.org> wrote:
>
> > I would like to create new repo (called 'fluo-yarn') using Gitbox to hold
> &g
it may be better to put commands in
> their own module, so the commands can have a dependency like
> jcommander w/o adding that to core.
>
> On Fri, May 19, 2017 at 1:18 PM, Mike Walch <mwa...@apache.org> wrote:
> > For Fluo 1.2, I would like to improve how Fluo applicati
For Fluo 1.2, I would like to improve how Fluo applications are
launched/run. This involves deprecating the current tarball distribution
and creating downstream repos that create distributions for running Fluo
applications locally and cluster managements tools suchs as YARN, Mesos,
Kubernetes,
+1
* Verified sha1 & md5 hashes matched
* Verified signatures
* Was able to build and run integration tests for Fluo-recipes & Webindex
using staging repo
On Fri, Jun 2, 2017 at 12:54 PM Keith Turner wrote:
> Fluo Developers,
>
> Please consider the following candidate for
+1
* Verified sha1 & md5 hashes matched
* Verified signatures
* Built and ran ITs for Webindex & Stresso using fluo-recipes jars in
staging repo
On Mon, Jun 12, 2017 at 7:16 PM Keith Turner wrote:
> Fluo Developers,
>
> Please consider the following candidate for Fluo Recipes
20 matches
Mail list logo