# Mistakenly identifies Multiple ES Hadoop Versions on Azure
**URL:** https://discuss.elastic.co/t/mistakenly-identifies-multiple-es-hadoop-versions-on-azure/48696
**Category:** Elasticsearch
**Tags:** es-hadoop
**Created:** [April 28, 2016, 2:56pm UTC](https://discuss.elastic.co/t/mistakenly-identifies-multiple-es-hadoop-versions-on-azure/48696 "2016-04-28T14:56:53Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@sor123](https://discuss.elastic.co/u/sor123)
#### Post date: [April 28, 2016, 2:56pm UTC](https://discuss.elastic.co/t/mistakenly-identifies-multiple-es-hadoop-versions-on-azure/48696/1 "2016-04-28T14:56:53Z")
Hi,
I'm running ES-Hadoop on an Azure HDinsight cluster. When I register version 2.3.0 in Pig it immediately fails with a "multiple ES-Hadoop versions" error. I created a new cluster and only registered one version. So I don't know if this is a bug that it finds multiple versions or if there is any other issue.
See below for the error message. It lists the same path twice with just the minor difference of the lower-case versus upper-case drive C/:. Obviously these are not different versions. Is this sthg that can be fixed or prevented?
Error:
Multiple ES-Hadoop versions detected in the classpath; please use only one
jar:file:/c:/apps/temp/hdfs/nm-local-dir/usercache/userxyz/appcache/application\_xyz/container\_xyz/elasticsearch-hadoop-2.3.0.jar
jar:file:/C:/apps/temp/hdfs/nm-local-dir/usercache/userxyz/appcache/application\_xyz/container\_xyz/elasticsearch-hadoop-2.3.0.jar
Thanks
---
### Author:  [@costin](https://discuss.elastic.co/u/costin)
#### Post date: [April 30, 2016, 2:37pm UTC](https://discuss.elastic.co/t/mistakenly-identifies-multiple-es-hadoop-versions-on-azure/48696/2 "2016-04-30T14:37:34Z")
That looks like a URL problem on Azure. Since the classpath are actually case sensitive the two resources do register twice so as far as the connector is concerned, there is indeed a classpath issue.
The whole reason this was added in the first place was to prevent the oh so common bug where multiple versions were added in the classpath (folks where just adding jars without checking) which led to very weird bugs and class conflicts.
After the check was added, this problem was pretty much eliminated.
Back to this case - the fact that a drive appears twice (c: vs C:) should be something configurable in your Azure cluster; maybe there's a symlink somewhere or the JVM classpath contains the drive registered twice.
---
### Author:  [@sor123](https://discuss.elastic.co/u/sor123)
#### Post date: [May 3, 2016, 3:48pm UTC](https://discuss.elastic.co/t/mistakenly-identifies-multiple-es-hadoop-versions-on-azure/48696/3 "2016-05-03T15:48:11Z")
thanks for the answer.
i haven't found a way to resolve this yet - but i'll keep looking or maybe work with a custom jar.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 1:24pm UTC](https://discuss.elastic.co/t/mistakenly-identifies-multiple-es-hadoop-versions-on-azure/48696/4 "2017-07-06T13:24:49Z")