# Sonar issue : t-digest🫙3.2 version is too old

**URL:** <https://discuss.elastic.co/t/sonar-issue-t-digest3-2-version-is-too-old/374353>\
**Category:** Elasticsearch\
**Created:** [February 11, 2025, 9:58am UTC](https://discuss.elastic.co/t/sonar-issue-t-digest3-2-version-is-too-old/374353 "2025-02-11T09:58:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![shadyiscrazy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shadyiscrazy/32/141347_2.png) [@shadyiscrazy](https://discuss.elastic.co/u/shadyiscrazy)\
**Post date:** [February 11, 2025, 9:58am UTC](https://discuss.elastic.co/t/sonar-issue-t-digest3-2-version-is-too-old/374353/1 "2025-02-11T09:58:44Z")

</div>

in one of our microservice project we are using  
org.elasticsearch.client:elasticsearch-rest-high-level-client:jar:7.17.23  
which internally uses "com.tdunning:t-digest:jar:3.2"  
this is sonar vulnerability issues, is there anything on the agent to maybe use latest version of implement it internally?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [February 11, 2025, 10:27am UTC](https://discuss.elastic.co/t/sonar-issue-t-digest3-2-version-is-too-old/374353/2 "2025-02-11T10:27:10Z")

</div>

Welcome!

That's one of the issues of the old client. It comes with a dependency on Elasticsearch core code which has also other deps like this one.  
The recommandation is to switch to the "new" Java client.

> **[Switching from the Java High Level Rest Client to the new Java API Client](https://www.elastic.co/blog/switching-from-the-java-high-level-rest-client-to-the-new-java-api-client)**
>
> Let's say you have a Java project using Elastic 7.17 and the deprecated High Level Rest Client (HLRC). You have been asked to switch to Elastic 8.11 but the HLRC does not exist for this version. This ...

HTH