+1 for a separated user mail list.
It is convient for newbies like me. And most of the development discussion
are irrelevant to me.
- Jay
On Sun, Sep 18, 2016 at 10:12 AM, Khurrum Nasim
wrote:
> Chris & Sijie,
>
>
> I felt it is worth separating the user and dev discussion into two mail
> list
Hello,
Do you have a tutorial of setting up a global replicated log cluster?
Thanks,
Jay
Khurrum, thank your for your comment.
A few use cases for your reference.
- we partitioned the data by keys (for example, user id). An operation may
update keys at the same time. We'd like the updates should only be seen by
the readers by only once. There is no partial failure state in between. A
Sijie,
I attempted to create a wiki page under that space. I found that I am not
authorized with edit permission.
Can any of the committers grant me the wiki edit permission? My account is "
xi.liu.ant".
- Xi
On Tue, Sep 13, 2016 at 9:26 AM, Sijie Guo wrote:
> This sounds interesting ... I wi
+1
On Mon, Sep 12, 2016 at 6:16 PM, Stevo Slavić wrote:
> + 1 (non-binding) for doing it asap
>
> On Mon, Sep 12, 2016 at 11:40 AM, Flavio Junqueira wrote:
>
> > It isn't strictly necessary, here is what the documentation says:
> >
> > On Repackaging
> >
> > It is recommended - but not mandated
+1 for the interface.
- KN
On Mon, Sep 12, 2016 at 5:46 PM, Jon Derrick
wrote:
> Sijie, thank you for your comments.
>
> I'd like to make a proposal by introducing a `NamespaceResolver`.
>
> What does a namespace resolver do? A namespace resolver is basically
> resolving the log stream name int
Xi,
The "stream level" transaction makes more sense to me. It is an extension
of 'atomic write' records over the size limitation. I can see the value of
having such ability.
But I am not convinced by the namespace level transaction. Do you have any
concrente use cases that you can talk about more
Thanks Sijie and Flavio for your helps.
- KN
On Thu, Sep 15, 2016 at 10:21 AM, Sijie Guo wrote:
> Ah. sorry. I forgot to update the podling report.
>
> - Sijie
>
> On Wed, Sep 14, 2016 at 11:12 AM, Flavio Junqueira wrote:
>
> > I have signed off even though it hasn't been updated. Let's leave
Awesome. The website looks good.
Sijie, it would be good if you can add a documentation on how to build the
website and the documentation.
- KN
On Tue, Sep 13, 2016 at 5:29 PM, Sijie Guo wrote:
> We shipped the website and it is live under
> http://distributedlog.incubator.apache.org/
>
> The
Chris & Sijie,
I felt it is worth separating the user and dev discussion into two mail
lists. As from subscribers' perspective, I can easily setup filtering rules
on two different mail lists and get all the information that I really care
about.
I'd prefer setting up a separated user list if we c
Good job, Jia.
- KN
On Wed, Sep 14, 2016 at 1:10 PM, Sijie Guo wrote:
> FYI.
>
> All the ci jobs are green now (both Travis CI and Jenkins). Huge shout out
> to Zhaijia for his work on helping improving the CI status.
>
> https://github.com/sijie/incubator-distributedlog/tree/sijie/update_readm
No objection from me. Thank you, Henry.
- Sijie
On Sat, Sep 17, 2016 at 3:01 PM, Henry Saputra
wrote:
> The JIRA issues for infra are these:
>
> https://issues.apache.org/jira/browse/INFRA-12243
> https://issues.apache.org/jira/browse/INFRA-12245
>
> It didnt specify the target list so I assume
The JIRA issues for infra are these:
https://issues.apache.org/jira/browse/INFRA-12243
https://issues.apache.org/jira/browse/INFRA-12245
It didnt specify the target list so I assume it was a mistake from infra.
If no objection, I will create JIRA to infra to update target list to dev@
instead of
13 matches
Mail list logo
