-
Notifications
You must be signed in to change notification settings - Fork 26
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
Queryability of dataframe attribute columns #99
Comments
This was referenced May 19, 2022
This was referenced May 27, 2022
Nothing more to do here. When we have true Unicode values on disk, that will be an internal change, and existing unit-test cases will ensure we don't have a regression. |
This was referenced Aug 25, 2022
This was referenced Sep 16, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview
obs
/var
columnstiledb.cc.TileDBError: [TileDB::QueryCondition] Error: Clause non-empty attribute may only be var-sized for ASCII strings: cell_type
Details
Core issue
As of summer 2022:
Comparison of writes
tiledbsc-py
0.1.7 just to make this a stable permalink:Comparison of reads
If we try to query the
Krasnow-bad
SOMA -- the one where we omitted the crucial Unicode-to-ASCII on write -- then the query fails entirely due to the aformentioned core issue:Query script (copied out of https://github.com/single-cell-data/TileDB-SingleCell/blob/0.1.7/apis/python/src/tiledbsc/annotation_dataframe.py#L194-L221 for brevity in presentation here):
Script output when run on
Krasnow-bad
which lacks the crucial Unicode-to-ASCII on write:Next query the `Krasnow-good' SOMA, which has the crucial Unicode-to-ASCII on write, but without and with the ASCII-to-Unicode conversion on read:
Here we see that if we omit the ASCII-to-Unicode on read, we are handing the user back a dataframe which has columns as bytes, not strings, which breaks the UX for them. (In particular, any users of non-English languages with things like umlauts or accents in their column data are going to have a negative experience.)
The text was updated successfully, but these errors were encountered: