Yes, I suspect so. I have never tried a match query aganist a float field, so am not sure how it behaves. I would expect it to be either a keyword field (if it is an identifier and you do not need to query by integer range) or an integer (it does not to be a float based on the data you have shown so far).
the warning i get when i run the command mapper [cvID] cannot be changed from type [float] to [long]
When I searched, these values were default floats when the first index was created.
there is no way to change this i need to recreate the directory
You can not change existing mappings in Elasticsearch but may be able to add multi fields and perform an update for it to take effect. You can also reindex your data into a new index with appropriate mapping set via an index template.
IDs which are only retrieved using exact matches are best indexed as ‘keyword’ fields. The numeric field mappings like ‘long’ etc are optimised for performing range queries eg matching all the values between 1000 and 2000