-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: queries on categorical string columns in read_hdf return unexpected results #39189
Closed
2 of 3 tasks
Comments
Can confirm. When I query my datetime index on a 3 million row table, I get different numbers of results every time.
Also strange is that I can't read this HDF with the filename anymore. I need to use a HDFStore - trying to use
Also on pandas 1.2.0, tables 3.6.1, but on python 3.9.1. |
take |
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 23, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 23, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 23, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 23, 2021
4 tasks
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 23, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 23, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 23, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 23, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 23, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 23, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 26, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 26, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 26, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 26, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 26, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 26, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 26, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 26, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 26, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 26, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 26, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 26, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 26, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 26, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 26, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 26, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 30, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 30, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 30, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 30, 2021
nofarm3
pushed a commit
to nofarm3/pandas
that referenced
this issue
Jan 30, 2021
Open
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pandas.
(optional) I have confirmed this bug exists on the master branch of pandas.
Code Sample, a copy-pastable example
Problem description
Using the where clause for on disk hdf queries appears to give incorrect results sometimes. From what I have tested, this appears to only happen for columns that are both string based and categoricals. This is important because the output is completely inaccurate and makes this feature mostly unusable for these column types. I should note that I have not seen issues with querying for values that are present in the dataframe however.
Expected Output
For all read_hdf calls, the expected output is an empty dataframe.
Output of
pd.show_versions()
INSTALLED VERSIONS
commit : 3e89b4c
python : 3.7.9.final.0
python-bits : 64
OS : Linux
OS-release : 3.10.0-514.21.2.el7.x86_64
Version : #1 SMP Tue Jun 20 12:24:47 UTC 2017
machine : x86_64
processor : x86_64
byteorder : little
LC_ALL : None
LANG : en_US.UTF-8
LOCALE : en_US.UTF-8
pandas : 1.2.0
numpy : 1.19.2
pytz : 2020.1
dateutil : 2.8.1
pip : 20.2.4
setuptools : 50.3.0.post20201006
Cython : None
pytest : None
hypothesis : None
sphinx : None
blosc : None
feather : None
xlsxwriter : None
lxml.etree : None
html5lib : None
pymysql : None
psycopg2 : None
jinja2 : 2.11.2
IPython : 7.19.0
pandas_datareader: None
bs4 : None
bottleneck : None
fsspec : None
fastparquet : None
gcsfs : None
matplotlib : None
numexpr : 2.7.1
odfpy : None
openpyxl : None
pandas_gbq : None
pyarrow : None
pyxlsb : None
s3fs : None
scipy : None
sqlalchemy : None
tables : 3.6.1
tabulate : None
xarray : None
xlrd : None
xlwt : None
numba : None
The text was updated successfully, but these errors were encountered: