+1.
For EOL policy statement, just to throw something out here that i can think
of:
* Define what EOL means (such as: not supported by community dev team
anymore, no future 3.4 releases .. still accessible at download page for X
years..) and a date of EOL.
* Provide guidelines for upgrading path
Zili Chen created ZOOKEEPER-3782:
Summary: Replace filter with list comprehension for returning list
in zk-merge-pr.py
Key: ZOOKEEPER-3782
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3782
Pro
Thanks for reporting the issue. I think it is because `filter` in Py3
returns iterator instead of list. I will check all these cases and file a
ticket.
Best,
tison.
Andor Molnar 于2020年4月1日周三 下午11:04写道:
> Hey Tison,
>
> I’ve found a bug in the Py3 script after entering Jira fix version:
>
> Ent
Hey Tison,
I’ve found a bug in the Py3 script after entering Jira fix version:
Enter comma-separated fix version(s) []: 3.7.0
Traceback (most recent call last):
File "zk-merge-pr.py", line 533, in
main()
File "zk-merge-pr.py", line 519, in main
resolve_jira_issues(commit_title, merge
Weichu Liu created ZOOKEEPER-3781:
-
Summary: Zookeeper 3.5.7 not creating snapshot
Key: ZOOKEEPER-3781
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3781
Project: ZooKeeper
Issue Type:
Christopher, I have created an issue (
https://github.com/apache/accumulo/issues/1578) on the github page. Fyi
Thanks,
Karthick
On Wed, 1 Apr 2020 at 11:58, karthick rn
wrote:
> Hi Christopher, I have talked through this issue with Keith internally but
> haven't raised an official channel for d
Norbert Kalmár created ZOOKEEPER-3780:
-
Summary: restore Version.getRevision() to be bacward compatible
Key: ZOOKEEPER-3780
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3780
Project: ZooKee
I'll create a jira and the PR. I guess we should just return -1, that's
what 3.5.5 did anyway:
https://github.com/apache/zookeeper/blob/branch-3.5.5/zookeeper-server/src/main/java/org/apache/zookeeper/version/util/VerGen.java#L87
And keep it on 3.6 as well? Fine by me. So put this function back in
Hi Christopher, I have talked through this issue with Keith internally but
haven't raised an official channel for discussion, because I suspected the
issue could be related to ZK / Netty framework as only after enabling TLS
we are seeing this.
May be I should have opened an issue on Accumulo git fi
I agree with you.
Also as far as I can remember on some of my leader election bug jira
tickets people asked when the next 3.5.x release would happen.
Kind regards,
Mate
On Wed, Apr 1, 2020 at 12:18 PM Enrico Olivelli wrote:
> We should restore it as we did for ZKUtils#delete
>
> Both in 3.5x an
We should restore it as we did for ZKUtils#delete
Both in 3.5x and in 3.6
We just ensure smooth upgrade
Enrico
Il Mer 1 Apr 2020, 12:06 Norbert Kalmar ha
scritto:
> Hi all,
>
> We removed the getRevision() [1] function in 3.5.6 [2].
> I just tried updating to ZooKeeper 3.5.7 in our system, bu
Hi all,
We removed the getRevision() [1] function in 3.5.6 [2].
I just tried updating to ZooKeeper 3.5.7 in our system, but HBase is not
happy with this. It gets ZooKeeper's revision using this method. It is true
HBase could just move to using getRevisionHash, but they are still using
3.4.x, and g
+1
On Wed, Apr 1, 2020 at 7:35 AM Enrico Olivelli wrote:
> Maybe this is the death of 3.4...
>
> Enrico
>
> Il Mer 1 Apr 2020, 07:29 Jaikiran Pai (Jira) ha scritto:
>
> > Jaikiran Pai created ZOOKEEPER-3779:
> > ---
> >
> > Summary: Zookeeper cli
+1 (non-binding)
On Wed, Apr 1, 2020 at 5:04 AM Andor Molnar wrote:
>
> Hi folks,
>
> Based on Enrico’s latest post about a 3.4 client problem I’d like to push
> this initiative.
> Asking more senior members of the community what communicated policy is
> needed exactly to say 3.4 is EoL?
>
> In
Hi folks,
Based on Enrico’s latest post about a 3.4 client problem I’d like to push this
initiative.
Asking more senior members of the community what communicated policy is needed
exactly to say 3.4 is EoL?
In terms of timing I’d like Patrick’s suggestion about 1st of June, 2020.
Any objectio
Karthick, I haven't seen this discussed in the Accumulo community. Can you
point me to the conversation there?
On Wed, Apr 1, 2020 at 2:19 AM Andor Molnar wrote:
> Why would they need to be daemon threads?
> I’m not an expert of Java threading, but afaik I/O threads should not be
> daemon thread
16 matches
Mail list logo