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

Stefan Miklosovic edited comment on CASSANDRA-21444 at 6/18/26 10:05 AM:
-------------------------------------------------------------------------

I think this is such a nice improvement that it qualifies to be in 
cassandra-6.0 branch as well. It applies cleanly and is a net positive, I just 
don't see why we couldn't have it there too.


was (Author: smiklosovic):
I think this is such a nice improvement that it qualifies to be in 
cassandra-6.0 branch as well. It applies cleanly and is a net positive, I just 
see why we couldn't have it there too.

> Speed up nodetool documentation generation by producing all command help in a 
> single jvm
> ----------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-21444
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21444
>             Project: Apache Cassandra
>          Issue Type: Task
>          Components: Build
>            Reporter: Maxim Muzafarov
>            Assignee: Maxim Muzafarov
>            Priority: Normal
>             Fix For: 7.x
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Generating the nodetool AsciiDoc documentation is slow as the 
> gen-nodetool-docs script uses the nodetool command-line wrapper to capture 
> help text for eac command. Each invocation starts a brand-new jvm, so 
> building the documentation incurs the jvm startup cost over a hundred times 
> (100+ node tool commands). 
> This makes the documentation build unnecessarily slow and ties it to the 
> shell wrapper and its environment setup. The solution: Generate the raw 
> {{nodetool help}} text for every command in a single jvm.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to