Volunteer to try Fluo tour

[Keith Turner <ke...@deenlo.com>]

I just put a pull request[1] for something called the Fluo Tour.  The
tour is a set of exercises someone could follow to help them become
proficient using Fluo.  I am looking for feedback if anyone has a
chance to try following it.  Currently, need to do the following two
things to try the tour.

 * Install a snapshot version of Fluo (we are getting close to
releasing 1.0.0 I hope, so this step would not be needed after that)
 * Run Jekyll locally.

If anyone needs more info on either of these two steps, could ask here
or on the PR.

[1]: https://github.com/apache/incubator-fluo-website/pull/21

Re: Volunteer to try Fluo tour

[Josh Elser <jo...@gmail.com>]

Keith Turner wrote:
> On Wed, Oct 5, 2016 at 11:39 PM, Josh Elser<jo...@gmail.com>  wrote:
>> >  tl;dr This is really great to see, Keith and Mike. Kudos to you both on a
>> >  great tutorial.
>
> Thanks for taking a look and the excellent feedback.
>

Glad it was helpful :)

MiniFluo made it really easy to play around.

Re: Volunteer to try Fluo tour

[Keith Turner <ke...@deenlo.com>]

On Wed, Oct 5, 2016 at 11:39 PM, Josh Elser <jo...@gmail.com> wrote:
> tl;dr This is really great to see, Keith and Mike. Kudos to you both on a
> great tutorial.

Thanks for taking a look and the excellent feedback.

>
> Thoughts:
>
> * MiniFluo could have a check to verify that DNS is correct (really, we
> should fix this in Accumulo. Just do the rDNS and DNS and make sure they're
> consistent. I always screw this up on my laptop and forget to fix
> /etc/hosts).
>
> * Why is the method "gets(row, col)" on Snapshot? (I kept wanting to type
> "get(row, col)")
>
> * Nit: waitTotal and waitPeriod are not really.. informative. Does this mean
> it waited 1second this time and will wait 2seconds next time?
>
> 2016-10-05 22:22:37,023 [oracle.OracleClient] WARN : Waiting for timestamp
> from Oracle. Is it running? waitTotal=1s waitPeriod=2s
>
> * From "Collision Code"
>
> "tx3 commit exception message :
> org.apache.fluo.api.exceptions.CommitException"
>
> Looks like there's no exception message. Do you know in the client that
> there was a conflict (and an appropriate message could be given)? Trying to
> debug why I got this exception seems like it would be difficult to
> understand.
>
> * From "Transaction Logging"
>
> Why "log4j.logger.fluo.tx=TRACE" and not something like
> "log4j.logger.org.apache.fluo.tx=TRACE"? This is some generic logger name,
> not a real class, I assume?
>
> * From "Word count Exercise"
>
> Document and DocumentLoader could exist already?
> No solutions?
>
> In general, this one felt much less "put together" than the others.
>
> * From "Row Locking"
>
> s/its/it's/
>
> "These row locks can impact the performance of your transactions, so its
> something to be aware of when designing a schema." <- It's not as obvious as
> to how, as a user, I would do this. Do traditional approaches like a
> shard-bit on the row help? Are there other tricks that help with Fluo?
>
> * Application Configuration
>
> Nit: s/zookeeper/ZooKeeper/ (really, Apache ZooKeeper would be better)
> s/fluo/Fluo/
>
> "After fluo is initialized this information can be accessed anywhere by
> calling.." -- Technical question: is this always pulling a fresh copy from
> ZK? Or, maybe subject to the same Watcher-fire config propagation issue that
> Accumulo is?
>
> "com.foo.MysqlExporter" <- Make this? ;) Or maybe a generalized JDBC
> exporter? Not sure how to handle the schema/types, but this would be very
> cool way to ease adoption.
>
> * Overall thought
>
> You might be able to use some collapse-able divs to embed the solutions on
> the same page as the problems. This would help when the user wants
> cross-reference the problem instructions with the solutions. JQuery has some
> super-easy ways to do this.
>
> Change the package from "ft" to "org.apache.fluo.examples.tour"? Something
> to promote this as official Apache Fluo examples.
>
>
> Josh Elser wrote:
>>
>> No worries! I assumed as much :)
>>
>> I will _make_ time for this tonight then!
>>
>> Christopher wrote:
>>>
>>> I released the maven repo, dropped old staging repos, pushed the dist
>>> artifacts to the mirrors, and cleaned up git repo (merged in the tag,
>>> dropped old rc branches).
>>>
>>> So, once this tour is ready (and release notes/download page generated),
>>> we're ready to announce the release.
>>>
>>> On Wed, Oct 5, 2016 at 4:13 PM Christopher<ct...@apache.org> wrote:
>>>
>>> Sorry. I'm on it... last few days have been *busy*.
>>>
>>> On Wed, Oct 5, 2016 at 12:38 PM Josh Elser<jo...@gmail.com> wrote:
>>>
>>> Will do. At this point, I will likely wait for 1.0.0 to get promoted :)
>>>
>>> Keith Turner wrote:
>>>>
>>>> Awesome. Let me know if you need anything.
>>>>
>>>> On Tue, Oct 4, 2016 at 6:10 PM, Josh Elser<jo...@gmail.com> wrote:
>>>>>
>>>>> Sounds like fun. I want to try to do this.
>>>>>
>>>>>
>>>>> Keith Turner wrote:
>>>>>>
>>>>>> I just put a pull request[1] for something called the Fluo Tour. The
>>>>>> tour is a set of exercises someone could follow to help them become
>>>>>> proficient using Fluo. I am looking for feedback if anyone has a
>>>>>> chance to try following it. Currently, need to do the following two
>>>>>> things to try the tour.
>>>>>>
>>>>>> * Install a snapshot version of Fluo (we are getting close to
>>>>>> releasing 1.0.0 I hope, so this step would not be needed after that)
>>>>>> * Run Jekyll locally.
>>>>>>
>>>>>> If anyone needs more info on either of these two steps, could ask here
>>>>>> or on the PR.
>>>>>>
>>>>>> [1]: https://github.com/apache/incubator-fluo-website/pull/21
>>>
>>>
>

Re: Volunteer to try Fluo tour

[Keith Turner <ke...@deenlo.com>]

On Wed, Oct 5, 2016 at 11:39 PM, Josh Elser <jo...@gmail.com> wrote:
> tl;dr This is really great to see, Keith and Mike. Kudos to you both on a
> great tutorial.
>
> Thoughts:
>
> * MiniFluo could have a check to verify that DNS is correct (really, we
> should fix this in Accumulo. Just do the rDNS and DNS and make sure they're
> consistent. I always screw this up on my laptop and forget to fix
> /etc/hosts).
>
> * Why is the method "gets(row, col)" on Snapshot? (I kept wanting to type
> "get(row, col)")
>
> * Nit: waitTotal and waitPeriod are not really.. informative. Does this mean
> it waited 1second this time and will wait 2seconds next time?
>
> 2016-10-05 22:22:37,023 [oracle.OracleClient] WARN : Waiting for timestamp
> from Oracle. Is it running? waitTotal=1s waitPeriod=2s

Opened issue https://github.com/apache/incubator-fluo/issues/786

>
> * From "Collision Code"
>
> "tx3 commit exception message :
> org.apache.fluo.api.exceptions.CommitException"
>
> Looks like there's no exception message. Do you know in the client that
> there was a conflict (and an appropriate message could be given)? Trying to
> debug why I got this exception seems like it would be difficult to
> understand.

Opened issue https://github.com/apache/incubator-fluo/issues/785

>
> * From "Transaction Logging"
>
> Why "log4j.logger.fluo.tx=TRACE" and not something like
> "log4j.logger.org.apache.fluo.tx=TRACE"? This is some generic logger name,
> not a real class, I assume?
>
> * From "Word count Exercise"
>
> Document and DocumentLoader could exist already?

Are you thinking these files should exists as part of the tour?

> No solutions?

That was intentional.  When I took the Golang tour, I don't think it
provided any solutions to problems.  Forced me to do them myself,
which I think is better for absorbing/learning info.

>
> In general, this one felt much less "put together" than the others.

The intention was to have the person following the tour have to put
some thought into completing it.  The hope was that by doing this
mental exercise a more in-depth understanding would be obtained :).  I
tried to update the intro to convery this, not sure if I made it
explicit enough.

>
> * From "Row Locking"
>
> s/its/it's/
>
> "These row locks can impact the performance of your transactions, so its
> something to be aware of when designing a schema." <- It's not as obvious as
> to how, as a user, I would do this. Do traditional approaches like a
> shard-bit on the row help? Are there other tricks that help with Fluo?

I made a lot of updates to this section.   If you have a moment to
take a look, let me know what you think.

>
> * Application Configuration
>
> Nit: s/zookeeper/ZooKeeper/ (really, Apache ZooKeeper would be better)
> s/fluo/Fluo/
>
> "After fluo is initialized this information can be accessed anywhere by
> calling.." -- Technical question: is this always pulling a fresh copy from
> ZK? Or, maybe subject to the same Watcher-fire config propagation issue that
> Accumulo is?

Thats a really good question and I am not sure what the answer is.   I
have not tried doing this.   I have only set app config at
initialization time before starting the application.  I will open an
issue about testing this and documenting expected behavior.

>
> "com.foo.MysqlExporter" <- Make this? ;) Or maybe a generalized JDBC
> exporter? Not sure how to handle the schema/types, but this would be very
> cool way to ease adoption.

Yeah, how the model for mapping would need to be better defined.  if
something were done for this, it would fit nicely in Fluo Recipes.

>
> * Overall thought
>
> You might be able to use some collapse-able divs to embed the solutions on
> the same page as the problems. This would help when the user wants
> cross-reference the problem instructions with the solutions. JQuery has some
> super-easy ways to do this.
>
> Change the package from "ft" to "org.apache.fluo.examples.tour"? Something
> to promote this as official Apache Fluo examples.
>
>
> Josh Elser wrote:
>>
>> No worries! I assumed as much :)
>>
>> I will _make_ time for this tonight then!
>>
>> Christopher wrote:
>>>
>>> I released the maven repo, dropped old staging repos, pushed the dist
>>> artifacts to the mirrors, and cleaned up git repo (merged in the tag,
>>> dropped old rc branches).
>>>
>>> So, once this tour is ready (and release notes/download page generated),
>>> we're ready to announce the release.
>>>
>>> On Wed, Oct 5, 2016 at 4:13 PM Christopher<ct...@apache.org> wrote:
>>>
>>> Sorry. I'm on it... last few days have been *busy*.
>>>
>>> On Wed, Oct 5, 2016 at 12:38 PM Josh Elser<jo...@gmail.com> wrote:
>>>
>>> Will do. At this point, I will likely wait for 1.0.0 to get promoted :)
>>>
>>> Keith Turner wrote:
>>>>
>>>> Awesome. Let me know if you need anything.
>>>>
>>>> On Tue, Oct 4, 2016 at 6:10 PM, Josh Elser<jo...@gmail.com> wrote:
>>>>>
>>>>> Sounds like fun. I want to try to do this.
>>>>>
>>>>>
>>>>> Keith Turner wrote:
>>>>>>
>>>>>> I just put a pull request[1] for something called the Fluo Tour. The
>>>>>> tour is a set of exercises someone could follow to help them become
>>>>>> proficient using Fluo. I am looking for feedback if anyone has a
>>>>>> chance to try following it. Currently, need to do the following two
>>>>>> things to try the tour.
>>>>>>
>>>>>> * Install a snapshot version of Fluo (we are getting close to
>>>>>> releasing 1.0.0 I hope, so this step would not be needed after that)
>>>>>> * Run Jekyll locally.
>>>>>>
>>>>>> If anyone needs more info on either of these two steps, could ask here
>>>>>> or on the PR.
>>>>>>
>>>>>> [1]: https://github.com/apache/incubator-fluo-website/pull/21
>>>
>>>
>

Re: Volunteer to try Fluo tour

[Josh Elser <jo...@gmail.com>]

tl;dr This is really great to see, Keith and Mike. Kudos to you both on 
a great tutorial.

Thoughts:

* MiniFluo could have a check to verify that DNS is correct (really, we 
should fix this in Accumulo. Just do the rDNS and DNS and make sure 
they're consistent. I always screw this up on my laptop and forget to 
fix /etc/hosts).

* Why is the method "gets(row, col)" on Snapshot? (I kept wanting to 
type "get(row, col)")

* Nit: waitTotal and waitPeriod are not really.. informative. Does this 
mean it waited 1second this time and will wait 2seconds next time?

2016-10-05 22:22:37,023 [oracle.OracleClient] WARN : Waiting for 
timestamp from Oracle. Is it running? waitTotal=1s waitPeriod=2s

* From "Collision Code"

"tx3 commit exception message : 
org.apache.fluo.api.exceptions.CommitException"

Looks like there's no exception message. Do you know in the client that 
there was a conflict (and an appropriate message could be given)? Trying 
to debug why I got this exception seems like it would be difficult to 
understand.

* From "Transaction Logging"

Why "log4j.logger.fluo.tx=TRACE" and not something like 
"log4j.logger.org.apache.fluo.tx=TRACE"? This is some generic logger 
name, not a real class, I assume?

* From "Word count Exercise"

Document and DocumentLoader could exist already?
No solutions?

In general, this one felt much less "put together" than the others.

* From "Row Locking"

s/its/it's/

"These row locks can impact the performance of your transactions, so its 
something to be aware of when designing a schema." <- It's not as 
obvious as to how, as a user, I would do this. Do traditional approaches 
like a shard-bit on the row help? Are there other tricks that help with 
Fluo?

* Application Configuration

Nit: s/zookeeper/ZooKeeper/ (really, Apache ZooKeeper would be better)
s/fluo/Fluo/

"After fluo is initialized this information can be accessed anywhere by 
calling.." -- Technical question: is this always pulling a fresh copy 
from ZK? Or, maybe subject to the same Watcher-fire config propagation 
issue that Accumulo is?

"com.foo.MysqlExporter" <- Make this? ;) Or maybe a generalized JDBC 
exporter? Not sure how to handle the schema/types, but this would be 
very cool way to ease adoption.

* Overall thought

You might be able to use some collapse-able divs to embed the solutions 
on the same page as the problems. This would help when the user wants 
cross-reference the problem instructions with the solutions. JQuery has 
some super-easy ways to do this.

Change the package from "ft" to "org.apache.fluo.examples.tour"? 
Something to promote this as official Apache Fluo examples.

Josh Elser wrote:
> No worries! I assumed as much :)
>
> I will _make_ time for this tonight then!
>
> Christopher wrote:
>> I released the maven repo, dropped old staging repos, pushed the dist
>> artifacts to the mirrors, and cleaned up git repo (merged in the tag,
>> dropped old rc branches).
>>
>> So, once this tour is ready (and release notes/download page generated),
>> we're ready to announce the release.
>>
>> On Wed, Oct 5, 2016 at 4:13 PM Christopher<ct...@apache.org> wrote:
>>
>> Sorry. I'm on it... last few days have been *busy*.
>>
>> On Wed, Oct 5, 2016 at 12:38 PM Josh Elser<jo...@gmail.com> wrote:
>>
>> Will do. At this point, I will likely wait for 1.0.0 to get promoted :)
>>
>> Keith Turner wrote:
>>> Awesome. Let me know if you need anything.
>>>
>>> On Tue, Oct 4, 2016 at 6:10 PM, Josh Elser<jo...@gmail.com> wrote:
>>>> Sounds like fun. I want to try to do this.
>>>>
>>>>
>>>> Keith Turner wrote:
>>>>> I just put a pull request[1] for something called the Fluo Tour. The
>>>>> tour is a set of exercises someone could follow to help them become
>>>>> proficient using Fluo. I am looking for feedback if anyone has a
>>>>> chance to try following it. Currently, need to do the following two
>>>>> things to try the tour.
>>>>>
>>>>> * Install a snapshot version of Fluo (we are getting close to
>>>>> releasing 1.0.0 I hope, so this step would not be needed after that)
>>>>> * Run Jekyll locally.
>>>>>
>>>>> If anyone needs more info on either of these two steps, could ask here
>>>>> or on the PR.
>>>>>
>>>>> [1]: https://github.com/apache/incubator-fluo-website/pull/21
>>

Re: Volunteer to try Fluo tour

[Josh Elser <jo...@gmail.com>]

No worries! I assumed as much :)

I will _make_ time for this tonight then!

Christopher wrote:
> I released the maven repo, dropped old staging repos, pushed the dist
> artifacts to the mirrors, and cleaned up git repo (merged in the tag,
> dropped old rc branches).
>
> So, once this tour is ready (and release notes/download page generated),
> we're ready to announce the release.
>
> On Wed, Oct 5, 2016 at 4:13 PM Christopher<ct...@apache.org>  wrote:
>
> Sorry. I'm on it... last few days have been *busy*.
>
> On Wed, Oct 5, 2016 at 12:38 PM Josh Elser<jo...@gmail.com>  wrote:
>
> Will do. At this point, I will likely wait for 1.0.0 to get promoted :)
>
> Keith Turner wrote:
>> Awesome.  Let me know if you need anything.
>>
>> On Tue, Oct 4, 2016 at 6:10 PM, Josh Elser<jo...@gmail.com>   wrote:
>>> Sounds like fun. I want to try to do this.
>>>
>>>
>>> Keith Turner wrote:
>>>> I just put a pull request[1] for something called the Fluo Tour.  The
>>>> tour is a set of exercises someone could follow to help them become
>>>> proficient using Fluo.  I am looking for feedback if anyone has a
>>>> chance to try following it.  Currently, need to do the following two
>>>> things to try the tour.
>>>>
>>>>     * Install a snapshot version of Fluo (we are getting close to
>>>> releasing 1.0.0 I hope, so this step would not be needed after that)
>>>>     * Run Jekyll locally.
>>>>
>>>> If anyone needs more info on either of these two steps, could ask here
>>>> or on the PR.
>>>>
>>>> [1]: https://github.com/apache/incubator-fluo-website/pull/21
>

Re: Volunteer to try Fluo tour

[Christopher <ct...@apache.org>]

I released the maven repo, dropped old staging repos, pushed the dist
artifacts to the mirrors, and cleaned up git repo (merged in the tag,
dropped old rc branches).

So, once this tour is ready (and release notes/download page generated),
we're ready to announce the release.

On Wed, Oct 5, 2016 at 4:13 PM Christopher <ct...@apache.org> wrote:

Sorry. I'm on it... last few days have been *busy*.

On Wed, Oct 5, 2016 at 12:38 PM Josh Elser <jo...@gmail.com> wrote:

Will do. At this point, I will likely wait for 1.0.0 to get promoted :)

Keith Turner wrote:
> Awesome.  Let me know if you need anything.
>
> On Tue, Oct 4, 2016 at 6:10 PM, Josh Elser<jo...@gmail.com>  wrote:
>> Sounds like fun. I want to try to do this.
>>
>>
>> Keith Turner wrote:
>>> I just put a pull request[1] for something called the Fluo Tour.  The
>>> tour is a set of exercises someone could follow to help them become
>>> proficient using Fluo.  I am looking for feedback if anyone has a
>>> chance to try following it.  Currently, need to do the following two
>>> things to try the tour.
>>>
>>>    * Install a snapshot version of Fluo (we are getting close to
>>> releasing 1.0.0 I hope, so this step would not be needed after that)
>>>    * Run Jekyll locally.
>>>
>>> If anyone needs more info on either of these two steps, could ask here
>>> or on the PR.
>>>
>>> [1]: https://github.com/apache/incubator-fluo-website/pull/21

Re: Volunteer to try Fluo tour

[Christopher <ct...@apache.org>]

Sorry. I'm on it... last few days have been *busy*.

On Wed, Oct 5, 2016 at 12:38 PM Josh Elser <jo...@gmail.com> wrote:

> Will do. At this point, I will likely wait for 1.0.0 to get promoted :)
>
> Keith Turner wrote:
> > Awesome.  Let me know if you need anything.
> >
> > On Tue, Oct 4, 2016 at 6:10 PM, Josh Elser<jo...@gmail.com>  wrote:
> >> Sounds like fun. I want to try to do this.
> >>
> >>
> >> Keith Turner wrote:
> >>> I just put a pull request[1] for something called the Fluo Tour.  The
> >>> tour is a set of exercises someone could follow to help them become
> >>> proficient using Fluo.  I am looking for feedback if anyone has a
> >>> chance to try following it.  Currently, need to do the following two
> >>> things to try the tour.
> >>>
> >>>    * Install a snapshot version of Fluo (we are getting close to
> >>> releasing 1.0.0 I hope, so this step would not be needed after that)
> >>>    * Run Jekyll locally.
> >>>
> >>> If anyone needs more info on either of these two steps, could ask here
> >>> or on the PR.
> >>>
> >>> [1]: https://github.com/apache/incubator-fluo-website/pull/21
>

Re: Volunteer to try Fluo tour

[Josh Elser <jo...@gmail.com>]

Will do. At this point, I will likely wait for 1.0.0 to get promoted :)

Keith Turner wrote:
> Awesome.  Let me know if you need anything.
>
> On Tue, Oct 4, 2016 at 6:10 PM, Josh Elser<jo...@gmail.com>  wrote:
>> Sounds like fun. I want to try to do this.
>>
>>
>> Keith Turner wrote:
>>> I just put a pull request[1] for something called the Fluo Tour.  The
>>> tour is a set of exercises someone could follow to help them become
>>> proficient using Fluo.  I am looking for feedback if anyone has a
>>> chance to try following it.  Currently, need to do the following two
>>> things to try the tour.
>>>
>>>    * Install a snapshot version of Fluo (we are getting close to
>>> releasing 1.0.0 I hope, so this step would not be needed after that)
>>>    * Run Jekyll locally.
>>>
>>> If anyone needs more info on either of these two steps, could ask here
>>> or on the PR.
>>>
>>> [1]: https://github.com/apache/incubator-fluo-website/pull/21

Re: Volunteer to try Fluo tour

[Keith Turner <ke...@deenlo.com>]

Awesome.  Let me know if you need anything.

On Tue, Oct 4, 2016 at 6:10 PM, Josh Elser <jo...@gmail.com> wrote:
> Sounds like fun. I want to try to do this.
>
>
> Keith Turner wrote:
>>
>> I just put a pull request[1] for something called the Fluo Tour.  The
>> tour is a set of exercises someone could follow to help them become
>> proficient using Fluo.  I am looking for feedback if anyone has a
>> chance to try following it.  Currently, need to do the following two
>> things to try the tour.
>>
>>   * Install a snapshot version of Fluo (we are getting close to
>> releasing 1.0.0 I hope, so this step would not be needed after that)
>>   * Run Jekyll locally.
>>
>> If anyone needs more info on either of these two steps, could ask here
>> or on the PR.
>>
>> [1]: https://github.com/apache/incubator-fluo-website/pull/21

Re: Volunteer to try Fluo tour

[Josh Elser <jo...@gmail.com>]

Sounds like fun. I want to try to do this.

Keith Turner wrote:
> I just put a pull request[1] for something called the Fluo Tour.  The
> tour is a set of exercises someone could follow to help them become
> proficient using Fluo.  I am looking for feedback if anyone has a
> chance to try following it.  Currently, need to do the following two
> things to try the tour.
>
>   * Install a snapshot version of Fluo (we are getting close to
> releasing 1.0.0 I hope, so this step would not be needed after that)
>   * Run Jekyll locally.
>
> If anyone needs more info on either of these two steps, could ask here
> or on the PR.
>
> [1]: https://github.com/apache/incubator-fluo-website/pull/21