[GitHub] incubator-fluo-website issue #21: Fluo tour

[keith-turner]

Github user keith-turner commented on the issue:

https://github.com/apache/incubator-fluo-website/pull/21
  
I am finished making changes to this for now.  I think its ready to merge.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-fluo issue #787: Test and document updating app config.

[keith-turner]

GitHub user keith-turner opened an issue:

https://github.com/apache/incubator-fluo/issues/787

Test and document updating app config.

The following is feedback from @joshelser on this [mailing list thread][1] 
and my response.  Need to test and document updating app config.

>>
>> * 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
>nitialization time before starting the application.  I will open an
>issue about testing this and documenting expected behavior.

[1]: 
https://lists.apache.org/thread.html/f4fabfec7ce8c70f599691b249f0ef96a36c021e3c0e83c9f350d4cd@%3Cdev.fluo.apache.org%3E






---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-fluo issue #786: Improve Oracle log message

[keith-turner]

GitHub user keith-turner opened an issue:

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

Improve Oracle log message

The following feedback is from @joshelser on this [mailing list thread][1].

> * 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

[1]: 
https://lists.apache.org/thread.html/f4fabfec7ce8c70f599691b249f0ef96a36c021e3c0e83c9f350d4cd@%3Cdev.fluo.apache.org%3E






---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-fluo issue #785: Provide useful message with commit exception

[keith-turner]

GitHub user keith-turner opened an issue:

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

Provide useful message with commit exception

The following feedback is from @joshelser on this [mailing list thread][1].

> "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.

[1]: 
https://lists.apache.org/thread.html/f4fabfec7ce8c70f599691b249f0ef96a36c021e3c0e83c9f350d4cd@%3Cdev.fluo.apache.org%3E






---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Jenkins build is still unstable: Fluo #84

[Apache Jenkins Server]

See