That'd be awesome, Mingliang!
I have Rajeshbabu and Vladimir on my team who I hope will be able to
start helping out on this work (among others). I know Rajeshbabu has
been poking around the codebase. I hope to also get involved as much as
I can :)
Thanks for the warm-welcome everyone. I hope to get some rubber on the
road asap!
On 7/23/18 3:16 PM, Mingliang Liu wrote:
I'm +1 on the module approach.
I'm interested in this feature and I hope I have some bandwidth on the
development of somes JIRAs.
Thanks,
On Thu, Jul 19, 2018 at 6:18 AM Josh Elser <josh.el...@gmail.com> wrote:
Thanks, all. Nice to have positivity behind the proposal :) Let me see
if I can start creating some JIRA items.
One immediate question is how folks would like to manage this code:
1. New module in the current Ratis Maven build
2. New repository, depending on previous Ratis release
I think #2 is a nicer separation, but I'm not sure if there is enough
API stability to make that approach not painful. If the API in ratis is
evolving/not-well-defined, we would waste a bit of time trying to work
around unrealized breakages. So, I would lean towards #1.
Thoughts?
On 7/14/18 2:25 AM, Mingliang Liu wrote:
This is very interesting work. I have not gone through the details in the
doc, but I'm +1 on the idea.
On Fri, Jul 13, 2018 at 9:36 PM Shashikant Banerjee <
sbaner...@hortonworks.com> wrote:
+1.
Thanks
Shashi
On 7/14/18, 2:28 AM, "Anu Engineer" <aengin...@hortonworks.com> wrote:
+1, This would be extremely useful for Ozone too.
Thanks
Anu
On 7/13/18, 1:26 PM, "Lokesh Jain" <lj...@hortonworks.com> wrote:
+1
Thanks
Lokesh
> On 14-Jul-2018, at 1:55 AM, Jitendra Pandey <
jiten...@hortonworks.com> wrote:
>
> +1
>
> On 7/13/18, 1:22 PM, "Josh Elser" <josh.el...@gmail.com>
wrote:
>
> Hi all,
>
> I'd like to share a document that I've been working on for
many months
> with Jitendra about building a distributed-log "recipe" on
top of Ratis.
>
>
https://docs.google.com/document/d/1Su5py_T5Ytfh9RoTTX2s20KbSJwBHVxbO7ge5ORqbCk/edit?usp=sharing
>
> The primary use case is for Apache HBase, replacing its
HDFS-backed
> write-ahead log construct with something a bit more
flexible.
Our hope
> is that by building a distributed log with Ratis, HBase
could
observe
> similar levels of performance as we do with HDFS and
better
enable our
> flexibility to run on "dynamic" cloud IaaS platforms.
>
> At the bottom of that document, you'll find a high level
breakdown of
> work items for both Ratis as well as HBase. My hope is
that
both of
> these will be able to be worked on concurrently.
Furthermore,
while
> HBase is a primary "customer" for the work, I hope that
you
would find a
> DistributedLog recipe for Ratis (what we've been calling
the
> "LogService") generally reusable for the Ratis community.
>
> Please let me know what you think (either on the mailing
list
or via
> comments on the google-doc). Thanks!
>
> - Josh
>
>
>
