[
https://issues.apache.org/jira/browse/HBASE-29853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aman Poonia updated HBASE-29853:
--------------------------------
Description:
Currently we set ASYNC_PROFILER binary path and then use that binary to execute
in a shell. Instead we can use below maven dependency
{code:java}
https://mvnrepository.com/artifact/tools.profiler/async-profiler -->
<dependency>
<groupId>tools.profiler</groupId>
<artifactId>async-profiler</artifactId>
<version>2.9</version>
<scope>compile</scope>
</dependency>{code}
This will make it easier to use async profiler everywhere in hbase.
was:
* *Velocity 2.4* disallows hyphens in variable names, requiring template
changes.
* Updating the syntax now prepares us for upgrading to newer Velocity versions.
* This improves compatibility with plugins like
{*}maven-remote-resources-plugin{*}, which use the latest Velocity.
* The current setup is pinned to {*}Velocity 1.7{*}, while the latest version
({*}3.3.0{*}) runs on the *Velocity 2.x engine* by default.
> Move from async profiler binary to a maven dependency
> -----------------------------------------------------
>
> Key: HBASE-29853
> URL: https://issues.apache.org/jira/browse/HBASE-29853
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 3.0.0-beta-1, 4.0.0-alpha-1, 2.6.4, 2.5.13
> Reporter: Aman Poonia
> Assignee: Aman Poonia
> Priority: Minor
>
> Currently we set ASYNC_PROFILER binary path and then use that binary to
> execute in a shell. Instead we can use below maven dependency
> {code:java}
> https://mvnrepository.com/artifact/tools.profiler/async-profiler -->
> <dependency>
> <groupId>tools.profiler</groupId>
> <artifactId>async-profiler</artifactId>
> <version>2.9</version>
> <scope>compile</scope>
> </dependency>{code}
> This will make it easier to use async profiler everywhere in hbase.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
