# How do you verify that an eland-imported tree model matches the original?

**URL:** <https://discuss.elastic.co/t/how-do-you-verify-that-an-eland-imported-tree-model-matches-the-original/390787>\
**Category:** Elasticsearch\
**Tags:** language-clients\
**Created:** [October 1, 2026, 1:34am UTC](https://discuss.elastic.co/t/how-do-you-verify-that-an-eland-imported-tree-model-matches-the-original/390787 "2026-10-01T01:34:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Milivoje\_Simonovic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/milivoje_simonovic/32/148310_2.png) [@Milivoje\_Simonovic](https://discuss.elastic.co/u/Milivoje_Simonovic)\
**Post date:** [October 1, 2026, 1:34am UTC](https://discuss.elastic.co/t/how-do-you-verify-that-an-eland-imported-tree-model-matches-the-original/390787/1 "2026-10-01T01:34:36Z")

</div>

Hi,

Laura Trotta at Elastic suggested I post this here.

When eland imports an XGBoost, LightGBM or scikit-learn model into Elasticsearch, what Elasticsearch runs is a converted copy of the trained model. I am curious how people check that the copy gives the same predictions as the original. A comparison on a test set can miss differences that only show up near a split threshold, at exactly zero, or when a feature is missing. I have seen that kind of silent mismatch in other converters, for example XGBoost missing value handling in the OpenSearch learning to rank plugin.

Has anyone run into eland imports that did not match the original model? And are there known differences in how missing values or thresholds are handled compared with XGBoost or LightGBM?

For disclosure, I am building a tool called Leafparity that checks a tree model against its converted copy for every possible input. Today it works with ONNX only, not with Elasticsearch, so it does not help here yet. I would only build support for eland models if people in this forum actually need it.

> **[Leafparity](https://leafparity.com)**
>
> Exact equivalence checking for tree-ensemble models converted to ONNX.

Milivoje

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 1, 2026, 1:34am UTC](https://discuss.elastic.co/t/how-do-you-verify-that-an-eland-imported-tree-model-matches-the-original/390787/2 "2026-10-01T01:34:37Z")

</div>

OpenSearch/OpenDistro are AWS run products and differ from the original Elasticsearch and Kibana products that Elastic builds and maintains. You may need to contact them directly for further assistance. See [What is OpenSearch and the OpenSearch Dashboard? | Elastic](https://www.elastic.co/elasticsearch/opensearch) for more details.

(This is an automated response from your friendly Elastic bot. Please report this post if you have any suggestions or concerns :elasticheart: )