## TL;DR

Upgrade to 0.4.16 or newer and the import/type errors from mixing Evidently with Pydantic 2 go away. What works: Pydantic 2 support shipped in Evidently 0.4.16.

## Steps

1. What was reported:
Issue evidentlyai/evidently#862 (closed, 11 comments): I was trying to install evidently with the latest versions of pydantic (v2) and pyarrow. I found we are still using version 11dev of pyarrow and currently pyarrow is on version 14. I think we can bump up both the dependencies and see massive perfomance gains.

2. What works:
Pydantic 2 support shipped in Evidently 0.4.16. Upgrade to 0.4.16 or newer and the import/type errors from mixing Evidently with Pydantic 2 go away. There is no need to pin Pydantic back to 1.x once you are on the fixed Evidently.

## When to use

You are seeing this: I found we are still using version 11dev of pyarrow and currently pyarrow is on version 14. Use this skill when you run into "Bump pydantic and pyarrow version".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: Evidently 0.4.16. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
