[jira] [Commented] (CASSANDRA-18135) Accord: transition Node.Id from long to int

2023-02-06 Thread Benedict Elliott Smith (Jira)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-18135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17684792#comment-17684792
 ] 

Benedict Elliott Smith commented on CASSANDRA-18135:


Yep. CEP-21 should in fact allow us to keep it to 16 bits or less in most 
clusters.

> Accord: transition Node.Id from long to int
> ---
>
> Key: CASSANDRA-18135
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18135
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Accord
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Normal
> Fix For: 4.2
>
>
> Trimmed down version of the patch, swapping long for int, but still keeping 
> Node.Id class. Delaying the rest (elimination of Node.Id as a class) until 
> immutability work lands, to ease rebase pain.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Commented] (CASSANDRA-18135) Accord: transition Node.Id from long to int

2023-02-06 Thread Jacek Lewandowski (Jira)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-18135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17684791#comment-17684791
 ] 

Jacek Lewandowski commented on CASSANDRA-18135:
---

So what is the plan for id - is going to stay 32bit?

> Accord: transition Node.Id from long to int
> ---
>
> Key: CASSANDRA-18135
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18135
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Accord
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Normal
> Fix For: 4.2
>
>
> Trimmed down version of the patch, swapping long for int, but still keeping 
> Node.Id class. Delaying the rest (elimination of Node.Id as a class) until 
> immutability work lands, to ease rebase pain.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Commented] (CASSANDRA-18135) Accord: transition Node.Id from long to int

2023-02-03 Thread Aleksey Yeschenko (Jira)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-18135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17683940#comment-17683940
 ] 

Aleksey Yeschenko commented on CASSANDRA-18135:
---

https://github.com/apache/cassandra-accord/pull/34
https://github.com/apache/cassandra/pull/2134
https://app.circleci.com/pipelines/github/iamaleksey/cassandra?branch=18135

> Accord: transition Node.Id from long to int
> ---
>
> Key: CASSANDRA-18135
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18135
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Accord
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Normal
> Fix For: 4.2
>
>
> Trimmed down version of the patch, swapping long for int, but still keeping 
> Node.Id class. Delaying the rest (elimination of Node.Id as a class) until 
> immutability work lands, to ease rebase pain.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org