[jira] [Commented] (CASSANDRA-18061) Add compaction type output result for nodetool compactionhistory

2023-01-19 Thread Jacek Lewandowski (Jira)


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

Jacek Lewandowski commented on CASSANDRA-18061:
---

Thank you for your contribution [~maxwellguo] !

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.2
>
>  Time Spent: 12h 10m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-17 Thread maxwellguo (Jira)


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

maxwellguo commented on CASSANDRA-18061:


Thanks [~smiklosovic][~jlewandowski][~brandon.williams][~mck];)

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.2
>
>  Time Spent: 12h 10m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-17 Thread Stefan Miklosovic (Jira)


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

Stefan Miklosovic commented on CASSANDRA-18061:
---

here is also a build with multiplexer (1) (new tests were run hundreds of times 
on repeat to detect possible flakiness).

https://app.circleci.com/pipelines/github/instaclustr/cassandra/1730/workflows/745efd7a-6ffb-43ab-8e2c-5e99d2fd9c98

going to merge this soon!

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 12h
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-16 Thread Jacek Lewandowski (Jira)


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

Jacek Lewandowski commented on CASSANDRA-18061:
---

+1,
[~smiklosovic] I'm ok with merging that


> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 12h
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-16 Thread maxwellguo (Jira)


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

maxwellguo commented on CASSANDRA-18061:


[~smiklosovic][~jlewandowski] a new version has been updated.:)

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 12h
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-16 Thread Jacek Lewandowski (Jira)


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

Jacek Lewandowski commented on CASSANDRA-18061:
---

sure

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 11h 10m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-16 Thread Stefan Miklosovic (Jira)


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

Stefan Miklosovic commented on CASSANDRA-18061:
---

thanks, I am +1, I am running the build. [~jlewandowski] would you mind to take 
a look again?

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 11h 10m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-15 Thread maxwellguo (Jira)


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

maxwellguo commented on CASSANDRA-18061:


 Thanks [~smiklosovic] [~jlewandowski],
I have modified  the code, 
PR:https://github.com/apache/cassandra/pull/2047/files#diff-f57518f964c71328146aeca95be5e697ca81a77261719eeef4dd4b1ed8daf63b
java8 precommit : 
https://app.circleci.com/pipelines/github/Maxwell-Guo/cassandra/386/workflows/91f5622b-c109-4c67-b01b-9693fa752fb7
The ut and jvm-dtest-upgrade is green.

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 10.5h
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-13 Thread Stefan Miklosovic (Jira)


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

Stefan Miklosovic commented on CASSANDRA-18061:
---

OK, his PR is fine.

[~maxwellguo] I believe we are almost done! If you address the last few 
comments around tests.

Thank you

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 10h 10m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-13 Thread Jacek Lewandowski (Jira)


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

Jacek Lewandowski commented on CASSANDRA-18061:
---

Also I already reviewed today and left some comments on the [~maxwellguo] PR

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 9h 40m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-13 Thread Jacek Lewandowski (Jira)


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

Jacek Lewandowski commented on CASSANDRA-18061:
---

which PR is the current one?

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 9h 40m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-13 Thread Stefan Miklosovic (Jira)


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

Stefan Miklosovic commented on CASSANDRA-18061:
---

[~jlewandowski] could you review please? I will run the build soonish but it 
might be reviewed already.

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 9h
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-13 Thread Stefan Miklosovic (Jira)


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

Stefan Miklosovic commented on CASSANDRA-18061:
---

Tested and it looks good to me. I put one more commit on top of your work here 
(1) (just very small cleanup of the code).

(1) [https://github.com/instaclustr/cassandra/tree/CASSANDRA-18061]
(2) 
[https://app.circleci.com/pipelines/github/instaclustr/cassandra?branch=CASSANDRA-18061]

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 9h
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-13 Thread maxwellguo (Jira)


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

maxwellguo commented on CASSANDRA-18061:


[~smiklosovic]
I update the code .
pr:https://github.com/apache/cassandra/pull/2047/files#diff-ad515f26e664fe1525daf7c6388fe1a66a853bd389c350cd39c76aed8e121d43R47
and java-8 precommit : 
https://app.circleci.com/pipelines/github/Maxwell-Guo/cassandra/366/workflows/532a29f6-7a1b-430d-9dd1-f46343c4a037
ut passed.

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 9h
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-12 Thread Stefan Miklosovic (Jira)


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

Stefan Miklosovic commented on CASSANDRA-18061:
---

Correct, nodetool compaction history would return "{}" (string representation 
of empty map). So no default value is needed.

Please incorporate this work and I will review again.

Thank you!

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 9h
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-12 Thread maxwellguo (Jira)


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

maxwellguo commented on CASSANDRA-18061:


Hi [~smiklosovic], that means emtyp map will return as the  nodetool 
compactionhistory output ? then no default value is needed?
Besides I have left one comment on the git and mention , can you take a look if 
you are convenient。:D

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 8h 50m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-12 Thread Stefan Miklosovic (Jira)


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

Stefan Miklosovic commented on CASSANDRA-18061:
---

Hey [~maxwellguo]

We we discussing with [~jlewandowski] this improvement:

{code}
cqlsh> CREATE KEYSPACE ks WITH replication = {'class': 'SimpleStrategy', 
'replication_factor': 1};
cqlsh> CREATE TABLE ks.tb ( id int, compaction_properties frozen>, primary KEY (id));
cqlsh> INSERT INTO ks.tb (id) VALUES ( 1);
cqlsh> select * from ks.tb ;

 id | compaction_properties
+---
  1 |  null

(1 rows)
cqlsh> update ks.tb SET compaction_properties = {} WHERE id = 1;
cqlsh> select * from ks.tb ;

 id | compaction_properties
+---
  1 |  {}

(1 rows)
cqlsh> CREATE TABLE ks.tb2 ( id int, compaction_properties map, 
primary KEY (id));
cqlsh> INSERT INTO ks.tb2 (id) VALUES ( 1);
cqlsh> update ks.tb2 SET compaction_properties = {} WHERE id = 1;
cqlsh> select * from ks.tb2 ;

 id | compaction_properties
+---
  1 |  null

(1 rows)
{code}

Could you please change the type of compaction_properties to frozen> ?

We were suggesting in above comments to have empty map inserted with no 
defaults in case the original value was null.

When that is done, when we migrate, we would insert empty map ({}) into 
compaction_properties and not map with one entry. It is very easy that way as 
we do not need any additional logic in CompactionHistoryProperty and I think 
that class can be completely removed.

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 7h 50m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-11 Thread maxwellguo (Jira)


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

maxwellguo commented on CASSANDRA-18061:


Hi [~jlewandowski][~smiklosovic], I adjusted part of the code , so can you help 
to take a look agagin? Thanks 

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 3h 50m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-11 Thread Jacek Lewandowski (Jira)


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

Jacek Lewandowski commented on CASSANDRA-18061:
---

... which means that no additional information was stored

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 3h 40m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-11 Thread Stefan Miklosovic (Jira)


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

Stefan Miklosovic commented on CASSANDRA-18061:
---

what would be displayed in nodetool compactionhistory then? The string 
representation of an empty map? OK, that might work as well. 

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 3h 40m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-11 Thread Jacek Lewandowski (Jira)


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

Jacek Lewandowski commented on CASSANDRA-18061:
---

Just one nit - the default value in this case would be rather an empty map, 
wdyt?

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 3h 40m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-11 Thread Stefan Miklosovic (Jira)


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

Stefan Miklosovic commented on CASSANDRA-18061:
---

Great, thanks for the confirmation. So two things are remaining:

1) change type of column to map
2) populate null values for compaction_type column with default value 

When type is changed to map, the default should be a map with one entry - key 
is "compaction_type" and value is "Unknown compaction type" (whatever is the 
value of OperationType.UNKNOWN.type)

For output of nodetool - it is questionable how to return this map in it. I 
would say we would just read what the value of "compaction_type" entry in that 
map is but it should be way nicer as we do not need any null checks anymore.

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 3h 40m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-11 Thread Jacek Lewandowski (Jira)


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

Jacek Lewandowski commented on CASSANDRA-18061:
---

Indeed, I do not think that we need a new table. A new table is probably needed 
if we change the structure in a way that we modify some type or remove a 
column. Though adding is fine without adding a new table.

And yes, I meant adding that new column as a part of system migrator work and 
populating it there so that we do not deal with various versions in the rest of 
the system

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 3h 40m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-11 Thread Stefan Miklosovic (Jira)


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

Stefan Miklosovic commented on CASSANDRA-18061:
---

I tested the current branch and it just works. When I create table and compact 
it in 3.0, I take all sstables from 3.0 (literally whole data dir) and put it 
into trunk or 4.1, it just starts fine (minus some irrelevant configuration). 

It is true, as [~jlewandowski] observed, that new column added in 
system.compaction_history is not populated (contains null) and in nodetool it 
is some nice string. This should be unified so we do not need checks on nullity 
when returning it via JMX.

[~maxwellguo] I think that what [~jlewandowski] suggested was to have same 
table as it was (no v2) but it would just populate that table with default 
"Unknown compaction type" when there is null for such row. 

[~jlewandowski] do I understand it right there should not be any table renaming 
to v2? Otherwise I think we are already violating this logic of migrating every 
time we introduced a new column into some system table and it was not reflected 
by migrator.

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-11 Thread maxwellguo (Jira)


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

maxwellguo commented on CASSANDRA-18061:


Thanks [~jlewandowski] , [~smiklosovic] can you help to see the comments ?
[~jlewandowski]after read your comment , My question is , it seems that every 
time we modify the system table(I mean just add some columns) , a 
SystemKeyspaceMigrator will need to add the modified table . But there is so 
much system table, so some times a column is added , a V2 table should be 
created and doing some migrate.There may be V2 /V3 /V4 ,so much verisions plus 
the huge number of system table, there will be much system table in the 
process
In SystemKeyspaceMigrator41  I saw that only the schema changed (primary key is 
changed), then a migrate will be added. 

I(y) think  it is  a good idea  to make the newly added column  as a type of map

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 3h
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-11 Thread Jacek Lewandowski (Jira)


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

Jacek Lewandowski commented on CASSANDRA-18061:
---

Hey, I've commented on the ticket. Some idea you may consider - maybe the new 
column should be a map so that we can store more compaction 
properties without changing the table structure in the future.

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 3h
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-10 Thread Stefan Miklosovic (Jira)


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

Stefan Miklosovic commented on CASSANDRA-18061:
---

thanks [~maxwellguo] I will check it again.

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-09 Thread maxwellguo (Jira)


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

maxwellguo commented on CASSANDRA-18061:


[~smiklosovic] New test with 3.x was update now . and java8 precommit 
jvm-upgrade-dtest is green : 
https://app.circleci.com/pipelines/github/Maxwell-Guo/cassandra/362/workflows/e9b6a349-3d7d-4b50-9018-e407e584be8f
commit change :  
https://github.com/apache/cassandra/pull/2047/files#diff-ad515f26e664fe1525daf7c6388fe1a66a853bd389c350cd39c76aed8e121d43R47

And I check the git history of SystemKeyspace.java , some system table also add 
new regular column (not primary key).,But SystemKeyspaceMigrator is not added . 
But if the system column type change I think SystemKeyspaceMigiration is still 
need,For this case Only a new column is added , and if the column is selected 
and null is returned ,and for nodetool compactionhistory if older version do 
not have this column , UNKNOW will return ,I think the backward compatibility 
has been done.
[~brandon.williams][~mck]

[~jlewandowski] I saw  SystemKeyspaceMigrator41 was added by you . And it seems 
[~aweisberg] have add many columns to system keyspace tables . So can you help 
with this too ? I just add a new regular column to compaction_history system 
table.
So should it doing some migration for system keyspace data just like some 
system keyspace in SystemKeyspaceMigrator41 ?I think there is no need but 
should handle backward compatibility

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-09 Thread Michael Semb Wever (Jira)


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

Michael Semb Wever commented on CASSANDRA-18061:


bq. Am I correct we need to support 4.0 -> 5.0 upgrade so we need to migrate 
compaction_history to a new table?

Yes. All `(N-1).x.y` to `N.xx.yy` upgrade paths must be supported.

That also means that if the patch doesn't support upgrades from 3.x it cannot 
be committed while build.xml is at 4.2
(you would then change the fixVersion to 5.x and wait til build.xml is bumped, 
or enhance the patch to support 3.x upgrades)

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-09 Thread maxwellguo (Jira)


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

maxwellguo commented on CASSANDRA-18061:


v40 and v41 are all ok , I add both of them now.
java8 precommit : 
https://app.circleci.com/pipelines/github/Maxwell-Guo/cassandra/361/workflows/ff85f81b-6100-43fa-b897-75a6ee17fd5e
For me I think we do not need a compaction_history_v2 for the compaction_type 
is a newly added column and when people upgrade from lower version to some 
version that added the compaction_type existed syystem table , the column data 
is null and an UN_KNOW flag will return if the column added is finally used。
I have check the table described in 
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/SystemKeyspaceMigrator41.java
It seems that all of the schema (primary key or column name) have changed . So 
if upgrade from lower version I think the data must be migrated. for 
LEGACY_PEERS/PEER_EVENTS_V2/TABLE_ESTIMATES/SSTABLE_ACTIVITY_V2 primary key is 
changed. FOR AVAILABLE_RANGES_V2 column name is changed. 
But compaction_type is only a newly added column and the primary key nor 
cluster name is not change. The original data can be read , and 
The new compaction_type column that have no data will return UN_KNOW(I have 
just test in my own cluster.)
Besides for system schema PAXOS_REPAIR_HISTORY I saw it is add in Cassandra-4.1 
but none SystemKeyspaceMigrator41 is needed 
and for [CASSANDRA-10857|https://issues.apache.org/jira/browse/CASSANDRA-10857] 
a new column "value" is also added for "IndexInfo" system table [code line 142 
SystemKeyspace.java 
|https://github.com/apache/cassandra/commit/07fbd8ee6042797aaade90357d625ba9d79c31e0#diff-f57518f964c71328146aeca95be5e697ca81a77261719eeef4dd4b1ed8daf63bR142]
 and none SystemKeyspaceMigrator41 is needed too, patched by [~ifesdjeen]
So it seem no SystemKeyspaceMigrator41 is needed for a newly added column .

Also I think this is a little patch , and tt doesn't even matter.So I am ok if 
we just set the Status to "wan't fix" :)


> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-09 Thread Brandon Williams (Jira)


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

Brandon Williams commented on CASSANDRA-18061:
--

bq.  Am I correct we need to support 4.0 -> 5.0 upgrade

I think that is something we would like to have, yes.

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2023-01-09 Thread Stefan Miklosovic (Jira)


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

Stefan Miklosovic commented on CASSANDRA-18061:
---

[~maxwellguo] ,

the problem I see with that failing test I mentioned in my last reply is that 
we are trying to upgrade from 4.0 to 4.2 and it fails. What you did is that you 
changed it in such a way that you are upgrading from 4.1. I do not think this 
is the fix.

I believe we have to be able to upgrade straight from 4.0 to 4.2 (or to 5.0 if 
4.2 will be eventually called like that).

The reason that test fails is that after upgrade, 4.x node tries to read / 
write to system.compaction_history table from / to column called 
"compaction_type" but schemas from 4.0 do not have that column yet. 

There is this class (1) which _migrates_ system schemas from older to newer 
schema (whatever that means) by creating _v2 tables and copying all data there 
(and optionally modifying it).

I think that we should do something similar here so we would have a table 
called "system.compaction_history_v2" with this new column and all interaction 
would be done with it.

However, I am not completely sure if we want to introduce new 
compaction_history_v2 table into system keyspace just to be able to see 
compaction types.

I am summoning the heavyweights to know their opinion on this: 
[~brandon.williams]  [~mck]. Am I correct we need to support 4.0 -> 5.0 upgrade 
so we need to migrate compaction_history to a new table?

Thanks

[https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/SystemKeyspaceMigrator41.java]

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2022-12-21 Thread maxwellguo (Jira)


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

maxwellguo commented on CASSANDRA-18061:


[~smiklosovic]Thanks very much.
Sorry for offline these days , I think what I did was inappropriate ,next time 
I should contact you after modifying the code and passing the test,not 
immediately after the modification.
I have already fix the exception what occurs at java-jvm-dtest.
My ci test is ok at this test case in  upgrade tests  for java8 preommit 
:https://app.circleci.com/pipelines/github/Maxwell-Guo/cassandra/355/workflows/5e9a984a-3dd1-43a3-8347-832918a0f1c1

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2022-12-19 Thread Stefan Miklosovic (Jira)


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

Stefan Miklosovic commented on CASSANDRA-18061:
---

I have run this branch of mine (1) where I put some additional commit and 
squashed all previous commits.

The upgrade test is failing here (2), for example:

{code}
junit.framework.AssertionFailedError: Error in test '4.0.8 -> [4.2]' while 
upgrading to '4.2'; successful upgrades []
at 
org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:348)
at 
org.apache.cassandra.distributed.upgrade.CompactionHistorySystemTableUpgradeTest.compactionHistorySystemTableTest(CompactionHistorySystemTableUpgradeTest.java:74)
Caused by: org.apache.cassandra.exceptions.InvalidRequestException: Undefined 
column name compaction_type in table system.compaction_history
at 
org.apache.cassandra.schema.TableMetadata.getExistingColumn(TableMetadata.java:372)
at 
org.apache.cassandra.cql3.selection.Selectable$RawIdentifier.prepare(Selectable.java:1219)
at 
org.apache.cassandra.cql3.selection.Selectable$RawIdentifier.prepare(Selectable.java:1188)
at 
org.apache.cassandra.cql3.selection.RawSelector.prepare(RawSelector.java:53)
at 
org.apache.cassandra.cql3.selection.RawSelector.lambda$toSelectables$0(RawSelector.java:48)
at 
com.google.common.collect.Lists$TransformingRandomAccessList.get(Lists.java:603)
at 
org.apache.cassandra.cql3.selection.SelectorFactories.(SelectorFactories.java:94)
at 
org.apache.cassandra.cql3.selection.SelectorFactories.createFactoriesAndCollectColumnDefinitions(SelectorFactories.java:80)
at 
org.apache.cassandra.cql3.selection.Selection.fromSelectors(Selection.java:181)
at 
org.apache.cassandra.cql3.statements.SelectStatement$RawStatement.prepareSelection(SelectStatement.java:1007)
at 
org.apache.cassandra.cql3.statements.SelectStatement$RawStatement.prepare(SelectStatement.java:946)
at 
org.apache.cassandra.cql3.statements.SelectStatement$RawStatement.prepare(SelectStatement.java:928)
at 
org.apache.cassandra.cql3.statements.SelectStatement$RawStatement.prepare(SelectStatement.java:903)
at 
org.apache.cassandra.cql3.QueryProcessor.getStatement(QueryProcessor.java:756)
at 
org.apache.cassandra.distributed.impl.Coordinator.executeInternal(Coordinator.java:91)
at 
org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:65)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at 
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:750)
{code}

Otherwise the build looks quite fine (3), Java 11 build is all green (4)

(1) https://github.com/instaclustr/cassandra/commits/CASSANDRA-18061
(2) 
https://app.circleci.com/pipelines/github/instaclustr/cassandra/1673/workflows/57b04087-a629-4049-a9e7-cd755785df8a/jobs/8115/tests
(3) 
https://app.circleci.com/pipelines/github/instaclustr/cassandra/1673/workflows/57b04087-a629-4049-a9e7-cd755785df8a
(4) 
https://app.circleci.com/pipelines/github/instaclustr/cassandra/1673/workflows/b34ad3b7-cbb5-4eb7-908d-98dc1b8d3c5d

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



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

-
To unsubscribe, 

[jira] [Commented] (CASSANDRA-18061) Add compaction type output result for nodetool compactionhistory

2022-12-17 Thread maxwellguo (Jira)


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

maxwellguo commented on CASSANDRA-18061:


[~smiklosovic] Thank you for your review. I have modified all the comments. 
https://github.com/apache/cassandra/pull/2047/commits

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2022-12-16 Thread Stefan Miklosovic (Jira)


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

Stefan Miklosovic commented on CASSANDRA-18061:
---

[~maxwellguo] I have fixed more things in this commit (1). Please include that 
commit into your branch.

Some tests are failing in CompactionHistoryTest because you do not check the 
result of `anyMatch` in compactionHistoryResultVerify method. When I check that 
it returns true, it fails. Please fix these tests. 

Thank you.

(1) 
https://github.com/instaclustr/cassandra/commit/f71afd10a3d6a3e21b427165252b66d9be23ae50

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2022-12-16 Thread maxwellguo (Jira)


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

maxwellguo commented on CASSANDRA-18061:


[~smiklosovic]Thank you for your commets, I have modify the code  and leave a 
commet reply on the PR. :D

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2022-12-16 Thread Stefan Miklosovic (Jira)


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

Stefan Miklosovic commented on CASSANDRA-18061:
---

[~maxwellguo] I put more commets to PR. Please check. Thank you.

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2022-12-15 Thread Stefan Miklosovic (Jira)


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

Stefan Miklosovic commented on CASSANDRA-18061:
---

https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/2108/

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2022-12-15 Thread maxwellguo (Jira)


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

maxwellguo commented on CASSANDRA-18061:


Thanks [~brandon.williams] and [~smiklosovic]
and I have update the patch agagin [~smiklosovic], would mind rerun this CI  to 
cover dtests? it seems all unit test have passed. 

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2022-12-15 Thread Stefan Miklosovic (Jira)


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

Stefan Miklosovic commented on CASSANDRA-18061:
---

this failed test is suspicious 
https://ci-cassandra.apache.org/job/Cassandra-devbranch/2105/testReport/junit/org.apache.cassandra.distributed.upgrade/CompactionHistorySystemTableUpgradeTest/compactionHistorySystemTableTest/

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.x
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2022-12-15 Thread Brandon Williams (Jira)


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

Brandon Williams commented on CASSANDRA-18061:
--

I don't have time to commit to a full review right now but I started a CI run 
that can cover dtests: 
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/2105/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/2105/pipeline]


> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.2
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2022-12-11 Thread maxwellguo (Jira)


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

maxwellguo commented on CASSANDRA-18061:


hi [~brandonwilliams][~blambov] 
can you help to look at this little patch ?:D

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.2
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



--
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-18061) Add compaction type output result for nodetool compactionhistory

2022-12-09 Thread maxwellguo (Jira)


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

maxwellguo commented on CASSANDRA-18061:


PR : https://github.com/apache/cassandra/pull/2047
java8 precommit 
:https://app.circleci.com/pipelines/github/Maxwell-Guo/cassandra/344/workflows/6eb8544f-d31e-45e1-a3a1-838579e32077
java11 precommit 
:https://app.circleci.com/pipelines/github/Maxwell-Guo/cassandra/344/workflows/3a206631-1dac-496a-b0e1-5e59edf5cb02

> Add compaction type output result for nodetool compactionhistory
> 
>
> Key: CASSANDRA-18061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18061
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction, Tool/nodetool
>Reporter: maxwellguo
>Assignee: maxwellguo
>Priority: Low
> Fix For: 4.2
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> If we want to see whether we have made a compaction and what kind of 
> compaction we have done for this node, we may go to see the 
> compaction_history system table for some deftails or use nodetool 
> compactionhistory command , But I found that the table do not specify the 
> compaction type so does the compactionhistory command too, like index build , 
> compaction type, clean or scrub for this node. So I think may be it is need 
> to add a type of compaction column to specify the compaction tpe for 
> system.compaction_history and so we can get the type of compaction through 
> system.compaction_history table or nodetool compactionhistory to see whether 
> we have made a major compact for this node  .:)



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