You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When pd.Timestamp, pd.NaT and timezone aware pd.Timestamp are used in the same column write throws a misleading exception. It appears to be working if any two appear in the same column e.g. (nat and timestamp, timestamp and timezone aware timestamp, etc...).
[2024-06-27 12:01:28.560] [arcticdb] [error] Error while normalizing symbol=test, data= col
0 2017-01-01 00:00:00
1 NaT
2 2017-12-15 19:02:35-08:00, metadata=None, 'float' object cannot be interpreted as an integer
Traceback (most recent call last):
File "C:\Users\vasil\Documents\arcticdb_venv_symlink\lib\site-packages\arcticdb\version_store\_store.py", line 344, in _try_normalize
item, norm_meta = self._normalizer.normalize(
File "C:\Users\vasil\Documents\arcticdb_venv_symlink\lib\site-packages\arcticdb\version_store\_normalization.py", line 1242, in normalize
return self._normalize(
File "C:\Users\vasil\Documents\arcticdb_venv_symlink\lib\site-packages\arcticdb\version_store\_normalization.py", line 1189, in _normalize
return normalizer(
File "C:\Users\vasil\Documents\arcticdb_venv_symlink\lib\site-packages\arcticdb\version_store\_normalization.py", line 876, in normalize
columns, column_vals = _normalize_columns(
File "C:\Users\vasil\Documents\arcticdb_venv_symlink\lib\site-packages\arcticdb\version_store\_normalization.py", line 493, in _normalize_columns
column_vals = [
File "C:\Users\vasil\Documents\arcticdb_venv_symlink\lib\site-packages\arcticdb\version_store\_normalization.py", line 494, in <listcomp>
_to_primitive(
File "C:\Users\vasil\Documents\arcticdb_venv_symlink\lib\site-packages\arcticdb\version_store\_normalization.py", line 234, in _to_primitive
return arr.astype(DTN64_DTYPE)
TypeError: 'float' object cannot be interpreted as an integer
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "C:\Users\vasil\Documents\arcticdb_venv_symlink\lib\site-packages\arcticdb\version_store\library.py", line 455, in write
return self._nvs.write(
File "C:\Users\vasil\Documents\arcticdb_venv_symlink\lib\site-packages\arcticdb\version_store\_store.py", line 569, in write
udm, item, norm_meta = self._try_normalize(
File "C:\Users\vasil\Documents\arcticdb_venv_symlink\lib\site-packages\arcticdb\version_store\_store.py", line 366, in _try_normalize
raise ArcticNativeException(str(ex))
arcticdb_ext.exceptions.ArcticException: 'float' object cannot be interpreted as an integer
Describe the bug
When pd.Timestamp, pd.NaT and timezone aware pd.Timestamp are used in the same column write throws a misleading exception. It appears to be working if any two appear in the same column e.g. (nat and timestamp, timestamp and timezone aware timestamp, etc...).
Steps/Code to Reproduce
Expected Results
Either make it possible to write the column or throw a reasonable exception.
OS, Python Version and ArcticDB Version
Python: 3.10.11 (tags/v3.10.11:7d4cc5a, Apr 5 2023, 00:38:17) [MSC v.1929 64 bit (AMD64)]
OS: Windows-10-10.0.22631-SP0
ArcticDB: 4.4.3rc1
Backend storage used
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: