+1
* Verified sha1 & md5 hashes matched
* Verified signatures
* Successfully built Fluo using fluo-parent in staging repo
On Mon, Sep 11, 2017 at 5:44 PM Christopher wrote:
> Fluo Developers,
>
> I've taken the liberty of preparing some release candidates to update our
> build tooling. I've pre
Sounds like a great idea to me. You could add a link to those issues on
website too.
On Mon, Sep 18, 2017 at 12:23 PM Keith Turner wrote:
> I would like to create a helpwanted label in github for issues that
> are posted to helpwanted.apache.org. Does anyone have any objections
> or thoughts?
Hi Michael,
Thanks for wanting to help out!
It looks like that issue was completed and closed. See
https://github.com/apache/fluo/issues/923
Take a look at our issues at https://github.com/apache/fluo/issues
There some other 'help wanted' issues available.
Best,
Mike
On Mon, Oct 16, 2017 at
Hi Kenneth,
If you are looking for work to do, any of our issues[1] would be great to
work
on. As for problems that can be solved by Fluo, check out the example Fluo
applications on the related projects page[2] and the slides[3] for a talk
that I gave at the Accumulo Summit. Any research or white
+1
* Verified signatures & hashes
* Built Fluo using new parent
On Fri, Nov 17, 2017 at 6:01 PM Christopher wrote:
> Fluo Developers,
>
> Please consider the following candidate for Fluo Parent POM 3. This release
> candidate includes the fix in PR#970
>
> My vote is +1; I checked:
> * Fluo m
I think 1.2.0 release would be great. I have no outstanding issues. I am
going to start running some tests this week.
On Fri, Dec 1, 2017 at 1:56 PM Keith Turner wrote:
> I think it would be good to start working towards a 1.2.0 release.
> Does anyone have any outstanding issues they would like
I think we should create a user list. I am going to start a separate
thread on this topic.
On Tue, Dec 19, 2017 at 11:21 AM Keith Turner wrote:
> On Tue, Dec 19, 2017 at 8:18 AM, Alan Camillo
> wrote:
> > Hello Fluo group!
> >
> > My name is Alan, I'm a big date architect and owner of a compan
When Fluo started incubation, a user mail listing wasn't created to limit
the number of mailing lists. However, I think we are due for one. Does
anyone have any views on one being created? If there are no objections, I
will create a user mailing list this week.
; > necessarily care about dev concerns). The former doesn't really apply
> > because we're so low traffic, but the latter might. I'm +0.
> >
> > On Tue, Dec 19, 2017, 11:54 Keith Turner wrote:
> >
> >> I am in favor. A user list would follow the pa
Hi Furkan,
Welcome to the community! Please let us know if you have any questions or
need help finding stuff to work on. Contributing to the Fluo Recipes tour
would be great.
-Mike
On Sun, Dec 24, 2017 at 8:39 AM Furkan KAMACI
wrote:
> Hi All,
>
> I'm Furkan KAMACI who is a person loves open
/fluo-tour/src/main/java/ft/Main.java
On Tue, Dec 26, 2017 at 3:06 PM Furkan KAMACI
wrote:
> Hi Mike,
>
> Thanks for the welcome! Is there any issue for Fluo Recipes about what to
> follow or should I create one?
>
> Kind Regards,
> Furkan KAMACI
>
>
> On Tue, Dec 26,
Hi Alan,
>From your screenshot, it looks like your Fluo application was initialized
but never started. After an application is running in YARN, it's YARN
application ID is written to Zookeeper and viewable when you run 'fluo
list'. However, your output says 'not started yet' for the application
I
11 4605-5082 <+55%2011%204605-5082>
>
> 2017-12-27 12:33 GMT-02:00 Mike Walch :
>
> > Hi Alan,
> >
> > From your screenshot, it looks like your Fluo application was initialized
> > but never started. After an application is running in YARN, it's YARN
&g
Hi Alan,
It sounds like you are using 1.2.0-SNAPSHOT, correct? That's great. I
just don't want to confuse others with the explanation below.
You should be able to use the same fluo-conn.properties if you start
workers as local processes on other nodes. If you run Fluo in YARN, YARN
will distri
Nice work. Is there anyway to compare this release with previous ones?
On Wed, Jan 10, 2018 at 10:19 AM, Keith Turner wrote:
> I completed a successful 24hr run of the Fluo stress test on a 10 node
> EC2 cluster. For the test 1 billion random integers were loaded via
> map reduce and then 370 m
Does anyone know why we are still getting these emails?
On Mon, Jan 29, 2018 at 11:20 PM, wrote:
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
t ping John directly. Probably his CC list just needs updating.
>>
>> On 1/30/18 4:28 PM, Mike Walch wrote:
>>
>>> Does anyone know why we are still getting these emails?
>>>
>>> On Mon, Jan 29, 2018 at 11:20 PM, wrote:
>>>
>>> Dear pod
He fixed something. We should not get the reminder again.
On Wed, Jan 31, 2018 at 10:46 AM, Mike Walch wrote:
> Good idea. I sent him an email.
>
>
> On Wed, Jan 31, 2018 at 10:38 AM, Josh Elser wrote:
>
>> n/m, that says "automated system" :)
>>
>
Hi Alan,
I assume you are referring to the preInit() method in the documentation
below:
https://fluo.apache.org/docs/fluo-recipes/1.1.0-incubating/export-queue/
Yes, this should be called in a Main method before initializing Fluo. You
can still initialize Fluo using "fluo init" command but you
+1
* Verified sha1 & md5 hashes matched
* Verified signatures
* Ran 'mvn verify' for Fluo Recipes (using Accumuo 1.7.3) and Webindex
using RC
* Successfully ran phrasecount application locally using Uno & Fluo 1.2.0
RC tarball
On Wed, Feb 21, 2018 at 4:45 PM, Christopher wrote:
> Fluo Developer
Both files existed inside the jars to set up logging when Fluo ran in
YARN/Twill. I fixed this in the new Fluo YARN repo.
I could fix it here but the fluo-cluster module is deprecated so not sure
if this code should be touched.
On Fri, Feb 23, 2018 at 1:57 PM Mike Walch wrote:
> +1
>
Starting with Fluo 1.2.0, we tell users that they can obtain an apache/fluo
image from DockerHub:
https://fluo.apache.org/docs/fluo/1.2/administration/run-fluo-in-docker
I would like to put in a ticket with INFRA to create this repo. If no one
has objections, I will do this tomorrow.
+1
* Verified sha1 & md5 hashes matched
* Verified signatures
* Ran integration tests for Stresso & Webindex using release
On Thu, Mar 1, 2018 at 12:56 PM, Christopher wrote:
> Fluo Developers,
>
> Please consider the following candidate for Fluo Recipes 1.2.0.
>
> Git Commit:
> 6e8956c39c9
+1
* Verified sha1 & md5 hashes matched
* Verified signatures
* Ran Fluo App w/o observers and Webindex locally using Uno & release
binary distribution
On Thu, Mar 1, 2018 at 1:02 PM, Christopher wrote:
> Fluo Developers,
>
> Please consider the following candidate for Fluo YARN 1.0.0.
>
> Git
+1 Sounds like a good plan.
On Wed, Mar 7, 2018 at 3:13 PM, Christopher wrote:
> For much of Fluo's early life, it was hosted at https://github.com/fluo-io
> As many will be aware, this was renamed to https://github.com/astralway to
> satisfy concerns about trademark use during Fluo's transition
Hi Alan!
No worries about emailing the list. Your email is actually helpful. It's
made it clear that we need to improve our troubleshooting docs. There is
some documentation at the link below but we could use more:
https://fluo.apache.org/docs/fluo/1.2/administration/manage-applications
What ver
Sounds good. All pull requests are welcome.
On Tue, Mar 13, 2018 at 6:52 AM, Alan Camillo wrote:
> We were able to run Fluo with Kerberos without big problems.
>
> Suggestions: add some properties on fluo-app to informe principal, keytab
> and the other necessary attributes related to Kerberos.
I opened a PR to add some troubleshooting docs to the website.
https://github.com/apache/fluo-website/pull/142
On Tue, Mar 13, 2018 at 10:59 AM, Keith Turner wrote:
> On Tue, Mar 13, 2018 at 7:11 AM, Alan Camillo
> wrote:
> > Hey fellas!
> > Sorry to demand so much from you. But we are really
#x27;ll let you know.
> >
> > Alan Camillo
> > *BlueShift *I IT Director
> > Cel.: +55 11 98283-6358 <+55%2011%2098283-6358>
> > Tel.: +55 11 4605-5082 <+55%2011%204605-5082>
> >
> > 2018-03-13 15:04 GMT-03:00 Mike Walch :
> >
> >
; On Wed, Feb 28, 2018 at 11:54 AM Keith Turner wrote:
> >
> > > I am in favor of creating this.
> > >
> > > On Wed, Feb 28, 2018 at 11:15 AM, Mike Walch
> wrote:
> > > > Starting with Fluo 1.2.0, we tell users that they can obtain an
> >
+1
On Mon, Apr 16, 2018 at 6:07 PM, Christopher wrote:
> Fluo developers,
>
> It is the desire of the primary administrators of the astralway project on
> GitHub (myself, Keith Turner, and Mike Walch, who are also PMC members for
> Fluo), which currently hosts these projects,
I created a #fluo channel on the ASF Slack workspace. Check out the page
below for instructions on how to join:
https://fluo.apache.org/contactus/
Welcome Mike!
On Wed, Oct 30, 2019 at 12:06 PM Christopher wrote:
> Welcome, Mike!
>
> On Wed, Oct 30, 2019 at 11:43 AM Keith Turner wrote:
> >
> > The Apache Fluo Project Management Committee (PMC) invited Mike Miller
> > to become a committer/PMC member and we are pleased to announce that he
Welcome Arvind!
On Wed, Oct 30, 2019 at 2:15 PM Christopher wrote:
> Welcome Arvind!
>
> On Wed, Oct 30, 2019 at 2:13 PM Keith Turner wrote:
> >
> > The Apache Fluo Project Management Committee (PMC) invited Arvind
> > Shyamsundar to become a committer/PMC member and we are pleased to
> > annou
34 matches
Mail list logo
